How to Choose an Automation Partner in the UK: What to Ask Before You Sign

How to Choose an Automation Partner in the UK: What to Ask Before You Sign

Search "business automation company UK" and you'll get dozens of nearly identical pitches: AI-powered, bespoke, end-to-end, results-driven. Almost none of them tell you the thing that actually determines whether the project goes well, which is what happens after the workflow is built and the invoice is paid.

We've written before about the mistakes that sink automation projects once they're underway. This is the step before that: how to tell, at the proposal stage, whether the person or agency you're about to hire is going to leave you in a good position or a dependent one.

The demo is the easy part

Any competent automation freelancer can show you a slick demo where a form submission triggers an email, updates a spreadsheet, and pings a Slack channel. That's a genuinely useful capability, but it's also the easiest 20% of the job. The hard part is mapping your actual process, which usually has exceptions, judgement calls, and at least one step that "we've always just done manually because it's complicated."

Before you sign anything, ask to see how they'd handle a specific, messy example from your own business, not a generic template. If they can only describe the automation in vague terms ("we'll use AI to streamline your intake process") without asking you detailed questions about how your intake process actually works today, that's worth noticing. A proposal that names specific tools, specific trigger conditions, and specific edge cases is a sign someone has actually thought about your workflow rather than pattern-matched it to a template they sell to everyone.

Ask who can access the workflow once it's built

This is the question most small business owners forget, and it's the one that causes the most pain later. Automations built in Zapier, Make, or Power Automate live inside an account, not inside your website or your codebase. If that account belongs to the agency and nobody else has admin access, you don't actually own the automation in any practical sense. You're renting access to something you paid to build.

Ask directly: whose account will this run in, who has login access, and what happens to it if we stop working together. A good answer is that the automation lives in an account you control (even if they manage it day-to-day), with documented credentials and clear ownership. A vague answer, or one that implies the system "can't really be handed over because it's complex," is a sign the arrangement is designed to keep you dependent rather than to serve you.

Get the handover in writing, not just a training call

A 30-minute screen-share at the end of a project isn't a handover. Ask what documentation you'll actually receive: a written map of what each workflow does and why, the credentials and account access, and a plain-English explanation of what to check first if something breaks at 6am on a Saturday. If the proposal only mentions "training sessions" with no written deliverable, ask for one to be added before you sign. This is the single easiest thing to negotiate up front and the hardest thing to get after the fact.

Understand there's no easy way to switch platforms later

Zapier, Make, and Microsoft Power Automate all do broadly similar things, but there's no export button that moves a finished workflow from one to another. If you want to switch platforms, or switch agencies, every automation has to be rebuilt from scratch on the new tool. That's not a reason to avoid automation, but it is a reason to ask your prospective partner which platform they're proposing and why, rather than assuming it doesn't matter. A partner who picks the platform that suits your budget and technical comfort, and explains the trade-off, is doing you a favour that most won't bother with.

Push for a measurable definition of "done"

Vague success criteria are the most common thing that goes wrong in automation proposals, and it's rarely obvious until months in. "The system will work reliably" isn't a success criterion. "Leads submitted through the contact form will be logged in the CRM within 60 seconds, with a fallback email alert if the CRM is unreachable" is. Ask your prospective partner to define, in writing, what "finished and working" actually means for your project, including what happens in the failure cases, not just the happy path. If they can't answer that before the contract is signed, they haven't actually scoped the work yet, whatever the proposal document says.

Start smaller than feels necessary

It's tempting to hand over your whole quoting-to-invoicing process in one go, especially if a proposal promises to. In practice, the automation projects that go well tend to start with one workflow that's genuinely painful today, get that working properly, and expand from there once you've seen how the partner actually operates day to day. A partner who insists the first engagement has to be a large, multi-month programme before you've worked together at all is asking you to take a lot on trust. One who's happy to start with a single workflow and prove the approach is usually the safer bet, and it gives you a real, low-stakes way to check the handover and support actually work the way they were described.

What this looks like in practice

None of this needs to be adversarial. A partner worth hiring will usually answer these questions without being pushed, because they've had this conversation before and know it builds trust rather than slowing things down. The ones who get defensive, or answer with more marketing language instead of specifics, are telling you something useful before you've spent a penny.

If you're weighing up an automation project and want a second opinion on a proposal you've already received, or want to talk through what a first, low-risk workflow might look like for your business, book a free 15-minute consultation with Digital Hand. We're happy to look at someone else's proposal, not just pitch our own.