Skip to content
Claude for Operators

Proposals & Pitches

Last verified: 13 February 2026 | Applies to: All plans (Cowork recommended for multi-document proposals)

In 30 seconds

Section titled “In 30 seconds”

Writing proposals is high-stakes, high-effort work — and most operators either spend too long on them or rush and send something generic. Claude drafts structured proposals, pitch deck outlines with speaker notes, RFP responses, and partnership pitches that you refine with your specific knowledge and pricing. The structure and language come fast; you add the substance that wins the deal.

Step by step

Section titled “Step by step”

Client proposal for a consulting engagement

Section titled “Client proposal for a consulting engagement”
Draft a proposal for a consulting engagement with [Client Name]. We're [Your Company], a 12-person operations consulting firm specialising in process improvement for mid-market ecommerce companies. The engagement: a 10-week operational efficiency review covering their fulfilment, customer support, and returns processes. They're doing about $15M in annual revenue with a team of 45. The problem they described: fulfilment errors running at 8% (industry standard is 2-3%), customer support response times averaging 18 hours, and returns processing taking 10+ business days. Our proposed fee: $200,000 for the full engagement, structured as $80,000 discovery phase (4 weeks) + $120,000 implementation support (6 weeks). Include: executive summary, scope of work, methodology, timeline, team, pricing, and terms. Tone: confident, specific, outcome-focused.

Claude produces:

  • Executive summary — the client’s problem, your solution, and the expected outcome (lead with their ROI, not your credentials)
  • Scope of work — specific deliverables per phase, clearly bounded
  • Methodology — how you’ll work, not just what you’ll do
  • Timeline — week-by-week with milestones and decision points
  • Team — who’s doing the work and their relevant experience
  • Investment — pricing with clear payment terms
  • Terms and conditions — standard engagement terms
  • Next steps — exactly what happens if they say yes

Pitch deck outline with speaker notes

Section titled “Pitch deck outline with speaker notes”
Create an outline for a 12-slide pitch deck. We're [Company Name], raising a $3M seed round for an AI-powered inventory management platform for restaurants. Key stats: $180K ARR, 35 restaurant clients, 94% retention rate, average client saves $2,800/month on food waste. Founded 14 months ago, team of 5 (2 technical co-founders + 3 in sales/ops). Market size: $12B restaurant technology market. Our ask: $3M at a $15M pre-money valuation. For each slide, give me: the slide title, 3-4 bullet points of content, and speaker notes — what I should actually say when this slide is up. Keep the slides sparse; put the detail in the speaker notes.

Claude generates:

  • Slide-by-slide outline — title, key content, and speaker notes for each
  • Narrative arc — problem, solution, traction, market, team, ask
  • Data callouts — which numbers to highlight visually
  • Anticipated questions — investor questions each slide is likely to prompt

Note: Claude produces the outline and talking points. For the actual designed deck, use the Document Creation workflow to generate a PowerPoint, or use the outline as a brief for your designer.

Responding to a 20-question RFP

Section titled “Responding to a 20-question RFP”

Upload the RFP document in Cowork, then:

I've uploaded an RFP from [Organisation Name]. They're looking for a [type of service/product]. Read the full document and respond to each question. For context about us: we're [Company Name], we do [what you do], our key differentiators are [list 3-4], our pricing model is [describe], and our relevant experience includes [list 2-3 similar clients/projects]. Answer each question directly — lead with the answer, then provide supporting detail. Where a question asks for specifics I haven't provided, flag it with [NEEDS INPUT] so I can fill in the gaps. Keep responses concise — RFP reviewers read dozens of these.

Claude works through each question, producing:

  • Direct answers — leading with the response, not preamble
  • Supporting evidence — client examples, metrics, differentiators
  • Flagged gaps — anything that needs your specific input, clearly marked
  • Compliance matrix — a summary table showing which requirements you meet, partially meet, or don’t meet

Tip: After the first draft, ask Claude: “Review the full response. Is it consistent in tone? Are there any contradictions between answers? Where is it weakest?”

Partnership proposal email

Section titled “Partnership proposal email”
Draft a partnership proposal email to [Partner Company], a CRM platform with 5,000+ SMB clients. We want to propose an integration partnership: we build a native integration between our inventory platform and their CRM, they promote it to their client base, we offer their clients a 20% discount for the first year. The mutual benefit: their clients get a more complete solution, we get distribution. The contact is [Name], VP of Partnerships. We've never spoken — this is a cold outreach. Keep it under 250 words. Lead with what's in it for them, not what's in it for us.

How operators actually use it

Section titled “How operators actually use it”
Section titled “Related”

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.