Scoping a WhatsApp build, and the numbers behind it

Candidates ask what an automation engineer does here all day, and the honest answer surprises people. A good chunk of it is not building. It is working out what a thing will cost to run before anyone commits to building it, because a flow that works and costs four times what it should is a flow we will be rewriting in six months.

WhatsApp is the clearest example, so here is the whole model, the way a new engineer gets taught it in their first fortnight.

The thing everyone gets wrong first

Meta used to bill per 24-hour conversation window. You opened one, sent what you liked inside it, and paid once. That ended on 1 July 2025, with utility templates having moved on 1 April 2025. Billing is now per template message delivered.

That sounds like a detail. It is not. It flips which decisions are expensive. Under the old model, the question was how many conversations you had. Under the new one it is how many messages you start, and those are very different numbers for the same business.

If someone quotes you in conversations, they have not built on the platform since the change.

The rate card an engineer works from

Every template belongs to a category, and the category sets the price. These are Meta's published UAE rates as of mid 2026.

Marketing costs roughly three times utility for the same delivered message. The single most valuable thing a junior learns in this area is to check what category each template in a flow will send under, because the difference between a well-categorised build and a careless one is most of the client's bill and none of the functionality.

Where the judgement is

The rate card is public. Anyone can read it. What takes practice is the three places where a design decision quietly changes the running cost.

1. Who opens the conversation. Replies inside a customer-opened 24-hour window are free. A flow that gives customers a reason to message first costs a fraction of one that pushes outward, for the same commercial result. Designing entry points is a cost decision, not a marketing one.
2. Where the customer is. Meta bills on the recipient's country, not where the business number is registered. A UAE number messaging Germany is billed at the German rate. Clients regularly plan around this backwards, and catching it early is worth more than any optimisation later.
3. What counts as utility. An order update is utility. Attach an offer to it and it becomes marketing, legitimately, at triple the rate. That is a real editorial choice, and someone has to be the person who points out the cost of it.

The two bills that are not the rate card

A quote has three layers, and the messages are usually the smallest of them.

• The platform subscription. You reach the API through a provider such as BotSpace, WATI or Respond.io. For a typical UAE SME that is roughly AED 150 to 600 a month. Some pass Meta's per-message fee through untouched, others fold a markup of about 10 to 20 percent into their rate.
• The build. Verification, connecting the platform to a CRM, writing and getting templates approved, designing the routing. Around AED 2,600 to 5,200 for straightforward enquiry intake, AED 5,200 to 13,000 once qualification and routing are involved, more where AI agents or several departments are in scope.

Which means the interesting engineering problem is almost never WhatsApp. It is whatever WhatsApp has to talk to, and whether the data going into it is clean enough to route on.

Why this is on a careers site

Because this is the shape of the work. Not a ticket queue, and not a tutorial you follow. Somebody hands you a business that gets four hundred enquiries a month, and you decide what happens to each of them, what it costs, and who has to be told when the answer is inconvenient.

People who enjoy that tend to stay. People who wanted to be handed a spec tend not to. Worth knowing which you are before you apply.