The ones we get asked every time.
What happens when it gets something wrong?
It's built to stop rather than guess. Anything outside the rules — an unusual clause, a refund over your limit, a supplier it doesn't recognise — is held and handed to a named person with the reason attached. For the first month nothing reaches a customer without someone pressing send, so the errors you find are found by you, not by a client.
Do we have to change the tools we use?
No. We build onto what you already pay for — your CRM, your inbox, your accounting package, your phone system. If something genuinely can't connect, we'll tell you before you spend anything, and usually there's a way round it. Migrating you to different software is a separate project and we'll say so.
How long before it's actually doing something?
One workflow is typically two to three weeks from the first call to it running beside your team. Bigger ones — voice, quoting off a complicated price sheet — run four to six. The order matters more than the total: we build the fastest-paying one first so it's earning while the next one is being built.
Who owns it? What if we stop working with you?
You do, including the accounts, the keys and the configuration. It runs in your infrastructure, not ours. If you stop the retainer it keeps working exactly as it did — you just don't have anyone maintaining it when a vendor changes something. We'll hand over documentation either way.
Is our data going into someone's AI training set?
No. We use business-tier API access from the model providers, which is contractually excluded from training. Where the work can be done without a model at all — matching, routing, arithmetic — we don't use one. Anything with real sensitivity in it we'll scope to stay inside your own systems.
We're small. Is this worth it for us?
Sometimes not, and we'd rather say so. The rough line is about eight hours a week of the same repeated job. Below that, the build cost takes too long to clear. The time audit on the home page will tell you if you're under it — if it says "doesn't pay back", believe it.
Will this mean laying people off?
Not in anything we've built. What actually happens is the coordinator stops doing four hours of copy-paste and starts answering customers, and the business takes on more work without hiring. If your plan is to cut the team, be upfront about it — the build looks different, and we may not be the right people for it.
Most of what goes wrong with automation projects is a scope nobody said out loud. So here it is.
What you get
Every build, no negotiating for it.
- ✓The thing running in your own accounts, on your own data, with your logo on it.
- ✓A written record of every decision it made, readable by someone who isn't technical.
- ✓A hard stop rule: anything it isn't confident about goes to a person instead of being guessed.
- ✓An off switch your team can hit without calling us.
- ✓The credentials and the config. If you fire us, it keeps running.
What we won't do
Some of this is us being careful. Some of it is us not being the right people.
- ✗Let it send anything to a customer unsupervised in the first month.
- ✗Make you move CRM, helpdesk or accounting to a tool we prefer.
- ✗Automate a process that's broken. We'll say so and stop.
- ✗Sell you six workflows at once when one of them pays for the rest.
- ✗Take the work if the numbers say it won't pay back. You'll get that in writing, free.
And some work we turn down
Worth knowing before a call rather than after one.
- No anti-bot circumvention
- No CAPTCHA solving
- No scraping of paid or access-restricted sources
- No personal data collected or processed without a lawful basis