📁 Sales
Sales Proposal Draft from Discovery Call Notes (Pricing Only If Given)
Turn discovery call notes into a client-ready proposal - scope, timeline, and pricing only from what was actually said, never invented rates.
0Reviews
Prompt
Act as a sales engineer who drafts a proposal from discovery call notes. You turn the buyer's own words into scope, timeline, and success criteria. You never invent pricing, case studies, ROI numbers, or commitments that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Discovery call notes, pasted in full: [Notes] - Scope bullets agreed so far: [Scope] - Pricing only if it was stated, else NONE: [Pricing] - Timeline or dates the buyer mentioned: [Timeline] - Case studies or references you may cite, else NONE: [Proof] - Decision makers named: [People] - Language: [Lang] - Output format: [Format] Generate: 1. Notes ledger: date, attendees if given, what was decided vs open. Forbidden: invented metrics, invented ROI. 2. Executive summary: 3-4 sentences in the buyer's vocabulary from Notes - their problem, their words, not your pitch. 3. Problem statement: quoted pain points with counts of how often raised; no problems not in Notes. 4. Proposed scope: in-scope and out-of-scope lists derived only from Scope and Notes; anything ambiguous goes to "To confirm". 5. Pricing: only numbers present in Pricing; if NONE, write "Investment: to be confirmed in follow-up - NOT IN INPUTS". 6. Timeline: from dates in Timeline/Notes only; unscheduled items become "date not set". 7. Risks and assumptions: buyer-stated constraints (budget caps, freeze dates, competitor mentioned) as bullets. 8. Next steps: owners from People, each step a real action from Notes; format as Format. Constraints: - Every claim traces to a quoted line in Notes or Scope. Quote or drop. - No invented pricing, no invented case studies, no fabricated metrics or logos. - Mark NOT IN INPUTS wherever Inputs are silent. End with a gaps list of five bullets the user still owes you.
Instructions
Paste your discovery call notes, agreed scope bullets, and any pricing the prospect stated. Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Notes: Call 2026-10-14 with Priya (Head of Ops) and Tom (IT lead). Problem: "we close the books in 11 days and half of it is manual re-keying from three systems." Priya: "if it is not under 30k a year, I cannot sign off." Tom wants SSO and asked about our Salesforce sync. Freeze: no new vendors between Nov 15 and Jan 5. Competitor evaluated: Flowline, "their reporting was weak." Scope: onboarding of 2 connectors (Salesforce, NetSuite), monthly close dashboard, 3 training sessions. Pricing: NONE (budget cap 30k/year stated) Timeline: wants go-live "before the Dec close" Proof: NONE People: Priya (signs), Tom (technical), Dana (finance, joins next call) Lang: English Format: summary + problem + scope + pricing + timeline + risks + next steps
Example Output
1. Notes ledger. Call 2026-10-14. Attendees: Priya (Head of Ops), Tom (IT lead). Decided: connector list, dashboard, 3 training sessions. Open: pricing, SSO depth, Salesforce sync details, Dana's finance sign-off. Forbidden: invented metrics - none used. 2. Executive summary. Ops closes the books in 11 days, roughly half of it spent re-keying data across three systems. The team has scoped two connectors (Salesforce, NetSuite), a monthly close dashboard, and three training sessions, with a go-live targeted before the December close. A budget cap of 30k per year has been stated. 3. Problem statement. - "we close the books in 11 days and half of it is manual re-keying from three systems" (raised once, Priya). - Weak competitor reporting: "their reporting was weak" (Flowline, raised once). No other pain points stated in Notes. 4. Proposed scope. In-scope: Salesforce connector onboarding, NetSuite connector onboarding, monthly close dashboard, 3 training sessions. Out-of-scope: NOT IN INPUTS (nothing excluded yet - confirm with buyer). To confirm: SSO requirement depth, Salesforce sync direction, whether Dana needs a finance-specific view. 5. Pricing. Investment: to be confirmed in follow-up - NOT IN INPUTS. Buyer-stated ceiling: "if it is not under 30k a year, I cannot sign off" - treat as an annual cap of 30k, not a quote. 6. Timeline. Go-live: "before the Dec close" - target date not set. Freeze window: Nov 15 - Jan 5, no new vendors (Notes), so signature and start must happen before Nov 15. 7. Risks and assumptions. - Vendor freeze Nov 15 - Jan 5: signing after Nov 14 delays start to January. - Budget cap 30k/year is a ceiling, not approval. - Competitor Flowline already evaluated; reporting was their objection. - SSO + Salesforce sync details unverified (Tom's questions, no answers in Notes). 8. Next steps. 1. Priya - approve pricing within 30k cap (send proposal by 2026-10-17). 2. Tom - share SSO and Salesforce sync requirements in writing. 3. Dana - join next call for finance sign-off (date not set). 4. Us - confirm connector scope before Nov 15 freeze. Gaps the user still owes you: our actual price list, SSO documentation, Salesforce sync capability, Dana's availability, contract length preferences.