"How long until it's actually doing something?" is a fair thing to be sceptical about, because most tech projects answer it with a shrug and a Gantt chart. Ours is boringly specific: two weeks from the first call to a system quietly working. Here's what fills those two weeks, so there are no surprises.
The call: your time audit (20 minutes)
Before anything, we spend twenty minutes on your actual week - not a sales pitch, a genuine look at where the hours go. You talk, we map. By the end we've agreed on the one job to start with: the task that's the most repetitive, the most annoying, and the most obviously worth it. We also tell you honestly if something isn't worth automating yet. Then you decide whether to go ahead. No pressure, no deck.
Days 1–3: we listen before we build
Once you're in, we don't disappear into a lab. We gather the raw material: how you currently handle that job, samples of your real messages, the tools you already use, and the edge cases that make you nervous. Nothing new for you to learn - we build inside the systems you've already got. This is quick, and it's mostly us asking questions and you forwarding a few examples.
Days 4–9: we build it in draft mode
We construct the system so it does the whole job - reads, decides, and drafts the action - but sends nothing on its own yet. You start seeing its work: drafted replies, proposed bookings, ready-to-send follow-ups, each waiting for your tick. This is where you get your first "oh, that's exactly what I'd have written" moment, and also where you catch the bits that need tuning.
Days 10–14: we switch it on
With a few days of drafts you've approved and corrected, the system goes live - still in draft-and-approve for anything with real stakes, on autopilot only for the safe, repetitive bits you're already comfortable with. From here it's working. Not "nearly ready." Working.
- You've watched it handle dozens of real situations before it ever acted alone.
- The line between "it does this" and "I approve this" is set exactly where you want it.
- You have one less job on your plate - the specific one you named on day one.
Then: every month after
This is the part that isn't really "onboarding" but matters most. We don't hand you a system and vanish. Every month we monitor, fix and tune it, and send a plain-English report of what got handled and the hours you got back. When you're ready, we start the two-week clock again on the next job. That ongoing part is the whole model, and you can read more about it in how it works.
The fortnight starts with the audit. It's free, it's twenty minutes, and it's the only step that needs anything from you right now.