How do I plan a business automation before paying an agency to build it?

Plan the automation yourself before you pay anyone. Map the process, measure the time it costs, and write down the trigger, steps, outputs and exceptions on one page. Then ask two or three builders for fixed-scope quotes against that same brief, keep every account in your business's name, and agree acceptance tests in writing.

Key takeaways

• Decide what to automate yourself, and measure the hours it costs before asking for a price.
• Define the trigger, steps, outputs, data and exceptions in plain words.
• Send the same one-page brief to two or three builders and ask for fixed-scope quotes.
• Keep every account, key and workflow in your business's name, and settle ownership in writing.
• Agree an acceptance checklist and maintenance terms before work starts.

Decide what you are buying before you talk to anyone

Agencies are good at building. But the question of what to automate also decides the size of their invoice. Do the deciding first.

Map the process as it really runs

Pick one process and walk through it with the person who does it today. Write each step in plain words: what arrives, what they look at, what they type, where it goes. Note every app involved, from the inbox to the spreadsheet to the accounting tool. If people do it differently, settle on one way first. An agency will happily automate a muddle.

Measure the time it costs

Count how often the process happens in a month and roughly how long each run takes. Minutes multiplied by frequency gives hours a month, which tells you what a build is worth to you. If the process takes two hours a month, a large build is hard to justify. If it takes forty, it may be worth it. Write the figure down, because you will compare quotes against it.

Define the automation in your own words

Every hour an agency spends working out what you meant is an hour on your bill.

1. Trigger. The single event that starts each run: a new form entry, a paid invoice, an email to a specific inbox, a time of day.
2. Steps. Each action in order, with the app it happens in.
3. Outputs. What must be true at the end: a record created, a message sent, a file saved, a person notified.
4. Data. The fields that move between steps, such as name, email, order total and reference number.
5. Exceptions. What should happen when data is missing, a record already exists, an app is down, or a case does not fit the rules. Name the person who should be told.

If you cannot write a rule for a decision a person makes today, keep that decision human. For a deeper walkthrough, see how to plan a business automation before you build it.

Shortlist the tools

Tell the agency which platform you already pay for, such as Zapier, Make or n8n. A build on a platform nobody in your business can open is one you cannot maintain. Note which app plans you are on, because some connections need a paid tier.

Write a one-page brief and get comparable quotes

Turn your notes into a single page. A good brief contains:

• A one-sentence goal and the hours a month it should save.
• The trigger, steps, outputs, data and exceptions from above.
• The apps and plans you use, and your preferred platform.
• Expected volume, for example "about 300 enquiries a month".
• What is out of scope, so nobody quotes for extras you did not ask for.
• How you will test and accept the work.

Send the same brief to two or three agencies or freelancers. Ask for a fixed-scope quote: one figure for exactly what is in the brief, with any change handled as a separate request. Ask each to list their assumptions, estimated build hours, the monthly tool cost at your volume, and what support after launch involves.

Because everyone quotes against the same page, the numbers become comparable. Big differences become questions worth asking.

If you would rather not write the plan yourself, Automation Blueprint is one option. You describe the process in plain language and get a written plan with a workflow diagram, a suggested platform, numbered build steps, error handling and a testing checklist. It is a plan to hand to a builder, not a build service.

More red flags in proposals

• Pressure to automate several processes at once before the first one works.
• A price that ignores the exceptions in your brief.
• No handover note or documentation in the deliverables.

Keep ownership of accounts and workflows

Ownership is where many small businesses get caught out. In the UK, the person who creates a work is usually its first owner, not the person who paid for it. GOV.UK's guide to ownership of copyright works says a freelancer working under a contract for services usually keeps copyright unless a written agreement says otherwise. Custom code and documentation can fall under this, so put ownership in the contract.

Before any build starts, agree in writing that:

• Every platform and app account is created in your business's name, with your billing details, and the agency is invited as a user rather than the owner.
• API keys and connections sit under accounts you control, and you can revoke the agency's access when the work ends.
• The finished workflows, any custom code and the documentation belong to you.
• You receive a short handover note: what each workflow does, where it runs, which accounts it uses and who is alerted when it fails.

Protect those accounts too. The NCSC's guidance on securing your important online accounts says turning on two-step verification is one of the most effective ways to protect accounts when passwords are still in use.

If an agency keeps the automation in its own account, you are renting it, not buying it.

Agree acceptance tests and maintenance up front

Write the acceptance tests into the brief so "done" means the same thing to both sides. A simple checklist:

1. A normal case runs end to end and produces the expected output.
2. A run with a missing field stops cleanly and alerts the named person.
3. A duplicate does not create a second record.
4. Each branch behaves as described.
5. A failure in one app, such as an expired login, is reported rather than ignored.
6. Tests use test records or a test account, not real customers.
7. You can open the workflow, read its run history and switch it off yourself.

Point 6 matters more than it looks. Zapier's guide to testing Zap steps warns that testing is live and may make changes in your apps.

Pay the final instalment only when the checklist passes. After launch, agree who watches for failures, how quickly they respond, and how small changes are handled. Apps change and logins expire, so plan for some maintenance.

Worked example: an estate agent's enquiry automation

Example: a small lettings agency handles about 300 enquiries a month. Each one is copied from email into the CRM and answered with a standard viewing-times email. It takes about 4 minutes each, so roughly 20 hours a month. These figures are estimates for illustration.

The owner writes a one-page brief:

• Goal: every enquiry logged in the CRM with an automatic reply within 5 minutes, saving about 20 hours a month.
• Trigger: new email to the lettings inbox.
• Steps: extract name, phone and property reference; find or create the contact; send the viewing-times reply; post to the team chat.
• Exceptions: no property reference found means route to a person; CRM down means retry, then alert the office manager.
• Platform: the agency already pays for Make.
• Acceptance tests: the seven points above, run on a test inbox.

She sends it to three builders. Two quote fixed scope with similar build hours. The third quotes an hourly rate, does not mention error handling and plans to build in its own account. She drops the third. Of the remaining two, she chooses the one whose quote lists her exceptions line by line and assigns ownership of the workflow and documentation to her business.

FAQ

How much detail should I give an agency?

Enough that they could quote without a discovery call: the trigger, each step and app, the data fields, the exceptions, your volume and how you will test it. Less detail usually means a vaguer quote.

Should I pay for a discovery phase?

It can be worth it for complex processes that cross several teams. For a single, well-defined workflow, a clear brief often makes it unnecessary.

What if the quotes differ wildly?

Ask each builder to explain their assumptions against your brief. Differences usually come from error handling, testing, platform choice or support after launch.

Who owns an automation an agency builds for me?

In the UK, the creator usually owns copyright in commissioned work unless a written agreement says otherwise. Put ownership of workflows, code and documentation in the contract.

Can I switch builders later?

Yes, if the accounts and workflows are in your name and you have a handover note. That is the main reason to settle ownership before the build starts.

Related guides: what an automation blueprint should include and how to run an automation audit for a small business.

More Automation Blueprint articles