MEDDIC vs Miller Heiman: Building a Strategy and Training Programme for Complex Technical Solution Selling

Why standard sales training fails technical people

Put a BMS engineer or a lighting controls specialist in a room and tell them the day is about "building rapport" and "asking open-ended questions," and you've lost them before the coffee's gone cold. Not because they can't sell — plenty of them sell every day, informally, in every technical conversation they have with a contractor or an FM manager. They lose interest because the training doesn't address their actual problem. Their problem isn't a lack of charm. It's that they have no structured way to work out whether a deal is real, who actually controls the budget, or whether the person feeding them information inside the account can genuinely get things approved.

This shows up everywhere in the smart building world. An M&E contractor's estimator pushes a BMS quote for six weeks, convinced it's progressing, only to discover the client was benchmarking three vendors and never had sign-off from the person who matters. A system integrator's sales engineer builds a beautiful technical proposal for an FM operator who loves the product but has no budget authority and no urgency to get one. These aren't failures of personality. They're failures of qualification and stakeholder discipline — and that's precisely the gap MEDDIC and Miller Heiman were built to close.

Both frameworks assume the same starting point: your buyer is sophisticated, your sales cycle is long, and the deal involves more than one person with more than one motive. That's exactly the environment in BMS, IoT, and smart lighting sales. But the two frameworks solve different halves of the problem, and understanding that difference is the first step to building a training programme that technical people will actually use.

What MEDDIC actually is

MEDDIC is a qualification framework — a checklist you run against every opportunity to decide whether it deserves your time, and if so, what's still missing before you can forecast it with confidence. Each letter is a gate.

Metrics

The quantified business value of solving the problem. Not "improves efficiency" — a number. Kilowatt-hours saved per annum, hours of FM labour recovered per month, pounds of compliance risk avoided. If you can't attach a number to it, you don't have a Metric, you have a hope.

Economic Buyer

The person who can sign the cheque without needing anyone else's approval. On a £40k BMS retrofit this might be a facilities director. On a smaller lighting controls job it might be an M&E contractor's commercial director. The point of this letter is brutal: if you haven't identified this person, or worse, if you've never spoken to them, you don't know if the deal is real.

Decision Criteria

The formal and informal list the buyer will use to choose a vendor. Formal criteria show up in a tender document — protocol compatibility, warranty terms, commissioning support. Informal criteria rarely get written down — trust in the installer, fear of being the one who picked the system that failed. Both matter, and most reps only chase the formal ones.

Decision Process

The actual sequence of steps, and who's involved at each one, between now and a signed contract. Site survey, technical review, commercial negotiation, board sign-off, procurement paperwork. If you can't map this sequence with dates, you're guessing at your close date, not forecasting it.

Identify Pain

The specific, documented problem creating urgency to act now rather than next year. "The BMS is old" is not pain. "Three false fire alarm triggers this quarter caused by a failing BMS integration, and the insurer has flagged it" is pain.

Champion

Someone inside the account with genuine influence who wants you to win and will sell on your behalf when you're not in the room. Not a friendly contact — an active advocate with something to gain from your solution succeeding.

What Miller Heiman (Strategic Selling) actually is

Where MEDDIC asks "is this deal worth pursuing," Miller Heiman's Strategic Selling method asks "who, precisely, do I need to influence, and how are they each going to react." It's a stakeholder mapping and account-navigation framework, not a qualification gate.

Strategic Selling defines four Buying Influences on any complex deal:

• Economic Buyer — controls the money, has final veto, usually singular, often invisible to the sales rep until late in the cycle.
• User Buyer — will use or operate the solution day to day and judges it on "will this make my job easier or harder." In a BMS deal, this is the FM operator or building manager who lives with the interface every day.
• Technical Buyer — screens the proposal against specifications and can say no, but can rarely say yes alone. This is the M&E consultant checking protocol compatibility, cybersecurity posture, or compliance with BS EN standards.
• Coach — provides you with information about the other three and how to navigate them. Unlike MEDDIC's Champion, a Coach doesn't have to be internal to the account — it could be a specifier, a controls subcontractor, or a previous client who knows the politics.

Strategic Selling's central diagnostic tool is the Blue Sheet, a working document that scores your position with each Buying Influence, tracks whether their perception of you is a "Win" (they see this as good for them personally and professionally) or purely a "Response to their organisation's needs," and flags red flags — an influence you haven't covered, or one who's actively opposed.

This is where Miller Heiman earns its keep on complex technical deals: it forces you to separate the four roles even when, in reality, two or three of them are sometimes held by the same person, or scattered across a contractor, a client, and a consultant on the same job. In BMS sales, it's common to have a Technical Buyer at the M&E consultancy, a User Buyer at the FM company, and an Economic Buyer sitting inside a completely different organisation — the client's asset management team. Miller Heiman gives you the map. MEDDIC doesn't.

MEDDIC vs Miller Heiman: the comparison

Dimension	MEDDIC	Miller Heiman (Strategic Selling)
Primary focus	Deal qualification — is this winnable and worth pursuing?	Account navigation — who has influence and how do I cover them?
Strongest application	Forecast accuracy and pipeline discipline	Multi-stakeholder, matrixed, or politically complex accounts
Stakeholder model	Single Economic Buyer + single Champion	Four Buying Influences (Economic, User, Technical, Coach), can be multiple people per role
Deal qualification discipline	Explicit — six-point checklist forces a go/no-go decision	Implicit — assumes qualification happened elsewhere
Documentation tool	One-page MEDDIC scorecard per opportunity	Blue Sheet per account, updated through the cycle
Best for	Reps who over-invest time in unqualified deals	Reps who qualify fine but get blindsided by an influence they never covered
Weakness	Light on stakeholder complexity — treats "Economic Buyer" and "Champion" as if they're the whole picture	Light on hard qualification — doesn't force you to prove the Metrics or Pain are real

Which framework to choose for smart building and BMS sales

A typical UK BMS or smart lighting deal touches four kinds of organisation: the FM operator running the building day to day, the M&E contractor or system integrator installing and often specifying the kit, a procurement or finance function controlling the purchase order, and — on larger capex jobs — a facilities director or even a main board sponsor who owns the budget line. That's a genuinely complex buying committee, frequently spread across two or three separate companies rather than one.

In that environment, both frameworks matter, but they're not equally urgent. The biggest cause of wasted sales effort in this sector isn't poor stakeholder mapping — it's reps and partners chasing deals that were never real. No confirmed budget, no Economic Buyer contact, no documented pain, no Champion. MEDDIC's qualification discipline is the bigger lever, because it stops the bleeding before you invest three months of technical design time into a tender that was a box-ticking exercise for procurement.

Miller Heiman then earns its place once a deal clears the MEDDIC gate. Once you know the deal is real, the next question is tactical: who exactly do I need in the room, in what order, and what does each of them need to hear? That's where the Buying Influence model and the Blue Sheet pay for themselves, particularly on larger, multi-organisation capex projects where the Technical Buyer at the M&E consultancy and the Economic Buyer at the client are two entirely different conversations happening on two different timelines.

The practical recommendation: use MEDDIC as your primary qualification gate and forecasting language, and layer Miller Heiman's stakeholder concepts — specifically the four Buying Influences and the discipline of tracking Win vs Response-to-need perception — on top of it. Don't try to train both as equal, parallel systems from day one. Technical people, in particular, need one primary mental model to anchor to. Pick MEDDIC as the spine. Introduce Miller Heiman's stakeholder map as a tool that sits inside the "Economic Buyer" and "Champion" letters, giving them more resolution rather than competing with them.

Building a training programme: the six-week plan

Sales training fails most often because it's delivered as a single offsite event with no reinforcement. A six-week programme, run in short weekly sessions against live deals in the actual pipeline, works far better with technical audiences because it mirrors how they already learn — theory, then applied practice, then correction.

Week 1: The business case for structure

Start with an honest autopsy of three recent losses. Not a blame exercise — a diagnostic one. For each lost deal, ask: did we know the Economic Buyer? Could we state the Metrics in a number? Did we have a Champion, or just a friendly contact? Almost every technical sales team discovers the same pattern here — deals were lost to "no decision" or lost late in the cycle to a competitor nobody saw coming, both classic symptoms of weak qualification. This session builds buy-in for the rest of the programme because the evidence comes from their own pipeline, not a textbook.

Week 2: MEDDIC qualification deep dive

Work through each letter against two or three live, active deals in the room. Force the team to write down the actual Metrics number, name the actual Economic Buyer, and state the actual Decision Process with dates. Where they can't, that's the point — it identifies exactly what needs to happen next in the deal, not just in the training.

Week 3: Stakeholder mapping

Introduce the Blue Sheet concepts — the four Buying Influences and the Win/Response-to-need distinction — and apply them to the same live deals from Week 2. Have the team map every named individual in the account to a Buying Influence role and score whether that person currently sees the deal as a personal win or merely an organisational obligation.

Week 4: Value proposition and metrics

This is the session technical people engage with most naturally, because it's closest to their own discipline. Build a shared cheat sheet for quantifying ROI on BMS and IoT deals — payback period on sensor retrofits, energy cost savings per zone from optimised HVAC scheduling, FM labour hours recovered from remote diagnostics instead of site visits, and compliance cost avoidance from automated logging against F-Gas or fire safety obligations. The goal is that every rep and technical sales engineer can build a Metrics case without needing a business analyst.

Week 5: Champion development

Teach the difference between a friendly contact and a genuine Champion — someone with real internal influence who has something personally to gain from the project succeeding. Cover how to test for a Champion (will they set up the meeting with the Economic Buyer themselves? will they tell you what's really going on in the decision process?) and how to coach one — giving them the language and evidence they need to sell internally when you're not there.

Week 6: Deal review cadence

Establish a recurring pipeline review structured entirely around the MEDDIC checklist. Every deal above an agreed threshold gets scored against all six letters in front of the team, in minutes, not in a rambling narrative update. This session sets the operating rhythm the whole programme is building toward.

What training materials to prepare

Training without artefacts evaporates within a month. Before running the six-week programme, prepare:

• A one-page MEDDIC qualification worksheet, completed per deal, forcing a written answer against all six letters.
• A stakeholder map template based on the four Buying Influences, with space to record each individual's role, current disposition, and whether they've been personally contacted.
• An ROI and metrics cheat sheet specific to BMS and IoT — energy savings per sensor point, FM time savings from remote monitoring versus site visits, and compliance cost avoidance figures the team can quote with confidence.
• A Champion coaching guide — a short script and set of questions for testing and developing a Champion inside an account.
• A pipeline review agenda template that keeps deal reviews to the MEDDIC structure rather than free-form updates.

Common training mistakes

• Running it once. A single offsite session generates enthusiasm and nothing else. Without reinforcement in weekly pipeline reviews, the framework is forgotten within a month.
• Training only the salespeople. Technical sales engineers and controls specialists sit in on client calls constantly and shape the buyer's perception as much as anyone with "sales" in their title. Leave them out of the training and they'll undermine the qualification discipline without meaning to.
• Not practising on real, live deals. Generic case studies don't stick. Every exercise should use the team's actual pipeline, with real names and real numbers.
• Buying a certified trainer course and stopping there. A certification gives people vocabulary. It doesn't build the habit of using that vocabulary in every deal review, every week, indefinitely. The certification is the start, not the finish.
• Confusing the framework with the process. MEDDIC and Miller Heiman are checklists and diagnostic tools — they tell you what you know and don't know about a deal. They are not a replacement for having an actual, disciplined sales process that dictates what happens at each stage of an opportunity. Teams that treat the checklist as the whole system end up with well-qualified deals and no consistent way of actually running them to close.

What good looks like 90 days after training

You'll know the programme has worked, rather than just been attended, when the following are true without prompting:

• Every rep can state the Metrics, Economic Buyer, and Champion status for every deal above roughly £15k without checking notes.
• Any deal without an identified Champion is either explicitly deprioritised or has an active Champion-development plan attached to it — not left to drift.
• Pipeline reviews take twenty minutes for a dozen deals, not ninety, because the MEDDIC structure eliminates rambling narrative updates.
• Win rates on deals the team has forecast as likely to close are measurably higher than before the programme, because "likely to close" now means something specific rather than a gut feeling.

If those four things aren't true after ninety days, the training didn't fail because the frameworks are wrong — MEDDIC and Miller Heiman are both proven, decades-old methods used across the technical solution-selling world. It failed because it wasn't reinforced into the weekly rhythm of the business. That reinforcement, not the workshop itself, is the actual work of building a sales programme.