Best for
- AEs who need to turn discovery into proposals faster
- Founder-led sellers creating custom proposals without a sales ops team
- Sales engineers supporting technical proposal creation
Convert discovery call notes into a buyer-specific proposal outline with pain points, scope, ROI assumptions, proof points, and next-step language.
A buyer-specific proposal draft with executive summary, scoped problem, ROI assumptions, proof points, and open questions for approval.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
7 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Most proposals are either too generic or take too long to customize. This workflow uses the buyer's own discovery notes to build the proposal narrative, then separates confirmed facts from assumptions. The result is a faster first draft that still needs human review, but starts much closer to what the buyer actually cares about.
Expected results
Drafting time saved
3-6 hours per proposal
The workflow replaces blank-page writing with a structured source packet, outline, AI-assisted draft, and reusable review checklist.
Buyer relevance
Discovery-backed proposal sections
Every major section is mapped to buyer evidence, scope rationale, ROI assumptions, or proof points rather than generic template language.
Review risk reduction
Assumptions visible before send
Separating facts, assumptions, open questions, and approval items reduces the chance of sending unsupported claims or accidental delivery commitments.
Proposal system learning
Reusable feedback loop
Buyer feedback is captured back into CRM, templates, proof libraries, and discovery questions so each proposal improves the next one.
Step-by-step workflow
The first 2 steps are open. Confirm your email to unlock all remaining steps, prompts, and implementation tips for free.
25-35 min
25-35 min
Create one working folder or Google Doc for the deal before drafting begins. Pull the Sybill or Gong call summary, transcript snippets, HubSpot deal fields, buyer emails, pricing guidance, implementation constraints, proposal template, and approved proof points. Add a short source index that labels what came from the buyer, what came from CRM, what came from internal teams, and what is still missing. QA check: do not proceed until pricing, legal terms, timeline commitments, and delivery assumptions are either approved or clearly marked as open. For each input, keep the source, collection date, owner, and confidence level so later AI summaries can be checked instead of trusted blindly.
A proposal source packet with buyer evidence, CRM context, approved materials, and open gaps.
Most bad AI proposals start with incomplete inputs. The model sounds confident even when the source packet is weak, so the packet quality is the real control point.
15-20 min
15-20 min
Use Claude to turn the source packet into a facts, assumptions, and open questions table. Require evidence for every confirmed fact, such as transcript language, CRM notes, buyer emails, or internal pricing guidance. Mark reasonable assumptions separately from unsupported assumptions so the proposal does not accidentally present guesses as truth. QA check: anything tied to price, timeline, integration effort, legal terms, or customer outcomes must be validated before it appears in buyer-facing copy. Give the AI concrete source material, required fields, and a review checklist so the output can be judged by a human operator. Use the prompt template in this step only after pasting the relevant source material; require the answer to return assumptions, missing information, and a clear next action.
A fact, assumption, and open-question table for safe proposal drafting.
This is the step that keeps AI proposal writing from becoming dangerous. Buyers notice when a proposal confidently restates something they never said.
Confirm your email to read the remaining 10 steps, prompts, and implementation tips. One sign-in unlocks the whole library.
By joining, you agree to the Terms and Privacy Policy.
Already have an account? Sign inAnalyze this proposal source packet and separate confirmed facts from assumptions.
Source packet:
{{proposal_source_packet}}
Output a table with:
1. Confirmed fact
2. Evidence source
3. Reasonable assumption
4. Unsupported assumption
5. Open question
6. Who should validate it
7. Whether it can appear in buyer-facing copy
Rules:
- Do not infer pricing, timelines, legal terms, implementation effort, or outcomes
- Mark uncertain items as open questions
- Quote buyer language only when it is present in the source material.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A system for generating tailored one-pagers for active deals based on buyer pain, industry context, deal stage, and competitive situation.
A procurement objection battlecard library with talk tracks, proof assets, risk responses, and rep guidance for late-stage deals.
Create custom first-call or follow-up sales decks for target accounts using enriched company data and AI-generated slide narratives.