Proposals built from approved sections
SalesSales engineers writing proposals in a git repo of Markdown templates
We keep proposal sections in a repo: scope, security, pricing terms. Each proposal took the agent about 25k tokens of reading templates and old proposals. Then legal changed the data-retention clause, and an agent copied the old wording from a proposal it had written in August.
How do I stop AI agents copying outdated clauses from old proposals into new ones?
Have the agent save each finished section with complete_task, and ArcRoom stores the git hashes of the template files it used. When a template like templates/security.md changes, every saved section built on it is marked stale and rewritten. This works because the templates are in git. Proposals kept only in Google Docs can't be checked this way.
Also asked as: Legal changed a clause and our AI still used the old wording. How do we prevent that? · How do I reuse approved proposal sections with an AI agent? · Can an AI agent tell when a proposal template has changed?
The agent saves each finished section with complete_task. ArcRoom stores the git hashes of the template files it used.
- Reused answer
- Saved answer
- Decision
- Freshness check
find_task → similar, but stale: templates/security.md changed since this was saved.
Step by step
- The agent saves each finished section with complete_task. ArcRoom stores the git hashes of the template files it used.
- The next proposal's agent gets sections back through find_task instead of re-reading every template.
- When legal edits templates/security.md, every saved section built on it is marked stale and gets rewritten.
- Pricing wording is saved once with arcroom decide, with the reason.
What the agent sees
find_task → similar, but stale: templates/security.md changed since this was saved.
Rewrite the data-retention paragraph from the current template.
Decision: 'annual prepay only for 3-year terms' (why: finance, Oct 12)Compared with today's tools
Template library in Google Docs
Reps copy the latest template and paste sections into the agent by hand.
- Setup
- 1–2 days to organise
- Ongoing
- Hunt for the right version, ~10 min per proposal
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
Mem0 and Zep can store the old clause as a fact but can't see that templates/security.md changed in git, so they'd keep handing out August's wording; ArcRoom marks it stale.
Where it stops
Freshness works because the templates are in git. Proposals kept only in Google Docs can't be checked this way.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.
More in sales
- Account research one rep did, reused by the nextB2B sales team doing account research in Claude Code
- RFP answers reused, but only while they're trueMid-size SaaS team answering security questionnaires and RFPs with Claude Code
- Call prep that builds on the last callAccount executive running a five-call enterprise deal