What really happens between the first call and delivery

"I want to automate my appointment booking and get more clients, easily." That's the first sentence this practice said to me on the phone. Thirty minutes later, I knew two things: roughly what we were going to build, and what I wasn't going to sell them. Between that phone call and the day the tool started running, five weeks went by. Here's what's inside them, without the varnish.

The first 30 minutes of the call

I don't spend that first call talking about AI. I spend it understanding where the time goes. On a booking system, I look at three things before anything else: where requests come from today (phone, email, form, word of mouth), how many there are a month, and above all how many people don't turn up once a slot has been booked.

That's where I gently reframe the opening line. A booking tool doesn't magically bring in new customers. What it does is stop losing the ones who already wanted a slot: the one who gives up because they have to play email ping-pong to fix a date, the one who forgets the appointment for lack of a reminder. "More clients, easily" usually means, in practice, "fewer clients slipping away along the way." It's not the same job, and it's better to say so straight away.

If your need can be solved with a free tool and an afternoon of settings, I'll tell you during those 30 minutes. I'd rather lose the sale than sell you something you don't need.

The baseline measurement: looking at how you actually work

If the need justifies a proper tool, I hand you in writing the scope and the firm price of the project, valid for 60 days. The project then starts with the baseline measurement, which is never billed separately. On paper, it's a map: your automatable tasks, your data, your booking funnel, and at the end a roadmap costed in hours and recoverable euros.

In real life, most of that time goes elsewhere: understanding how the practice actually works. Who answers the phone, when they want to be notified, which slots they refuse to give out, what needs to land in the diary and what has no business there. It took longer than I'd estimated, and that's normal. A booking tool modelled on an organisation you've misunderstood is a tool nobody's using within two weeks. That time spent listening is what makes the rest hold together.

What you need to prepare (and where things almost always get stuck)

To move forward, I need concrete things from your side: access to the diary, an account to connect the reminders, a clear decision on your availability, and someone on your team who takes ten minutes to test before it goes live. Nothing exotic.

The sticking point, every time, is access. Handing over the keys to your diary and your inbox to a provider isn't a one-click decision, and that's healthy. On this project as on others, the real friction wasn't technical: it was there. We resolved it by explaining precisely what data we touch, with which tools, for what purpose, and by signing a data-processing agreement from the start of the project. Once the practice had seen in black and white what was used and what wasn't, access came through. If you prepare that access list in advance, you easily save a week on any project of this kind.

The Sprint: three weeks, fixed scope

Next comes the Sprint. A scope written down before starting, a price that becomes fixed once that scope is set, and a delivery date. Three weeks here. What we installed: a booking tool under their own brand, hosted in France, with no per-person subscription; 30-minute slots bookable from a phone in under a minute, with confirmation and a diary entry; automatic reminders the day before and two hours before, for no-shows; cancellation and rebooking via a simple link, with no need for the prospect to create an account; and the diary syncing both ways, so a slot already taken elsewhere never shows as free.

We added the part the practice hadn't asked for but secretly wanted: after every appointment, a summary of the conversation, the next steps and a draft follow-up email, ready to check and send. The follow-up that used to happen in the evening, from memory, whenever there was energy left.

The price, and when you get to know it

I don't put a project amount in this article, because a price needs its context to mean anything. The scoping call, however, is free, as shown on the site. The firm price of the project is handed to you in writing after the scoping call, valid for 60 days.

I work this way for a simple reason: you have the right to know the exact price before you commit to the project. And while we're on transparency, I might as well be clear about what I turn down too. I don't sell six-month projects with a fuzzy scope: the scoping call lasts 30 minutes, a Sprint is a fixed-scope project delivered in 2 to 6 weeks, and if a free tool is enough, I say so. When something needs to last, because a system running every day deserves upkeep, I offer an optional monthly subscription, cancellable with 30 days' notice, rather than a project that drags on. Its price is handed over with the price of the project. It's more restful for you, and more cost-effective than calling someone in an emergency the day it breaks.

That's roughly everything that happens between a first phone call and a tool up and running: a lot of listening, time spent understanding rather than coding, access obtained by reassuring, and a scope closed off so it doesn't balloon. Nothing magic. If this rings a bell, the story of this plumber who used to spend two hours a night on paperwork follows exactly the same mechanics, in a completely different trade. And if you want the same kind of setup on your own tasks, it starts with automation built onto your existing tools.