Writing an RFP for Consulting Services (With a Model Structure)
Most consulting RFPs score responses on completeness — which reliably selects the firm with the best proposal team rather than the best thinking.
An RFP for consulting services should do one job: make it easy for good firms to show you how they think, and hard for weak ones to hide behind boilerplate. Most do the opposite. They specify a method in detail, ask for credentials and rate cards, and score the responses on completeness — which reliably selects the firm with the best proposal team rather than the best thinking.
The cost of getting this wrong is rarely the fee. It is a year spent with a partner who was excellent at responding to documents.
Before you write anything: decide what you are buying
Three different things get procured under the same label, and they need different documents.
A decision — you need an answer to a strategic question. Buy thinking; specify the question and the evidence standard, not the method.
A delivery outcome — you need a programme run to a date. Buy accountability; specify the outcome, the constraints, and the governance you expect.
Capacity — you need experienced people to augment your team. Buy capability and fit; specify the roles, seniority, and duration.
Writing a decision RFP for a capacity need produces expensive over-scoping. Writing a capacity RFP for a decision need produces bodies and no answer.
The structure that produces useful responses
1. Context and the real problem (1–2 pages). Say what is actually happening, including the uncomfortable parts — a previous attempt that failed, an internal disagreement, a constraint you cannot move. Firms that respond to a sanitised brief give sanitised answers.
2. The decision or outcome required. One paragraph, stated as a question or a result, not as a workplan.
3. Constraints. Timeline, budget range, internal capacity available, systems, geographies, and anything politically fixed. Publishing a budget range is contentious and, on balance, correct: it removes the game of guessing and lets firms scope honestly.
4. What we will provide. Access to people, data, and decision-makers. Weak access is the most common cause of engagement failure, and naming it in advance forces an honest internal conversation.
5. What we want to see in the response. Be specific and keep it short — see the next section.
6. Evaluation criteria and weightings. Publish them. Firms optimise for what is scored; if you do not publish, they optimise for length.
7. Process and dates. Questions deadline, submission date, presentation window, decision date. Honour them; slipping your own dates is the first signal of how you will govern the engagement.
What to ask for — and what to stop asking for
Ask for:
- A point of view on the problem, written before any work has been done. Two pages, at most. This is the single most discriminating element of any consulting RFP.
- The named team, with time commitments and evidence they will be present. Insist that the people at the presentation are the people on the engagement, and put it in the contract.
- Two comparable references the panel may contact directly, with the outcome and what went wrong.
- A worked example of a similar engagement — the approach, the surprise, and how they handled it.
- How the engagement ends — capability transfer, artefacts handed over, exit date.
- Commercial model — fixed fee by phase, with assumptions stated.
Stop asking for: generic methodology sections, full firm credentials, boilerplate on quality management, and lengthy tool descriptions. They are uniformly excellent across all bidders and therefore carry no information.
Evaluate for thinking, not for tidiness
A workable weighting for a decision or delivery engagement: quality of the point of view 30%, named team seniority and availability 25%, relevant comparable experience 20%, commercial value 15%, and approach and governance 10%. Note that price sits at 15% — enough to matter, not enough to select the cheapest team of juniors.
Two mechanics improve outcomes more than any scoring change. Run a working session, not a pitch: give the shortlisted firms a real problem, ninety minutes, and your actual stakeholders in the room. You learn more about how a team thinks in that session than in fifty pages. And score independently before discussing; panel conversation converges quickly on the most confident voice.
The signals worth weighting heavily
The firms worth hiring tend to challenge the brief during the questions period, name a constraint you did not mention, propose a smaller first phase than you asked for, and volunteer what could go wrong. The ones to be wary of accept the brief entirely, price exactly to the top of the range, and present a partner you will never see again. This is the same due diligence logic that applies to choosing a market entry consulting partner — ask for an example of a time they told a client no.
The takeaway
Write the RFP around the decision, publish your budget range and your weightings, ask for a written point of view instead of a methodology section, contract for the named team, and replace the pitch with a working session. You will get shorter responses, better differentiated — and a partner selected for how they think rather than how they write.
If you are scoping an engagement and want a straight read on how to frame it, a 20-minute diagnostic is a useful place to start — including if we are not the right firm for it. Book Executive Consultation.
TF Global Advisory Partners provides strategic consulting and programme delivery to enterprise clients, ministries and government departments, and UN agencies — across 500+ international projects and stakeholders from more than 50 countries.
