Failure PatternDecision layer

The Bookwhen Free-Tier Trap: Why Agencies Underprice Class Booking Retainers

Symptom: Client booking pages sit on the Free plan past 50 bookings/month, so new signups silently fail and the studio blames the agency's embed rather than the plan ceiling. Root cause: The Free tier caps at 50 bookings/month with free events only, which is enough to demo but not enough to run a paying studio, and agencies pilot on Free then forget to migrate the client to Lite ($16/mo, 300 bookings) or Standard ($29/mo, 800 bookings).

By InnovaAI ResearchPublished

Subscriptions Billing
How do you recognize it?
  • •Client booking pages sit on the Free plan past 50 bookings/month, so new signups silently fail and the studio blames the agency's embed rather than the plan ceiling.
  • •Agency invoices show a flat $399/mo setup retainer while the underlying Bookwhen seat is $16/mo Lite, and nobody has scoped who pays the vendor subscription.
  • •Waiting lists and reminder emails were never switched on, so the client keeps manually emailing attendees and asks why the 'automation' retainer exists.
  • •Multi-attendee bookings and discount codes go unused because the pilot only tested a single one-off event, and the client's recurring class schedule was never configured.
  • •Booking pages still carry Bookwhen branding on a client-facing URL, and the client's marketing lead flags it two months into the retainer.
Why does it happen?
  • •The Free tier caps at 50 bookings/month with free events only, which is enough to demo but not enough to run a paying studio, and agencies pilot on Free then forget to migrate the client to Lite ($16/mo, 300 bookings) or Standard ($29/mo, 800 bookings).
  • •Bookwhen publishes no white-label or reseller documentation, so agencies that promise a branded booking experience cannot deliver one and discover this after the contract is signed.
  • •Setup effort is front-loaded (roughly 12 hours to configure branding, schedules, payment gateways, and iframe embed) while the recurring work is only about 2 hours/month, so agencies price the retainer as if delivery were ongoing and lose margin on the build.
  • •Payment processing runs through the client's own PayPal or Stripe account, and agencies that bundle payment setup into their fee without clarifying account ownership create reconciliation disputes at month end.
How do you fix it?
  • •Audit every client booking page's plan tier against actual monthly booking volume, and move any account near the 50, 300, or 800 booking ceilings to the next tier before the cap blocks a sale.
  • •Rebuild the offer as a one-time setup fee plus a smaller monthly support line, matching the 12-hour build and 2-hour monthly maintenance split instead of flattening both into one retainer.
  • •Turn on waiting lists, automated confirmations, and reminder emails in each client's Bookwhen settings, then screenshot the active toggles into the monthly report as delivery evidence.
  • •Document in the client contract that the Bookwhen subscription and the PayPal or Stripe merchant account sit in the client's name, with the agency holding admin access only.
Open the Bookwhen courseBookwhen decision recordBrowse the Academy

More on Bookwhen

More for Subscriptions Billing