Inside the two-week setup: what actually happens

Automation consulting has a trust problem: vague scopes, endless timelines, and a login you don't control when the consultant disappears. We work to one scope and one outcome, agreed before anything gets built. Here's what those two weeks look like.

The two weeks, day by day

• Days 1–2 — accounts and access. Everything gets built inside tools you own. If we set up a new account, it's created under your email, your billing, your control.
• Days 3–8 — the three automations from your audit go live one at a time, each tested against real scenarios from your own inbox and books.
• Days 9–11 — your team gets walked through everything. Not a manual: we sit with whoever runs the front desk or books, and adjust wording and rules until it feels like yours.
• Days 12–14 — burn-in. The automations run with real customers while we watch the logs and tighten anything that wobbles.

What it deliberately doesn't include

No custom software you can't maintain. No subscription to a platform we own and rent back to you. No rip-and-replace of tools that already work. If something on your wishlist needs those, we'll say so in the audit — that's what it's for.

And if we finish and something isn't sticking, we keep working until it does. The scope was agreed up front — the risk of underestimating it lives with us, where it belongs.