- Ya
- 5 Septemba 2026, 02:12 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 9ecdf03
The site said "$0 setup fees" three times in the pricing page's metadata and listed "No mandatory onboarding fees" as an advantage over HubSpot. All of it is now false: paid plans carry a one-time $99 per seat. A pricing page that omits a four-figure charge on a 25-seat order is not merely incomplete, it is the reason someone meets the number for the first time at checkout. The HubSpot comparison survives honestly. Their $1,500-$3,000 Professional onboarding recurs per Hub; ours is once per seat and an order of magnitude smaller. That was always the real point — the old bullet just made it by claiming a zero we no longer charge. The fee is read off the catalog rather than written into the copy, for the same reason the seat ceiling is: it is a number the server bills on, and a sentence stating it would keep stating the old one the day it changes. The arithmetic lives in plan-pricing.ts beside the term ladder, mirroring SetupFees on the server, and the guard that exists to catch a wrong number rendering perfectly now checks it. One deliberate asymmetry at the catalog boundary: an absent model defaults to PER_SEAT here, where the server defaults to FLAT. This site renders exactly one catalog and every paid plan in it is per-seat; the API reports the amount with no model until the services are rebuilt against the shared library that introduced it. Defaulting to FLAT in that window would print "$99" against an order really billed $2,475, and understating a charge in public is the failure worth defaulting away from. An explicit FLAT is always believed. The calculator carries the fee on its own line rather than in the total, which is a recurring monthly figure that perUser divides — summing them would budget a one-time charge twelve times over.