Create a [type of document — e.g., tailored sales proposal] for [audience — e.g., the buying committee at a 300-person fintech company, including the VP Sales (economic buyer), Head of RevOps (champion), and CFO (final approver)]. Purpose: [what this document should accomplish — e.g., justify a $180K annual investment by connecting our platform capabilities to their specific operational pain points and showing projected ROI].

Include these sections:
1. Executive Summary (3-5 sentences — the business case, not the product pitch)
2. [Section — e.g., Current State — the prospect's specific challenges based on what we learned in discovery and demo]
3. [Section — e.g., Proposed Solution — how our platform addresses each challenge, with emphasis on the features they responded to most]
4. [Section — e.g., ROI Projection — projected time savings, revenue impact, and payback period based on the data I'll provide below]
5. Implementation & Timeline (specific milestones, not vague phases)
6. Recommended Next Steps (specific actions with owners and dates)

Constraints:
- Total length: [target — e.g., 2,000 words]
- Tone: [e.g., strategic and confident — this is a business case, not a brochure]
- [Any specific inclusions — e.g., reference the pilot results I'll paste below]
- [Any exclusions — e.g., do not include standard pricing — that's a separate conversation with procurement]
- [Stakeholder framing — e.g., the CFO cares about payback period and risk; the VP Sales cares about rep productivity; the Head of RevOps cares about integration depth and migration timeline]

Context: [2-3 sentences — e.g., "They completed a successful 30-day pilot with their East Coast team. Pipeline visibility improved 40% during the pilot. The VP Sales said 'this is the first time I've trusted a forecast' in their pilot debrief. Main blocker: the CFO wants to see hard ROI before approving a company-wide rollout."]