Sales Proposal Executive Summary
Turn proposal details into a concise, decision-ready five-section executive summary.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste the proposal text or document content and include its approximate original length.
State the primary business problem, impact, and urgency identified for the customer.
Summarize the proposed product, service, scope, and relevant deliverables.
Provide pricing, fees, payment terms, assumptions, and exclusions stated in the proposal.
Include milestones, target dates, dependencies, owners, and the immediate next action.
Live prompt
5 fieldsCreate a concise executive summary of the sales proposal using only the information provided below. Produce approximately 350–450 words, suitable for a one-page equivalent and usable after one light edit. Do not ask follow-up questions, add hype, use politeness padding, or invent facts, savings, outcomes, testimonials, or commitments. If a required detail is unavailable, write "Not specified in the proposal."\n\nUse exactly these five labeled sections in this order, with no additional sections:\n\nProblem\nState the customer's business problem, impact, and urgency based on the proposal.\n\nSolution\nExplain what is being proposed and how it addresses the problem.\n\nInvestment\nSummarize the pricing, fees, commercial terms, and any relevant assumptions.\n\nTimeline\nSummarize the implementation or delivery schedule, milestones, and dependencies.\n\nNext step\nState the agreed or proposed immediate action, owner if specified, and timing if specified.\n\nSource proposal and context:\n{{proposal_context}}\n\nKey customer problem:\n{{customer_problem}}\n\nProposed solution details:\n{{proposed_solution}}\n\nInvestment and pricing information:\n{{investment_pricing}}\n\nProject timeline and agreed next steps:\n{{timeline_next_steps}}\n\nUse a professional, direct tone. Preserve important numbers, dates, conditions, and distinctions. Keep each section focused and do not repeat the same information across sections.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"customer_problem": "The current nurse call system is 14 years old, has frequent hardware failures, and provides limited escalation visibility. Facilities staff spend significant time troubleshooting, while clinical leadership lacks reliable response-time reporting.",
"proposal_context": "Proposal for Meridian Medical Center, a 300-bed regional hospital. Approximate original length: 11 pages. The proposal covers replacement of the nurse call system across three buildings, including installation, training, and a five-year maintenance plan.",
"proposed_solution": "Supply and install a connected nurse call platform with room terminals, mobile alerts, escalation rules, reporting dashboards, battery backup, staff training, and integration with the hospital's existing patient monitoring system.",
"investment_pricing": "Equipment and installation: $640,000. Software license: $72,000 annually. Five-year maintenance: $38,000 annually after the first year. Payment is 40% at contract signing, 40% at equipment delivery, and 20% after commissioning.",
"timeline_next_steps": "The project will be delivered in three building phases over 16 weeks, with no planned outage during patient care hours. Meridian's Chief Nursing Officer and Facilities Director will attend a technical validation workshop on 6 September. The proposed next step is approval to proceed to a final site survey."
}A small ritual that works
How to use it
- 01Paste the full proposal content and approximate original length into Proposal context.
- 02Enter the key customer problem and proposed solution details.
- 03Add investment and pricing information.
- 04Add the timeline and agreed next steps, then run the prompt.
Why it works
The prompt gives the summarization task a clear operating frame: a defined audience, a target length, five required sections, a fixed order, and explicit rules against invention and unnecessary padding. Each section has a focused job, which separates business need, proposed response, commercial details, delivery timing, and immediate action. The five dedicated input fields also direct attention to the information most important in a sales proposal, while the full proposal field provides broader context. The fallback wording for unavailable details creates a consistent way to represent gaps without filling them with assumptions. Instructions to preserve numbers, dates, conditions, and distinctions help protect commercially important details during compression.
Where it fails
The structure is less suitable when the proposal needs a different narrative shape, such as a detailed risk analysis, competitive comparison, technical architecture, legal review, or multi-stakeholder decision record. Its fixed five-section format leaves limited room for information that does not fit naturally into those categories. The approximate 350–450-word range can also constrain proposals with substantial commercial conditions, dependencies, or exceptions. Because the prompt prohibits follow-up questions and requires a fixed fallback phrase, unresolved ambiguity is recorded rather than explored.
Customisation tips
Adjust the section labels and instructions to match the decision the summary must support. For a procurement audience, consider adding evaluation criteria, risks, or contract considerations; for an executive audience, prioritize strategic rationale, financial exposure, and decisions required. Change the target length when proposals vary substantially in complexity. If the summary will be reused in a specific document or system, define formatting requirements such as heading syntax, bullet limits, or maximum length per section. Keep the source fields aligned with the sections so users know where to place assumptions, exclusions, dependencies, and ownership details. Replace the fallback wording only if the destination document uses a different approved phrase.
Watch-outs
- The prompt asks for both the full proposal and structured supporting fields, so users should keep those inputs consistent and clearly distinguish confirmed information from context.
- The instruction to use only provided information limits interpretation; implied benefits, expected savings, and likely outcomes should not be presented as stated facts.
- Commercial details can be easy to compress incorrectly, especially when pricing depends on timing, assumptions, support periods, exclusions, or payment conditions.
- The fixed section order may cause related information to be separated, so dependencies and conditions should be stated explicitly in the input fields.
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.
Related prompts
Want to make AI useful across your team? Explore Atul's training.