How to Respond to an RFP: A Freelancer’s Step-by-Step Guide

To respond to an RFP, decide first whether the bid is worth your time. Then read the document and its scoring criteria closely. Map every requirement to a section of your answer, write for the buyer’s goals instead of your own résumé, price against the stated formula, and submit exactly as instructed. Most of the work happens before you write a word. The rest is discipline: answering the question that was asked, in the order it was asked.

This guide is written for independent project managers and consultants, who often answer RFPs alone, without a proposal team or a content library. The steps below still hold up in that situation. They scale down to one person and a long weekend.

TL;DR

• Score every RFP with a go/no-go checklist before you write anything. Pursuing every request is a fast route to burnout and a low win rate.
• Build a compliance matrix that maps each “shall,” “must” and “will” to a section of your response. A single missed mandatory item can disqualify you.
• Write to the evaluation criteria, using the buyer’s section numbers and wording. Evaluators score against a rubric, not against how good your prose sounds.
• Use the question-and-answer window. It is the cheapest way to clarify ambiguity and show you take the work seriously.
• If you decline, say so briefly and on time. A short, polite reply protects the relationship.

Table of Contents

• What an RFP is asking of you
• Step 1: Decide whether to respond
• Step 2: Read everything, twice
• Step 3: Use the question period
• Step 4: Build a compliance matrix
• Step 5: Write to the scoring
• Step 6: Price it the way it will be scored
• Step 7: Review like the buyer will
• Step 8: Submit, follow up, and debrief
• Our perspective: bid less, bid better
• Where to find RFPs worth answering
• Build your pipeline with The Freelance PM Club
• Common mistakes to avoid
• FAQ
• Sources

What an RFP is asking of you

A request for proposal is a formal way for a buyer to compare vendors. Organizations invited to respond are called vendors or suppliers, and they prepare a proposal that answers the buyer’s questions. For a freelancer, the buyer might be a mid-size company hiring a delivery lead, a university, a city agency, or a larger consultancy filling a seat on a client engagement.

The format matters because it changes how you are judged. In a casual sales conversation, charm and referrals carry a lot of weight. In an RFP, the buyer usually commits in advance to criteria and a scoring method. The University of Utah’s purchasing office, in its RFP instructions for proposers, describes evaluators rating proposals against pre-set criteria, and notes that criteria not stated in the RFP cannot be used to reward or penalize a vendor.

That has a practical consequence. You are not trying to impress. You are trying to make it easy for a scorer, often working through a stack of proposals, to give you full marks line by line.

Step 1: Decide whether to respond

The most common mistake is skipping the go/no-go decision. According to 101 Agencies, pursuing every RFP leads to burnout and weak win rates, and the firms that do well assess strategic fit, win probability and economic viability up front.

The same source notes that vendors who have already engaged the buyer or helped shape the requirements see win rates above 60%, while cold responses to unknown organizations often fall below 10%. Treat those as practitioners’ rules of thumb, not guarantees. The direction is clear, though: if you have never spoken to this buyer, the odds are long, and some RFPs exist mainly to justify choosing an incumbent.

A simple go/no-go scorecard

Build a weighted scorecard and fill it in within a day of receiving the RFP. A Rework template uses criteria such as strategic fit and win probability, each weighted and scored from 1 to 5. Many practitioners set a threshold of 70 out of 100, according to 101 Agencies, before committing real time.

Here is a version sized for a solo consultant:

Score honestly. If you land under your threshold, decline. If you are in the gray zone, consider a lean response: shorter, more targeted, built from material you already have.

Count the cost of bidding

Bids cost real money, even when the money is your own unbilled time. Research on the UK agency market, reported by Wadds Inc. on the PRCA pitch framework, puts the average investment per pitch between £7,000 and £20,000 for agencies. That is a different scale from a one-person practice, but the logic transfers: multiply your hours by your normal rate and ask whether the expected win is worth it. If you need help thinking through what your work should cost in the first place, this walkthrough on a service pricing strategy covers the groundwork.

How to decline

If you pass, tell the buyer. A one-sentence reply is enough, and no long explanation is needed. Something like: “Thank you for the invitation to respond to the [project name] RFP. We have decided not to submit a proposal on this occasion, and we would welcome the chance to be considered for future work.” You stay on the buyer’s radar and you avoid the awkward silence.

Step 2: Read everything, twice

Read the full document before you open a template. On the first pass, look for the shape of the engagement: scope, timeline, budget signals, and who the buyer is. On the second pass, extract rules.

The GSA’s guidance on responding to a solicitation tells bidders to read the solicitation thoroughly to understand both the requirements and the factors used to evaluate the proposal, and to sign up for notice of any amendments. That advice applies well beyond federal work. Private buyers amend RFPs too, and a changed deadline or revised scope you did not see is an avoidable way to lose.

On the second pass, highlight:

• Deadlines: question deadline, submission deadline, any presentation or interview dates.
• Format rules: page limits, file type, font, how to name files, whether to submit by portal or email.
• Mandatory requirements: anything phrased as “shall,” “must” or “will.”
• Evaluation criteria and weights: the section that tells you how points are awarded.
• Pricing instructions: whether you must use the buyer’s form.
• Required attachments: references, insurance certificates, sample work, signed forms.

Step 3: Use the question period

Most RFPs allow clarification questions, and many bidders ignore them. According to Loopio’s RFP process checklist, strategic participants use this window to show expertise, clarify ambiguities and signal seriousness, which often builds the relationship that shapes the outcome.

Good questions are specific and show you have read the document:

1. “Section 3.2 mentions a phased rollout. Is the budget range for all phases, or only phase one?”
2. “Who will be the day-to-day contact on the buyer side, and how much of their time is available?”
3. “Is there an incumbent vendor, and will any work transfer from them?”

Check whether questions are shared with all bidders. In many formal processes, answers are published to everyone, so do not ask anything that reveals your pricing or strategy.

Step 4: Build a compliance matrix

This is the single most useful tool in a response, and a spreadsheet is all it takes. According to 101 Agencies, successful firms use a compliance matrix that maps every “shall,” “must” and “will” in the RFP to a specific response section, so no requirement is missed before submission. The same source warns that missing even one mandatory requirement can mean automatic disqualification, however strong the solution.

Set up four columns:

If you also need an end-to-end task list, a response checklist from CheckFlow breaks the work into phases from intake to debrief. Whatever tool you use, the point is the same: nothing is assumed, everything is tracked.

Step 5: Write to the scoring

Evaluators use structured rubrics. Per the Utah purchasing document, scores are often given on a 0 to 5 scale, where 0 is a failure or non-response and 5 is a superior response that exceeds requirements. Scores are then weighted: for example, technical approach might be 60% of the points and cost the remaining 40%.

What follows is useful for anyone writing a response.

Mirror the structure

The same document warns that a response mapped directly to the RFP’s section numbers and requirements can outscore one that is merely well written. Use the buyer’s headings and numbering, in the buyer’s order. Answer the question first, then support it. If the question is “Do you have experience managing projects of this size?”, start with “Yes,” then give the project, the size, the outcome and a reference.

Be customer-focused, not feature-focused

According to PandaDoc’s guidance on responding to an RFP, winning responses show a clear roadmap and an understanding of the client’s goals, and they state benefits instead of just listing capabilities. A sentence like “We reduce time to value by 50%” tells a buyer more than “We have 12 years of experience.” Only claim numbers you can back with a reference or a documented result.

For a freelancer, a practical pattern for each major answer is:

1. Restate the buyer’s goal in a sentence, in their words.
2. Describe your approach, in steps, with named deliverables.
3. Show proof: a similar project, a result, a client who can confirm it.
4. Name the risk you see and how you would manage it. Project managers who do this stand out, because it is the actual job.

If you want to sharpen how proof shows up in your writing, the idea of building proof into your messaging applies as much to a proposal as to a web page.

Handle the cover letter

Many RFPs ask for a cover letter or executive summary. Keep it to one page. Open with the buyer’s problem in one or two sentences, state your recommended approach, name the person who will lead the work, and point to the sections where the evaluation criteria are answered. Do not recycle a generic pitch. Close with a clear contact and a statement that your proposal is valid for a stated period, if the RFP asks for one.

Step 6: Price it the way it will be scored

Price is rarely the only factor, but it is often scored by formula. The Utah document gives a standard example: lowest price divided by proposed price, multiplied by the available points. Under a formula like that, a technically stronger proposal at a higher price can still win, because the price points are only a portion of the total.

This changes how you think about pricing a bid:

• Do not undercut simply to win. If cost is 40% of the score, you gain only part of those points by being cheaper, and you may lose the margin you need to do the job well.
• Follow the buyer’s pricing form exactly. Add assumptions in a separate note if the form allows it.
• State what is included and what is not. Unclear scope is where freelance engagements go wrong.
• Consider offering tiered options if the RFP permits alternatives. Our guide on negotiating project management fees with three packages shows one way to do it, and value-based pricing for freelance PMs covers tying fees to outcomes.

Check contract-level requirements too. If the buyer expects coverage at a certain level, see our piece on professional indemnity insurance for $1M contracts before you commit.

Step 7: Review like the buyer will

Large firms run a red team review, where an internal group scores the draft against the evaluation criteria to find gaps, and a gold team review, where executives do a final quality and risk pass, according to 101 Agencies. You probably cannot staff either. You can imitate them:

• Red pass: put your draft aside for a day, then score it yourself against the rubric, line by line. Better still, ask a trusted peer to do it cold.
• Gold pass: read the final document as the buyer’s executive sponsor would. Is the recommendation clear? Is the price plausible? Is anything promised that you cannot deliver?
• Compliance pass: walk the matrix one last time. Every row should read “done.”
• Mechanical pass: file names, page counts, signatures, attachments, portal upload test.

Upload early. Portals fail, and a deadline is a deadline.

Step 8: Submit, follow up, and debrief

Submit exactly as instructed, and confirm receipt if the buyer does not send an automatic one. Short acknowledgment emails are fine. Then respect the process: do not lobby the evaluators if the RFP bars contact during evaluation.

If you win, move quickly to kickoff. If you lose, request a debrief. Ask which criteria you scored lowest on and how your price compared. Add what you learn to your own library of reusable answers: bios, case studies, references, insurance language and your standard delivery approach. A good library cuts the next response from days to hours, and that is how a solo consultant bids without burning out. Our post on project retrospectives for consultants shows how to turn finished work into proof for the next bid.

Our perspective: bid less, bid better

We work with independent project managers and consultants, and the pattern we see is consistent. People new to RFPs treat each one as a lottery ticket and write long, heavy responses to buyers they have never met. People who win steadily do something different: they build relationships first, choose their bids, and answer in the buyer’s language.

That is why we point freelancers toward visible, specific positioning rather than a general “I do project management” pitch. A productized offer, a clear niche and a handful of strong references make every response faster to write and easier to score. If you want a starting point, look at how productized consulting services can give you a repeatable scope, or how agency work for experienced freelance PMs often begins with a conversation long before any formal request appears.

Our advice is plain. Treat an RFP as the last step of a relationship, not the first. Say no to bids you would not want to win. And write every answer as if a stranger with a scoring sheet and a deadline will read it, because one will.

— Ashanti

Where to find RFPs worth answering

The best RFPs usually reach you because someone already knows your work. Still, a steady pipeline helps. Public buyers post opportunities openly, and the GSA explains in its guidance on responding to solicitations that a response may also be called an offer, proposal, quote or bid, so search under all of those terms. For private work, ask past clients and agency contacts to add you to their vendor lists. Our two-week plan to find better freelance PM work walks through outreach that creates those early relationships.

If you want a worked reference for the writing itself, our collection of project proposal examples shows structures you can adapt, and the consulting templates for freelance PMs can shorten the drafting time.

Build your pipeline with The Freelance PM Club

If you want curated freelance project management roles, templates and a community of peers who have answered these requests themselves, take a look at our membership plans. Job Board Access is $5 per month, Freelancer Pro is $10 per month and Freelancer Elite is $20 per month. If you would rather talk through a specific bid or a move from corporate work to independent consulting, our coaching is built for that.

Common mistakes to avoid

• Answering every RFP. Without a go/no-go filter, time disappears into bids you were never going to win.
• Ignoring the format. Exceeding page limits or missing a required form can sink a strong proposal.
• Generic copy. Pasted boilerplate that never mentions the buyer’s goals reads as exactly that.
• Skipping references. The Utah instructions warn that proposers who fail to give explicit references or cross-reference their experience to the evaluation criteria risk immediate disqualification.
• Leaving it to the last hour. The PRCA framework discussed by Wadds suggests a healthy response timeline allows at least three weeks for strategy development. You may not get that, but you should plan for as much time as the buyer gives you.

FAQ

How do I respond to an RFP if I have never done one?

Start with the go/no-go scorecard, then build a compliance matrix from the document. Answer each question directly using the buyer’s headings, and attach references that match the evaluation criteria. For a first bid, pick a small RFP in a field where you have clear experience.

How long should an RFP response be?

As long as the buyer’s instructions allow and no longer. Many RFPs set page or word limits, and exceeding them can count against you. Concise answers that map to the scoring criteria usually beat long ones.

Is it acceptable to decline an RFP?

Yes, and buyers expect it. A short, courteous reply sent before the deadline is enough, and it keeps the door open for future work. Silence is the only response that costs you goodwill.

Can a freelancer compete against large firms?

Often, yes, when the work is specialized and the buyer values direct access to the person doing it. Compete on fit, named experience and clear delivery, not on scale. Be candid about capacity, and propose a realistic team if the scope demands more than one person.

Sources

• Request for Proposal Instructions, University of Utah Purchasing
• RFP Response Strategy, 101 Agencies
• RFP Response Strategy, Rework
• PRCA pitch framework, Wadds Inc.
• Respond to a solicitation, GSA
• How to Create an Effective RFP Response Checklist, Loopio
• How to Respond to an RFP, PandaDoc
• RFP Response Checklist Template, CheckFlow

Recommended

• Copyable Project Proposal Examples for Academia, Freelance, and Business
• Land a Call in Two Lines: Freelance Project Manager Cover Letter
• Client Onboarding Checklist for Freelance Project Managers
• Protect Your Pay: 8 Freelance Contract Clauses and Snippets for PMs