BillBack

1. One-liner

Catches Meta silently repricing your WhatsApp templates 7x, rewrites them to stay cheap, and files the appeal.

2. Trend signal — why now?

Three things changed inside eighteen months, and together they turned a filing detail into a line item that shows up on a CFO’s desk.

One: WhatsApp billing went per-message. On 1 July 2025 Meta scrapped the 24-hour conversation window as the billing unit and moved to charging per delivered template message. Before that, sloppy category hygiene cost you rounding errors. Now every single delivered template is a separate charge, so a mis-categorised template that fires 300,000 times a month is 300,000 individually billed mistakes.

Two: the price gap between categories is enormous, and India’s marketing rate just went up. A utility template in India costs ₹0.115 per delivered message. A marketing template costs ₹0.8631 — Meta raised it roughly 10% from ₹0.7846 when India moved to local-currency billing in January 2026. That is a 7.5× spread on the identical message, decided entirely by which bucket Meta files it under. Better still: utility templates sent inside an open 24-hour customer service window are free — Meta’s own pricing doc says so plainly (“Utility template messages sent within an open customer service window are free”), while “all marketing template messages are charged,” with no free-window exception. So the true spread on a message sent to an engaged customer is not 7.5×. It’s ₹0.8631 versus zero.

Three — and this is the actual product — Meta reclassifies your templates on you, automatically, with one day’s notice. Since 9 April 2025 Meta has enforced categorisation aggressively, scanning approved templates for promotional intent and moving them from utility to marketing. Meta’s developer docs are explicit: “A 1-day advance notice is provided,” and if you’ve already been warned for categorisation misuse, “24 hour notice will not be provided” — no warning at all. The template keeps working. Its status stays APPROVED. Nothing breaks. The only thing that changes is that it now costs 7.5× more, and you find out when the invoice lands.

The trigger is absurdly sensitive. A shipping notification reading “Hi {{name}}, your order #{{order_id}} has been shipped! Track it here: {{link}}. While you wait, check out our exclusive offers.” gets pulled into marketing — because of two words at the end. The rest of the message is pure logistics.

The scale of the damage is not subtle. Industry write-ups put it at: 10,000 messages a day in India, one template reclassified, and you go from $14/day to $118/day — about $3,540 a month, from a single template you didn’t change. Enterprise teams have run up “tens of thousands of dollars in unexpected charges before teams realise what happened.”

And the escape hatch is real but time-boxed and manual. Meta gives you 60 days to appeal in Business Support Home. The correct_category field on the message-templates API endpoint tells you a repricing is pending before it bites. Almost nobody is watching that field.

Provenance:

• Signal 1 (Demand): Meta auto-reclassifies utility templates to marketing since 9 Apr 2025 with 1-day notice; a single reclassified template at 10k msgs/day costs ~$3,540/month extra; 60-day appeal window — https://helo.ai/resources/blog/whatsapp-template-category-changed-from-utility-to-marketing — observed 2026-07-11
• Signal 2 (Feasibility): Meta Cloud API exposes GET /<WABA_ID>/message_templates?fields=category,correct_category, surfacing pending repricing before it lands; utility-in-service-window is free while all marketing is charged — https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization — observed 2026-07-11
• Signal 3 (Economic): Indian WhatsApp Business market sized ₹4,200 crore; 1.5 crore Indian businesses on WhatsApp Business; India marketing rate raised ~10% to ₹0.8631 vs ₹0.115 utility in Jan 2026 — https://richautomate.in/research/state-of-indian-whatsapp-business-2026 and https://richautomate.in/blog/meta-whatsapp-per-template-pricing-2026-india-explained — observed 2026-07-11 Category: Platform shift

3. The opportunity

Meta unilaterally decides the price of your messages, changes that decision without asking, and gives you a narrow, manual, undocumented-in-practice path to reverse it. That is a platform shift dressed up as a billing footnote.

Here’s the thing I had to work through, because it nearly killed the idea. Alerting is already a commodity. Spur ships template category-change alerts today. BSPs will bundle a notification into their dashboards within two quarters, free, because it costs them nothing. If the product is “we email you when Meta reclassifies a template,” it is dead on arrival — and worse, the alert arrives after the money is gone.

So the product is not the alarm. The product is the reversal.

Knowing your template got reclassified is worthless on its own. What you actually need is: the rewritten template that carries the same operational payload but survives utility classification, the appeal filed inside the 60-day window with the right justification, and a number at the end of the month proving what you clawed back. That work is a rewrite against a published rulebook plus a deadline-driven filing loop. It is exactly the kind of thing that is tedious and specialised for a growth marketer and trivial for a machine that has read the rulebook.

The incumbents won’t do it. BSPs — AiSensy, Wati, Interakt — are the ones billing you for the messages. AiSensy’s whole pitch is “no per-conversation markup,” meaning they take a platform fee and pass Meta’s message charge through. A BSP that aggressively pushed your traffic from ₹0.8631 to free would be shrinking the invoice it exists to send. Some pass-through models are neutral on this, but none are hungry for it, and none will build a rewrite-and-appeal engine as their headline feature. That misalignment is the whole opening.

Ten-times-better, concretely: a growth marketer today finds out about a reclassification from an invoice, shrugs, and eats it, because reverse-engineering which of eleven words tripped Meta’s classifier is not their job. BillBack catches it at the correct_category warning — before the repricing takes effect — hands them a rewritten template that keeps the tracking link and drops “exclusive offers,” and files the appeal.

4. Target market

• Primary customer: Growth / CRM / retention lead at an Indian D2C, EdTech, fintech or online-services brand doing ₹5–100 crore annual revenue, running WhatsApp Business API (Cloud API) through a BSP, sending 50,000–1,000,000+ template messages a month. The buyer is the person whose budget the WhatsApp line comes out of — usually a head of growth or a founder at the smaller end. Secondary: the WhatsApp/performance agencies and BSP resellers who manage this channel for 10–40 brands each and get blamed when the invoice jumps.

• Why they buy: Because the bill went up and nobody can explain why. Cloud API adoption among Tier-1 Indian D2C/BFSI/EdTech companies is already 38–52%, so these are not laggards — they are heavy, sophisticated senders with real volume, which is exactly what makes a 7.5× repricing hurt. The pain is not “I might get reclassified someday.” It is “₹1.3 lakh went out the door last month and my order confirmations are now billed as ads.”

• Rough TAM reasoning: 1.5 crore Indian businesses are on WhatsApp Business, but that’s the consumer-grade app and irrelevant here. The real pool is Cloud API senders with enough volume that category matters. The Indian WhatsApp Business market is sized at ₹4,200 crore. Even a conservative cut — say 40,000–60,000 Indian businesses on the API sending enough volume for a 7.5× spread to be material — is a large enough pond for a ₹5,000–25,000/month tool. I don’t need many of them. This is also not India-only: Brazil reportedly runs a ~9× marketing-to-utility spread, which is worse than India’s, and the same product works there with a translated rulebook.

• Why now for them: Per-message billing (July 2025) plus India’s January 2026 rate hike plus stricter enforcement (April 2025 onward) all landed inside twelve months. Their WhatsApp bill is visibly climbing right now, and the reason is opaque to them.

5. Product sketch (MVP)

• Repricing radar. Connects to the brand’s WABA and polls the message-templates endpoint for the gap between category and correct_category — the field that reveals a pending reclassification before it takes effect. Catches the change while it’s still reversible, not on the invoice.
• Rewrite engine. For every template drifting toward marketing (or already there), produce a rewritten version that keeps the operational payload — order ID, tracking link, appointment time, functional CTA — and strips the contamination: “offer,” “exclusive,” “limited time,” “free,” “shop now,” warm re-engagement framing, promotional buttons. Shows the original and the rewrite side by side with the specific trigger phrases highlighted.
• Appeal packet. Drafts the Business Support Home appeal for templates already reclassified, with the justification framed against Meta’s own utility definition (responds to a specific user action, references concrete transaction detail, neutral tone), and tracks the 60-day window with a countdown so nothing lapses silently.
• Free-window router. Flags templates being blasted cold that could instead ride an open 24-hour customer service window, where utility is billed at zero. This is the biggest single lever in the product and most brands don’t know the rule exists.
• The savings ledger. One number, updated monthly: messages moved from marketing to utility to free, multiplied by the rate delta, equals rupees not spent. This is the renewal argument and it has to be the first thing on the dashboard.
• Pre-submission linter. Before a new template ever goes to Meta, score it — will this land as utility or marketing? — so brands stop creating the problem upstream.
• Portfolio view for agencies. One screen across every managed brand’s WABA, sorted by rupees at risk this month.

6. AI angle — what’s load-bearing

Delete the AI and this product collapses into a cron job with an email alert — which, as established, is already free inside Spur.

The AI does the part that actually pays: constrained rewriting against an adversarial, unpublished-in-full classifier. Meta documents the categories in prose but does not hand you the model. So the job is to take a template, infer which specific tokens and framings are dragging it toward marketing, and rewrite it to sit safely inside utility without destroying the operational content the business needs delivered. That is a judgment task with a hard constraint on both sides — strip too little and it gets reclassified again, strip too much and the message no longer does its job. A regex for “exclusive” doesn’t get you there; the flagged example above fails on tone and re-engagement framing as much as on any keyword list.

Second load-bearing use: the classifier gets better with every outcome we observe. Each rewrite we submit either survives as utility or doesn’t, and each appeal is accepted or refused. That is a clean, labelled feedback signal that no single brand can generate on its own — one brand sees a handful of templates a year; we see thousands across hundreds of brands. That accumulating outcome dataset is the only real moat here, and it’s an AI moat, not a code moat.

7. Localization angle

India-first, and deliberately so — but the product is not structurally Indian.

India is the right beachhead for three reasons. It’s the largest WhatsApp business market on earth (₹4,200 crore, 1.5 crore businesses on WhatsApp Business). The January 2026 rate hike made the pain fresh and specifically Indian. And the buyer profile — a ₹10-crore D2C brand running WhatsApp as its primary retention channel through Interakt or Wati — barely exists in the US, where the same brand would be on Klaviyo and email.

Pricing localises: a ₹7,999/month tool is an easy yes for a brand burning ₹1.3 lakh a month on WhatsApp, where a $299/month tool would stall in procurement.

But the mechanism is global. Meta’s categorisation rules are worldwide, the correct_category field is on every WABA, and the spread exists in every market — Brazil’s marketing-to-utility gap is reportedly ~9×, wider than India’s, which makes LATAM the obvious second market rather than the US. The rulebook is the same; only the rate card and the language of the templates change.

8. Business model — path to $1M–$5M ARR

Two revenue lines, and I want the second one because it aligns the product with the outcome.

• Pricing (base): tiered on monthly template volume.
  • Starter — ₹4,999/mo (up to 100K template messages/mo)
  • Growth — ₹12,999/mo (up to 500K)
  • Scale — ₹29,999/mo (1M+, multi-WABA)
  • Agency — ₹39,999/mo for up to 25 managed brands
• Pricing (performance): optionally, 15% of verified first-year savings in place of a higher tier, for brands that want to see it work before committing. The savings are computable from Meta’s own rate card and message counts, so this is auditable rather than a trust exercise — which is the only reason a performance fee is safe to offer here.
• ACV: blended ₹1.6 lakh ($1,900). Realistic, because the tool is arguing about a ₹5–20 lakh annual line item.
• Math to $1M ARR (₹8.5 crore): ~530 customers at ₹1.6L blended. Or fewer with agency accounts pulling more weight — 150 direct brands plus 40 agencies covering 600 downstream brands gets most of the way.
• Math to $5M ARR: needs the LATAM expansion (Brazil’s 9× spread), the agency/BSP-reseller channel doing real volume, and expansion of the product from “category recovery” into full WhatsApp spend governance — free-window routing, send-volume waste, quality-rating protection, template performance. The category problem is the wedge, not the whole company.
• Expansion path: ACV grows with the customer’s message volume (they’re on a volume tier), then with WABA count, then with the adjacent spend-waste modules. Natural land-and-expand: land on “you’re being overcharged,” expand into “we run your WhatsApp cost.”

Gross margin is high — this is API polling plus LLM inference on a few hundred templates per customer per month. Inference cost per customer is rupees, not thousands of rupees.

9. Go-to-market wedge — first 100 customers

The unlock: I can compute a prospect’s pain before they’ve ever heard of me, and much of it is publicly observable.

1. The free audit, cold. Any brand on the WhatsApp API is discoverable — they advertise WhatsApp opt-in on their site, their checkout, their Meta ads with “Click to WhatsApp.” Scrape Indian D2C brands from Shopify-India directories, marketplace seller lists, and the customer logos that AiSensy/Wati/Interakt publish on their own sites (they list them for social proof — that’s a prospect list, hand-delivered). Sign up for their WhatsApp flows as a real customer: place a small order, abandon a cart, join the list. Now I’m receiving their actual templates. I can read the wording and tell them, specifically, “three of your templates are one Meta review away from costing 7.5× more, here’s the rewrite.” That’s not a pitch, it’s a finding. Target 300 brands, expect a far better reply rate than a generic cold email because the email contains their own message with the trigger phrase highlighted.

2. Go through the agencies, not around them. WhatsApp/retention agencies and BSP resellers each manage 10–40 brands and currently have no answer when a client’s bill jumps. Sell them the Agency tier as a margin story: they either resell it or use it to look brilliant on the monthly call. Thirty agencies is several hundred downstream brands. This is the highest-leverage channel and it’s where I’d spend the most time.

3. Publish the number nobody has published. The whole category is being discussed in vague terms — “costs can rise.” Nobody has put out a rigorous, sourced teardown of the utility-vs-marketing spread by country with the free-service-window rule made explicit, plus a public template linter that anyone can paste a template into and get a verdict. That linter is the top-of-funnel: it’s genuinely useful, it’s shareable, and it qualifies the lead by definition (you only paste a template in if you have templates). Every paste is a prospect who has just been told they have a problem.

4. Fish where the complaints already are. The e-commerce and D2C operator communities in India — the Shopify/D2C founder groups, the growth-marketer WhatsApp and Slack groups, r/IndianStartups and adjacent — are where the “why did my WhatsApp bill jump” question gets asked. Answer it properly, with the mechanism and the fix, every time it comes up.

Time to first paying customer: the audit in channel 1 produces a quantified rupee number for a specific brand. That is about as close to a pre-sold deal as cold outreach gets.

10. Build complexity — justification

Low. No novel infrastructure anywhere in this.

The data layer is a documented Meta Cloud API endpoint — poll message_templates for category and correct_category, plus the webhook Meta already fires on category change. The rewrite engine is an off-the-shelf frontier model with Meta’s categorisation rules in the prompt and a growing set of observed outcomes as examples. The rest is a dashboard, an OAuth flow to connect a WABA, and a savings calculation that’s arithmetic against a published rate card.

Solo builder, 5–7 weeks to a v1 that can onboard a real brand. The genuinely hard part is not engineering — it’s the rulebook: building and maintaining an accurate model of what Meta actually classifies as marketing, which is empirical, adversarial, and changes without announcement. That’s ongoing work, and it’s also the moat.

The appeal filing is currently manual in Business Support Home. V1 drafts the appeal and the customer clicks submit. Don’t fight that; it’s a two-minute step, and pretending to automate it invites a ToS argument nobody needs.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Uses Meta’s official Cloud API with the customer’s own consented WABA access. Helping a business categorise its templates correctly and appeal through Meta’s own published appeal channel is exactly what the rules invite. Not evasion — compliance.
Ethical — no harm / dark patterns	✅	The product pushes brands to make promotional messages less promotional and to route more sends through the window where the customer already engaged. Meta’s rules and the customer’s inbox both benefit. If anything it reduces spam.
Market exists (evidence above)	✅	₹4,200 crore market; documented reclassification cost trap; competitors already selling the (weaker) alert.
1–5 person team can build this	✅	Solo, 5–7 weeks.
Launchable with <$50K / ₹40L	✅	Well under ₹5 lakh. It’s API calls, inference, and a dashboard.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Real money, felt monthly, and it recurs — Meta keeps reclassifying. Not a full 17+ because it’s a cost leak, not an existential threat: a brand that ignores it stays in business, just poorer. Nobody gets fined, nothing breaks, the templates keep sending. That’s the ceiling on urgency.
Demand evidence	15	12/15	Strong and well-sourced: documented cost trap, published rate spread, a competitor (Spur) already monetising the adjacent alert, ₹4,200cr market. Held back from 13+ because I could not find raw verbatim customer complaints — the pain is documented by vendors and BSPs, not by angry operators in public. That’s a real gap and it’s the thing I’d validate first.
Build feasibility	15	13/15	Documented API, off-the-shelf model, dashboard. Solo in 5–7 weeks.
Distribution clarity	15	12/15	The cold audit is unusually strong — I can quantify a stranger’s loss from their own templates. Agency channel is concrete. Not higher because reaching the right person inside a brand still takes work, and the public linter needs to actually get traction.
Revenue mechanics	15	11/15	Pricing is anchored to a real, computable line item, which is the best kind of anchor. But ~530 customers at ₹1.6L is a genuine sales grind, and the performance-fee model, while elegant, adds collection friction.
Time to first revenue	10	8/10	The audit produces a rupee figure before the ask. 4–8 weeks to first paid is realistic, not optimistic.
Defensibility	10	4/10	The weak axis, and I won’t dress it up. BSPs sit closer to the customer, own the billing relationship, and could bolt this on. The only durable moat is the accumulating dataset of which rewrites actually survived Meta’s classifier — real, compounding, but it takes a year to matter, and a BSP with distribution could out-run it. Execution-and-speed moat.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Technical because the value is a classifier that has to beat Meta’s classifier, and that’s an empirical grind. Content because the public linter and the “here’s what Meta is actually doing to your bill” teardown are the top of the funnel — this idea rewards someone who will write the definitive public explainer on the topic.

Key assumptions to validate (3–5)

1. Assumption: Reclassification is common enough at real brands to justify a subscription — i.e. a typical high-volume Indian sender has had at least one template repriced in the last six months. How to test: This is the whole ballgame, and it’s cheap to answer. Get 15–20 brands to run the category vs correct_category query on their own WABA (a two-line script I hand them, they run it, no access needed). Count how many have a pending or completed reclassification. If it’s under a third, the problem is rarer than the vendor blogs imply and the idea shrinks to a feature.

2. Assumption: Rewritten templates actually survive as utility at a materially better rate than the originals. How to test: Take 30 real reclassified templates, rewrite them, submit both versions, measure the classification outcome. If rewrites don’t hold up, there is no product — only an alert, and the alert is free.

3. Assumption: Brands will pay a third party rather than wait for their BSP to ship this free. How to test: Sell it before building it. Take the audit to 20 brands with a quantified number and ask for money. If the answer is consistently “I’ll ask Wati to add it,” that’s the real signal.

4. Assumption: Appeals filed with a well-constructed justification succeed often enough to be worth selling. How to test: File 10 appeals through Business Support Home with proper justification, measure the acceptance rate. Meta responds in 1–3 business days, so this is a two-week experiment.

Risk flags

1. Platform dependency — severe, and it’s the defining risk. The entire product exists because of a specific Meta pricing structure and a specific API field. Meta could collapse the utility/marketing spread, remove correct_category, make the classifier transparent, or simply ship its own “your template will be reclassified, here’s a fix” flow in WhatsApp Manager. Any one of those wounds the business badly. This is a company built on a crack in someone else’s floor, and the crack can be filled.

2. BSP encroachment. Spur already ships alerts. AiSensy, Wati and Interakt have the customer, the billing relationship, and the WABA connection. Their incentive is muddy (they profit from message volume) but not hostile enough to count on — a BSP could ship a decent version of this as a retention feature and the standalone tool loses its reason to exist. The counter is speed, a better classifier, and the agency channel — but I’d rather name the risk than pretend the misalignment protects me.

3. The demand evidence has a hole in it. Every number in this proposal about cost impact traces to vendor and BSP content marketing — companies with an interest in making the problem sound expensive. Meta’s own docs confirm the mechanism (the 1-day notice, the 60-day appeal, the free service window, the correct_category field) and the rate card confirms the spread, so the structure is solid. What’s unverified is the frequency at real brands. Assumption 1 exists to close exactly this gap, and if it comes back weak, this drops to a VALIDATE.

4. Cost leak, not a fire. Nobody gets fined and nothing breaks. That caps urgency, lengthens the sales cycle, and makes this a “next quarter” purchase unless the audit puts a large enough number in front of the buyer. The savings ledger has to be brutally concrete or this churns.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical solo founder who will also write the definitive public
                        teardown of WhatsApp template pricing. Bonus if they've run a
                        WhatsApp channel at a D2C brand or agency and have felt the invoice.
Time to revenue:        4–8 weeks
Capital to launch:      ₹3–5 lakh ($4–6K)
Top 3 assumptions to validate first:
  1. Reclassification frequency is real — have 15–20 brands run the
     category vs correct_category query on their own WABA. Under a third
     showing a hit = the problem is rarer than the vendor blogs claim.
  2. Rewrites survive — take 30 real reclassified templates, rewrite,
     resubmit, measure whether they hold as utility. If not, there's no product.
  3. Willingness to pay a third party — take a quantified audit to 20 brands
     and ask for money before building. "I'll ask my BSP" is the answer to fear.
Kill criteria:
  - Abandon if fewer than 30% of audited WABAs show a reclassification
    (pending or completed) in the trailing six months — the leak is too rare to sell.
  - Abandon if rewritten templates don't survive as utility materially more often
    than the originals — then the only product is the alert, and the alert is free.
  - Abandon if a major BSP (AiSensy, Wati, Interakt) ships integrated
    rewrite-and-appeal before v1 lands — they own the customer and the billing
    relationship, and the standalone loses.
  - Abandon if Meta collapses the utility/marketing price spread or removes
    the correct_category field.

15. Next step — 1-week validation sprint

The goal is to falsify assumption 1 — is this leak common, or is it a vendor’s scare story? — because nothing else matters if it’s rare.

• Day 1–2: Write the two-line audit script that queries message_templates for category vs correct_category and diffs them. Recruit 20 Indian D2C/EdTech brands running the WhatsApp API — through agency contacts, D2C founder groups, and BSP customer logos. They run it themselves on their own WABA; I ask for no access, which removes the trust barrier entirely and makes the ask nearly free for them.
• Day 3–4: Collect results. Count how many WABAs show a pending or completed utility→marketing reclassification in the last six months, and compute the rupee value of each at that brand’s actual send volume. In parallel, take 30 already-reclassified templates, rewrite them, and submit both versions to measure whether the rewrite holds as utility.
• Day 5: Decide.

Go/no-go, falsifiable: proceed only if ≥8 of 20 audited WABAs (40%) show a reclassification in the trailing six months, and the median annualised rupee impact per affected brand is ≥₹1.5 lakh (i.e. comfortably more than 12× the ₹12,999 Growth tier, so the ROI argument is trivial), and rewritten templates hold as utility in ≥70% of the 30-template test.

Miss the frequency bar and this is a feature inside a BSP, not a company — kill it. Miss the rewrite bar and I’m selling an alarm that Spur gives away — kill it. Hit all three and the cold-audit channel writes itself, because I’ll have twenty brands already holding a number that says they’re losing money.