The Enterprise Sales Process: 15 Steps to the Close

The classic enterprise sales process looks surprisingly clean in a CRM: intro, demo, proposal, contracting, closed-won.

The problem is, the customer doesn't buy that way.

They discuss it internally. They bring in IT. Then security. Then finance. Someone somewhere is enthusiastic. Someone else thinks the project is completely pointless. Procurement shows up later than expected and legal sends back a Word file full of red lines.

This isn't an exception. This is enterprise sales.

Jen Abel, co-founder of JJellyfish and GM of Enterprise Sales at State Affairs, broke this process down into about 15 steps on Lenny Rachitsky's podcast. Her most important point isn't the number 15. It's the mindset behind it: the five CRM stages are built for forecasting. Not as a guide for how a customer reaches a decision.

This fits quite well with current buyer research. Gartner describes B2B buying groups as having 5 to 16 people from multiple functions. According to the study, 74% of these buying teams show unhealthy internal conflict. Meanwhile, McKinsey now measures an average of 10 interaction channels along the buying journey in B2B.

No wonder a linear sales funnel starts to look odd at some point.

What you will learn

• Why the five CRM stages are not your enterprise sales playbook
• The 15 steps that actually happen between first contact and signature
• Why the demo should happen later than most sales teams show it
• How to manage your champion, pilot, pricing and procurement as one process
• Where AI helps in enterprise sales and where the human element is becoming more important

My take: Enterprise sales is guided decision-making

Enterprise sales doesn't mean pushing a prospect through your pipeline. You help a group of people collectively reach a sound decision.

That might sound too soft for sales. But it isn't.

An enterprise buying decision consists of several jobs at once. Gartner describes Problem Identification, Solution Exploration, Requirements Building, Supplier Selection, Validation and Consensus Creation as key tasks in the B2B buying journey.

Your sales process needs to support these jobs. Otherwise, you're optimising your CRM while the customer is working on a completely different problem.

The seller becomes less of a pitcher and more of a project manager for the decision. This is exactly where the parallel to good product management lies: listening, recognising patterns, reducing uncertainty, bringing the right people together and defining the next logical step.

Why does the classic 5-stage funnel fail?

The 5-stage funnel confuses forecasting with buying. Intro, demo, proposal, contracting and closed-won are good categories for a revenue forecast. But they say very little about the work that needs to happen between these stages.

That's exactly where deals die.

A sales rep dutifully enters "Demo" into the CRM after the intro. The calendar appointment is set. It feels like progress.

But maybe the executive sponsor is still missing. Maybe the champion doesn't know how to defend the price internally. Maybe security hasn't been informed at all. Maybe a buying committee shows up for the demo, half of whom have never even heard of the project.

The CRM says: Stage 2.

The customer says: We're not even sure what we're deciding on yet.

Current research makes this problem more visible. In 2025, Gartner found that 74% of B2B buying teams experience unhealthy conflict. Buying groups that reach a consensus are 2.5 times more likely to rate their deal as high quality.

For sales, this means your job doesn't end at "my champion likes us".

You need to understand how the group gets to a collective yes.

The 15 steps of the enterprise sales process

Abel's process can be read in 5 phases: Entry, Context, Decision, Proof and Paper. The 15 steps below are the actual work.

1. Get the right first meeting

Don't target ten people in the account. Start at the top.

Abel's recommendation: executive or N-1. For example, CPO plus VP Product, General Counsel plus Deputy, or CRO plus VP Sales.

The reason is simple. A big deal needs executive value. If you start too low in the organisation, you first learn user value. That can be important, but it often isn't enough for a £100,000 project.

So your first message doesn't need a feature list. It needs an answer to this question:

What can this leader do differently with us than they do today?

This is the core information Abel calls "alpha". I'd put it more simply: an advantage the person can defend internally.

2. Run the intro call without a demo

The first call is not a mini demo session.

30 minutes. Informal. No slides. No screen share. The customer speaks first.

The goal is not to run through BANT. Budget, Authority, Need and Timing belong in your head, not as a questionnaire in the conversation.

The better question is:

What needs to be different next year compared to this year?

This shifts the conversation from a generic problem to the planned change within the company.

Why now? Who is demanding this change? What would success look like? What happens if nothing happens?

These aren't tricks. It's discovery with a real purpose: you want to find out if you are even the right vehicle for this change.

Abel says she disqualifies about one in four intro calls, often because the organisation isn't mature enough yet. That number is her practitioner benchmark, not a general market statistic. The logic behind it is sound, though: a good enterprise team doesn't optimise for the most demos, but for the fewest wrong demos.

3. Have a second call before the demo

This is where it gets interesting, because almost everyone skips this step.

You have a champion. Now, don't just ask them for a demo slot. You build the demo with them.

Who should be in the room? What are these people interested in? Which two features must they see? Which topics are better left out? What question should be asked in the meeting?

The champion gets their fingerprints on the story.

This changes their role. They are no longer a recipient of your sales materials. They become a co-author of the internal decision.

This is the exact principle I also describe in Sales Enablement as a System: good sales work isn't in a deck. It's in a process that provides people with the right information.

4. Frame the demo around their decision

Only now do you build the pitch.

And not from your standard deck, but from the context of the previous conversations.

If the customer's goal is to reduce external legal costs, the demo starts there. If the goal is to align product decisions more quickly with engineering, it starts there.

No tour of 27 features.

Enterprise buyers don't buy a quantity of features. They buy confidence that the important things will work for their use case.

5. Hold the demo with the entire buying team

For the first time, part of the organisation is sitting together in the group demo.

This isn't a product presentation. It's an alignment meeting that includes the product.

For new people, start again from scratch: Why does this project exist? What is supposed to change? How does this approach fit in?

Then ask the new people what they need to get out of the meeting.

Only then do you show the product.

Abel's rule is harsh but fair: Show the 20% of the product that delivers 80% of the relevant value. Not everything you've built.

Every irrelevant feature creates a new question: "Why are we paying for that?"

It's the same mistake as with bad positioning. More information feels safer, but it makes the decision harder.

6. Debrief immediately after the demo

The work isn't done after the demo.

Message your champion immediately: How did it go? Who did we lose? Who was sceptical? Who do we need to talk to separately?

The fresh reaction is more valuable than a formal follow-up three days later.

In every larger buying team, there's someone who can stop the deal. Your champion helps you identify this person early.

This is also the moment when clean information becomes more important than CRM fields. If your team gathers more context, that context must be available to everyone. This is exactly why a marketing-to-sales handover only works with a single source of truth, not three different note-taking systems.

7. Define the pilot

This isn't automatically "free trial for everyone".

A good pilot is small.

Abel usually recommends 3 to 4 real power users. Not 25 accounts and not a C-level executive who won't log in anyway.

You want people who can test the product in their daily work and whose opinion carries weight internally.

8. Plan the pilot backwards from the purchase

Before you start, there's the most important pilot question:

If this works, what needs to happen next for you to sign?

Who needs security documents? Who is in procurement? Does legal need time? Who has the budget? Who signs?

If the customer says that a successful pilot can't move forward until next quarter at the earliest, then maybe now is the wrong time for the pilot.

A pilot consumes momentum. Only start it when success can lead to a decision.

9. Manage the pilot closely

A pilot is not a sandbox.

Define 3 specific tasks and the success criteria together. Onboard the 3 or 4 users. Then, for a simple test, give them 48 to 72 hours.

For technically complex products, a pilot can take a month or longer. In that case, Abel recommends charging for it and crediting the amount if they buy.

The logic: if you have real effort involved in integration and setup, a free two-month pilot is not a sales hack. It's unpaid project work.

The buying circle for software can widen quickly these days. The G2 Buyer Behavior Report 2025 shows that IT is involved in 47% of software purchasing decisions, InfoSec in 32%, Finance in 31%, Procurement in 19% and Legal in 18%. So a pilot doesn't just have to prove user value. It also has to be able to pass the subsequent internal checks.

10. Debrief the pilot with data

After the pilot, don't just ask: "So, how did you find it?"

You know beforehand what happened.

Who logged in? Which tasks were actually completed? Where did users drop off? Which feature was ignored? Were there any bugs?

Then you can put the feedback into context.

If someone says "The product can't do X", even though X was never tested in the pilot, you're having a different discussion than if there's a genuine product gap.

The champion remains your sensor within the company. If this person suddenly goes quiet, it's a serious signal.

11. Prepare for pricing and procurement

Pricing should not be the first slide of your demo.

Abel waits as long as possible, ideally until after the demo, when the value and the stakeholders are clearer. If pressure comes earlier, she names a range instead of a final number.

The interesting part comes next: discuss the price 1:1 with your champion first.

Don't just ask: "Does the price work for you?"

Ask: How will you defend this price internally?

This is how you get the real business case.

If the champion says that 200,000 won't fly, don't immediately drop it to 140,000 yourself. Ask what would work internally and why. Otherwise, you're negotiating against yourself.

12. Send the contract in an editable format

Enterprise contracts get redlined.

So send an editable Word document, not just a PDF. And ask whether you should use your contract template or the customer's.

What sounds legally trivial can save weeks.

13. Bring legal and procurement together live

If the redlines become extensive, don't get into a 14-day email tennis match.

Get the relevant legal and procurement people on a call. Quickly accept the non-critical points. Discuss the commercially or legally significant points live.

Procurement isn't the final boss on the last level.

Procurement is the function that ensures the company can purchase from you and pay you according to their rules.

14. Know the real signatory

Who actually signs the contract?

Not necessarily your champion. Not necessarily the executive sponsor.

It might be the CFO or a central signing authority.

Clarify this before the final routing. Otherwise, your finished contract will land with someone nobody knew was still involved.

15. After the close, expansion begins

An enterprise deal isn't done when the PDF is signed.

The economic sense of an enterprise motion often lies in expansion. More teams, more use cases, more volume or services around the software.

Abel puts it clearly: if you land at 100,000 and are still at 100,000 a year later, a central part of the enterprise model is missing.

This doesn't mean you should immediately try to upsell every customer. It means understanding from the start where real additional value can be created.

The champion is more important than your sales methodology

A champion is not the person who answers your emails. It's the person who wants the project to happen internally.

This person provides you with context, helps with the demo design, knows the sceptics, explains internal processes and can pre-discuss pricing internally.

This is especially important because enterprise decisions are group decisions. Gartner found that buying groups today can include 5 to 16 people. At the same time, too much personalisation for individual roles can actually worsen group consensus. Gartner reports that content with buying-group relevance promotes consensus, while purely role-based personalisation can increase conflict.

This is an important corrective for modern ABM.

You don't win in enterprise by telling 12 people 12 different stories. You win by helping them believe in one shared story.

What does AI change in the enterprise sales process?

AI doesn't automate away enterprise sales. It shifts where the human is valuable.

According to Gartner, by 2026, 67% of B2B buyers will generally prefer a rep-free experience. 45% have used AI in a recent buying process.

At first, that sounds like bad news for sales.

But the same research contains a more important piece of information: 69% want to validate AI-generated information with a sales rep. Sellers remain particularly important when buyers are understanding their problem, choosing a preferred supplier, securing internal support or finalising the purchase.

So, exactly in the places where context and trust count.

AI can take care of research, account mapping, meeting prep and follow-ups. As I write in my guide on getting started with AI in B2B sales: machines are strong at research and admin. The human remains the owner of the relationship.

Enterprise sales makes this distinction even clearer.

The worse future is an AI agent sending 5,000 "personalised" executive emails per week.

The better future is a seller who, thanks to AI, already knows before the call what change is happening at the customer, who is likely to be involved and what questions are open. They then use the call for what the machine is less good at: nuance, conflict, trust and decision-making.

What benchmarks are useful in enterprise sales?

Caution is advised here. Abel mentions a few practitioner benchmarks for her enterprise motion: about a 25% to 35% win rate on qualified opportunities and around 80% success from a properly qualified pilot.

These are not universal SaaS norms. Deal size, category, market, maturity and the definition of "qualified" change these values massively.

Her interpretation is the more interesting statement: an extremely high win rate can mean you're too cheap or qualifying too late. A weak pilot-to-close rate, on the other hand, can mean you're letting the wrong customers into the pilot or the product proof isn't there.

So use benchmarks as a diagnostic tool, not as a religion.

McKinsey's B2B Pulse also shows how non-linear modern buying journeys are. B2B buyers today use an average of 10 channels. More than half would switch suppliers after a bad cross-channel experience.

This argues against rigid sales scripts and for consistent context across all touchpoints.

Where the process works, where it doesn't, and the trap

✅ What works. More small alignment steps before the big meetings. A champion who really wants the project to happen internally. A demo that only shows what's relevant for the decision. A pilot with tasks, success criteria and a clear path to a signature.

❌ What doesn't work. Forcing the enterprise customer into your standard process. Showing a generic product demo to 8 people right after a 30-minute intro. Giving a month of free access and hoping someone tries something.

⚠️ Warning. Don't confuse "high touch" with "more meetings". Every call needs a job. More touchpoints without progress are just a slower pipeline.

We started with a clean CRM funnel. Five stages. Looks good. Easy to report.

The real enterprise sales process is less elegant. It's more human, more political and full of small decisions.

This is exactly why sales must actively lead it.

Not as a pressure machine. As a decision-making system.

If you take one thing away from this whole playbook, let it be this: Slow down to go fast. Gather context before the demo. Build the internal case with your champion. Only start the pilot when success can lead to a decision. Then "pipeline management" actually becomes enterprise sales.

If you are currently redesigning your sales system, start with the basics in the GTM and Sales Process. A clean process is less spectacular than a new tool. But it's what gets contracts signed.

If you want to apply this process to your product, book a 30-minute call and we'll go through your next three deals.