The demo is not evidence
How to choose an automation agency is mostly a question about what happens after the build, and a demo shows you none of that. Every vendor can make a workflow move on a screen.
The twelve questions below separate a partner from a supplier. Ask them in one meeting, write the answers on a single page, then compare vendors on those answers rather than on the deck.
None of them is a trap. A good agency has answered all twelve before, and will not need time to think.
Ownership and access
- Who owns the workflows when the project ends? The answer should be you, in your own accounts, under your own credentials.
- Is this built inside our tools or inside yours? A system that lives on the vendor platform is a subscription you cannot cancel.
- What do we get on the last day? Documentation, admin access and a recorded walkthrough for whoever joins next year.
Watch for the phrase "our platform". Some agencies build on a wrapper of their own, which is fine while you keep paying them and worthless the day you stop.
Ownership is not a legal detail either. It decides whether your next hire can improve the system, or whether every small change starts with an email to a supplier.
How the work gets built
- Who actually builds this, by name? The person in the meeting is often not the person in the tool.
- Do you test on real data before it touches live work? A sandbox with real historical records is the difference between a fix and an incident.
- What happens when a step fails at three in the morning? You want an exception queue with a human reading it, not a silent retry.
Ask to see a workflow they shipped last month, on a screen share. Reading the error handling on a real build tells you more than any case study.
Ask what they would tell you not to build. A firm that has never talked a client out of something has never been a consultant.
What happens after go live
- Is maintenance optional? A build that only works while a retainer is running was designed that way.
- Who fixes this if your company disappears next year? The honest answer names the platform and the documentation.
- Will our team be trained to change it? Small edits should never need a purchase order.
Maintenance is worth buying when you choose it. It turns into a trap when it is the only way the system survives, which is why managed maintenance belongs on a month to month agreement.
Money and proof
- Is the price fixed once the scope is agreed? Hourly billing on a build moves the risk of a bad estimate onto you.
- What number will this move, and what is it today? A vendor who cannot answer has not looked at your operation yet.
- Can we speak to a client who finished and left? References who still pay every month are easy to arrange.
A fixed price after scoping is not a discount. It means the thinking happened before the invoice, which is the only stage where thinking is cheap.
Three questions for your own side of the table
The vendor is only half of this decision. Answer these about your own company before any meeting, because a good agency will ask them anyway.
- Which process are we buying help with, in one sentence, with no tool named?
- Who signs off on the exceptions once the system is running?
- What are we willing to change about the way we work today?
A company that cannot answer the third one usually buys a system that mirrors its current mess, only faster. That is an expensive way to keep a bad process.
How to score the answers
Put the twelve answers on one page per vendor. Three patterns show up fast.
- A vendor who answers in your language rather than in tool names has run these projects before.
- The one who volunteers a risk before you ask has been burned once and learned from it.
- Anybody who agrees with everything is selling hours, not judgement.
Compare the three prices last. A number only means something once you know what sits inside it, and by then the answers have told you most of what you need.
The answer that should worry you
When a vendor quotes a full system on the first call, they are pricing a story. Scope comes from looking at real records and at how your team works today, which takes longer than an hour.
The same goes for a plan with nothing in production for six months. Long builds are not more careful. They move the moment of truth away from the day anyone can still act on it.
What a good proposal reads like
A proposal should describe your process back to you before it describes any solution. When you recognise your own company on the first page, somebody listened.
Look for the exceptions too. A document that mentions the awkward cases your team handles by hand was written by someone who spoke to the people doing the work, not only to the person signing.
Two things to watch in the room
Notice who the agency talks to. A firm that speaks only to the founder, never to the person doing the work, will build something that person quietly stops using.
Pay attention to what they ask about, too. Questions about your process and how it is documented are a better sign than questions about your tool stack, because the tools are the easy part.
Where to start
You do not need to hire anybody to get value out of this. Run the twelve questions past whoever builds your automations today, including someone already on the payroll. The answers tend to be revealing in both directions.
When you want a ranked list of what your own processes cost, an audit delivers it in writing in two working days. The systems page covers what a build looks like after that.
Five things you can do tomorrow.
- Write the twelve questions into one page and send it to every vendor before the meeting.
- Ask each one to screen share a workflow they shipped last month, error handling included.
- Check the contract for who owns the accounts, the credentials and the documentation.
- Confirm in writing that maintenance is optional and cancellable month to month.
- Compare prices only after the answers are on paper, never before.
