Build notes › topic
Cost & economics
What WhatsApp costs, who charges it, and where the bill comes from. Meta’s rates, what the middle layer earns, and our own billing held to the same standard.
Covered here: 24-hour customer service window · Business Solution Provider · Meta Tech Provider · October 1 2026 WhatsApp charges · order_details interactive message · per-message pricing · price reconciliation · Razorpay plans · Razorpay subscription webhook · self-deployed licence
-
29 August 2026 · platform & cost
The day there is no free way to answer a WhatsApp customer
Meta starts charging for WhatsApp service messages on 1 October. It starts charging for utility templates inside an open window on the same day, which closes the escape route every explainer is recommending. Our own cost screen called those replies free in six places, including a recommendation that overstated what you had wasted. Also: a deadline we asserted nine times and could not verify, and why Meta's own pricing page still says the window is free.
-
8 August 2026 · the landscape
What you are actually buying when you buy WhatsApp
Not about us, for once. Ask an owner sending ten thousand messages a month what Meta charges them per message and most cannot say, because the number arrives inside somebody else's invoice. A map of the three layers: what Meta actually bills for (less than you think, and replying is free), why the Solution Partner and Tech Provider distinction is about billing rather than capability, what the middle layer genuinely earns its fee doing, and the three questions that decide whether you can ever leave.
-
31 July 2026 · engineering
The WhatsApp CRM billing we fixed before charging anyone
A jeweller pays for three WhatsApp lines and silently receives one. She does not complain. She decides the software is small, and six weeks later she does not renew. That was a real defect in our code, and four others sat beside it, unnoticed because no money had ever moved through the system that held them. What we found in the room where the money moves, the two forks where the flattering answer lost, and the tool that now checks what we charge against what we publish.
-
In progress
The half of a sale that nobody demos
Every platform shows you the payment landing. Almost none show you the twenty minutes afterwards: who gets told, who packs it, what the buyer hears while they wait, and what happens when it ships four days later and the messaging window has closed.
-
In progress
Where the ask ends and the shop begins
A payment request is messaging machinery. A product library is a commerce application, and the part most likely to be replaced by a real one. On finding that seam in our own code, and making it a documented extension point instead of a function that happened to sit in the middle of a file.
-
In progress
What a feature looks like when nothing consumes it
Contact limits computed on every request and enforced nowhere. A tier ladder that is marketing copy at runtime. On the difference between building a capability and shipping one, found in our own codebase.
Get the next one on WhatsApp
Message the line and type NOTES. The latest one comes straight back, in the same thread, from the number that sends everything else. Reply STOP whenever you like and it stops.
Send NOTES on WhatsAppAsk our WhatsApp number what it costs
The most honest demo we have is the purchase itself. Message the line and type pricing: you will get our live catalog as a WhatsApp list, real remaining slots, and a payment link on whatever you tap. Buy the self-deployed licence and your signed key arrives in the same thread, for infrastructure we cannot reach. You are experiencing the product before you own it.
+91 97893 77634 · you message first, so nothing reaches you without your say-so.