The short answer
Ask who will actually build it, what they map before recommending tools, what you own and how you would leave, what they would tell you not to automate, what happens after go-live, what the escalation path is, and what happens if it does not work. Vague answers to any of the seven are the risk.
Everybody in this market can show you an impressive demo, because demos run on the best case and the best case is the easy part. What tells you whether a build will survive contact with your business is a different set of questions, and all 7 can be asked in the first call, before anybody opens a laptop.
1. Who actually builds this?
Find out who stays accountable for the build once the meeting ends. Every handoff between a salesperson, an account manager and a builder is a place where the specific detail of your process gets rounded off, and the detail is the whole job.
At Otomatic the Free Business Check is with Natan Trolka, the founder, who leads Otomatic's commercial strategy and client relationships. Otomatic remains responsible for the agreed delivery and ongoing service.
2. What do you map before recommending a tool?
The answer should describe your workflow rather than their stack: who touches what, where data moves, what breaks when somebody is away, which steps repeat often enough to justify building around.
A supplier who names a platform in the first 10 minutes has decided the answer before hearing the question, and you will spend the project bending your process to fit it.
3. What do I own, and how would I leave?
The answer should be specific and written down. Hosting is one arrangement and ownership is another: a supplier can run the infrastructure for you while you keep the agreed rights to the client-specific build you paid for, including the right to keep using it or move it to another provider.
Ask what a handover includes: the documentation, the exports and the access arrangements, and how a move to another provider would work in practice. Agree it while everybody is still friendly. If nobody can tell you how you would leave, the power sits on the wrong side of the table for as long as the arrangement lasts.
Otomatic hosts and runs the systems it builds by default, so there is nothing for you to maintain, and building in your own accounts remains an option. Either way, the client-specific build is yours, with documentation and a usable handover if you appoint someone else.
If nobody can tell you how you would leave, the power sits on the wrong side of the table.
4. What would you tell me not to automate?
This is the question that separates operators from sellers, and it is worth asking in exactly those words.
Some work looks automatable and is not, whether because the volume never justifies it, the exceptions arrive too often, or the client relationship depends on a person being the one who does it. A supplier who cannot name a single exclusion has not looked closely enough to have formed an opinion, and is describing a product rather than your business.
5. What happens after it goes live?
Ask what documentation you get, whether there is a recorded walkthrough, and how long somebody stays on the build after handover.
The first fortnight of live use always finds cases the mapping missed. That is the nature of the work rather than a failure, and it is why every live business system Otomatic builds runs under Managed AI Operations from go-live, which monitors, maintains and supports the system.
6. What does the system refuse to handle?
Every build needs a written list of what it must not decide alone, who those cases go to, and how quickly. Complaints, money already paid, anything outside the agreed scope.
Ask to see that list before the build rather than after. A supplier who treats it as a detail to sort out later has skipped the part where the risk lives, and it is the part you will be asked about if something goes wrong.
7. What happens if it does not work?
Get the answer in writing, and ask about 2 different failures. The first is a fault: the system does not do what was specified. The second is harder: it does exactly what was specified and still does not change how you operate.
The second is best handled before the build, by agreeing what success means for your business. Every Otomatic proposal sets out success criteria, and the system is tested against them before acceptance. Faults against the agreed specification are corrected at no charge for 30 days after acceptance, and Managed AI Operations keeps it maintained after that.
What to do with the answers
Ask all 7 of everybody you shortlist, then compare what they said about your process rather than what they showed you on screen. The demos will look broadly similar to each other. The mapping will not, and the gap between the best and the worst answer to question 4 usually tells you the rest.
The Free Business Check is a 30-minute call on your business priorities and bottlenecks. It ends in your AI Recommendation Plan, yours whether you hire us or not.
Frequently asked
Free resources
Ready to remove the work itself? Start with Workflow Automation.

