Plain Terms. Seven terms, in writing, before we start.
Most firms describe a process. We put ours in the agreement: seven terms you can hold us to.
The seven terms
In every agreement
Week one
Proved on your own work
At the end of week one you see the system working on your own calls or files, not on a demo.
Before the build starts we agree a pass mark with you, in writing: how much of your own past work the system has to get right.
It sits that test before launch, and it goes live only when it passes.
2 weeks, 2 hours
Live in two weeks, for two hours of your time
A standard system is live about two weeks after we start. Getting it live takes about two hours of your time.
We do the build and the testing. You give us one conversation to collect what we need, and one to go through the results.
A quoted system starts with a diagnostic, and gets its dates in writing after that.
No extra cost
If it misses the mark, we keep working at our cost
A system that misses its pass mark does not go live. We keep fixing it at no extra charge until it passes, or we both agree to stop.
The pass mark does not move to suit the system. The system changes, not the line.
One page
Its limits are written down
Before it goes live you approve one page: what the system may do on its own, what it never does, and what goes to a person.
A call or a chat says that it is automated. Anything outside the page is handed to a person with the details already written down, so nobody repeats themselves.
You can pause the whole system yourself, at any moment.
Same day
The person who builds it stays on it
The person on your first call builds your system and runs it. When something breaks we respond the same day, weekends included, at no extra cost.
If the system is down through our fault, that day of the run fee is credited, up to the fee for the month.
Every month
A report that includes the misses
Every month you get what the system handled, what it got wrong, and what we changed.
Every change to a model or a setting is run against the same test first. If it scores worse, it does not ship.
Day one
Yours from day one
The phone number, the accounts, the data and the workflows are set up in your name. The run fee is month to month.
If you stop, you keep all of it. There is nothing to hand back: we remove our own access and leave you the runbook.
Behind the terms
We run what we sell
We run these systems in our own business: our own calls, chat, follow-up, booking and reporting.
The price is published
Five systems have a list price. Everything else is quoted as a fixed price, in writing, before the work starts. Nothing is billed by the hour.
What the two weeks look like
For one of the five systems with a published price.
Day one
We collect what we need
A sample of your past calls or files, the rules your staff follow, and access to the accounts in your name. We agree the pass mark in writing.
End of week one
You see it working
On your own calls or files. You tell us what is wrong with it.
Week two
It sits the test, then goes live
It is tested against the pass mark. You approve the page of limits. Then it is live, and the first monthly report follows.
Seven systems start with a diagnostic
Seven of the twelve systems depend on your own rules and records, so they start with a diagnostic at a fixed fee. We measure the workflow as it runs today and prove it on your own files.
You get a short report that ranks the opportunities, names the risks and says what not to automate, with a fixed price to build the top one.
The same seven terms apply, with two things settled by the diagnostic: the dates, in writing, and whether a person approves each output first where more is at stake.
The limits, stated up front
- Build systems that make coverage decisions, give legal or medical advice, or act without a person where a person should decide.
- Rebuild what your existing software already does well.
- Automate a workflow the diagnostic shows is not worth automating.
- Lock you in. You own the code and the configuration.
- Bill by the hour.
Questions we are asked
How long does it take?
A standard system is live about two weeks after we start, and you see it working on your own calls or files at the end of the first week. A quoted system starts with a diagnostic, and its dates are set in writing after that.
What do you need from us?
About two hours to get a standard system live: one conversation to collect what we need, and one to go through the test results. We also need a sample of past calls or files to test against, and one person who can approve the pass mark and the page of limits.
What if it does not hit the numbers?
Then it does not go live. We keep fixing it at no extra charge until it passes the mark we agreed, or we both agree to stop.
Who maintains it?
We do, month to month. The person who built it runs it, and responds the same day when something breaks, weekends included. If you would rather take it in-house, it is already in your accounts: you have the code, the runbook and the data map, and we remove our access.
Can our IT provider review it?
Yes. We welcome it. Every system comes with documentation and a written data map, and your IT provider can read the code and the configuration at any point.
Start with one workflow
Tell us about one workflow on a free call. You will know whether it is worth building before the call ends.