Enterprise account executives, sales leaders, and deal teams managing complex, multi-stakeholder transformation opportunities.
I’ve spent most of my career selling into enterprise organisations and building sales functions.
One of the biggest lessons I’ve learned is that a $5M deal is not simply a larger version of a $100K deal.
The mechanics change, and the nuances become more pronounced as the numbers grow. Let me delve into this.
For one, the number of people involved increases. The financial scrutiny changes. Procurement becomes more influential. Security, legal, and architecture become potential blockers. Implementation risk becomes part of the buying decision. And you’ll need two hats, since the executive team looks at the investment differently from the technical team.
And perhaps most importantly to note:
You are no longer selling a product. You are helping an organisation make a significant capital allocation decision.
One of the largest enterprise deals I worked on was with Northern PowerGrid while I was at Microsoft as a Solution Sales Professional.
The opportunity covered approximately 3,500 users and ultimately crossed several parts of the Microsoft stack: Modern Workplace licensing, Microsoft Surface devices, Azure cloud services and security.
But the interesting part was how the deal had to be constructed and for how long.
Approximately one-third of the device investment was structured as CAPEX, while the remainder of the rollout was sequenced over three years through an OPEX model.
Any seller worth their title will tell you that enterprise deals are rarely won by simply proving that the technology works. You have to make the technical case, operational case, financial case, and political case work simultaneously.
This is how I think about winning enterprise mega deals consistently.
1. Start With the Buying Process, Not Your Sales Process
Every sales organisation loves its stages. You’ll find these in the CRM:
- Discovery.
- Qualification.
- Demo.
- Technical validation.
- Proposal.
- Negotiation.
- Closed Won/Lost.
But the customer does not experience the purchase that way. Those sales stages serve one specific function for your company: to track opportunities consistently and solve bottlenecks in YOUR sales process.
Inside the customer, something closer to this is happening:
Problem → Internal priority → Stakeholder alignment → Solution exploration → Business case → Technical validation → Risk validation → Budget approval → Procurement → Legal → Implementation planning → Executive approval → Contract
These processes overlap from their perspective.
Different stakeholders in this chain will be sitting at completely different stages. The CIO might already believe in the transformation. Security may still be evaluating architecture. Finance may be questioning the economics (they always do). Procurement may not even have been engaged, and when they are, they will have a span of their own questions and “alignments” that you’ll have to counter. The operational leader might be worried about disrupting 3,500 employees and the workflow that this “deal” will mean to the business.
This creates one of the biggest mistakes in enterprise selling:
The seller thinks the opportunity is at proposal stage while the organisation itself is still at consensus stage.
Your CRM stage is not the buying stage. The best sellers, the ones who consistently win, understand that the difference is fundamental, and they question the RIGHT people at the right time in the company’s buying process to ensure their solution is moving forward.
2. There Is Rarely One Buyer (never one buyer)
On a $5M+ opportunity, “the customer” doesn’t really exist.
There is a collection of stakeholders evaluating the same investment through completely different lenses. I’ve put together what a simplified buying committee might include:
| Stakeholder | What they are really asking |
|---|---|
| CEO / MD | Why does this matter strategically? |
| CFO | What return do I get for deploying this capital? |
| CIO / CTO | Does this fit our technology strategy? |
| CISO | What new risk does this introduce or remove? |
| COO | Can we implement this without disrupting operations? |
| Business Unit Leader | Does this materially improve my organisation? |
| IT / Architecture | Will this actually work in our environment? |
| Finance | How does this affect budget, cash flow and accounting treatment? |
| Procurement | Are we getting appropriate commercial terms? |
| Legal | What contractual exposure are we accepting? |
| Users | Is this going to make my job better or worse? |
So you see, you therefore cannot run a mega-deal through one champion. You need what we call in sales multi-threading (building relationships with multiple stakeholders inside the same account).
And not just because your champion might leave.
Your champion probably cannot answer the questions being asked in rooms they are not invited into, remember that.
3. Build the Stakeholder Map Early
For large opportunities, I want to understand four things about every important stakeholder:
Influence. Interest. Position. Motivation.
The questions you are basically asking are these:
- Who controls the budget?
- Who can veto the project? (this one is critical)
- Who owns the technical decision?
- Who owns implementation?
- Who benefits personally or organisationally? (this one is all about human nature)
- Who loses something if the project happens? (this one is all about human nature)
- Who controls procurement?
- Who ultimately signs?
MEDDPICC is useful here, particularly around the Economic Buyer, Decision Criteria, Decision Process, Champion and Paper Process.
But I would like to add another question:
Who has the ability to kill this deal without having the ability to approve it?
Enterprise organisations contain plenty of those people and/or these titles, and they are important to identify during the mapping phases.
- Security can block.
- Architecture can block.
- Legal can block.
- Procurement can delay.
- Finance can remove funding.
- A senior executive can deprioritise the programme.
So, what have we learnt thus far? Your stakeholder map therefore needs to include both the power to approve and power to obstruct. Identifying these crucial moving parts is ultimately core to lowering the sales cycle and limiting your exposure to risk.
4. Find the Economic Buyer, Then Understand Their WHY
Finding the economic buyer won’t be enough. A lot of companies will happily let you know who that is. Your task is to do something more crucial: understand why they would allocate millions to this initiative instead of something else.
This is where enterprise sales becomes capital allocation.
Imagine the CFO has €20M available for strategic investment. You learnt this over lunch or from a call with them after years of them using your products or asking you about potential solutions to a pertinent issue they need solving.
But your €5M transformation programme isn’t competing only against another technology vendor, it rarely does these days.
Your proposal is probably competing against:
a factory expansion, hiring, debt reduction, another IT programme, an acquisition, cybersecurity investment or simply keeping the capital available for a rainy day.
That changes the conversation dynamically, doesn’t it?
The question isn’t:
“Is our product worth €5M?”
The question now becomes:
“Why should this organisation deploy €5M here rather than somewhere else?”
That requires a business case to be drawn up.
5. Build the Financial Model With the Customer
Mega-deal financial modelling should go far beyond:
3,500 users × licence price × 36 months.
The business case should model the investment itself. At minimum, I would want to understand:
Total Cost of Ownership
TCO should incorporate licences, hardware, migration, implementation, integration, training, support, internal resources, infrastructure and ongoing operational costs.
Then you’ll need to model the economic benefit for the business and their people depending on the project, that could include:
productivity gains, infrastructure consolidation, reduced downtime, security risk reduction, lower support costs, retirement of legacy systems, reduced licensing duplication, automation benefits and avoided future expenditure.
From there you can build from data:
ROI
Their potential ROI = (Financial Benefit - Investment Cost) / Investment Cost
Payback Period;
How long before cumulative benefits exceed the investment?
Net Present Value
For multi-year programmes, future benefits should be discounted rather than pretending €1 received three years from now has the same economic value as €1 today. Have you heard of inflation and the speed of technological development? Account for that.
Cash-flow impact
This becomes particularly important when structuring CAPEX versus OPEX, which route they should take, and the core benefits of each, with the impact on THEIR business.
6. Commercial Architecture Can Win the Deal
Northern Powergrid was a good example of this. The requirement involved approximately 3,500 users, but the entire investment didn’t have to land financially on Day 1.
Part of the device estate was handled through CAPEX from gains they had recently reported in their quarterly results. The remaining rollout could then be sequenced across approximately three years through an OPEX model.
That accomplished something important for them. It aligned the commercial structure with the customer’s ability to consume the transformation and when.
This is an underappreciated enterprise sales skill. Sometimes the answer isn’t discounting. It’s how the proposal is structured. Break the pain down in parts, and it becomes easier to stomach.
But importantly, it gives you other things to work with in the relationship. You can change the structure of:
contract duration, deployment schedule, payment timing, consumption commitments, ramp periods, licence activation, implementation phases, renewal structures or CAPEX/OPEX allocation.
The objective is not financial engineering for its own sake but removing the mismatch between:
when the customer pays, when the customer deploys and when the customer receives value.
7. Your Business Case Needs Three Scenarios
For a large transformation, I like thinking about three cases.
Do Nothing
What happens economically if the organisation maintains the status quo?
This is frequently ignored. But “no decision” is usually your strongest competitor.
Model things like legacy infrastructure cost, security exposure, support costs, productivity loss, technical debt and upcoming refresh requirements, and also the loss of their competitive advantage.
Minimum Change
What happens if the customer fixes only the immediate problem?
This establishes the economics of your tactical response.
Strategic Transformation
What happens if the organisation implements the broader programme?
Now executives can compare:
status quo vs tactical investment vs strategic investment.
That is actually more useful for the buyer when they compare Vendor A with Vendor B, since they get to pit both technologies hand in hand and see the net value in their business.
8. Build a Deal Team, Not a Lone-Wolf Seller
No salesperson should attempt to carry a $5M+ deal alone. If they do, fire them… The Account Executive or Sales Specialist is effectively the deal orchestrator, and depending on the opportunity, the internal selling team might include:
Account Executive
They own the commercial strategy, stakeholder map, opportunity plan and overall customer relationship.
Solution Specialist
These teams connect business requirements to the relevant technology and use cases.
Solution Engineer / Architect
These teams prove technical feasibility and handle architecture, integrations, scalability and technical objections.
Customer Success / Adoption
They help you demonstrate how the organisation gets from signed contract to realised value.
Security Specialist
Addresses identity, compliance, data protection and security architecture.
Partner / Systems Integrator
Provides migration, implementation, integration and deployment capacity.
Finance / Commercial Desk
Models pricing, terms, consumption and deal economics.
Legal
Handles liability, contractual terms, data processing, warranties and regulatory considerations.
Executive Sponsor
Builds peer-level relationships with customer executives and helps resolve organisational roadblocks.
What I noticed and experienced is that, for very large deals, the seller becomes less of a traditional salesperson and more of a programme manager for a commercial decision.
9. Technical Validation Is Necessary, But It Isn’t the Deal
Enterprise sellers sometimes celebrate when the technical team says:
“This works.”
That could be important, but it means you have cleared one gate. Technical approval does not equal commercial approval; it just removes one blocker from the chain. A solution can be technically excellent and still lose because:
- Finance doesn’t see sufficient return.
- Procurement doesn’t accept the commercial structure.
- Security sees unacceptable risk.
- Legal doesn’t accept liability.
- Operations doesn’t believe implementation is feasible.
- The executive sponsor doesn’t see strategic importance.
- Or the organisation simply has another priority.
- The technical win therefore has to connect to the business case.
Instead of simply proving:
“The platform can do X.”
prove:
“The platform can do X, which enables Y operational change, producing Z financial or strategic outcome.”
Do this consistently and identify gaps in your own solution process and the business case and you’ll be closer to winning these types of opportunities consistently.
10. Understand What the C-Suite Actually Cares About
Different executives will interpret exactly the same project differently.
CEO
The CEO generally cares about strategic outcomes.
- Growth.
- Competitive position.
- Transformation.
- Customer experience.
- Operational resilience.
- Execution risk.
The question for them is:
“Why does this matter to the company?”
CFO
The CFO is looking at the proposal through an investment lens.
- Cost.
- Cash flow.
- ROI.
- Payback.
- Budget certainty.
- Risk.
- CAPEX versus OPEX.
Their question is:
“Why should I fund this?”
CIO / CTO
They care about architecture and technology strategy.
- Integration.
- Scalability.
- Legacy reduction.
- Technical debt.
- Operating model.
- Vendor strategy.
Their question is:
“Does this move our technology estate in the right direction?”
CISO
Their perspective is fundamentally risk-oriented.
- Identity.
- Data protection.
- Attack surface.
- Compliance.
- Incident exposure.
- Governance.
Their question is:
“What happens to our risk profile?”
COO
The COO cares about execution.
- Migration.
- Downtime.
- Adoption.
- Business continuity.
- Operational disruption.
Their question is:
“Can we actually deliver this?”
You have the task of an AE or AM with competing expectations in the same programme/deal, but with five completely different whys.
Your job is to connect them… consistently.
11. Procurement Is Not the Enemy
One of the worst mistakes sellers make is treating procurement as the department that appears at the end and asks for 20% off. Good procurement teams have a legitimate mandate.
They need to establish a few things that are important for their organisation:
commercial fairness, competitive tension, contractual protection, supplier viability, cost certainty and negotiating leverage.
If procurement enters the opportunity for the first time after your proposal, you’ve probably engaged them too late, and you have to understand the paper process early.
- Who approves?
- What procurement thresholds exist?
- Is an RFP required?
- Does the customer require competitive bids?
- Who handles vendor onboarding?
- What insurance requirements exist?
- What legal review is required?
- Are security assessments mandatory?
- Who signs the contract?
- What happens after signature?
For mega-deals, I would build these milestones directly into the mutual action plan, because “verbally approved” can still be months away from revenue. The earlier you action this for that team, the faster your sales and their buying process. It’s a good one to note and keep in mind.
12. Never Give Something Away Without Getting Something Back
Large procurement negotiations can quickly turn into incremental concessions.
- “Can you give us another 5%?”
- “Can payment move to 60 days?”
- “Can you include implementation?”
- “Can we reduce the first-year commitment?”
Potentially is the right answer here.
But every concession should have a corresponding exchange.
- If price decreases, perhaps term increases.
- If payment terms extend, perhaps volume commitment increases.
- If additional services are included, perhaps signature timing moves forward.
The principle is simple:
Give/Get. Read negotiation books I always recommend, such as “The Kremlin School of Negotiation by Igor Ryzov.”
And remember, you are not trying to “beat” procurement. You are trying to construct a commercially sustainable agreement for both organisations. People respect that.
13. Build a Mutual Action Plan
A mega-deal should have an explicit path to decision.
Not:
“Customer says they want to sign in December.” If a rep says this and only this, strongly consider having an Executive Sponsor at the next meeting with the buyer.
I mean an actual plan.
For example:
- Technical validation complete.
- Security assessment complete.
- Architecture approval.
- Business case approved.
- CFO review.
- Procurement engaged.
- Commercial proposal.
- Legal review.
- Implementation partner confirmed.
- Deployment plan approved.
- Executive sign-off.
- Contract signature.
- Kickoff.
You see what happened there? I replaced the original CRM steps we all use with clear strategic expectations in the buildout of the opportunity.
Every milestone should ideally have:
Owner + Date + Dependency + Evidence of Completion.
This transforms the opportunity from a seller’s forecast into a jointly managed programme, and it exposes risk early.
If security review requires six weeks and hasn’t started 30 days before your supposed close date, you don’t have a closing problem. Yours is a forecasting problem, and you probably need CommitControl (shameless plug).
14. Forecast the Evidence, Not the Enthusiasm
Mega-deals create enormous forecast bias:
- The salesperson has invested months.
- Executives know about the opportunity.
- Technical teams have invested resources.
- The customer sounds positive.
- Everyone wants the deal to happen.
That creates dangerous momentum inside the seller’s organisation, so separate belief from evidence. Basically, set aside the gut feelings and emotions at play, go cold and…
Ask:
- Has the economic buyer validated the business case?
- Is funding confirmed?
- Has procurement started?
- Has security approved?
- Is legal engaged?
- Has the implementation model been accepted?
- Is there an agreed decision date?
- Does the customer have an internal project owner?
- Has the commercial structure been validated?
- Has the customer completed the actions they committed to?
The bigger the opportunity, the more disciplined your forecast needs to become. A $5M opportunity should not enter Commit because everyone feels “good about it.”
It should enter Commit because the evidence underneath the deal supports the call. If it doesn’t, keep it at the current stage, go back to the client, and bring forward the concessions that warrant the change of stage in your CRM. And in your CRM, don’t just take notes; add the collective proof of why a decision is being made. Include the emails and the documents your company sent, who they were sent to, and who in their company has access to which documents. Orchestrate the opportunity. It’s a living, breathing machine, and the best salespeople have a hand on its heart.
15. Objections Change at $5M+
At smaller deal sizes you hear objections like:
“It’s too expensive.”
Mega-deal objections are usually more sophisticated.
“Why now?”
Reason behind this: The status quo hasn’t become painful enough.
“Why this project?”
Reason behind this: Another strategic initiative may have a stronger business case. Yours is to identify what it is…
“Why this vendor/solution?”
Reason behind this: The customer is evaluating long-term dependency, and there may be a counterparty risk.
“Can we actually implement this?”
Reason behind this: Transformation risk outweighs product enthusiasm, or they just don’t have the people resources to allocate to you.
“What happens if adoption is poor?”
Reason behind this: The projected ROI depends on behavioural change.
“What happens if the assumptions are wrong?”
Reason behind this: Finance is stress-testing your model.
“Can we phase this?”
Reason behind this: The organisation wants to reduce financial or operational exposure (this is good, actually).
Remember, these ARE NOT objections to overcome with clever responses. They are legitimate investment questions.
Treat them accordingly. They will make or break your opportunity.
16. Stress-Test Your Own Deal
Before an executive customer meeting, run what the IT team does, run a “red-team” session internally.
For this, pretend you’re the CFO.
- Why should we spend $5M?
Pretend you’re procurement.
- Why shouldn’t I demand another 15%?
Pretend you’re the CISO.
- What new exposure does this create?
Pretend you’re the COO.
- What happens when deployment goes wrong?
Pretend you’re the board.
- What happens if we do nothing?
Pretend you’re the competitor.
- Where is this proposal weakest?
The last one is crucial. At mine, I had four competing vendors who were undercutting us on commercials in some cases, support on others, and so on. If your deal team cannot answer those questions internally, your customer eventually will. If they do your homework for you, the impact is rarely on your side.
17. The Close Happens Long Before the Contract
This might be the biggest lesson I can offer. Mega-deals aren’t normally won during negotiation.
Negotiation is where the work done during the previous six or twelve months becomes visible.
If you have:
- an executive sponsor,
- a genuine champion,
- a quantified business case,
- technical validation,
- security approval,
- implementation confidence,
- budget alignment,
- procurement engagement,
- legal alignment,
- commercially workable terms,
- and a mutually agreed decision process,
The contract becomes the final expression of a decision the organisation has already made. If those things are missing, asking:
“What do we need to do to get this signed?”
isn’t closing, and you have this wrong, that question is trying to compress months of unresolved buying work into the final weeks of a quarter.
The Mega-Deal Equation
After working enterprise opportunities, I’ve come to think about large deals through a fairly simple framework:
Strategic Value × Economic Value × Technical Confidence × Organisational Consensus × Implementation Confidence ÷ Perceived Risk
A weakness in any one of those areas can undermine the entire opportunity. That is why enterprise selling is fundamentally an orchestration discipline.
Your job isn’t simply to persuade somebody that your product is good. Your job is to help dozens of people with different responsibilities reach sufficient confidence to make the same decision again and again.
And sometimes that requires changing the commercial structure itself. That was one of the important lessons from the Northern Powergrid opportunity.
We weren’t simply talking about Modern Workplace licences or Surface devices.
We were dealing with thousands of users, Azure consumption, security, hardware, deployment capacity, budget cycles and the economics of implementing a transformation over multiple years.
The solution therefore needed a commercial architecture that reflected how the organisation could realistically consume it.
- Part CAPEX.
- Part OPEX.
- Phased over three years.
- Technology aligned with deployment.
- Deployment aligned with finance.
- Finance aligned with the business case.
- And the business case aligned with executive priorities.
That is enterprise selling.
A Final Thought
There is a temptation to think the salesperson who wins a $5M, $10M or $50M contract must be an extraordinary negotiator.
Negotiation matters, and I touched on it lightly above.
But I think the more important skill is orchestration.
- Can you understand the customer’s organisation?
- Can you identify how the decision will actually be made?
- Can you build consensus between technical and commercial stakeholders?
- Can you translate technology into economics?
- Can you help the CFO understand the investment?
- Can you help the CIO understand the architecture?
- Can you help the CISO understand the risk?
- Can you help procurement construct workable terms?
- Can you help operations understand how implementation will happen?
- And can you coordinate your own organisation well enough to answer all of those questions?
Because at $5M+, you aren’t really closing a sale.
You’re helping an enterprise build enough technical, financial and organisational confidence to make a major investment decision.
Get that right, and the signature becomes the outcome of the process rather than the objective of it.
By Brian Bendera
Continue with the complete guide
The full guide continues with technical validation, C-suite priorities, procurement, negotiation, mutual action plans, forecast evidence, objections, deal stress-testing, and the close.
Get the complete guideSee the deals that need a manager now.
CommitControl surfaces stalled momentum, missing buying-process signals, and commercial risk across the pipeline, so managers can focus on the next move that changes the outcome.
Book a walkthrough