2 September 2026
Why our free plan has no limits
Most scheduling tools cap the free plan at one event type. That cap is a growth tactic, not a cost constraint, and we decided not to run it.
Most scheduling tools let you create exactly one event type on the free plan. Want a 15 minute intro and a 60 minute working session? That will be a subscription.
We looked hard at whether to do the same, and decided not to. Here is the reasoning, because it explains a lot about how the rest of the product is built.
The cap is not about cost
A second event type costs us a row in a database. It does not consume a calendar API call, it does not send an email, it does not use meaningful storage. The marginal cost of your second event type is somewhere around zero.
So a one-event-type limit is not covering an expense. It is a growth lever: pick the thing every user needs on day two, and put a price on it.
That works. It also means the first thing your product teaches a new user is that it will be taken away.
What we charge for instead
Things that genuinely cost us money, or that only a team needs:
- More calendar connections. Each one is real API traffic and token refresh on a schedule.
- Removing our branding. You are getting something of value: your booking page stops advertising for us.
- Team scheduling and routing. Round-robin, collective availability and routing forms only matter once several people share one link.
If you are one person who wants a link that books meetings correctly, that is free, permanently. We would rather have you telling people about it than paying eight dollars reluctantly.
The trade we are making
This is not charity. A free plan that is genuinely useful is a distribution strategy: every booking page is seen by someone who did not know we existed. We are betting that is worth more than the revenue from users who would have upgraded grudgingly.
If we are wrong, we will have to change something. We will tell you plainly rather than quietly adding a cap to a plan you already rely on.