Twenty minutes to live: what setup actually involves
We timed ourselves setting Joe up for a car rental firm, a padel club and a plumber. Here is where the time goes.
We claim under twenty minutes to live. Claims like that are usually measured under conditions nobody actually has, so we timed three real setups end to end and wrote down where the minutes went.
The three
A car rental firm. Fleet categories, deposits, an excess policy, and a hard rule about under-25 drivers.
A padel club. Court booking, peak and off-peak pricing, membership tiers, and a lot of “is there a court free at seven”.
A plumber. No fixed diary, callout charges, and a genuinely urgent category that must reach a human immediately.
Where the time went
Roughly consistent across all three:
- Describing the business: 6–9 minutes. Typed in plain language. This is the bulk of it, and it is the part that cannot be skipped, because it is the actual content.
- Connecting the diary: 2–4 minutes. Mostly an OAuth screen. The plumber had no diary to connect, which made setup faster and the result worse — more on that below.
- Setting the escalation rules: 3–5 minutes. What never gets handled automatically. Fastest for the club, slowest for the rental firm, whose excess policy has genuine edge cases.
- Testing: 4–6 minutes. Calling it, messaging it, deliberately asking things it should refuse.
Total, in every case, between 16 and 23 minutes. So the claim holds, with one important qualification.
The qualification
Twenty minutes gets you live, not finished. What it produces is an agent that handles the common cases correctly and escalates everything else — which is genuinely useful on day one, and is not the same as fully configured.
The real work shows up in the first fortnight, and it is not configuration work. It is discovering the things you never wrote down. Every business has twenty of them, and none of them are in the initial description because nobody thinks to mention what they consider obvious.
The car rental firm forgot to mention that one-way rentals are quoted manually. The padel club forgot that coaches book differently from members. The plumber forgot that he does not do gas.
You find these by reading escalations, which is why the escalation log is the most useful screen in the product for the first two weeks and mostly ignored afterwards.
Where it goes slowly
Two things reliably blow the estimate:
No diary. If bookings live in a paper book or one person’s head, there is nothing to connect, and the agent can take enquiries but not close them. This is the plumber’s case, and it halves the value. Fixing it is a bigger project than setup.
Undecided policy. If the business has never actually decided its refund rule, setup surfaces that, and you are now having a management conversation rather than a configuration one. This is not a product problem, but it is the most common reason a setup takes an afternoon instead of twenty minutes.
The honest version of the claim
Twenty minutes to a working agent that handles your common cases and escalates the rest, if your diary is digital and your policies are decided.
If either is not true, fix that first. The setup was never the bottleneck.