RFP Process Workflow
When you know the outcome you need but not the solution — how do you get from ambiguity to acceptance?
An RFP is typically used when the buying organisation knows the outcome but wants suppliers to propose the best approach, delivery method, and solution. The formal RFP is not the start of the journey. It appears after upstream work converts uncertainty into a buyable scope. The full lifecycle runs from problem realisation through to commissioned, signed-off implementation.
The Realisation Moment
In JTBD terms, the trigger is the shift from "unmet need" to "actively trying to define what progress we need to make." The organisation has a significant problem or opportunity but cannot yet define the solution well enough to buy it cleanly.
| JTBD Element | What Happens |
|---|---|
| Struggling moment | Existing systems or processes are failing at scale |
| Current workaround | Spreadsheets, manual processes, tribal knowledge, point solutions |
| First thought | "We need to do something about this" |
| Hidden objection | "We don't even know what we need — how can we buy it?" |
| Switch trigger | A missed deadline, compliance failure, or lost opportunity forces action |
This is where the upstream advisory market lives — helping the buyer convert ambiguity into a clear, defensible scope.
Upstream: Problem Framing
Before launching any formal procurement, the buying organisation must define the need, scope, success measures, risks, budget, governance, and approvals. This upstream phase is where the highest-value work happens, because it shapes every downstream decision.
The Two Markets
| Market | Job | Output | Strategic Position |
|---|---|---|---|
| Upstream | Diagnose, frame, align stakeholders, define requirements | Business case + investable scope | Shapes criteria and budget |
| Downstream | Design solution, select vendor, implement, commission | Working solution + formal acceptance | Delivers against shaped scope |
If one consultancy defines what is needed and another scopes and sells the solution, the upstream advisor captures the most influence — they shape the language, criteria, scope, and evaluation model. Being "up the chain" means helping the client define the job before the market narrows into products and vendors.
Upstream Activities
- Internal stakeholder alignment — Who feels the pain, who owns the budget, who signs off?
- Current-state review — What exists, what works, what fails, what data proves it?
- Desired outcomes — What does success look like in terms the business can measure?
- Constraints and risks — Regulatory, technical, budget, timeline, organisational
- Requirements definition — Translate needs into scope, options, and evaluation criteria
- Business case — Cost-benefit, risk assessment, funding approval
- Route-to-market decision — Is an RFP the right mechanism?
When RFP Is the Right Mechanism
An RFP suits complex procurements where the outcome is known but the solution approach is open. Confirm this is the right path before investing in the process:
| Mechanism | Use When |
|---|---|
| RFQ | Spec is tight, price is the only variable |
| RFT (Tender) | Scope is defined, compliance and cost dominate |
| Panel / framework | Recurring need, pre-qualified suppliers |
| RFP | Outcome known, solution approach open to suppliers |
| Staged (EOI then RFP) | Market is unknown, need to learn before defining |
| Direct negotiation | Sole source justified, strategic relationship |
The End-to-End Process
Phase Detail
Phase 1: Need and Planning
| Activity | Output |
|---|---|
| Identify business need | Problem statement, desired outcomes, initial scope |
| Confirm sponsorship | Named sponsor, budget authority, governance structure |
| Assess route-to-market | Decision: RFP vs RFQ vs panel vs direct negotiation |
| Build business case | Cost-benefit, risk assessment, approval to proceed |
Gate 1: Procurement approval — Named decision-maker confirms funding, sponsorship, and authority to go to market.
Phase 2: RFP Preparation
| Activity | Output |
|---|---|
| Define scope of work | Requirements document, desired outcomes |
| Set evaluation criteria | Scoring model, weighting, mandatory requirements |
| Draft commercial terms | Pricing template, contract terms, liability |
| Build response format | Submission structure, compliance requirements |
| Set timeline and contact rules | Key dates, Q&A process, point-of-contact rules |
Gate 2: RFP release approval — Governance confirms the pack is complete, criteria are defensible, and the process is proportionate.
Phase 3: Market Process
| Activity | Output |
|---|---|
| Issue RFP to market or shortlist | Published RFP, distribution record |
| Manage supplier questions | Q&A log, addenda issued fairly to all |
| Receive submissions | Timestamped proposals, compliance record |
Phase 4: Evaluation
| Activity | Output |
|---|---|
| Compliance check | Compliant / non-compliant per submission |
| Score against pre-set criteria | Evaluation matrix, individual scores |
| Manage conflicts of interest | Declarations, recusals documented |
| Shortlist and clarify | Presentations, demos, interviews if needed |
| Best-and-final-offer (if required) | Revised pricing, final positions |
| Write recommendation report | Preferred supplier with evidence trail |
Gate 3: Preferred supplier approval — Evaluation panel presents recommendation. Decision-maker approves or requests further evaluation.
Phase 5: Award
| Activity | Output |
|---|---|
| Negotiate final deal | Agreed scope, price, terms, SLAs |
| Obtain internal approval | Signed authority to execute contract |
| Execute contract | Signed agreement |
| Notify unsuccessful suppliers | Debrief offers, published award notice |
Gate 4: Contract execution approval — Legal and commercial confirm terms. Authority signs.
Phase 6: Implementation
| Activity | Output |
|---|---|
| Mobilise supplier | Kickoff, governance, project controls |
| Finalise solution design | Approved design documents |
| Build / configure / integrate | Working system or deliverable |
| Test and fix defects | Test reports, defect register, evidence |
| Train users | Training materials, competency confirmation |
| Data migration (if relevant) | Migrated data, validation reports |
| Operational readiness checks | Runbook, support arrangements, rollback plan |
Phase 7: Commissioning and Acceptance
| Activity | Output |
|---|---|
| Go-live approval | Named decision-maker confirms readiness |
| Commission into live use | Service transition, production deployment |
| Hypercare period | Monitoring, rapid response, KPI tracking |
| Staged acceptance | Design sign-off, test acceptance, go-live approval |
| Final acceptance | All criteria met, defects within tolerance, docs complete |
| Handover to BAU | Closure report, lessons learned, support transition |
Gate 5: Go-live approval — Operational readiness confirmed. Named decision-maker authorises production deployment.
Gate 6: Final acceptance — Agreed success criteria met, defects within threshold, documentation complete, training delivered, support arrangements operational. Formal sign-off.
Governance Gates
Each gate should have named decision-makers, clear entry criteria, documented evidence, and an explicit record of approval. This creates auditability and reduces the risk of arguments later about whether obligations have been met.
| Gate | Decision | Entry Criteria | Evidence Required |
|---|---|---|---|
| G1 | Procurement approval | Business case, budget, sponsor, route-to-market | Signed approval to proceed |
| G2 | RFP release | Complete pack, defensible criteria, proportionate | RFP document, evaluation model |
| G3 | Preferred supplier | Evaluation complete, recommendation with evidence | Scoring matrix, recommendation report |
| G4 | Contract execution | Terms agreed, legal review complete | Signed contract |
| G5 | Go-live | Testing passed, training complete, ops ready | Readiness checklist, stakeholder sign |
| G6 | Final acceptance | Success criteria met, defects within tolerance | Acceptance certificate, closure report |
Connecting to Commissioning
The RFP governance gates (G5 and G6) map directly to the commissioning protocol used for software delivery in this codebase:
| RFP Gate | Commissioning Equivalent | What It Proves |
|---|---|---|
| G5: Go-live approval | L3: Tested | Automated + manual verification passes |
| G6: Final acceptance | L4: Commissioned | Independent verification against success criteria |
The principle is identical: the builder never validates their own work. The commissioner checks what actually shipped against what was specified. Whether the deliverable is a software capability or a procured solution, the discipline is the same — staged acceptance with evidence at each gate.
Practical Model
| Phase | Main Output |
|---|---|
| Need identified | Problem statement, desired outcomes, sponsor |
| Procurement planning | Business case, budget, risk, route-to-market, approval |
| RFP preparation | RFP document, scope, pricing template, evaluation model, terms |
| Market process | Issued RFP, Q&A log, addenda, supplier responses |
| Evaluation | Compliance review, scoring, shortlist, recommendation report |
| Award | Negotiated deal, signed contract, notifications, debriefs |
| Implementation | Design, build, test, train, readiness checks |
| Commissioning | Go-live approval, service transition, hypercare, KPI monitoring |
| Final sign-off | Acceptance certificate, handover to BAU, closure report |
Important distinction: The RFP process usually ends at contract award. The programme lifecycle continues through implementation and acceptance. Define both explicitly so procurement completion is not confused with successful solution delivery.
The JTBD Articulation
"When we realize we have a significant, high-stakes problem or opportunity but cannot yet define the right response, help us diagnose the situation, align stakeholders, and translate ambiguity into a clear, defensible scope so we can confidently choose and implement the right solution."
The valuable job is not selecting a vendor. It is converting uncertainty into decision-quality requirements.
Context
Process:
- Procurement — Parent hub: sourcing mechanisms, functions, skills
- Work Charts — Human/AI split per business function — this workflow maps to the Operations > Vendor Management row (50% AI)
- Contract Negotiations — Legal deal closure
- Process Re-engineering — Continuous improvement methodology
- Quality Assurance — Deming's 14 points
Decision Frameworks:
- Buy or Build — Technology procurement decision matrix
- Decisions — The P-C framework for choices
- Business Development Process — How procurement fits Idea → Strategy → Operations → Growth
Commissioning and Verification:
- Commissioning Protocol — L0-L4 maturity model and flight readiness
- Scoreboard Reality — Instruments that read whether delivery matched intent
- Commissioning Dashboard — Live capability status
Templates:
- RFP Bid Template — Response template for bid submissions
- PRD Spec Template — Tight Five PRD structure
Product:
- Sales CRM & RFP — Construction-vertical tool that implements the downstream RFP workflow
- Jobs To Be Done — Demand-side thinking framework
Questions
What is the real cost of starting the RFP before the upstream problem-framing is done — and who pays for that ambiguity?
- If the upstream advisor shapes the evaluation criteria, what governance prevents bias toward their preferred downstream supplier?
- At which gate does the most value leak in your current procurement — and is the gate missing or is the evidence weak?
- When does staged acceptance actually happen versus a single yes/no decision at the end — and what does the difference cost when things go wrong?