When should you use it?
- You answer RFPs or tenders
- Reviewers miss requirements
- Deadlines leave little review time
Not for: Writing the response from scratch; Pricing decisions
What do you need, and what do you get?
You need
- RFP document
- Draft response
You get
- Requirement matrix
- Gap list
- Suggested fixes
How does it work, step by step?
- Extract requirementsList every must, shall and required item with section numbers.
- Map the responsePoint each requirement to the response section that answers it.
- Rate coverageMark met, partial or missing, with reasons.
- Suggest fixesDraft wording only from your own facts.
- Final reviewThe proposal lead approves changes.
The prompt
Our own prompt, inspired by u/Motor-Draft8124 on r/replit and written to work in Claude, ChatGPT and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Extract every requirement from this RFP with section numbers: {rfp}. For each, find where this response addresses it: {response}. Return: requirement, RFP section, response section or NONE, coverage (MET / PARTIAL / MISSING), reason. Suggest fixes using only facts in {facts}.
Inspired by u/Motor-Draft8124 on r/replit: My first application build using Replit Agent - a Simple RFP Analysis Tool! 🚀. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Requirements in attachments are easy to miss; include them.
- Do not let it invent certifications or references.
Our take
Of the app's features, the gap analysis is the one worth copying, because missed requirements lose bids regardless of how well the rest is written. A requirement matrix with section references makes review fast and checkable. Extract every shall and must from the RFP into rows. Map each to a section of your response or mark it uncovered. Rate coverage honestly, including partial answers. Suggest fixes only after the gaps are listed. Keep a human final review for pricing, legal terms and claims you must be able to defend. Version the matrix with the RFP filename and date. Do not invent compliance you do not have. When the RFP is ambiguous, flag the question instead of guessing. Store client confidential RFPs in approved systems only. Run the gap-check again after major edits so new holes do not appear late. Share the uncovered list with subject-matter owners the same day, not the night before the deadline.
Where the time goes back: Review becomes a requirement checklist instead of a full reread.
FAQ
Does it write the proposal?
Can I trust 'met'?
Source and credit
Inspired by u/Motor-Draft8124 on r/replit. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- My first application build using Replit Agent - a Simple RFP Analysis Tool! 🚀
- Creator
- u/Motor-Draft8124 on r/replit
- Published on
- Original date
- Sep 12, 2024
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.