Contract signed at 11pm, project fully set up by 11:01pm.
The problem
Every new client kicks off the same twenty minutes of clicking — create the folder, copy the project template, add them to the tools, send the welcome email, tell the team. It is not hard, which is exactly why it gets done late, done inconsistently, or done at the end of a long day with a step missed. The client's first impression is a gap where onboarding should have been.
What it does
What you provide
Accounts stay in your name and are billed to you, so nothing depends on us staying in the picture.
What you get
A running automation on a server you own, matching your existing onboarding steps rather than replacing them, tested end to end on a dummy client before go-live. You get a login, a one-page guide, and a pause switch. If it breaks, we're alerted before you notice, and once a month you get an email showing what it did.
Before you ask
Then we haven't finished. We don't consider a build done until it's run against your real data, including the messy cases. If we can't make it work for you, you don't pay the setup fee.
Watching it, and the work that comes out of watching it. When a run fails we're told automatically and we go and fix it — you don't have to notice it or report it. When your phone system changes a setting, or a provider changes something underneath, that's ours to sort out too, and small changes to the wording or the rules are included rather than quoted. Once a month you get a plain email showing what it actually did, which is also how you decide whether this is still worth paying for.
Thirty days' notice and the monthly fee stops. The automation doesn't — it's on your server, under your accounts, so it carries on working without us, and we hand over everything needed to keep it that way. There's nothing to migrate off and nothing to export. What you're cancelling is us watching it, not the thing itself.
You do, entirely. It runs on your own server, under your own accounts, with your own API keys. There's no platform to be locked out of. If you leave, it keeps running and we hand over the keys.
No. You tell us what happens now and who it happens to. We build it, test it against your real data, and hand you one page explaining what it does and how to switch it off.
We're told automatically, usually before you notice. Every automation we build has failure alerting wired in before it goes live — that's not an upgrade, it's a condition of us shipping it.
Onto infrastructure you control and nowhere else. We never hold your API keys — you enter those yourself, and they're encrypted where even we can't read them back. For regulated work this is usually the whole reason people call us.
About fifteen minutes to connect your accounts, a description of the process you want automated, and someone to answer a question or two while we build. That's it.