1. Measure the inputs
Use a baseline from the business and mark every forecast as an assumption until it is measured.
| Input | Source | Use in the calculation |
| Current manual hours | Measured in the business | Baseline for comparison |
| Expected hours released | Process mapping or pilot | Assumption to verify after launch |
| Hourly cost | Business records | Converts time into a monetary value |
| Build and operating cost | Project proposal | First-year cost against the calculated value |
2. Additional costs to include in the comparison
- BSP onboarding and usage fees — check the provider's current quote, per-message charges and any setup fee. See the WhatsApp Business API guide for the comparison method.
- Message category pricing — utility and marketing messages may be priced differently. Verify the current Meta or provider rate for the business's country and use case.
- After-launch adjustments — check which minor adjustments are included during the 30-day period and how later work is priced.
3. The break-even point: custom vs SaaS
Add the build, operations and third-party licenses for each option over the same period. The break-even point changes with the proposals, usage volume and required changes, so no fixed range is presented here. For a deeper breakdown, see the 2026 WhatsApp bot pricing guide.
Calculation method only. No client median or promised result is asserted.