In a considered industrial purchase, five people ask five different questions and only one of them signs. Here is a mapping exercise you can run in a client workshop and finish in a morning.
In a considered industrial purchase, whether that is a capital machine, a component programme or a multi-year materials contract, no single person decides. A group forms, sometimes formally and sometimes not, and each member holds a veto over a different part of the decision.
Your client's material almost never reflects this. There is one website, one line card, one capabilities deck, and all of it is written for a composite person who does not exist: part engineer, part accountant, part operator. Everyone in the room reads it and nobody finds their own question answered.
The framework below is deliberately small. Five roles, one question each, and a mapping exercise. It fits inside a half-day session and produces a gap list the client can act on without commissioning further analysis.
Roles are functions, not job titles. One person can hold two of them, and at a small manufacturer the owner often holds three. What does not change is that each function asks a different question, and material that answers one does not answer the others.
Technical sales organisations concentrate on the specifier, and it is easy to see why. The specifier takes the call, asks good questions and enjoys the conversation. That relationship is real and it is necessary. It is not sufficient.
The specifier's power is mostly negative. They can remove a supplier on technical grounds, and they can sometimes write a specification only one supplier meets. What they generally cannot do is release the money. When they carry your client's material upward it stops working, because it was written for someone with their training.
The practical correction is small. Everything given to a specifier should include something they can forward without rewriting it: a one-page cost and risk summary attached to the technical document. Ask your client how often their engineering contact has had to build that summary themselves, and whether anyone has ever seen the version that reached the approver.
When a client writes for a generic customer, they write for the role they know best. At industrial firms founded by engineers, that is the specifier, so the website carries dense technical detail and says almost nothing about cost, risk or process.
The failure is not that the other roles disagree. It is that they find nothing addressed to them, so each falls back on a default assumption. The evaluator assumes risk. The gatekeeper assumes friction. The economic buyer assumes the incumbent is fine. The end user assumes disruption. Those defaults all favour the status quo, and the status quo is doing nothing.
This is quick to demonstrate live. Take the client's main sales page, read it aloud a paragraph at a time, and have the room call out which of the five roles would care about each one. The same name comes back repeatedly, and the group reaches the conclusion faster than any slide would take them there.
Build a grid with the five roles across the top and existing assets down the side. Website pages, product sheets, the capabilities deck, case studies, quote templates, the proposal itself, the after-sales handover pack. Include anything a prospect actually receives, including documents sales built privately without telling marketing.
Mark each cell as serves, mentions or absent, and be strict about the difference. A datasheet with one line about return on investment does not serve the economic buyer, it mentions them. Most clients find a dense column under specifier, something under evaluator, and very little under gatekeeper and end user.
Those gaps are usually cheaper to close than they look, because the content already exists inside the business in a form nobody has made shareable. Onboarding paperwork, standard terms, a maintenance schedule, an operator training outline and a typical installation timeline are documents the company already produces for other reasons.
The roles do not arrive at once. In most the end user or the specifier raises the need, the specifier defines it, the evaluator qualifies the suppliers, the economic buyer approves, and the gatekeeper closes. Material delivered out of that order is ignored even when it is good.
So commercial justification arriving in the first technical conversation is premature, and technical depth arriving after budget approval is late. The sequencing test for each asset is simple: name the stage at which it becomes the most useful thing the client could send. If nobody in the room can name one, the asset probably exists to satisfy an internal preference.
Set the grid against that sequence and two problems surface. Assets sent too early, which teach the recipient to stop opening the client's email, and stages with nothing to send at all. The quiet stages are commonly the evaluator and gatekeeper stages, and your client will recognise them as the point where deals go silent.
The loudest role is the one that responds, and responsiveness is not authority. Sometimes it is a specifier who enjoys the technical exchange. Sometimes it is a purchasing contact who returns calls because managing suppliers is the whole job. Either way the client hears a great deal from one seat and infers that the seat is the decision.
Two symptoms are diagnostic. Deals that pass technical evaluation cleanly and then stall with no stated reason, and deals lost to an incumbent on grounds the client never had a chance to answer. Both usually point to a role that was never addressed and never objected out loud.
The correction is not to neglect the loud role. It is to ask them directly who else has to be comfortable before this moves, and most will say. Then ask what those people will want to see, and what normally goes wrong at that step. Contacts who like your client are generally willing to describe their own approval process.
The session needs about three hours and the right people: whoever owns marketing, two salespeople who carry accounts, and one technical person who joins customer calls. Anyone who has never spoken to a customer will slow it down.
A map built once decays, because contacts move and organisations restructure. The cheapest defence is a single question added to the client's opportunity review: who else has to be comfortable with this, and what will they want to see. It costs nothing and it forces the roles into the record.
Ask the client to record the answer in the same place they track the deal, so patterns accumulate. After a quarter of this, the recurring gaps become obvious without another workshop, and the client can prioritise by frequency rather than by whichever loss is most recent.
Set one review date before you finish the session, roughly a quarter out, with a defined agenda: which gaps were filled, which deals stalled and at which role. That is a short meeting when the work has been done, and a useful conversation when it has not.
Key takeaways
Five functions recur: the specifier who defines the requirement, the evaluator who qualifies the supplier, the economic buyer who releases the budget, the gatekeeper who runs the process, and the end user who lives with the result. They are functions rather than job titles, so one person can hold two or three of them. At smaller manufacturers the owner frequently holds several.
Specifiers usually hold negative authority. They can rule a supplier out on technical grounds, and they can write a specification only certain suppliers meet, but they do not control the budget. The case has to be carried upward by someone else, which is why technical material needs a forwardable commercial summary attached to it.
Allow about three hours with marketing, two salespeople who carry accounts and one technical person who joins customer calls. Map a recent win and a recent loss by role, then audit existing assets against the five roles as serves, mentions or absent. Finish by choosing two gaps, naming an owner for each and setting a date.
Deals tend to clear technical evaluation and then stall without a stated reason, or go to an incumbent on grounds the supplier never had a chance to answer. The unaddressed roles do not argue, they simply default to the safer option, which is doing nothing. Asking the responsive contact who else has to be comfortable usually exposes the missing seat.
