A preferred product is a hypothesis; the business outcome is the starting point.
Start with the change the business needs
Ask what must improve, who experiences the problem and how improvement will be recognized. Capture the present performance and the consequence of doing nothing. “Buy a new platform” specifies a solution; “reduce reconciliation time without weakening controls” defines an outcome that several approaches may satisfy.
Test whether process changes, existing capacity or a currently licensed capability could meet the need. Record why those options are sufficient or insufficient. This gives market discovery a defensible starting point and prevents an inherited specification from quietly choosing the winner.
Establish actual demand and the current state
Reconcile requested volumes with usage, commitments and operational records. Distinguish demand that exists today from a forecast dependent on growth, adoption or a later project. Identify unused capacity, duplicate suppliers and contractual restrictions on reallocating work.
| Question | Evidence | Buyer decision |
|---|---|---|
| What is consumed? | Usage, volumes, invoices and service records. | Separate necessary demand from preference or waste. |
| What already exists? | Current contracts, capabilities and operating processes. | Reuse, improve or replace. |
| What will change? | Funded plans and demand scenarios. | Commit now or retain a flexible option. |
| What constrains delivery? | Data, access, dependencies and staff availability. | Sequence work and fund buyer responsibilities. |
Use ranges when demand is uncertain. State the assumptions rather than hiding uncertainty inside a single volume. Later commercial comparisons should use these same scenarios.
Distinguish outcomes, gates and preferences
Write requirements so a supplier can explain how it will meet them and an evaluator can identify evidence. Separate mandatory conditions from desirable capabilities. A gate should have a reason, a test and an owner; too many arbitrary gates can eliminate credible alternatives without improving the decision.
Describe real workflows, exception cases and operating conditions. Avoid copying a supplier feature list into the requirement. Where a specific technology, location or delivery method is necessary, document why and whether an equivalent approach can satisfy the outcome. Use the RFP requirements guide when translating this baseline into a supplier-facing request.
Align stakeholders, money and implementation capacity
- Name the business owner who accepts the outcome and the approver who can commit funds.
- Confirm the budget boundary, cost categories and conditions for additional approval.
- Include users, finance, operations, technology, security and other relevant owners before requirements become fixed.
- Identify whose time is needed for evaluation, migration, training and ongoing governance.
- Record conflicting priorities and who has authority to resolve them.
A requirement is not ready merely because stakeholders have commented on a document. Obtain agreement on the tradeoffs: speed versus scope, standardization versus flexibility, and lower recurring price versus upfront effort. Make the approval path work within the real decision timetable.
Leave the stage with a validation plan
Maintain a short assumption register: statement, current evidence, consequence if wrong, owner and validation date. Examples include forecast growth, integration feasibility, supplier capacity and the business’s ability to change its operating process. Prioritize assumptions that could reverse the route or supplier choice.
Carry the requirement baseline into market analysis. Update it when new evidence changes what is feasible, preserving the reason for the change rather than silently altering the evaluation basis.
Sources & context
- CIPS · Strategic sourcing ↗Professional foundation: sourcing connects organizational objectives, market understanding and ongoing review.
The decision frameworks and illustrative examples are original editorial guidance. Sources support the stated context; they do not endorse this guide.