Most AI automation projects don't fail because the technology isn't good enough. They fail because the brief was vague. An agency can build almost anything — but if you walk in saying "we want to automate some of our admin work," you're likely to spend three discovery meetings going in circles before a single workflow gets touched. The businesses that see the fastest results — often cutting 10–15 hours of manual work per week within the first month — come in knowing exactly what problem they're handing over. This guide will show you how to write a brief that gets you there.
Start With the Pain, Not the Solution
The single biggest mistake people make when briefing an automation agency is leading with the tool they think they need. "We want a chatbot" or "can you integrate our CRM with Slack?" are solution-first statements. They skip over the actual problem, which is where the value lives.
Instead, open your brief by describing the pain point in plain operational terms. What task is eating your team's time? Where do things fall through the cracks? What happens when someone is on holiday and a process doesn't get done?
A good pain description sounds like this: "Every time a new client signs a contract, our operations manager manually copies their details from DocuSign into our CRM, creates a folder in Google Drive, sends a welcome email, and adds a task to Asana. This takes about 25 minutes per client, we onboard around 12 clients a month, and it's been done wrong or late at least four times in the last quarter."
That paragraph tells an agency everything they need to know: the trigger (contract signed), the steps involved (four distinct actions), the volume (12 clients/month), the time cost (5 hours/month), and the current failure rate. An experienced automation team can scope a solution in under an hour from a description like that. Contrast that with "we need to streamline our onboarding" — which tells them almost nothing.
Map Out Your Current Process Step by Step
Once you've described the pain, walk through the existing process in sequence. You don't need to be technical. You're not writing code — you're writing a recipe. The agency will handle the implementation details.
For each step, note:
- What triggers it (an email arrives, a form is submitted, a date is reached)
- Who does it (a specific person or role)
- Which tool is involved (Gmail, HubSpot, Xero, a spreadsheet)
- How long it takes
- What can go wrong
Even a rough version of this is enormously useful. A consultancy in Manchester that came to BrightBots for help with their invoice chasing process had never written this down before. When they did, they discovered the process involved six steps across four tools and three different people — and that two of those steps were only happening because of a workaround someone had invented two years ago. Mapping it out didn't just help the agency; it helped the client realise they were solving a more complex problem than they thought. The resulting automation cut their average invoice payment time from 34 days to 21 days by sending timely, personalised follow-ups without anyone lifting a finger.
If you can draw a simple flowchart — even in a Word document or on paper — include it. If not, a numbered list works perfectly well.
Be Specific About Your Tools, Data, and Constraints
Automation is only as good as the systems it connects. A detailed brief tells the agency exactly what they're working with before the project starts, which prevents expensive surprises mid-build.
Include the following in your brief:
Your current tools: List every piece of software involved in the process — your CRM, email platform, project management tool, accounting software, booking system, communication apps. Note which plan you're on, because many integrations require paid tiers.
Your data: Where does the information live? Is it in a clean, structured format (like a CRM field) or is it messy and inconsistent (like a free-text email inbox)? Are there GDPR or data sensitivity considerations the agency needs to know about?
Your constraints: Do you have an IT policy that restricts third-party tools? Are there integrations your current software doesn't support? Is there a team member who needs to stay in the loop even if the task is automated? These aren't blockers — they're parameters. A good agency works around them, but only if they know about them upfront.
Your budget and timeline: Even a rough range helps. "We're looking to spend between £1,500 and £3,000 and want something live within six weeks" is actionable. It tells the agency whether to propose a lightweight solution using existing tools like Zapier or Make, or whether there's room for a more custom-built agent that handles exceptions and edge cases. Being coy about budget wastes everyone's time.
Define What Success Looks Like
A brief without a success metric is a project without an ending. Before you send anything to an agency, agree internally on what "done" looks like — and what "working well" looks like three months later.
This doesn't need to be complicated. Some examples:
- "The new client onboarding sequence runs without any manual input, and no steps are missed."
- "Our team spends less than 30 minutes per week on invoice chasing, down from three hours."
- "Appointment reminder no-shows drop from 18% to under 10%."
Quantified targets give the agency something to build toward and give you something to evaluate the project against. They also make it easier to decide whether a slightly more expensive build is worth it — if an automation is going to save your team 8 hours a week at a fully-loaded cost of £35/hour, that's £280/week or around £14,500 a year. A one-off build cost of £2,500 pays back in under three months.
Also note any non-negotiables around quality. If the automation involves customer-facing communication, you'll want to specify the tone, and whether a human should review outputs before they go out. If it's an internal data process, define what an acceptable error rate looks like — because no automation is perfect, and knowing when to escalate is part of a well-built system.
Conclusion
The difference between a vague brief and a great one isn't technical knowledge — it's specificity. You don't need to know how automation works. You need to know your own processes well enough to describe them clearly: what triggers them, what steps they involve, which tools touch them, and what a good outcome looks like. Do that, and you'll hand an agency everything they need to build something that genuinely moves the needle. The time you spend writing a thorough brief — usually an hour or two — saves weeks of back-and-forth and dramatically increases the chance that what gets built actually solves your problem.