What an automation project brief is, and why it changes your quote
An automation project brief is a one-to-two-page description of the workflow automation you want built, written before anyone quotes it. It is the document that decides everything downstream, because every number a vendor gives back is a guess about whatever you left out.
Two shops quoting the same use case from a vague email will differ by a factor of four. Quoting from a brief that names the trigger, the systems, the volume, the approval steps and the exception rate, they land within a reasonable band of each other. The spread was never about the vendors, it was the missing information each one priced defensively.
This is a template you can fill in yourself in about an hour, with no automation consulting required to produce it. You do not need to know which automation tools will be used, and you should resist picking them upfront. Your job is to describe the work precisely. Choosing between Zapier, Make.com, n8n or custom scripts is the vendor's job, and it depends on what you write here.
The nine sections every automation brief needs
Write these in order. If a section is genuinely unknown, write "unknown" rather than guessing, because a guess gets priced as a fact.
1. The workflow as it runs today
Describe the current process in plain sentences, start to finish, naming the job title of whoever does each step and every stakeholder who has to agree to a change. Not what you wish happened, what actually happens including the workaround everybody uses. Most automation projects that fail were built against the documented process rather than the real one.
2. Trigger, steps, approval and routing
Name the exact event that starts the workflow: a form submission on your contact us page, an email hitting a shared inbox, a status change in the CRM, a file landing in a folder. Then list the steps in order, and mark which ones need a human approval and which involve routing to different people depending on a value. Approval and routing rules are where simple workflows quietly become multi-step ones.
3. Systems, integrations and where the data lives
List every system the workflow touches and what each one holds: CRM, accounting, email, storage, phone, scheduling, spreadsheets. For each, say whether you have admin access and whether it has an API. Integration surface is the biggest single factor in an automation cost estimate. One legacy system with no API can cost more than the other five combined.
4. Volume, hours per week and exception rate
Give real numbers: how many workflow runs per week or month, how many hours per week the team spends on it, the labor cost of those hours, and roughly what share of cases go off the happy path. Volume drives the ROI case, the exception rate drives the build effort. A process running 40 times a week with a 2% exception rate is a different job from the same volume at 30%.
5. What success looks like, in measurable terms
State the outcome you are buying: time saved per week, faster client communication, fewer errors on a named step, invoices paid sooner. Pick one primary metric and baseline it now. "Efficiency gains" is not a target. "Cut time from job completion to invoice sent from three days to same-day" is, and it tells the vendor which corners not to cut.
6. Constraints, audit trails and who must stay in the loop
Write down the rules that cannot be broken: which data may not leave your environment, what needs audit trails, which decisions a human must sign off, any retention obligation. If steps must stay manual for compliance reasons, say so here rather than letting a vendor design them out and rediscover the constraint at testing.
7. Budget, pricing model and timeline
Give a range, not a secret. Withholding your budget does not get a better price, it gets three proposals scoped at random. Say whether you want a one-time build, a build plus a support retainer, or a monthly subscription, and give your timeline including any hard date. AutomateNexus builds start at $7,500 with a typical build running about 30 days, a useful anchor for a scoped single workflow in 2026.
8. Ownership and ongoing support after launch
State up front that you expect to own the code, the automation platform account and the API keys, and ask what ongoing maintenance costs. Then ask who fixes it at 2am. Long-term support and error handling are ongoing costs, not a one-time line, and a brief that ignores them invites a quote that ignores them too.
9. What you have already tried
List the automation tools you already pay for, anything half-built and abandoned, and why it stopped working. Existing tool subscriptions often cover more than teams realise, and a good automation partner builds on what you have rather than adding another platform.
A worked example: chasing unpaid invoices
Here is what a filled-in brief looks like. This is an illustration, not a client, and the numbers are the sort you would replace with your own.
Workflow today: the bookkeeper exports an aged debtors report from the accounting system every Monday, filters anything past 14 days, and writes individual chase emails. Anything past 45 days gets escalated to the owner by message. Trigger: invoice crosses 14 days overdue. Steps: identify invoice, check for a recorded dispute in the CRM, send reminder one; at 30 days send reminder two with the statement attached; at 45 days create an alert for the owner instead of sending anything.
Systems: accounting software (API available, admin access yes), CRM (API available), shared mailbox. Volume: around 60 overdue invoices a month, roughly four hours per week of chasing, about 15% have a dispute or partial payment that must not receive a reminder. Success metric: average days-to-payment, baselined this quarter. Constraint: no automated email may go to an account flagged in dispute, and every send must be logged against the invoice record.
That is enough to quote without a discovery call, and enough for you to tell whether the quote reflects the 15% exception path or quietly assumes it away.
How the brief changes automation pricing
Vendors price uncertainty. A brief that pins down volume, integrations and exception rate removes the padding, and a vendor who still cannot give a fixed number against it is telling you something useful.
The brief also forces a real cost breakdown rather than one headline figure. Ask any proposal to separate the upfront build, the recurring tool costs, the AI model usage, and ongoing support. Those are four different cost structures: a one-time payment, a subscription, a usage bill and a retainer. Bundling them into a single monthly number is the most common way automation projects turn out to cost more than expected.
The hidden costs to name explicitly in your brief are data cleanup before anything can run, employee training and onboarding, and the customization that arrives after the first two weeks of real use. On the model side, insist on bring-your-own-key so AI usage bills land on your account at cost, typically $30 to $150 a month for a small business workload rather than a marked-up line item. If self-hosted infrastructure is on the table, our breakdown of n8n cloud versus self-hosted real costs shows how the operating costs actually compare.
Mistakes that make an automation brief useless
Specifying the solution instead of the problem. "We need an AI agent that reads emails" removes every cheaper option before anyone looks. Describe the outcome and let the vendor propose the mechanism; sometimes the answer is a filter and a template, not AI automation at all.
Describing the process you designed rather than the one people run. Sit with whoever does the work for twenty minutes before you write section one.
Bundling six workflows into one brief. Write one per workflow, then rank them. Scaling to the second and third gets cheaper once the first build exists, while a single mega-brief gets quoted as a mega-project.
Leaving out the exception rate. It is the most common omission and the biggest source of overrun, because the happy path is the easy part of the build and the exceptions are the rest.
If you are not sure which workflow deserves the first brief, the free automation health audit takes about three minutes, needs no call, and returns ranked quick wins plus an estimate of what manual work is costing you annually. The automation playbook covers how to sequence projects after the first one lands, and our AI agent builds page shows what a scoped single-workflow project usually contains.
Frequently asked questions
How long should an automation brief be?
One to two pages per workflow. Longer than that and you are writing a specification, which is the vendor's job and which you will pay to have rewritten anyway. A section that runs long usually means the workflow is really two, and should be split.
Do I need to pick the tool before writing the brief?
No, and picking one early costs you options. Zapier, Make.com, n8n and custom code all suit different volume, complexity and compliance profiles. Name what you already pay for so a vendor can build on it, then let the proposal justify its own choice against your integration list and workflow runs.
How much does business automation cost?
It varies with integration count, exception rate and volume more than with the number of steps. Ask for a cost breakdown split into upfront build, tool subscriptions, model usage and ongoing support rather than one figure. As an anchor, AutomateNexus builds start at $7,500 and an MVP runs four to eight weeks depending on complexity.
Should I send the same brief to multiple vendors?
Yes. Identical inputs are the only honest way to compare quotes. Send it to three, and when numbers diverge sharply, ask each to walk through their assumptions on volume and exceptions. That conversation reveals who actually read it.
How long until an automation pays for itself?
Divide the build cost by monthly labor cost savings, using a fully loaded hourly rate for whoever does the work today. If payback runs past 12 months on that arithmetic, the workflow is probably too low-volume to be your first project. Rank candidates by that ratio before committing.
What hidden costs should I watch out for in automation projects?
Data cleanup, employee training, marked-up AI model usage, per-seat licences that grow with headcount, and change requests after sign-off. Ask for a written exclusions list in every proposal. What is deliberately not included tells you more about the total cost than the headline price does.
What if I do not know my volumes or hours per week?
Measure for one week before sending the brief, or write "unknown" and say you will measure during discovery. Either is fine. Inventing a number is not, because it becomes the basis of a fixed quote and an ROI case you cannot defend later.