A good automation project scope says, in writing, what will be built, which systems it touches, how success will be measured, what it costs, how long it takes, what access the provider needs, who owns the result and what happens when something changes. If a scope can't answer those questions, the price and the deadline are guesses, and the disagreements show up halfway through the project. This checklist walks through each part so you can judge a scope, or a quote that calls itself one, before you sign it.

Why the scope matters more than the quote

The quote tells you a number. The scope tells you what that number buys. Two proposals with the same price can describe very different projects: one includes testing with your real data, documentation and training, and the other stops when "the flow runs".

A written scope also protects both sides. You know exactly what you're getting, and the provider knows exactly what they've promised. When a question comes up mid-project ("is this included?"), the scope answers it instead of a phone call that nobody remembers the same way.

If the provider bills by the hour, the scope matters even more, because anything vague turns into extra hours. We compare billing models in How Much Does Business Automation Cost?

What an automation project scope should include

1. The problem and the outcome

Start with one or two plain sentences: what is slow, manual or error-prone today, and what should be true when the project is done. For example: "Supplier invoices are retyped into the accounting system by hand. After the project, invoices that arrive by email are read, checked against purchase orders and entered automatically, with exceptions sent to a person for review."

If the provider can't write this in plain language, they may not understand the problem yet.

2. The workflows in scope, and what's out of scope

List each workflow by name, with where it starts and where it ends. Then list what is not included. The "out of scope" list is often more useful than the "in scope" list, because it's where assumptions hide. Common examples: historical data cleanup, other departments' versions of the same process, or a second integration "for later".

3. Every system it touches

Name each system the automation will read from or write to: your email, CRM, accounting software, file storage, line-of-business tools and any older on-premises software. For each one, the scope should say how it will be connected (a built-in connector, an API, or something custom) and whether that connection has been checked.

Connecting systems is often the largest piece of work, so a provider should check how each system connects before quoting, not discover it after you've signed.

4. Where AI is used, and where a person reviews

If the project uses AI to read documents, sort requests or draft replies, the scope should say exactly which steps use it, which AI service runs it, and in whose account. It should also name the points where a person reviews or approves the result before anything important happens: a payment, a customer message or a change to a record.

We explain how we decide where AI earns its place, and where it doesn't, on our AI page. For document-heavy work, AI document processing shows typical review steps.

5. Success criteria you can measure

This is the part most scopes skip. "Automate invoice entry" isn't a success criterion. "Invoices from the top 20 suppliers are entered without retyping, with fewer than one in ten needing manual correction during the test month" is.

Good success criteria are specific, measurable and agreed before work starts. They decide whether the project is finished, so they should be in writing and both sides should sign off on them.

6. A fixed price, with software costs listed separately

The scope should state the price for the work, and whether it's fixed. Separately, it should list any ongoing costs you'll pay: new software licenses, AI usage and hosting. Those should be billed to accounts in your name, at the vendor's price, not marked up and resold to you.

Our project prices are published on our pricing page. AutoStart starts at $2,500, and every price is fixed once the written scope is signed.

7. A timeline with milestones

A start date, an end date and a few milestones in between: design approved, first working version, testing with real data, handover. The scope should also say what the timeline depends on, such as getting access to your systems or a person on your side to answer questions.

8. The access the provider needs, and how it's removed

List the accounts and permissions the provider needs, why they need each one, and when that access will be removed. Access should go through user accounts your company controls, never your own login shared by email.

9. Testing, documentation and training

The scope should say that testing uses your real data (not tidy samples), and that you'll receive written documentation of what each workflow does, what it connects to, what can go wrong and how to fix it. Training for the people who'll run it day to day belongs here too. If documentation isn't listed as a deliverable, assume you won't get it.

10. Ownership and handover

Everything should be built in accounts in your company's name, with your company as administrator, and the work should belong to you once it's paid for. The scope should also say what happens if you move on: export of your workflows and data, a handover to your team or next provider, and no exit fee. These are the commitments in our No Lock-in Pledge. Our article Who Owns Your Automations When the Consultant Leaves? goes through the ownership questions in detail.

11. Support after launch

Say how long support lasts after handover, what it covers and what happens after that. Ongoing upkeep can be in-house, as needed, or a monthly plan. If it's a plan, check for minimum terms and notice periods. Ours are month to month with 30 days' notice; see care plans.

12. How changes are handled

Projects change. The scope should explain how: you ask, the provider tells you in writing what the change costs and how it affects the timeline, and nothing is built until you approve it. That simple rule prevents most billing surprises.

Red flags in an automation scope

  • No success criteria, or criteria such as "working automation" that can't be measured.
  • Vague systems, such as "integrate with your CRM" with no mention of how or whether it's been checked.
  • Documentation and testing missing, or listed as optional extras.
  • Accounts in the provider's name, or plans to "move it to you later".
  • Open-ended hours with no cap, or a fixed price with a long list of exclusions that cover the hard parts.
  • No change process, which usually means changes get billed after the fact.

How we write a scope

We write a scope after a free 30-minute discovery call. The written proposal lists the systems in scope, success metrics, a fixed cost, the timeline, the access we need, and software or hosting fees separately. You can read the full process on how we work. If what we deliver doesn't meet the success criteria in your scope, we keep working at no charge until it does.

Frequently asked questions

What is a scope of work for an automation project?

It's a written document that defines what will be automated, which systems are involved, how success is measured, the price, the timeline, the access needed and who owns the result. It's the reference both sides use to decide what's included and when the project is done.

How detailed should an automation scope be?

Detailed enough that someone outside the project could read it and tell whether the work was delivered. For a single workflow, that's usually a few pages: the outcome, the systems, measurable success criteria, the price, milestones and the handover terms.

What's the difference between a quote and a scope?

A quote gives a price. A scope says what the price buys, how success is measured and what happens if things change. Always ask for the scope before you compare quotes, because the same price can describe very different projects.

Who should own the accounts in an automation project?

You should. Every platform and AI service should be set up in your company's name, with your company as administrator, so the automations keep working and stay yours if the provider leaves.

What happens if the project needs to change?

A good scope includes a change process: you ask for the change, the provider tells you the cost and timeline effect in writing, and nothing changes until you approve it.

Get a written scope for your first workflow

If you have a process you'd like to automate, book a free 30-minute discovery call. We'll help you pick the workflow that would save the most time, and you'll get a written scope and a fixed price before any work starts.