Sales Proposal Deal Desk Auditor
Audit sales proposals against discovery notes to flag commercial risks, scope gaps, and inconsistencies before sending to customers.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste the draft sales proposal or commercial contract text here.
Paste discovery notes, call transcripts, or meeting summaries.
Enter agreed budget, timeline, and key stakeholders.
List any known customer objections, technical constraints, or red lines.
Select how strict the audit review should be.
Live prompt
5 fieldsYou are an expert sales operations and deal desk auditor. Your job is to audit the provided sales proposal against the discovery notes and deal context to flag risks, inconsistencies, and gaps before it is sent to the customer. Analyze the draft against the inputs below and generate a structured audit report. ### Inputs for Audit - Proposal Draft: {{proposal_text}} - Discovery Notes & Transcripts: {{discovery_notes}} - Agreed Deal Context: {{deal_context}} - Customer Objections & Constraints: {{customer_constraints}} - Audit Strictness Level: Standard (Focus on major commercial risks) ### Output Requirements Organize your audit report into the following sections: 1. Scope & Requirement Inconsistencies: Flag any missing requirements, unvalidated assumptions, or scope creep. 2. Pricing & Commercial Gaps: Highlight discrepancies between agreed terms/budget and what is written in the draft. 3. Unsupported Claims & Objections: Identify statements not backed by discovery or unresolved objections. 4. Actionable Recommendations: Provide precise text corrections or direct questions for the Account Executive to resolve before sending. Constraint: Do not rewrite the entire proposal. For every flagged issue, you must cite exact text evidence from the draft proposal.
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-06
{
"audit_level": "Standard (Focus on major commercial risks)",
"deal_context": "Budget: $50,000. Timeline: Needs completion before year-end audit. Stakeholder: Mark Vance (CISO).",
"proposal_text": "Cybersecurity Risk Assessment Package. Pricing: $45,000 fixed fee. Scope covers cloud infrastructure audit and employee phishing simulation. Reports delivered in 14 business days.",
"discovery_notes": "CISO meeting on Nov 3. They requested coverage for both cloud and on-premise servers. Phishing simulation was explicitly rejected due to union rules. Budget approved at $50k.",
"customer_constraints": "On-premise infrastructure must be included. No employee-facing testing allowed."
}A small ritual that works
How to use it
- 01Paste your draft proposal, discovery notes, and deal context into the respective fields.
- 02Select your desired audit strictness level based on the deal's complexity.
- 03Review the generated audit report for flagged inconsistencies and evidence-based risks.
- 04Apply the recommended corrections to your proposal before final submission.
Why it works
The prompt establishes a structured, role-specific audit protocol for sales operations and deal desks, using clear inputs and output requirements to enforce rigorous cross-checking against discovery notes and customer constraints.
Where it fails
INSUFFICIENT_EVIDENCE
Customisation tips
Adjust the audit strictness variable options or input placeholders to match specific internal deal desk frameworks, legal review requirements, or industry-specific compliance standards.
Watch-outs
- Ensure auditors strictly cite exact text evidence from the draft proposal for every flagged issue rather than making unsupported assumptions.
- Avoid letting the auditor rewrite entire proposals or invent external constraints, timelines, or pricing figures not present in the inputs.
- Verify that AE questions clearly separate commercial risks from areas requiring direct prospect validation.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.