How do you write an AI project scope a vendor can’t inflate?
Name one workflow end-to-end, state what it costs you today, define “done” in operations language, list what is explicitly out, make the vendor state the monthly run cost, and get the price fixed in writing before work begins. Those six properties make changes visible and easier to price before anyone does additional work.
Most owners have bought plenty of software but have never bought AI, and some vendors price that inexperience in. This guide is procurement armor: what each clause does, the inflation patterns it blocks, and a ten-line template at the end you can copy into your next conversation. We build under these terms ourselves — every price we charge is published — and the written agreement should identify the scope, dependencies, and responsibilities for your project.
Why must the scope name exactly one workflow?
Because “AI transformation” can absorb any invoice, and “the proposal workflow, from intake email to filed PDF” cannot. Scope inflation begins with nouns that have no edges.
Name the workflow end-to-end: what event starts it, what artifact ends it, and everything a person touches in between. A workflow with a named beginning and a named end can be priced, tested, and declared finished; a “transformation” can only be extended. This is also the honest unit of delivery — roughly 90 days per workflow is a realistic yardstick, and it is the rhythm we publish for our own work. The second workflow is not scope creep waiting to happen; it is a second project with its own scope, priced after the first one has proven itself.
What does the workflow cost you today — and why put it in the scope?
Start with frequency, preparation time, and a loaded hourly rate. Then add any distinct costs of delay or errors that you can support. Do not count the same benefit twice, or assume that every saved minute becomes cash.
An illustrative workflow taking six hours a week at a $55 loaded rate represents $17,160 of annual labor value over 52 weeks. A build must justify its cost against the share you can actually recover after review and running expenses. Other benefits need their own evidence. Your measured hours are more useful than the assumptions in our calculator.
What do good acceptance criteria look like?
They are written in operations language: “drafts the response, files it in the job folder, and a person approves before anything sends.” If a criterion mentions model names, unmeasurable accuracy percentages, or the word “intelligent,” rewrite it.
Good acceptance criteria identify the test cases, required output, tolerable errors, approval owner, and failure behavior. An accuracy percentage can be useful only when the sample, denominator, and error types are defined. Include cases where the system should stop or escalate, and measure the review work it creates.
What belongs explicitly out of scope?
The next workflow, the website redesign, and any data cleanup beyond what this workflow needs. Out-of-scope lines are not pessimism — they are the walls of the room.
Change orders live in ambiguity. Every adjacent thing the scope fails to exclude is a thing the project can quietly grow to include, billed at whatever the moment allows. Data cleanup is the classic: your records will need some work, and the scope should cover exactly the cleanup this workflow requires — not a general data-hygiene program that runs for two quarters. Writing the exclusions down feels blunt in the meeting. It is far friendlier than the alternative, which is discovering in week seven that you and the vendor were building different projects all along.
Who owns what at handoff, and what does it cost to run?
State what transfers at handoff: custom code and configuration, prompts, documentation, credentials, and data. List third-party services and licenses separately. Our sprint includes ownership of what we build and team training; the agreement should make those boundaries clear.
Our $50–$500 monthly planning band covers typical small-business tools and model usage, not internal review, hardware, or paid maintenance. Ask for volume assumptions and a handoff walkthrough. A competent successor should understand the dependencies and operating instructions, but the time needed to take over will depend on the system.
Why is a fixed price in writing the strongest clause?
Because it makes the price of the agreed work explicit. It does not eliminate unknowns or cover every future request. Pair the fixed price with dependencies, exclusions, acceptance criteria, and written approval for additional work.
At Main & Machine, a defined workflow can go from the free assessment to sprint scoping. If investigation is needed, an AI Readiness Audit is $3,500–$8,500 over 2 to 4 weeks. An Implementation Sprint is $18,000–$60,000 over 4 to 12 weeks, with the scoped price agreed in writing before work begins. The free call begins the conversation; it does not promise a completed scope or quote in 30 minutes.
What are the vendor-inflation patterns to catch?
Four recur: discovery that never ends, “phase 1” pricing, platform lock-in dressed as architecture, and change-order pipelines. Each converts an ambiguity in your scope into billable time.
They are easiest to catch in the proposal language itself, so here they are side by side — the clause as commonly written, what it turns into, and the rewrite that closes the door.
| Inflatable clause | What it becomes | Inflation-proof rewrite |
|---|---|---|
| “Phase 1 begins with discovery, billed monthly until requirements stabilize.” | Discovery that never ends — requirements never quite stabilize | “Discovery is a fixed-price, fixed-length audit (2–4 weeks) that ends with a written implementation quote.” |
| “Phase 1 investment: $15,000.” | Phases 2 through 5, unpriced and assumed | “This price covers the named workflow running in production — or the document states exactly what it excludes.” |
| “We build on our proprietary platform for long-term scalability.” | Lock-in dressed as architecture — leaving costs a rebuild | “Client owns all code, prompts, documentation, and accounts at handoff; a competent third party could take over from the docs.” |
| “Additional requirements are handled through our change-request process.” | A change-order pipeline priced after you are committed | “The out-of-scope list is written down. Any additional work needs an agreed scope and price before it begins.” |
“Inflatable” clauses are composites of common proposal language, not quotes from any specific firm.
What goes in the scope document, line by line?
Ten lines. Copy them, fill them in, and bring the page to every vendor meeting — if a vendor pushes back on more than two, that is the finding.
- The workflow, named end-to-end. “From [intake event] to [filed output].” One workflow. The next one is a separate project.
- Who touches it today, and for how many hours a week. Named roles, measured or carefully estimated hours.
- The current annual cost. Hours × loaded rate. This is the ceiling every quote answers to.
- Acceptance criteria in operations language. What “done” does on an ordinary Tuesday — drafts filed, statuses updated, nothing sent without sign-off.
- The human approval point. Who reviews, what they approve, and the 2–3 hours a week budgeted for it.
- Explicitly out of scope. The next workflow, the redesign, and any data cleanup beyond what this workflow needs.
- Ownership at handoff. You own the code, prompts, documentation, and accounts; your team is trained to run it.
- The run cost, stated by the vendor in writing. Tools plus model usage — $50–$500 a month is the normal band for a small business.
- A fixed price, in writing, before work begins. With the payment schedule. Not an estimate, not a target.
- A timeline with an end date. Roughly 90 days per workflow is a fair yardstick; a project with no end date is a retainer wearing a hard hat.
Owners in trades businesses tend to take to this fastest — construction firms have been burned by open-ended change orders before and recognize the pattern instantly. The same armor works in every industry. Pair this template with the ten vetting questions when you take meetings, and if you want to watch the process from the other side of the table first, the free 30-minute assessment is where we begin with one workflow and discuss what evidence is needed to scope it. We reply within 24 hours.
If you would rather order a part than commission a project, the build catalog explains the available components and how they are scoped within an engagement.