The Decision Making Unit: Six Roles in Organisational Buying

The decision making unit is the set of people who take part in an organisational purchase decision. It is a behavioural concept and not a structural one: the members hold no common job title, appear on no organisation chart, and frequently do not describe themselves as being involved at all.

Its purpose is to correct the assumption that a purchase has a buyer. In organisational markets the person who signs the order is often the least influential participant, and selling to them alone is the single most expensive mistake in business-to-business marketing.

The six roles

Webster and Wind's formulation identifies roles rather than people, and one person can hold several while one role can be held by several people.

Initiator. Recognises the problem and starts the process. Often junior, often the person who operates the thing that has failed. Their influence is over whether a purchase happens at all, not over which supplier wins.

User. Works with the product once bought. Users carry disproportionate weight on repeat purchases and almost none on first-time ones, because their objection is credible only after experience.

Influencer. Shapes the specification or supplies the criteria by which options are judged. Technical specialists, consultants, and increasingly the external standards a sector adopts. The influencer frequently decides the outcome before the decision is made, by writing a specification only one supplier meets.

Decider. Makes the actual choice. May be formally authorised or may hold the effective veto — a safety officer who cannot buy anything but can stop anything is a decider in all but name.

Buyer. Holds the formal authority to select terms and place the order. Procurement's role is often confined to commercial terms after the technical choice is settled, which is why negotiating hard with procurement rarely changes who wins.

Gatekeeper. Controls the flow of information and access. Personal assistants, procurement portals and category managers all perform this function. The gatekeeper cannot choose the supplier and can prevent a supplier from being considered.

How membership changes with the buying situation

Robinson, Faris and Wind's buyclass framework explains why the same organisation behaves differently on different purchases, and it is the part most often left out.

A new task — buying something for the first time — produces the largest unit, the longest process and the highest information need. Influencers dominate because nobody yet knows what the criteria should be, and this is the situation in which a supplier can shape the specification.

A modified rebuy — buying something familiar but with changed requirements — produces a medium-sized unit. The existing supplier is advantaged and vulnerable at once: advantaged by incumbency, vulnerable because the review has been opened.

A straight rebuy — reordering on existing terms — may involve one person or no person at all, with the order generated automatically. Here the incumbent's position is nearly unassailable and the challenger's only route is to force a reclassification into modified rebuy by creating a reason to review.

The practical implication is that identifying the buyclass comes before mapping the unit, because it determines how many people are in it and which roles carry weight.

What each role actually responds to

Treating the unit as one audience with one message is the failure the concept exists to prevent. Each role is answering a different question.

The user asks whether this will make their work better or worse, and responds to demonstration and to reference from someone doing the same job.

The influencer asks whether the solution is technically sound, and responds to specification detail, evidence and standards compliance. Influencers are also the group most damaged by overstatement, because they are the ones equipped to check.

The decider asks what happens if this goes wrong, and responds to risk reduction — references, contractual protection, the supplier's stability. On large purchases the decider is frequently buying insurance rather than capability.

The buyer asks whether the commercial terms are defensible, and responds to comparability, total cost and process compliance.

The gatekeeper asks whether this is worth the time of the people they protect, and responds to relevance and brevity.

A proposal that answers only the technical question will convince the influencer and lose to a competitor who also addressed the decider's exposure.

How the unit relates to the buying process

The roles describe who; the buyphase model describes when, and the two together are more useful than either alone.

Robinson, Faris and Wind set out eight stages: problem recognition, general need description, product specification, supplier search, proposal solicitation, supplier selection, order-routine specification, and performance review. Different roles dominate different stages, and a supplier arriving at the wrong stage is talking to the wrong people.

The decisive stage is product specification, because it converts an open problem into a list of requirements. Everything after it is comparison against criteria already fixed. A supplier who first makes contact at proposal solicitation is competing on a specification someone else influenced, which is why the industry maxim that a tender you did not shape is a tender you will probably lose has empirical support.

Performance review matters for the opposite reason: it determines whether the next purchase is a straight rebuy for the incumbent or a modified rebuy open to challengers. Incumbents lose position here more often than they lose it in competition.

The practical reading is that the supplier's opportunity to influence and the buyer's willingness to be influenced both peak early and decline steadily, while most selling effort is spent late.

Mapping a unit in practice

Three questions surface the unit more reliably than an organisation chart.

Who raised this, and when? The initiator establishes what problem is actually being solved, which is frequently not the problem stated in the tender.

Who wrote the specification? Whoever did is the influencer, and where the specification names a standard or a feature set, the criteria were set before any supplier was approached.

Who has to sign, and who can stop it without signing? These are different people. The second is the one missed.

Two errors recur in account plans. The first is mapping titles and not roles, which produces an accurate chart of the hierarchy and no information about the decision. The second is treating the unit as static across a long sales cycle: people move, budgets transfer, and the safety officer who was irrelevant at specification becomes decisive at approval.

A worked map on a single purchase

A manufacturer replaces the maintenance management system it has run for eleven years.

Initiator. The maintenance supervisor, who has spent two years reporting that the current system cannot schedule preventive work against actual running hours. Nothing happened until an unplanned outage cost a shift.

Users. Fourteen engineers and three planners. They have strong views about the existing system and, on a first-time purchase of this kind, very little influence over which replacement is chosen — a gap between interest and power the supplier should read, not exploit.

Influencers. The IT architect, who will not approve anything that cannot authenticate against the existing directory, and an external consultant engaged to write the requirements. The consultant's document is the real battleground: whichever supplier has shaped its structure has won most of the evaluation before it begins.

Decider. The operations director, on paper. In practice the IT architect holds a veto that has never been overruled, which makes two deciders with different criteria.

Buyer. Procurement, entering at shortlist stage, mandated to run a comparative process and extract a discount. Their influence is over price and contract, not over selection.

Gatekeeper. The procurement portal. A supplier not registered on it cannot be sent the tender, whatever the operations director thinks.

The lesson from laying it out is that the supplier's effort belongs in two places that look unglamorous — with the consultant during requirements, and with the IT architect on integration — while the natural instinct is to spend it on the operations director, who is visible, senior, and will be advised by both.

Where the concept is limited

The framework is descriptive and does not weight the roles. It says a decision making unit contains an influencer and a decider; it does not say which matters more here, and the answer varies with the purchase, the sector and the organisation's culture.

It also predates the change in how organisational buyers gather information. A substantial proportion of a business purchase decision is now made before any supplier is contacted, through independent research by people whose role the supplier cannot identify because no contact has occurred. The unit still exists; the supplier's ability to observe it has declined, which shifts effort towards material that works without a salesperson present.

There is also no account of how large a unit becomes. Studies report averages from three participants on routine purchases to well over ten on major capital items, and the number rises with value, with risk and with the count of functions affected — but the framework offers no way to estimate it in advance, which is exactly what an account plan needs.

Finally, the model treats participation as rational role performance and says little about organisational politics. A purchase that consolidates one department's budget at another's expense is contested on grounds the buyclass framework does not describe, and in those cases a power analysis explains more than a role map does.