How to Brief an Automation Project (So You Actually Get an Accurate Quote)

Ask three automation agencies to quote the same project and you'll often get three wildly different numbers. The usual explanation people reach for is that one agency is overcharging or another is cutting corners. In practice, the real reason is almost always the brief: three agencies looked at three different versions of the same project, because the business owner described it three different ways, to three different people, on three different calls.

A good automation brief isn't a technical document. You don't need to know what an API is or draw a flowchart. You just need to describe the actual, current, slightly messy way the work gets done right now, in enough detail that someone else could picture themselves doing it.

Start with the process, not the solution

The most common mistake in an automation brief is skipping straight to the tool. "I want a chatbot," "I need Zapier set up," or "can you connect our CRM to our invoicing system" are all solutions, not problems, and they box an agency into pricing the thing you've asked for rather than the thing you actually need.

Instead, describe what happens today, step by step, including the annoying bits. A real example: a client once asked for "an automated follow-up system" for their sales enquiries. What they actually meant, once we talked it through, was that enquiries landed in a shared inbox, sat there until someone had five minutes, got replied to manually, and then lived in nobody's calendar for a follow-up call. The fix wasn't a chatbot. It was logging enquiries automatically, assigning an owner, and scheduling a follow-up task, which is a smaller and cheaper job than the "automated system" they'd pictured, and it solved the actual problem.

Write down every tool that's already involved

List every piece of software the process touches, even the ones that feel irrelevant. Spreadsheets, your accounting package, your email provider, your booking system, WhatsApp if that's genuinely how your team coordinates, and any tool a client or supplier insists you use. Agencies price automation projects partly on how many systems need to talk to each other and how well those systems play with others. A CRM with a well-documented integration option is a very different quote to a bespoke internal spreadsheet with no way in except manually opening the file.

If you don't know whether a tool has an "API" or integration option, that's fine, that's the agency's job to find out. What you can tell them is simply what the tool is called and roughly how your team uses it day to day.

Say what "done" actually looks like

Vague success criteria are the second biggest cause of quote mismatches. "Save us time" isn't a target, because an agency scoping to "save some time" might build something minimal, while another might assume you want every edge case handled and price in weeks of extra testing.

Be specific about the version of the process you'd be happy with. If an enquiry currently takes three days to get a reply and you'd be satisfied with same-day, say that. If you're currently losing track of about one in ten jobs and would accept the occasional miss as long as it's not weekly, say that too. Perfection costs more than "good enough and reliable," and you should decide which one you're actually paying for before you ask for a price, not after.

Be honest about the exceptions

Every process has a version that works 90% of the time and a version that handles the awkward remaining 10%: the client who always pays by bank transfer instead of card, the job that gets quoted differently because it's a repeat customer, the supplier who still only takes orders by phone. These exceptions are usually where automation project costs and timelines actually come from, not the straightforward part of the process.

A brief that only describes the clean, simple version of a workflow will get a quote for the clean, simple version. Then the exceptions turn up mid-project as "oh, and also," and that's how a fixed-price project turns into scope creep, delays, or an uncomfortable conversation about additional costs. Listing the known exceptions upfront, even roughly, lets an agency either price them in or tell you honestly that some of them aren't worth automating yet.

Decide who owns it once it's built

This gets left out of almost every brief we see, and it matters more than people expect. Automations need a person on your side who understands roughly what it does, who gets told first if something looks wrong, and who can make small decisions about it without waiting on an agency for every tweak. If that's going to be you, say so. If it's going to be an office manager who's never touched this kind of tool before, say that too, because it changes how much documentation and handover time should be built into the project, and that's a real cost that belongs in the quote, not a surprise afterwards.

What a genuinely useful brief looks like

It doesn't need to be long. A page is usually enough: a description of the current process in plain steps, the tools involved, what a successful outcome looks like in concrete terms, the exceptions you know about, and who'll own it day to day. Screenshots of the actual spreadsheet or system you're using are often more useful than paragraphs of description, because they show an agency exactly what they're working with rather than your summary of it.

If you've already read about what automation typically costs for a UK small business, this is the brief that makes that estimate accurate rather than a guess. The better the brief, the closer the first quote lands to the final bill, and the fewer awkward conversations happen halfway through the project about things that should have been scoped in from the start.

At Digital Hand, we'll usually spend time on a proper discovery conversation before quoting anything substantial, precisely because most businesses haven't written a brief like this before and shouldn't have to get it perfect alone. If you're weighing up an automation project and want a second pair of eyes on what you'd actually need to brief in, book a free 15-minute consultation and we'll help you work out what's really worth automating before anyone prices anything.