How to Use Claude for RFPs and Bid Management, Stage by Stage

Using Claude for RFPs means running each stage of a bid as a repeatable method in Claude, from the go/no-go before anyone writes to the contradiction check before submission, with the bid team making every decision.

A bid team sets it up as one Claude project per live tender, a skill for each repeated job, a connector to the approved answer library, and Cowork or Claude Code for work across a folder of files. Claude does the first pass and flags what the files cannot support; people decide, fill the gaps and sign off.

I built most of the skills this guide uses, and wrote it for bid and proposal managers who already work in Claude. Buyers writing or scoring RFPs with Claude are doing a different job. Plan names and features are as of November 2026.

Below: a map of bid jobs to Claude surfaces, the seven stages, where Claude stops, and the team setup.

How Do Bid Managers Use Claude for RFPs?

Bid managers who get real value from Claude use it for the first pass of every stage, in a fixed order, and keep each decision with a person. Three habits make that work:

• Decide before you write. In my walkthrough of a mock RFP in Claude (YouTube, October 7, 2026), the go/no-go came first: “I have not written a word. I’ve maybe read the RFP.”
• Save the method as a skill. A skill runs the same method the same way on every bid. As I put it in that video, “that skill is my complicated prompt that is saved in my organization.”
• Ask where each answer came from. Even with good skills, “occasionally you will get back, ‘Yeah, you’re absolutely right. I made that up.’” Hence the gap rule: name the file behind each answer, or write GAP.

Claude suits this method-led work. It reads a long tender pack, follows a saved method the same way each time, and produces working files such as a compliance matrix, a scorecard or a punch list.

Match Each Bid Job to a Claude Surface and Skill

Each bid job has a natural home in Claude: a project chat for decisions and summaries, Cowork or Claude Code for work across a folder of files, and connectors wherever the job needs the CRM or the approved answer library.

• Skills, projects or prompts: see what skills, projects and prompts are, and when to use each.
• What Claude can reach: stages 3 to 5 depend on Claude connectors, including the one to your approved answer library.
• Each tender as a folder: start with getting started with Claude Code as a bid manager.

The surfaces are my recommendation for bid work, with Anthropic’s features as of November 2026.

Run the Seven Bid Stages in Claude, in Order

A Claude bid runs in seven stages, in the order a good bid team already follows: Claude does the first pass, and a named person makes the call. The stages sit inside the wider process in the full RFP response guide.

1. Qualify the Bid Before Anyone Writes

Decide whether the bid is worth writing before anyone drafts.

• Skill and surface: the AI Go/No-Go Agent Skill, in a chat inside the tender’s project.
• What Claude does: scores seven weighted categories against the tender pack and your company profile, cites the section behind each finding, and returns Strong Go, Conditional Go, Executive Review or No-Go.
• What to check: answer every “REQUIRES USER INPUT” item before anyone trusts the score.
• Watch for: deal-breakers outside the main RFP, such as a mandatory standard named only in the buyer’s Q&A.

For how the skill is built and shared, see building the go/no-go skill yourself, file by file.

2. Shred the RFP Into a Compliance Matrix

Turn every file in the pack into one list of requirements, so nothing mandatory goes unanswered.

• Skill and surface: the Compliance Matrix Builder, in Cowork or Claude Code on the tender folder.
• What Claude does: quotes each requirement exactly, tags it mandatory, desirable or informational, adds the criteria, a submission checklist and key dates, and lists what it could not read.
• What to check: that “could not read” list first, then an owner on every row and a clarification question for anything ambiguous.
• Watch for: a text-only read. It can miss a security workbook embedded in the RFP’s Word file, so add that workbook, and each Q&A, as its own file.

The full method is in shredding an RFP with Claude.

3. Research the Buyer and the Competition

Learn the buyer from your own records first, then from public sources and the competition.

• Skills and surface: Internal Research and External Research, merged by the Completed Insight Brief skill, plus the Competitor Intelligence skill, with CRM, email and meeting connectors and web search.
• What Claude does: writes an insight brief with a source on every line and “Missing” where the records are silent, and a battlecard that flags sources older than 12 months.
• What to check: the seller and the bid manager close each Missing gap.
• Watch for: filling the brief from the RFP or the buyer’s website, which Internal Research rules out. Both Internal Research and Completed Insight Brief put government tender processes out of scope, so use them on private-sector deals.

I call competitor positioning “one of my favourite skills to run on RFPs we get” (LinkedIn, November 2, 2026).

4. Assign Owners and Prepare the SME Interviews

Give every requirement an owner, and spend expert time only where your records fall short.

• Skills and surface: the Assign Owners skill and the SME Interview Prep skill, with the answer library and file connectors.
• What Claude does: proposes an editor, an accuracy reviewer and a narrative reviewer for each requirement, and assigns nothing without approval. It then rates each question Covered, Refresh, Thin or Unknown and writes only the ones the records cannot answer.
• What to check: the bid manager approves the plan first.
• Watch for: interview questions the library already answers.

5. Draft From Approved Content and Flag the Gaps

Draft from approved content, and keep every gap visible instead of filled.

• Skill and surface: no dedicated skill. Use the tender’s project instructions, with the library reached through a connector.
• What Claude does: drafts each answer with the file behind it, and writes GAP where the files say nothing.
• What to check: approved wording stays word for word, SMEs fill each GAP, and reviewers approve every answer.
• Watch for: a prompt with no gap rule, which can let a capability your files never mention through as met.

To see one draft built end to end, follow a step-by-step walkthrough of one mock RFP in a Claude project.

6. Write the Executive Summary From the Finished Response

Write the summary last, so it claims only what the answers support.

• Skill and surface: the RFP Executive Summary Generator, in a chat inside the tender’s project.
• What Claude does: reads the completed response as its list of claims, mirrors the RFP’s criteria, writes six blocks of prose and ends with “Flags for SME validation”.
• What to check: SMEs check each flag, and the bid manager owns the page.
• Watch for: running it before the response is finished.

A guide to executive summary prompts in Claude is coming.

7. Check for Contradictions Before Submission

Catch the answers that disagree with each other before the buyer does.

• Skill and surface: the RFP Contradiction Checker, in Cowork or a project chat on the near-final response.
• What Claude does: compares every answer with every other and with approved content, product documents and the website, then returns a punch list that quotes both sides, sorted by severity. It does not rewrite the response.
• What to check: the SMEs who wrote the answers pick the right version, and the bid manager signs off.
• Watch for: skipping a rerun after late edits and the executive summary.

What Claude Caught and Missed on a Public Tender

We ran each stage once on State of Maine RFP# 202506081, a state agency software RFP posted on July 15, 2025, for a fictional bidder; nothing was submitted. Each step ran in a fresh Claude Code session (Opus 5.5) on November 6, 2026, and the go/no-go, matrix and summary steps re-ran on skills version 1.1 on November 9, 2026.

The misses were a workbook Claude never received, a prompt without a gap rule, and a caveat the summary dropped. So give Claude every file, keep the gap rule, and rerun the contradiction check after the summary.

Every figure is from one run, on bidder files and answer keys our team wrote, in Claude Code sessions that could run scripts, which a chat in the Claude app may not.

Where Claude Stops on Bid Work

Yes, a bid team can use Claude to write RFP responses. Whether a general assistant is enough on its own is answered in how far ChatGPT or Claude go against purpose-built RFP software. Plan for three limits:

• Additions nobody approved. Watch for a capability your files never mention marked as met, or new commitments in paragraphs Claude adds around approved wording. A gap rule and a quote-first instruction are the controls, and Claude’s strengths and weaknesses on bid work has the detail.
• Work across a team. As I said in the walkthrough video, “You’ll notice in Claude, collaboration is incredibly difficult.” Several writers, approvals and answers kept current across bids need more than one person’s setup, so weigh whether to build on general AI or buy RFP software.
• Other assistants. A side-by-side run of Claude, ChatGPT and Microsoft 365 Copilot, scored blind, is in progress.

How Should a Proposal Team Set Up Claude?

A proposal team gets consistent results from Claude across people and bids when it shares four things: the plan, the skills, one project per tender and one approved answer library.

Choose the plan first. Use Team or Enterprise before a buyer’s confidential documents go in: as of November 2026, both fall under Anthropic’s Commercial Terms and let owners control feedback, connectors and skills, while individual plans suit trying skills on public documents. For data rules by plan and what to send IT, see is Claude safe for confidential bid documents.

On those plans, Anthropic says “organization Owners can provision skills for all users” (What are skills?, read November 9, 2026), so everyone runs one agreed version of each method. Give each live tender one project, shared with the people working on that bid, and let every skill draft from one approved answer library instead of an export that goes stale.

AutoRFP.ai’s MCP connector gives a team’s Claude setup the answers the team has already approved, each returned with its source: read scopes cover lookups, and full scopes let Claude write to projects and content as the signed-in user, with approvals staying in AutoRFP.ai’s workflow.

Inside its own workspace, AutoRFP.ai drafts only from approved content, cites the source behind each answer and routes anything the content cannot support to a person, which is what AI proposal software built on approved, sourced answers means for a bid team that also works in Claude.

Start With Two Skills on Your Next Bid

Start with your next live tender: give it one project, add every file the buyer sent, and run the go/no-go and compliance matrix skills before anyone writes.

1. Install the first two skills from the skills library, with a Claude download for each stage. Each is free, and its download unlocks with an email address.
2. Upload each .skill file on claude.ai under Customize > Skills.
3. Add the rest one stage at a time, opening each stage’s guide as you reach it.