Build notes · the landscape

Lo que Realmente Compras cuando Adquieres un Proveedor de WhatsApp (BSP)

8 August 2026 · three layers, one invoice, and the questions that decide whether you can leave · Founder, Klaros

Ask a business owner who sends ten thousand WhatsApp messages a month what Meta charges them per message, and most cannot answer. Not because they are careless. Because the number arrives inside somebody else's invoice, in somebody else's units, and nothing in their setup was ever designed to let them check it.

Every other note here is about a defect in our own software. This one is not about us at all. It is a map of the supply chain a business joins when it starts messaging customers on WhatsApp, written because we had to learn it the slow way and the explanations available at the time were mostly written by people selling one particular layer of it.

Layer one: what Meta actually charges

The base layer is the WhatsApp Business Platform itself. Two things about it surprise most people, and both come straight from Meta's own pricing documentation rather than from anybody's marketing page.

The first is that the billing model changed. Until mid-2025 the unit was a 24-hour conversation window. Since 1 July 2025 it is the individual delivered template message. If you are still budgeting in "conversations", you are budgeting in a unit that no longer exists.

The second is how much of it is free. Meta's documentation is direct about this: service conversations are free for all businesses, and all non-template messages are free, with the qualification that non-template messages can only be sent inside an open customer service window. Utility and authentication templates are also free inside that window, and charged outside it.

That single fact reorganises how a sensible business uses the channel, and it is not in most vendors' interest to lead with it. A platform whose revenue scales with your message volume has no reason to open with "most of what you want to do costs nothing."

Rates themselves vary by the recipient's country, not yours, and they move. As a dated example rather than a quotable constant: reporting in early 2026 put India's marketing template rate at roughly ₹0.86 per delivered message after a January increase, with utility and authentication an order of magnitude below that. Treat every number in that sentence as perishable and check Meta's current published rates before you plan around them.

Layer two: the part with the confusing names

Between Meta and your software sits a partner tier, and this is where the vocabulary does the most damage. "BSP", "Business Solution Provider", "Solution Partner" and "Tech Provider" get used interchangeably in the wild, including by people who should know better.

Meta's own distinction is narrower and more useful than the marketing use of these words suggests.

The distinction is billing, not capability. Neither tier unlocks a messaging feature the other lacks. If a vendor implies that their partner status gives them access to something the platform otherwise withholds, that is a claim worth asking them to name precisely.

What the middle layer genuinely earns

It would be easy, and dishonest, to describe this layer as pure margin. It is not, and a business that removes it without understanding what it was doing usually rediscovers the reasons one at a time.

A business that wants none of that responsibility should buy from this layer without embarrassment. The fee is not a scam. It is a service, and for a lot of buyers it is the correct service.

Where it stops being worth it

The arrangement gets worse in three specific circumstances, and it is worth knowing which one you are in before you renew.

The first is volume. A percentage markup on messaging is a fee that grows with your success while the underlying work stays flat. What was a sensible convenience at two thousand messages a month is a different proposition at two hundred thousand.

The second is opacity. If your invoice reports a total rather than a per-message rate you can reconcile against Meta's published numbers, you cannot actually verify what you are paying for the messaging as distinct from the software. That is not necessarily malice. It is frequently just how the billing was built. But it means a price rise and a volume rise look identical from where you stand.

The third is the exit, which deserves its own section.

The three questions

If you take nothing else from this, take these. They are worth asking before signing, in writing, of any vendor including us.

• Whose Meta Business Account holds the WhatsApp Business Account and the phone number? This is the question that decides all the others. If the WABA and number sit inside your own Meta Business Account with the vendor granted access, changing vendor is revoking one access grant and issuing another. If they sit inside the vendor's, leaving is a migration you will be negotiating from a weak position.
• Who does Meta bill? If Meta bills you directly, your messaging cost is a fact you can read at source. If the vendor is billed and invoices you, your messaging cost is a number they report. Both can be honest. Only one is checkable by you.
• What survives if I leave? Specifically: the phone number, the approved templates, and the number quality rating. Those represent months of accumulated standing with Meta, and whether they come with you follows almost entirely from the first answer.

What we cannot tell you

This would be a dishonest map if it did not mark its own edges.

We have not audited anyone's contracts. Everything above about how partners behave is drawn from public documentation, published rates, and our own onboarding, and specific vendors vary enormously. Some Solution Partners hand over WABA ownership without being asked. Naming who does what today would be a table that is wrong within a quarter, so we have described the mechanism instead and left you to ask.

Our own rate figures are strongest for India, which is the market we operate in, and thinner elsewhere. Meta's rates change, and one already changed in January of this year.

And the obvious one: we sell software in the third layer. We think the questions above are the right questions regardless of who you buy from, but we would think that, because our product happens to answer them the way we like. Weigh it accordingly.

Why we wrote this one

The rest of these notes are about digital distance, the gap between what somebody believes and what the system actually does. We usually write about it as a defect in our own code.

This is the same gap at the scale of an industry. A business owner who cannot say what they pay per message, who owns their number, or what they would lose by leaving is not being defrauded. They are simply holding a picture of their situation that nobody has had a reason to correct.

Correcting it does not require them to buy anything from us.

Written 8 August 2026. Rates and partner-tier terminology change; we append when the facts change. Related: digital distance, cost calculator, how Klaros compares to a managed BSP, Twilio, WATI and Interakt, what we found auditing our own billing, all build notes.