Enterprise Software Sales: Selling Through People, Not To Them

Enterprise software sales is usually described by its size: bigger contracts, bigger customers, longer cycles, more people. All true, and none of it explains why good mid-market reps so often struggle when they move up. The difference is not the size of the deal. It is where the deal is decided.

In a smaller sale, the person you are talking to is usually the person who decides, and the conversation you are in is the one that matters. In an enterprise sale, the decision is made in meetings you will never attend — a budget review, a steering committee, a conversation between your champion and their CFO — by people you may never meet. Someone else carries your deal into those rooms.

That changes the job. An enterprise rep is not mainly persuading a buyer. They are equipping someone else to persuade their own organisation, and organising a team of their own to support it. This article is about that motion: what it is, how the cycle is shaped around it, who else is involved, what kills it, and which habits from smaller deals do not survive the move up.

If you are still deciding whether an account counts as enterprise in the first place, that question is settled in what is an enterprise customer. This piece assumes it does.

The motion: selling through, not to

Think about what has to happen inside a large company for it to buy software. Someone has to decide the problem is worth solving this year rather than next. Someone has to find budget, usually by taking it from something else. Someone has to convince security, IT, legal and procurement to spend their time on it. And someone has to put their name on the recommendation, knowing that if it goes badly, it is their name.

None of those people is the rep. All of that work happens inside the buyer's organisation, through the buyer's people, mostly in rooms the rep is not in. The person who does most of it is the champion: someone inside the account who wants the outcome, has enough standing to be listened to, and is willing to spend that standing on your deal.

In a smaller sale, you sell to the buyer. In an enterprise sale, you sell through the champion — and your champion's pitch to their CFO matters more than any pitch you will give.

So the enterprise rep's core question changes from "have I convinced this person?" to "can this person convince everyone else, without me in the room?" That is a much harder thing to know, and most of the motion exists to find it out.

The champion test

A contact who likes your product is a fan. A champion is someone who can and will sell it internally. The practical difference shows up in three questions:

• Can they explain the business case without you? Not your slides — their version, in their company's language, with their numbers.
• Have they spent anything on it yet? Time, a meeting with their boss, a favour from IT. People who are going to spend standing on your deal usually start before you ask.
• Will they tell you bad news? A champion warns you when a competing project is gaining ground or a stakeholder is unhappy. A fan tells you everything is going well until it is not.

The single most useful technique in enterprise selling follows from the first question. Ask your champion to present the business case to you as if you were their CFO — before they present it to the real one. You will learn in ten minutes whether they can carry it, which objections they cannot answer, and what you need to give them. It is also the only rehearsal of the most important conversation in the deal, the one you will not be in.

Multi-threading is risk arithmetic

Everyone agrees that enterprise deals should be multi-threaded — that a rep should have real relationships with several people in the account, not one. It is usually presented as good practice. It is easier to take seriously as arithmetic.

Over a long cycle, any single contact can become unavailable to your deal: they leave, change role, go on leave, lose an internal argument, or have their priorities reset by a reorganisation. Suppose, purely for illustration, that each contact who could carry your deal has a 25% chance of that happening before signature.

Threads that could carry it	Deal keeps a carrier*
1	75%
2	94%
3	98%

* Chance at least one is still there at signature — illustrative.

With one thread, a quarter of deals die of something that has nothing to do with your product. With three, almost none do. And the longer the cycle, the larger that 25% becomes, which is why multi-threading matters more in enterprise than anywhere else: the deal is exposed for longer.

Two caveats make this honest rather than a slogan. First, only threads that could carry the deal count — a friendly analyst with no influence is not a second thread. Second, contacts are not independent. A reorganisation can remove three of them at once, which is why the strongest second thread is often in a different part of the business from the first.

The roles worth threading to are well mapped. The economic buyer who signs; the technical evaluator who can say no; the users who will live with it; your coach inside the account. The Miller-Heiman Blue Sheet is still one of the clearest ways to lay them out, and MEDDPICC is the qualification framework built for exactly this environment.

The shape of the cycle

Enterprise stages are best defined by what the buyer has done, not what the seller has done. "Demo delivered" is a seller activity; it tells you nothing about whether the deal moved. "Champion has presented the business case to the economic buyer" is a buyer milestone, and it does.

A typical enterprise cycle passes through gates like these:

1. Problem agreed. The buyer accepts there is a problem worth solving this year, in their words.
2. Champion confirmed. Someone passes the champion test above.
3. Business case built — by them, with you. The case exists in the buyer's format and the champion can defend it.
4. Technical win. The people who evaluate fit, integration and risk are satisfied.
5. Economic approval. The person who controls the budget has agreed in principle.
6. Permission. Security, legal and procurement complete their work.
7. Signature routing. The contract moves through the buyer's approval chain.

Two things about this shape matter. The gates are sequential in principle but should overlap in practice — starting the security and procurement work at gate 6 rather than gate 2 is the most common way to add a quarter to a deal, which we worked through in software sales training. And because the plan spans both organisations, writing it down with the buyer is worth more here than in any other kind of sale. A mutual action plan is how most enterprise teams do it.

Who else is in the deal — on your side

Enterprise deals are not sold by one person, and a rep who tries usually loses time and credibility in equal measure. A typical pursuit draws in:

• A solutions engineer or solutions consultant, who owns the technical win: the deep demo, the architecture conversation, the proof of concept. The technical win and the business win are separate, and a deal needs both.
• An executive sponsor, who meets their counterpart at the buyer — once or twice, at the right moment, with a clear purpose. Used carelessly, executives become an expensive way of repeating what the rep already said.
• Security, legal and the deal desk, who answer the permission layer's questions and shape the contract.
• Customer success or professional services, who make the post-sale plan credible before signature.

The rep's job becomes orchestration: deciding who speaks to whom, when, and why, and making sure every one of those conversations moves a buyer milestone rather than filling a calendar. That is a different use of a week from running your own calls, and it is the part of the job new enterprise reps are least prepared for.

What actually kills enterprise deals

The other priorities. In most enterprise deals your strongest competitor is not another vendor. It is every other project competing for the same budget, the same executive attention and the same IT capacity. A deal can be won on every evaluation criterion and still lose to a cloud migration or a restructuring that needed the money more.

The champion who could not carry it. Enthusiastic, well-meaning, and unable to explain the business case without the rep's slides. These deals look healthy until the internal meeting, then go quiet.

The stakeholder you met once, late. Someone with a veto — often in finance, security or the user group — who was never part of the conversation and sees the proposal for the first time when asked to approve it. People treated as a formality tend to behave like one: they say no, or nothing.

The business case only you believe. If the case is in your format, with your numbers, the buyer has not built it and will not defend it. It needs to be theirs.

The permission layer, discovered late. A security review, a procurement process or a legal redline that nobody planned for, adding a quarter at the end of a deal that was forecast to close.

Notice that none of these is about the product, the demo or the close. Every one is about something happening inside the buyer's organisation without the rep.

The skills that do not transfer up

Reps moving from mid-market into enterprise usually bring strengths with them. Some of those strengths stop working.

Creating urgency with deadlines and discounts. In smaller deals, an end-of-quarter offer can move a decision. Enterprise budgets and approval calendars rarely bend to a vendor's quarter, and a discount offered to force timing mostly teaches procurement that the price was soft.

Demoing early. A demo before the problem is agreed answers a question nobody has asked yet, and in enterprise it can anchor the conversation on features when the decision will be made on business impact.

Closing the person in front of you. In enterprise, the person in front of you usually cannot say yes on their own. Pressing them to commit puts them in a position they cannot deliver on, and they tend to respond by going quiet.

Owning every conversation personally. A rep who insists on being in every meeting slows the deal down and cannot be in the ones that matter anyway.

Forecasting from enthusiasm. A warm, engaged contact is a weak signal in enterprise. Buyer milestones — the champion has presented, the economic buyer has agreed in principle, security has started — are strong ones.

What transfers intact is the underlying craft: real discovery, listening, honest qualification, and the ability to handle a hard question calmly. Those matter more in enterprise, not less. The difference is that they now have to work through other people.

Where practice fits

We build an AI roleplay tool, so read this with that in mind.

The most important conversations in an enterprise deal are hard to rehearse, because the rep is either not in them or gets one attempt. The champion rehearsal described above is the best tool for the first kind. For the second — the one meeting with the CFO, the security lead or the executive sponsor across the table — a rep can paste that person's LinkedIn profile into SalesArmor and practise the conversation against an AI buyer built from it, as many times as needed, before the one attempt that counts. Our page on selling to a CFO covers what that particular conversation tends to turn on.

Common questions about enterprise software sales

What is enterprise software sales? Selling software to large organisations through a motion where the decision is made inside the buyer's company, by several people, often in meetings the seller does not attend. The rep's job becomes equipping a champion to sell internally and coordinating a pursuit team, rather than persuading a single buyer.

How is enterprise sales different from mid-market sales? Beyond deal size and cycle length, the main difference is where the decision happens. In mid-market sales the person you speak to often decides. In enterprise sales the decision is made through internal budget, technical, security, legal and procurement processes, carried by a champion, with the rep mostly outside the room.

What is a champion in enterprise sales? Someone inside the buyer's organisation who wants the outcome, has the standing to be listened to, and is willing to use it to get your deal approved. The test is whether they can explain the business case without you, have already invested effort in it, and will tell you bad news.

Why is multi-threading important in enterprise sales? Because long cycles give any single contact more time to leave, change role or lose an internal argument. Every additional contact who could carry the deal reduces the chance that it dies for reasons unrelated to the product. Only influential contacts count, and threads in different parts of the business protect against reorganisations.

What does a solutions engineer do in enterprise sales? They own the technical win: detailed demos, architecture discussions, integration questions and proofs of concept. The technical win and the business win are separate, and an enterprise deal usually needs both.

What are the stages of an enterprise sales cycle? Defined by buyer milestones: the problem is agreed, a champion is confirmed, the business case is built by the buyer, the technical win is secured, the economic buyer approves, security, legal and procurement complete, and the contract is routed for signature. Permission work should start early and run in parallel.

Why do enterprise software deals stall? Most often because of competing internal priorities, a champion who cannot carry the case, a stakeholder with a veto who was involved too late, a business case the buyer does not own, or security and procurement work that started at the end instead of the middle.

What skills do reps need to move into enterprise sales? The fundamentals transfer — discovery, listening, qualification — but several habits need to be unlearned: forcing urgency with deadlines and discounts, demoing before the problem is agreed, pressing the person in front of them to commit, and forecasting from enthusiasm instead of buyer milestones.

A note on sources

This article contains no figures for enterprise buying-group size, cycle length, win rates, or the share of deals lost to no decision. Those numbers are widely repeated and vary enormously by deal size, product category and how a "deal" is defined; most come from surveys that do not publish their definitions next to the headline.

The multi-threading table is illustrative, using an invented 25% chance that a contact becomes unavailable before signature, and assumes independence, which the article explains does not fully hold. Its conclusion — each additional contact who could carry the deal sharply reduces the risk of losing it to one person's departure — holds at any probability between zero and one. The arithmetic was checked before publishing.

The stakeholder roles described draw on the long-established buying-influence framework associated with Miller Heiman and on MEDDPICC. Defining stages by buyer milestones, the champion test, the champion rehearsal and the list of skills that do not transfer up are ours.