A client says yes on the call. Then the document lands in their inbox and the deal goes quiet for three weeks. That is not a pricing problem. That is a document problem. An AI automation proposal is a short written offer that states the process you will automate, what the client receives, what the client does not receive, the price, and the one step that starts the work.
Most operators send a quote. A quote hands someone a number to think about. A proposal hands someone a decision to make. Sixteen years of enterprise automation work taught me the difference, and the Army taught me the format first: nobody moves until the brief is written down.
Key takeaways
- An AI automation proposal is a written offer that names the process being automated, the deliverables, the exclusions, the price, and the next step.
- The BRIEF Proposal has five blocks: Baseline, Result, Inclusions, Exclusions, Fee and first step.
- Research presented at the PMI Global Congress 2009 lists ambiguous or unrefined scope definition as the first cause of scope creep, which is why the exclusions block matters as much as the inclusions block (Larson & Larson, 2009).
- The strongest proposals are written after a paid diagnostic, so the baseline numbers come from the client’s own process instead of a guess.
- Two pages beats twenty. The reader is looking for scope, price, and start date.
- Sending one costs very little. As of September 2026, PandaDoc lists an Individual plan at $9 per user per month and DocuSign lists a Personal eSignature plan at $11 per month on annual billing.
Why most AI automation proposals stall
Three failure patterns show up over and over.
The first is a technical spec dressed up as an offer. Twelve pages about webhooks, vector stores, and retry logic. The buyer is an operations manager who wants to stop paying someone to copy invoice numbers into a spreadsheet. Every paragraph about your stack is a paragraph that does not answer their question.
The second is a number with no baseline attached. They have nothing to compare your price against, so they compare it against zero. Zero always wins that fight.
The third is an open scope. No exclusions section means every future request is arguably included, and the project that was supposed to take two weeks is still open in month four. That is the mechanism behind scope creep, and the causes are well documented: work presented at the PMI Global Congress 2009 put ambiguous or unrefined scope definition at the top of the list, followed by the absence of any formal scope management process.
A proposal is not a sales document. It is an operations order the client signs.
The BRIEF Proposal: five blocks that do the closing
BRIEF stands for Baseline, Result, Inclusions, Exclusions, Fee and first step. Five blocks, two pages, no appendix. Write them in this order every time.
B is for Baseline: price the problem before the build
Open with the current state in the client’s own numbers. How many times per week the task runs, how long each run takes, who does it, and what that person costs per hour. Three sentences is enough.
You cannot write this block from a discovery call alone, because people underestimate their own processes. This is the reason to sell a paid diagnostic first. An AI agent audit gets you inside the process, and the findings become the first block of the proposal you send afterward.
R is for Result: one number they already track
State the outcome as a change to a metric the client measures today. Hours returned per month. Days to first response. Error rate on a data entry step. One metric, not five.
Write it as a projection based on the baseline you measured, and label it that way. “Based on the 14 hours per month we logged in the audit” is a defensible sentence. “Save thousands” is not, and a buyer who has been pitched before will read it as noise.
I is for Inclusions: what they get, in their words
List the deliverables as objects the client can picture. “An agent that reads the shared inbox every 15 minutes, extracts the purchase order number, and writes it to the tracking sheet.” Not “an n8n workflow with an AI agent node.”
Include the handover items too: a one page runbook, a test log, and a 30 minute walkthrough. Those cost you almost nothing and they are the difference between a build and a service. If you find yourself rewriting this block from scratch for every client, that is the signal to move toward a productized AI service with a fixed scope.
E is for Exclusions: the fence that keeps the project alive
This is the block almost everyone skips, and it is the one that protects both sides. Name what is not included: additional systems, data cleanup on historical records, changes to the client’s software licenses, and anything requiring access you were not granted.
Then add one line that turns an argument into a process: out of scope requests are quoted as a change order before work begins. You are not refusing the work. You are routing it. Ongoing obligations such as uptime and fix times belong in a separate document, and the AI agent SLA is where those terms live.
F is for Fee and first step: one price, one action
State the price plainly. No value stacking, no anchoring theater, no countdown. If you offer tiers, cap it at two, because a third option usually produces a delay rather than a decision.
Then name exactly one next step with a date attached: approve this document by Friday and the build starts Monday. Setting the number itself is a separate skill, and the method I use to price AI automation services starts with a cost floor rather than a guess at what the market will bear.
Example scenario: the purchase order backlog
Example scenario, constructed to show the format. The numbers below are illustrative, not a client result.
A 20 person distributor has a coordinator who opens a shared inbox twice a day, finds purchase order confirmations, copies the PO number and delivery date into a tracking sheet, and replies to the supplier. The audit logs 46 entries per week at roughly four minutes each, so about 13 hours per month.
Here is how that becomes five blocks.
- Baseline: 46 confirmations per week, about four minutes each, roughly 13 hours per month of coordinator time, with an average two day lag on supplier replies.
- Result: supplier replies move from about two days to same day, and the coordinator’s 13 hours per month go back to order exceptions.
- Inclusions: an agent that checks the shared inbox every 15 minutes, extracts PO number and delivery date, writes both to the tracking sheet, sends a confirmation reply from a template, and flags anything it cannot read to a review folder. Plus a runbook, a test log, and a walkthrough.
- Exclusions: no changes to the ERP, no cleanup of the 2024 and 2025 order history, no supplier onboarding, and no handling of attachments that are scanned images unless optical character recognition is added as a change order.
- Fee and first step: one build fee, one monthly support figure, approve by Friday and the build starts Monday.
Notice what is missing. No architecture diagram. No model names. The buyer does not care whether the extraction runs through one tool or another, and once the monthly support line is in the document you have already opened the door to an AI agent retainer instead of a one time build.
What to send it with
You do not need a proposal platform to start. A clean PDF and an email work. When you want tracking and signatures in one place, two options are worth checking, and both publish their pricing openly.
PandaDoc lists a free eSign tier, an Individual plan at $9 per user per month, and a Business plan at $49 per user per month on its pricing page as of September 2026. DocuSign lists a Personal eSignature plan at $11 per month on annual billing with a five envelope monthly limit, and a Standard plan at $30 per user per month on annual billing. Verify both before you quote them to anyone, because software pricing moves.
For the money side, Stripe Invoicing publishes 0.4% per paid invoice on Starter and 0.5% on Plus, with standard payment processing fees on top. That means you can send a signable document and collect the deposit with no monthly subscription at all.
Your action steps this week
- Open the last proposal you sent and find the exclusions section. If there is not one, that is your first edit.
- Build a two page template with the five BRIEF headings already in place. Fill nothing in yet.
- Write your standard exclusions list once. Most of it will be identical on every project you take.
- Add the change order sentence to the template so you never have to improvise it mid project.
- On your next opportunity, sell the audit first and write the baseline block from what you measured, not from what the client remembers.
Frequently asked questions
How long should an AI automation proposal be?
Two pages. The decision maker reads the scope, the price, and the start date, and long documents delay approval rather than strengthen it. If a technical appendix is genuinely required, attach it as a separate file so it does not sit between the reader and the price.
Should I put the price in the proposal or save it for a call?
Put it in the document. A proposal without a price is a brochure, and it forces another meeting before anything can move. Holding the number back also signals that the price is negotiable, which invites a conversation about discounting before the client has finished reading the scope.
What goes in an automation scope of work?
An automation scope of work names the systems touched, the trigger that starts the process, the actions the agent takes, the exception path when it fails, and the handover items. It should also name what is excluded, because an unbounded scope of work is the most common reason a fixed fee project loses money.
Do I need e-signature software to send a proposal?
No. An emailed PDF with a written reply saying “approved” is a workable agreement for a small engagement. E-signature tools such as PandaDoc and DocuSign add tracking, templates, and a cleaner audit trail, which becomes worth the monthly cost once you send proposals regularly.
What if the client asks for changes after signing?
Quote it as a change order before any work starts, exactly as the exclusions block says you will. The document already established the process, so you are following a procedure the client agreed to rather than renegotiating under pressure.
To recap
An AI automation proposal closes when it answers five questions in order: what is happening now, what changes, what you deliver, what you do not deliver, and what the client does next. That is the BRIEF Proposal. Baseline, Result, Inclusions, Exclusions, Fee and first step.
The baseline comes from a paid audit rather than a guess. The result is one metric the client already tracks. The inclusions are written as objects, not architecture. The exclusions are a fence with a gate, and the gate is the change order. The fee is a plain number with one dated next step attached.
Write the template once and you stop rebuilding the same document under deadline pressure. If you want the rest of this build out, subscribe to the blog and the next post lands in your inbox.
References
DocuSign. (2026). Plans and pricing: eSignature. https://ecom.docusign.com/plans-and-pricing/esignature
Larson, R., & Larson, E. (2009). Top five causes of scope creep and what to do about them [Conference paper]. PMI Global Congress 2009, North America, Orlando, FL. Project Management Institute. https://www.pmi.org/learning/library/top-five-causes-scope-creep-6675
PandaDoc. (2026). Pricing. https://www.pandadoc.com/pricing/
Stripe. (2026). Invoicing pricing. https://stripe.com/invoicing/pricing
Leave a Reply