Most AI automation projects don't fail because the technology isn't good enough. They fail because the brief was vague. If you walk into a conversation with an automation agency and say "we want to use AI to save time," you'll get a generic solution that half-fits your workflow and costs more to fix than it would have to specify properly in the first place. The good news: writing a strong brief doesn't require any technical knowledge. It just requires you to describe your business clearly. Here's exactly what to include.
Start With the Problem, Not the Solution
The single most common mistake people make when briefing an automation agency is leading with the tool they think they need. "We want a chatbot" or "can you set up something with ChatGPT?" puts the cart before the horse. Start with the pain instead.
Describe the specific task or process that's costing you time, money, or errors right now. Be precise. "Our admin team spends roughly three hours every Monday manually copying appointment data from our booking system into our CRM, then sending confirmation emails one by one" is a brief. "We have a lot of manual admin" is not.
The more granular you can be, the better. Think about:
- How often does this task happen? (Daily, weekly, per customer?)
- Who does it? (One person, a whole team?)
- How long does it take? Even a rough estimate is useful.
- What happens when it goes wrong? Missed follow-ups, duplicate records, delayed invoices?
That last question matters more than people realise. If a missed follow-up costs you a £2,000 client on average and it happens four times a month, that's £8,000 a month in recoverable revenue — not a "minor admin issue." Putting a number on the problem helps an agency prioritise the right solution and helps you evaluate whether the investment makes sense.
Map Out Your Current Tools and Hand-offs
You don't need to be technical here. You just need to trace the journey a piece of information takes through your business. Think of it like describing how a ball gets passed between players.
For example: a new lead fills in a contact form on your website → someone copies the details into your CRM manually → a colleague checks the CRM and sends a welcome email → the lead gets added to a spreadsheet for the sales pipeline review on Friday. That's four hand-offs, three of which are manual. Each one is a point where something can get lost, delayed, or entered incorrectly.
List the tools you use at each stage. Common ones include:
- CRM (HubSpot, Salesforce, Pipedrive)
- Email (Gmail, Outlook)
- Project management (Asana, Monday, Notion)
- Communication (Slack, Teams)
- Booking or scheduling tools (Calendly, Cliniko, OpenTable)
- Invoicing or finance (Xero, QuickBooks)
You don't need to know how these systems connect technically — that's the agency's job. But knowing which tools are in the chain tells them where the automation needs to live. A good agency will use this to identify whether a simple integration handles the problem or whether an AI agent (a piece of software that can reason and make decisions, not just move data) is needed.
A real example: A 12-person consultancy was losing around five hours per week across their team because project updates in Asana weren't syncing with client-facing reports in Notion, so someone had to manually rewrite them every Friday. After briefing an automation agency with a clear map of that hand-off, they had a working AI agent within two weeks that pulled updates, summarised them in plain English, and populated the client report automatically. Their estimate: 200+ hours saved per year, and one less thing falling through the cracks during busy periods.
Be Honest About Your Constraints
A brief that only describes what you want, without mentioning what you're working with, sets you up for a solution that's technically brilliant but practically useless.
Cover these four areas honestly:
Budget range. You don't need an exact figure, but a ballpark helps enormously. There's a big difference between "we want to spend under £500 to set this up" and "we're prepared to invest £3,000–£5,000 if the ROI is clear." Automation builds can range from a few hundred pounds for a simple workflow to tens of thousands for a complex, multi-system agent. Being vague about budget wastes everyone's time.
Technical capacity. Do you have anyone in-house who can manage a tool once it's built, or do you need everything handed over with zero maintenance? Some lightweight automation platforms (like Zapier or Make) are manageable by a non-technical team member with a bit of training. Others need ongoing oversight. Tell the agency what your team can realistically handle.
Data sensitivity. If you're in healthcare, legal, or finance, you need to flag this upfront. GDPR compliance, data residency, and client confidentiality all affect which AI tools can be used in your workflow. An agency that doesn't ask about this early is one to be cautious about.
Timeline. Do you need this live in two weeks because a staff member is leaving and this replaces their manual task? Or is this a longer-term efficiency project? Urgency affects how an agency scopes the work.
Define What "Success" Looks Like
This is the section most briefs skip entirely, and it's the one that determines whether the project actually delivers value.
Before the build starts, agree on what you're measuring. Good success metrics for an automation project might include:
- Hours saved per week (aim to quantify this — "saves Sarah 4 hours on Mondays" is more useful than "saves time")
- Error rate reduction (e.g., duplicate CRM entries drop from 15 per week to near zero)
- Response time improvement (e.g., new enquiries get an acknowledgement within 2 minutes instead of 4 hours)
- Revenue recovered (e.g., no more missed follow-ups on quote requests)
You should also define what "done" means. Is it when the automation is live? When it's been running for two weeks without errors? When you've seen a measurable change in the metric you defined? Getting this clear upfront avoids the awkward situation where the agency thinks they've delivered and you feel like something's missing.
If you're not sure what metric to pick, ask the agency to suggest one based on your brief. A good agency will welcome this conversation — it keeps them accountable too.
Conclusion
A well-written brief is the difference between an automation that genuinely changes how your business operates and one that gets built, half-used, and quietly abandoned. You don't need to understand AI to write a good one — you just need to describe your workflow honestly, name your tools, acknowledge your constraints, and define what winning looks like. The more clearly you can paint the picture of your current reality, the more precisely an agency can design the solution. Spend an hour getting your brief right, and you'll save weeks of back-and-forth — before a single line of automation is even built.