Prompt Chain: Turn Any RFP Into a Complete Proposal Draft in One Session

What This Builds

A multi-step prompt chain that takes a raw RFP as input and produces a complete first-draft proposal — with the right sections, in the right order, at the right word counts — in a single focused session. Instead of writing one section at a time across multiple days, you sit down for two hours and walk away with a complete draft.

Prerequisites

• Claude Pro subscription ($20/month) — the long context window is essential for holding an entire RFP and emerging draft simultaneously
• Your organization's boilerplate document (mission, programs, outcomes data)
• The RFP text in copyable format
• A clear sense of which program you're applying for and what amount you're requesting
• Time to build: 30 minutes to learn the chain; 2 hours per proposal run
• Cost: $20/month (Claude Pro)

The Concept

A prompt chain is a conversation where each step's output becomes the next step's input. Instead of asking Claude one big question and hoping for the best, you're guiding it through the same stages a professional grant writer uses: read the RFP → extract requirements → plan the proposal → draft each section. The output of each stage informs the next, and you review and refine at each checkpoint — maintaining quality control throughout.

Build It Step by Step

Part 1: Context Setup (5 minutes)

Start a new Claude conversation. Paste your organizational context first — this is the same setup as in the Level 3 guide:

I'm writing a grant proposal. First, here's our organizational context:
- Organization: [name]
- Mission: [paste]
- Program applying for funding: [name and 2-3 sentence description]
- Key outcomes: [paste your best numbers]
- Geographic focus: [location]
- Budget for this program: $[X]
- Requesting: $[X]

Do not draft anything yet. Confirm you have this context.

Claude will confirm. Now you're ready to start the chain.

Part 2: Step 1 — RFP Extraction (10 minutes)

Paste the full RFP text and ask Claude to extract the structure:

Here is the RFP we're responding to: [paste full RFP text]

Please create a structured proposal outline with:
1. A list of ALL required sections with their word/page limits
2. Any required attachments
3. Eligibility criteria we should confirm
4. Evaluation criteria the funder will use to score applications
5. Any specific language or themes the funder emphasizes

Do not draft any proposal content yet. Just give me the structure.

Checkpoint: Review the outline. Does it capture every required section? Correct any missed requirements before moving on.

Part 3: Step 2 — Proposal Planning (10 minutes)

Based on the RFP requirements and our organizational context, recommend:
1. The strongest angle for our proposal (which of our outcomes best align with their priorities?)
2. Any gaps between their requirements and our typical program description
3. The sequence for drafting sections (which sections inform others?)
4. Any red flags or requirements that might be challenging for our organization

Still no drafting — just the strategic plan.

Checkpoint: Does Claude's recommended angle match your judgment? Add any context it's missing: "You should also know that their program officer told us at the informational webinar that they're especially interested in X."

Part 4: Step 3 — Section-by-Section Drafting (60–90 minutes)

Now draft each section in the sequence Claude recommended. For each section:

Now draft the [section name] section. Requirements from the RFP: [paste the specific requirements for this section]. Word limit: [X].

Use our actual program data and outcomes from the context I provided. Match our organizational voice. Include specific statistics and do not invent any data — use [NEED: X] placeholders if you need information I haven't provided.

After each section, check:

• Does it meet the word limit?
• Does it use our actual data accurately?
• Does it directly answer what the funder asked?
• Does it connect to the funder's evaluation criteria?

If a section needs adjustment: "Reduce by 50 words while keeping all the statistics" or "The connection to their equity priority is weak — add 2-3 sentences specifically addressing their equity framework."

Part 5: Step 4 — Cross-Section Consistency Check (20 minutes)

After all sections are drafted:

Here is our complete proposal draft: [paste all sections in order]

Please review the full proposal for:
1. Consistency — do the same numbers appear consistently across sections?
2. Narrative coherence — does the overall story flow logically from problem to solution to evidence to capacity?
3. Funder alignment — does each section speak to the evaluation criteria from the RFP?
4. Missing elements — any required elements from the RFP that aren't addressed?
5. Redundancy — any significant overlap between sections that should be trimmed?

Return a list of specific issues to address, not a rewrite of the whole thing.

Address the flagged issues in targeted follow-up prompts.

Part 6: Step 5 — Final Polish (15 minutes)

Read the complete proposal one more time. Give me:
1. The three strongest sentences in the entire proposal (these are what we'd pull for a cover letter or executive summary)
2. The three weakest sentences that most need strengthening
3. One overall impression: if you were a program officer scoring this application, what would your instinct be and why?

Use this feedback for your final editing pass before submission.

Real Example: Full Chain in Action

Setup: You have an RFP from a state government agency for youth mental health services. The RFP is 28 pages. Required sections: executive summary, needs assessment, program design, evaluation plan, organizational capacity, and budget narrative. 60-page maximum application.

Input at Step 1: You paste the full 28-page RFP text.

Output at Step 1: Claude returns a clean outline:

• Executive Summary: 1 page
• Needs Assessment: 5 pages (key themes: youth mental health crisis data, racial disparities, evidence-based interventions)
• Program Design: 10 pages (must include: Theory of Change, staffing plan, service delivery model, partnerships)
• Evaluation Plan: 5 pages (must include: logic model, data collection instruments, analysis plan, external evaluator requirement)
• Organizational Capacity: 3 pages
• Budget Narrative: 5 pages
• Attachments: 3 letters of support, most recent audit, current 501(c)(3) determination letter

Input at Step 2: Confirm strategic angle.

Output at Step 2: "Your strongest angle is your outcome data on youth served — 89% showing improvement aligns directly with the RFP's stated priority of evidence-based outcomes. One gap: the RFP requires partnering with schools; your context doesn't mention school partnerships. Do you have those?"

You add: "Yes, we have MOUs with 3 high schools — here are the names."

Input at Steps 3–5: Section-by-section drafting with checkpoints.

Output: By the end of the 2-hour session, you have a complete 40-page first draft across all sections with consistent data, funder-aligned framing, and 5 specific improvement suggestions from Claude's review. Compare this to the typical 2–3 weeks of scattered drafting sessions this application would have taken.

What to Do When It Breaks

• Claude loses context mid-chain: In long sessions, Claude may lose track of your organizational context. If output starts feeling generic, re-paste your context: "Reminder of our org context: [paste]."
• One section is much weaker than others: Don't try to fix it in place — start a new message, paste the weak section, and ask: "This section needs to be rewritten. Here's what it's missing: [specific issue]. Rewrite it with: [specific requirements]."
• The chain produces a coherent but wrong strategic angle: At Step 2, override Claude's recommendation: "I want to emphasize X, not Y. Restate the strategic plan with that emphasis."
• Word count creep across sections: Add to each section prompt: "Strictly stay within [X] words. I will ask for a specific word count reduction if you exceed it."

Variations

• Simpler version: Run only Steps 1 and 3 (extract requirements, then draft sections directly). Skip the planning step if you already have a clear strategic angle.
• Extended version: After Step 5, paste your complete draft into a separate conversation and ask Claude to write the cover letter, a one-page executive summary suitable for the funder's opening meeting, and a pull-quote for your board report announcing the submission.
• Team version: Run Steps 1–2 yourself (strategy), then share the section-by-section prompts and Claude context with a junior colleague or volunteer writer who can complete Steps 3–4. You review and run Step 5.

What to Do Next

• This week: Run this chain on one upcoming proposal — even a smaller application — to learn the rhythm of the process
• This month: Refine your organizational context document based on what Claude was missing during each section's drafting
• Advanced: Combine this chain with the Custom Grant Assistant (Level 4 guide) so the chain runs inside a Project that already knows your organization — eliminating the context-setup step entirely

Advanced guide for nonprofit grant writer professionals. This technique works with any advanced AI model with long context windows — Claude Pro, ChatGPT Plus, or Gemini Advanced.