A weak RFP produces weak proposals. If you copy a public-sector template into a mid-market advisory buy, you will get compliance theatre — not a plan to fix your problem.
Canadian operators hire consultants for pricing, integration, operating model redesign, digital roadmaps and interim leadership support. The request for proposal is still the most common formal gate — and the most frequently mishandled. Too long, too vague, or too focused on legal boilerplate, it wastes everyone’s time. This playbook shows how to write an RFP that serious firms want to answer and that your evaluation team can score without arguing about apples and oranges.
When you need an RFP at all
Use a written RFP when spend exceeds your informal threshold (often $50K–$75K CAD), when multiple stakeholders must agree, or when board/audit expects a documented process. For smaller, single-expert sprints, a tight brief and two competitive conversations may be enough. Do not invent process for its own sake — invent process that improves decision quality.
Page budget and tone
Aim for four to six pages plus appendices (data room index, org chart, sample data). Write like an operator: specific metrics, plain language, published evaluation weights. Avoid mandatory 40-page response formats unless you are truly public-sector constrained. Mid-market firms with real expertise will self-select out of theatre.
Section 1 — Company context
Revenue band, headcount, geography, industry, ownership (founder, PE, family, subsidiary). One paragraph on why this problem is urgent now — not a brand story. Mention languages required for workshops and deliverables (English, French, or both). Note unionized sites, regulated data, or seasonal peaks that constrain fieldwork.
Section 2 — Problem statement
Specific beats aspirational. Bad: “We need a growth strategy.” Better: “Organic growth slowed from 12% to 3% over two years while gross margin compressed 180 bps; we need root causes and a 24-month portfolio of actions with owners.” Include what you have already tried and why it failed. Consultants calibrate honesty to your honesty.
Section 3 — Outcomes and success metrics
List 3–5 outcomes you will use to judge the engagement 90 days after it ends. Examples: decision memo adopted by the board; playbook live in two plants; SKU rationalization list with margin impact estimate; integration Day-100 checklist executed. Separate “analysis delivered” from “business result” so nobody pretends slides equal impact.
Section 4 — Scope and boundaries
In scope: sites, functions, systems, stakeholder groups. Out of scope: list explicitly (e.g., ERP vendor selection deferred; U.S. subsidiary excluded). State access you will provide: interviews, data extracts, plant tours. State constraints: blackout periods, confidentiality, competitive sensitivity.
Section 5 — Timeline and process
Publish dates: questions due, answers posted to all bidders, proposal due, presentation window, decision date, desired start. Keep the Q&A channel fair — no private clarifications that advantage one firm. Allow 10–14 days for a serious response on mid-complexity work; less invites recycled decks.
Section 6 — Evaluation criteria with weights
Example weights that work for many mid-market buys: relevant experience 30%, approach and workplan 25%, named team 20%, commercial terms 15%, references 10%. Publish weights. Firms allocate partner time to winnable deals; opacity breeds either no-bids or spray-and-pray proposals.
- Require named individuals with % time committed for the first six weeks.
- Ask for two client references at similar revenue and problem type.
- Request a one-page risk register for the engagement itself.
Section 7 — Commercial terms
State preferred fee model (fixed, T&M with cap, hybrid), expense policy, invoicing cadence, IP ownership expectation, data handling (PIPEDA), and termination for convenience. You do not need a full MSA in the RFP — you need enough for comparable bids. Ask proposers to flag any non-standard terms early.
What to ask for in the response
Cap the narrative. Useful structure: understanding of the problem (2 pages), approach and timeline (2–3), team bios and staffing plan (2), commercial proposal (1–2), relevant case studies (2). Ban appendices that dump every methodology trademark. Ask one hard question unique to your file so you can see original thinking.
Running presentations without theatre
Finalists get 90 minutes: 45 on their diagnosis and plan, 30 on Q&A, 15 on commercials. Invite the people who will live with the work — ops and finance leads, not only the CEO. Score independently before group discussion to reduce anchoring on charisma.
Common RFP failure modes
- Solutioning in the RFP (“implement agile squads”) instead of stating the problem — you pre-select method and miss better approaches.
- Asking for free detailed workplans that amount to unpaid consulting.
- Inviting ten firms — serious players decline noisy processes.
- Hiding the budget entirely when a range would improve fit; a band (“$120–180K CAD”) is often enough.
- No internal owner for evaluation — decisions slip and good firms walk.
Canadian procurement nuances
Private SMBs can move faster than Crown corporations, but document fairness if minority shareholders or lenders are watching. For Quebec operations, specify French capacity. If Indigenous communities are stakeholders, say so in scope — do not surprise proposers in week three. Cross-provincial labour and tax issues belong in context when the mandate is expansion or restructuring.
After you select
Convert the winning proposal into a statement of work within five business days while memory is fresh. Reconcile any oral promises into writing. Share a kickoff charter: objectives, RACI, meeting rhythm, escalation path. Archive the RFP and score sheets — future you will thank present you when the next mandate arrives.
Sample scoring sheet (adapt the weights)
Give each evaluator a closed spreadsheet before presentations. Columns: criterion, weight, score 1–5, evidence note. Lock weights in advance. After presentations, collect sheets before open discussion so the loudest executive does not rewrite history. Average scores, then talk about outliers — a single 5 next to four 2s deserves conversation.
Useful tie-breakers: team availability in your start window; quality of questions the firm asked during Q&A; willingness to price assumptions explicitly. Charm is not a criterion. Neither is “we already know them” unless disclosed as a conflict and still scored on merit.
Data room etiquette
Provide a minimal data room to serious bidders under NDA: anonymized financials if needed, org chart, prior relevant reports, system list. Watermark exports. Track who downloaded what. Do not dump every messy folder — curated context produces better proposals than noise. If two firms receive different data, your comparison is invalid; keep access equal.
Refuse requests for unlimited employee interviews during the bid phase. A short site tour or one operator call per finalist is enough. Unpaid consulting dressed as “to improve our proposal” is a soft no.
Legal and procurement co-ownership
Have legal review the RFP’s commercial section for landmines, but do not let legal rewrite the problem statement into abstraction. Procurement (formal or informal) owns fairness and calendar; the business owner owns substance. Kickoff a 15-minute alignment so redlines later do not surprise the winning firm into a two-week MSA stalemate while your problem waits.
Keep a disputes file: what you asked, what they promised, what you scored. Future RFPs get faster when institutional memory exists beyond one champion’s inbox.
Bottom line
A good management-consultant RFP is short, specific, weighted and fair. It describes your problem in numbers, defines done, and asks for the team who will show up. Canadian mid-market buyers who write that way spend less time reading fluff and more time comparing real approaches — which is the whole point of competitive tension.
If your RFP could be reused for any company in any industry, it is not an RFP yet — it is a template looking for a problem.
