Partners
White label vs referral vs building your own WhatsApp platform: which fits your agency?
A decision guide for agencies and software firms: what referral, white-label reselling and building your own WhatsApp platform each cost, demand from Meta and give you in control, with a decision table.
By Broadchat teamPublished 6 min read
In short
Referral is the lowest effort: you introduce clients to a vendor and earn a commission, but the vendor owns the client and the brand. White label puts the product under your brand and prices while the platform runs the software and the Meta connection. Building your own platform gives full control but means becoming a Meta Tech Provider, passing App Review, and running engineering and support for years. For most agencies white label is the best fit; build only with a development team and a product reason.
Key takeaways
- Referral earns a commission with almost no work, but the client belongs to the vendor.
- White label gives you the brand, prices and client relationship without engineering.
- Building your own means a Meta app, App Review, Tech Provider onboarding, billing and constant upkeep as Meta changes the platform.
- Within about 15 months Meta changed WhatsApp pricing, messaging limits, the account model and Embedded Signup versions; a builder must absorb every change.
- Choose by your team: sales-led agencies resell, product companies with engineers may build.
Agencies that want to offer WhatsApp to clients face one strategic choice early: refer clients to a vendor, resell a white-label platform, or build their own. The answer to white label vs referral vs building your own WhatsApp platform depends less on ambition than on what your team is good at and how many clients you expect. This post lays out what each route really involves.
Route 1: referral (affiliate)
Many WhatsApp vendors run affiliate or referral programmes. You introduce a client, the client signs up on the vendor's website under the vendor's brand, and you earn a commission, sometimes one-time and sometimes recurring.
- What you do: introductions, maybe a first call.
- What you don't control: the brand, the price, the onboarding, the support and, in the end, the client.
- Fits when: WhatsApp is a side topic for you, for example a web design studio that gets asked about it twice a year.
The hidden cost is the client relationship. If the client is unhappy with the vendor's support, they are still unhappy with the person who recommended it, and you cannot fix it.
Route 2: white-label reselling
A white-label platform gives you a complete WhatsApp Business API product to sell as your own: your domain, logo, emails, plans and prices. The platform runs the servers, the Meta connection and product development. You run sales, onboarding and support.
- What you do: branding, plans and pricing, onboarding, templates and chatbot flows, first-line support.
- What you control: the brand, the price, the client relationship and the service around the software.
- What you don't control: the product roadmap and the platform's uptime.
- Fits when: you sell services to businesses and want a recurring product line in weeks, not years.
The details of getting started are in how to become a WhatsApp API reseller; what to check in a platform is in the reseller panel checklist.
Route 3: building your own platform
Building means writing software on Meta's Cloud API and onboarding clients through your own Meta app. Meta's solution provider overview calls a company in this position a Tech Provider; its clients pay Meta directly or through a Solution Partner's credit line. The work list is longer than most founders expect:
- Meta app and App Review for the WhatsApp permissions, plus business verification of your own portfolio.
- Embedded Signup so clients can connect numbers. Meta caps new business customers at 10 per rolling seven days by default, and 200 after business verification, App Review and access verification (Embedded Signup overview).
- Webhooks at scale for incoming messages and delivery statuses, with retries and ordering.
- Billing: either clients add their own payment method with Meta, or you need a credit-line arrangement through a Solution Partner. Then wallets, invoices and rate cards in every currency you sell.
- The product itself: template editor, campaigns with pacing by messaging limit, inbox, chatbot builder, CRM, integrations, mobile access, multi-tenancy and security.
- Keeping up. In about 15 months Meta moved to per-message pricing (1 Jul 2025), shut down the On-Premises API (23 Oct 2025), changed messaging limits to the business portfolio (8 Oct 2025), started charging service messages beyond 1,000 a month (1 Oct 2026), and is retiring Embedded Signup v2 and v3 on 15 Oct 2026. Each change needs engineering work, on Meta's timetable, not yours.
- Fits when: you are a software company whose own product needs WhatsApp built in deeply, you have engineers to spare for years, and you expect enough clients to justify it.
Decision table
| Factor | Referral | White label | Build your own |
|---|---|---|---|
| Time to first client | Days | Weeks | Many months |
| Upfront investment | None | Low: partner setup, demo account, wallet balance | High: a development team, hosting, Meta onboarding |
| Brand clients see | Vendor's | Yours | Yours |
| Who sets the price | Vendor | You | You |
| Who owns the client relationship | Vendor | You | You |
| Meta requirements on you | None | None beyond following the policy | Meta app, App Review, business verification, onboarding caps |
| Messaging billing | Vendor | Platform's wallets, your markup | You build it, plus a credit line or client-paid Meta billing |
| Ongoing engineering | None | None | Permanent |
| Your income | Commission | Plan margin, messaging markup, setup and services | All revenue, minus all costs |
| Biggest risk | Losing the client to the vendor | Depending on one platform | Cost and delay before break-even |
A quick way to decide
Answer three questions:
- Do you want WhatsApp to be a product line or a favour? A favour: refer. A product line: continue.
- Do you have engineers who could spend the next two years on it, and a reason a platform cannot serve your clients? No: white label. Yes: consider building, and still start on a white label while you build, so you learn what clients use.
- How many clients do you expect in year one? With a handful, building never pays back. With many, the white-label cost per client may start to matter; renegotiate before you rebuild.
Where Broadchat fits
Broadchat is a white-label platform on Meta's official Cloud API: you get a partner panel for branding, plans, wallets and clients, and your clients get campaigns, inbox, chatbot, CRM and automations under your brand. Partner pricing is per client account and quoted on request through the partner program. For the full business model, start with the pillar guide, how to start a WhatsApp reseller business.
Sources
- Solution Providers overview — Meta for Developers, checked 12 October 2026
- Embedded Signup overview — Meta for Developers, checked 12 October 2026
- WhatsApp Business Platform changelog — Meta for Developers, checked 12 October 2026
- On-Premises API sunset — Meta for Developers, checked 12 October 2026
- Pricing on the WhatsApp Business Platform — Meta for Developers, checked 12 October 2026
Broadchat team · Product and partner success team
The people who build and support Broadchat, the white-label WhatsApp Business API platform. We write from what we see while onboarding partners and their clients on the official WhatsApp Cloud API, and we check every article against Meta's current documentation.
Last updated:
Frequently asked questions
Is it better to refer clients or resell WhatsApp white label?
Refer if WhatsApp is occasional for you and you do not want support work. Resell white label if you want a recurring product line under your own brand and prices, and you are willing to onboard and support clients.
What do I need from Meta to build my own WhatsApp platform?
A Meta app with the WhatsApp permissions approved through App Review, a verified business portfolio, Embedded Signup for onboarding clients, and a billing arrangement: clients paying Meta directly or a credit line through a Solution Partner.
Can I start on white label and build later?
Yes. Because each client's WhatsApp account lives in the client's own business portfolio on an official platform, it can later be shared with or connected to another provider, including your own app.
How long does it take to build a WhatsApp Business API platform?
A basic sender can be built quickly, but a product clients pay for, with templates, campaigns, inbox, chatbot, billing and multi-tenancy, takes a team many months, and maintenance never stops because Meta updates the platform several times a year.