The first procurement question is not “who should supply this?” It is “what outcome are we actually trying to create?”
The Week 6 planning slides ask a set of deceptively simple questions about demand. Is the requirement a product, a service or a bundle? Is it critical or non-critical? Is demand stable, seasonal, fluctuating or one-off? Could demand be reduced? Could an alternative good or service satisfy the need? Has in-house provision been considered?
These questions shift procurement upstream.
Before the organisation optimises price, competition or supplier selection, it should challenge the need itself.
The Strategic Context
Procurement teams often inherit requirements after important decisions have already been made.
A business unit may decide it needs a particular software platform, machine, consulting service or maintenance arrangement. Procurement is then asked to “go to market”.
But the business requirement may have been framed too narrowly.
The real need might be improved reporting rather than a new software platform. It might be increased production capacity rather than a specific machine. It might be reduced equipment downtime rather than a larger stock of spare parts.
A procurement process can be efficient and still procure the wrong thing.
What Leaders Commonly Misread
The first misread is treating stakeholder demand as fixed.
Stakeholders are essential sources of requirements, but their proposed solution is not automatically the only valid response.
The second is assuming more specification produces more control. Over-specification can narrow competition and lock the organisation into one technical answer before the market has contributed expertise.
The third is focusing on purchase price rather than demand volume and usage. Reducing unnecessary demand can create more value than negotiating a small unit-price improvement.
The fourth is overlooking bundles. A “product” may actually require installation, training, support, data, maintenance and transition services. Conversely, a large bundle may contain components that could be sourced more effectively in different ways.
Reframing the Issue
Demand analysis should move through three levels:
Outcome → capability → requirement
The outcome defines the enterprise result.
The capability describes what the organisation needs to be able to do.
The requirement translates that capability into goods, services, performance or capacity that the market can provide.
This sequence prevents procurement from beginning with a preferred solution and working backwards to justify it.
Strategic Analysis: Demand Is a Portfolio Choice
Consider a hypothetical accounting firm entering a new service market, similar to the Week 6 study-note discussion scenario.
Off-the-shelf software is available but expensive and requires specialist configuration. The organisation could buy the software, develop internally, use consultants, adopt a hybrid model or adjust its service model so that a less specialised solution is sufficient.
The wrong question is: “Which software vendor should we select?”
The stronger questions are:
- What functions are essential?
- Which functions create competitive advantage?
- What demand will actually exist?
- What can be standardised?
- What must be customised?
- What capability should the firm own?
- What should remain with external specialists?
Demand analysis changes the sourcing decision before price competition begins.
Decision Framework
Leaders can challenge demand through six tests.
Outcome
What business or project result must be achieved?
Criticality
How important is the requirement to safety, revenue, operations or strategic capability?
Pattern
Is the demand stable, variable, seasonal, uncertain or one-off?
Alternatives
Can another product, service, process or internal capability produce the same result?
Reduction
Can demand be eliminated, simplified or standardised?
Packaging
Should the requirement be sourced as one bundle or as several components?
These questions should be resolved before detailed tender documentation is built.
From Strategy to Execution
Immediate action: require every significant procurement to contain a concise demand statement separate from the proposed solution.
Medium-term capability building: involve operational users, finance, technical specialists and procurement together in demand analysis.
Long-term strategic positioning: create portfolio visibility of recurring demand. Multiple projects may be buying similar services separately because each requirement was framed locally rather than enterprise-wide.
This can reveal opportunities for standardisation, aggregation, supplier development or internal capability building.
Signals to Monitor
Watch for business cases that name a vendor or product before requirements are defined, repeated emergency purchases, low utilisation after procurement, growing numbers of similar contracts across business units and large specification documents that cannot clearly explain the underlying business need.
Another signal is stakeholder resistance to alternatives. If the conversation becomes “procurement is changing our requirement”, leadership may need to distinguish genuinely essential characteristics from preferences inherited from past practice.
Questions for the Leadership Team
- What outcome are we buying rather than what item are we buying?
- Which parts of demand are genuinely essential?
- What could be reduced, standardised or eliminated?
- Are internal provision and alternative solutions being considered objectively?
- Does the proposed bundle increase or reduce competition?
- Are several projects independently purchasing capability that should be managed at portfolio level?
Closing Perspective
The cheapest tender cannot rescue unnecessary demand.
The most capable supplier cannot create value from a requirement that was badly framed.
Procurement becomes strategic when leaders challenge the need before they optimise the purchase.
Related article: The Executive Decision Behind Make-or-Buy
Related article: Design the Market, Do Not Just Enter It: Bundling, Unbundling and Supplier Development
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.