AI Agents in Proposal Generation: Where It Breaks
Every proposal is assembled from the same blocks, by hand, again.
The loop, as it actually runs
- Scope agreed
- template selected
- content assembled
- pricing applied
- reviewed
- sent and tracked
Where it breaks
Not in the steps. In the joins between them:
- Assembly is copy-paste from the last one
- Pricing errors slip through
- Version control is filenames
- Nobody knows if it was opened
What that actually costs
Proposal assembly by copy-paste from the last one has a specific failure: the previous client's name, scope or pricing survives into the new document. It happens to everyone, it is embarrassing in proportion to the size of the deal, and the effort spent proofreading to prevent it is a real recurring tax on the sales team. Underneath that, version control by filename means nobody is quite certain which document the client is looking at, which turns a scope conversation into an archaeology exercise at exactly the wrong moment.
What we would build first
Assembly from approved blocks goes first, because it removes the copy-paste that causes the errors rather than trying to catch them afterwards. Pricing application and send-tracking are both useful and both assume a document that is already correct. Building the block library also forces a decision about what your standard scope and terms actually are, which most teams discover they have never agreed — and that discovery is worth as much as the automation.
It runs inside Google Docs, DocuSign, HubSpot, Slack, Gmail — the tools already in use.
How this one goes wrong
Assembled documents break at their cross-references and at their pricing. A block omitted because it did not apply leaves a document still referring to a section that no longer exists, and a pricing table populated from a variable that was not set produces a number that looks deliberate. Both read perfectly until someone relies on them. The guard is validation at assembly: any document with an unresolved cross-reference or an unpopulated pricing field stays in the queue rather than going out. These are mechanical checks that a person proofreading their fourth proposal of the day will miss and software never will.
The individual jobs inside this loop — what starts each one and where it has to hand back to a person — are covered under sales & CRM.
In most companies this work sits with sales representatives and document specialists. Each of those pages carries the wage arithmetic for that role, and says plainly where the numbers do not justify the spend.