Where we stop
The second question, answered before you ask it.
Any competent shop can wire two apps together. What actually decides this is what the system does when it is unsure, what it says under your name, where your customers' information goes, and what we will refuse to build. Here are our answers, in advance.
When it breaks, it breaks toward you.
Most automation fails silently and the owner finds out from an angry voicemail. When a step here cannot complete, the system stops and says so rather than continuing with a default. The worst case is that somebody does that one item by hand — which is what they were doing anyway.
- If the intelligence layer cannot be reached, you get an alert and your customer gets nothing. No wrong message goes out under your name.
- “Couldn't check” never renders as “nothing found.” Those are opposite answers. A check that cannot run stops the record; it never reports a comfortable zero.
- Unverified is not fake. A typo fails validation exactly like junk does, so unverified work lands with a named person at your business — not with us, because a safety net that lives with the contractor disappears when the engagement does.
- No error handler is allowed to turn a failure into a false negative. Blocking beats wrong-and-quiet, every time.
Why this is the hard part to copy
It is a decision made before the first line of code, not a feature added afterwards. Retrofitting it means revisiting every branch that was written to carry on regardless — which is why most systems never get it, and why it is the thing worth asking any vendor about first.
Things we will not build, at any price.
- Automated computation of anything with a legal or financial deadline. Not court dates, not filing dates, not limitations periods, not payment due dates. A miscalculated deadline is a claim with our workflow's name on it. We will build a reminder off a date a human entered. We will not build the arithmetic, and no amount of retainer changes that.
- Anything that advises your customer or states the merits of their situation. The system routes, records and replies in wording you approved. It does not give an opinion.
- Anything touching client funds. No trust accounts, no client-money movement, no payment processing against one.
- A cleared status on any screening step. The system reports what it found, by name. There is no state in which it returns “nothing to worry about,” because that is a judgement and it is yours.
- Automating a process you cannot describe. If nobody at the business can say what currently happens, discovery is not finished — building would only set the confusion in concrete.
- Client-facing copy you have not read aloud. Every automated message goes out under your name. We will not go live without that sign-off.
- Websites. One historical engagement includes one. It is not a product and it never appears on a proposal.
Where it goes, how long it stays, and who owns it.
The understanding stage means customer text transits a third-party model API. We are not going to bury that. Every engagement therefore includes documented vendor terms confirming submitted data is not used for model training, a written data-handling addendum naming each subprocessor and what it receives, and a documented exit.
- Your records live in your systems. The automation layer is a conduit, not a store of record.
- The automation layer's own log is short. Roughly a week of execution history. Anything that needs to be a durable record is written into your system at the time, not reconstructed from logs later. That is a design rule, not a limitation we apologise for.
- Your data is yours, exportable, always. A client leaving takes every record. Holding data as leverage is not a business we will operate.
- Deployments are separate. One client's information cannot be reached from another client's system, because there is no shared system.
- Recording consent is yours. Where telephony is in scope, the rules vary by state and that obligation is the client's, not something we can satisfy on your behalf. It goes on the pre-launch checklist.
Ownership, stated once and plainly
Your number, your domain, your accounts, your data, your business rules. We take delegated access and never ownership. The engine and the reusable components stay ours; what a build teaches us about your customers or pricing stays yours. The test is whether the knowledge would still be true with your name removed.
If a decision requires breaking one of these, the decision is wrong.
- The system fails toward the human. When it cannot be sure, it stops and says so. It never guesses quietly.
- We name what the system does not do. Precisely, in the sales conversation, even when the precision costs the deal.
- We do not automate judgement that carries consequence. Some work is supposed to be slow, because a person is supposed to be responsible for it.
There is a fourth that is really a measure of the first three: the test of whether any of this worked is whether a client who stopped paying would notice within a day.
Bring the hard questions.
If your first instinct reading this was to think of an objection we have not covered, that is the call worth having. Fifteen minutes to start.