A platform rate card of base costs and retail prices per unit (email send, text sent, text received, call minute, compliance fees), plus a resolution chain: a flat per-business override wins, then a per-business profit target, then a per-rate platform target, then the platform-wide default. Cost, markup and margin are visible only to platform owner routes.
Also called: what do texts cost · pricing per message · rates · margin
- 1The tenant-facing call returns id, channel, unit, label and price — nothing else.
- 2The price is derived from a profit target with the card-processing percentage folded in, clamped so a mistyped fee or profit can never produce an infinite or negative price.
- 3The fixed per-charge fee is deliberately not amortised into unit prices; it appears once on the invoice.
- 4Per-tier dials exist so an individual variant can be priced by hand without changing the model.
The markup arithmetic produced a 15% margin on the invoiced amount, and then the payment processor took 2.9% plus 30 cents out of that same amount — so a 15% margin actually settled at about 11.7%, and the gap came out of the platform on every usage invoice. The processor's percentage is now built into the rate and its flat fee is charged once per invoice rather than smeared across items, since folding 30 cents into the price of a fraction-of-a-cent email would either assume an invoice size nobody knows in advance or inflate it beyond recognition. Businesses see only their own effective rate; the underlying cost is never exposed on a customer-facing screen.
- Margin quietly eroded by processor fees.
- Nonsense prices from a percentage derived off the wrong base.
- Cost and margin data leaking to tenant-facing surfaces.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →