How to close $100K+ enterprise deals, step by step | Jen Abel

Why does it matter? Because 90% of enterprise salespeople are running a forecasting tool, not a sales process

Jen Abel has spent years watching founders and AEs lose deals they should have won — not because their product was wrong, but because they mistook a CRM pipeline for a sales motion. What she maps out here isn't a five-step process. It's fifteen, and the ones everyone skips are the ones that decide who closes.

• The intro-demo-proposal-contracting-close pipeline is a weighted forecasting artifact, not a guide for running a deal — treating it as one compresses 15 critical steps into 5 buckets and forfeits every conversation that builds information edge. • The intro call is the only moment prospects share unfiltered intel. Once they sense a formal sales process has begun, they clam up permanently. • Targeting anyone below the N-minus-one level means learning user value instead of executive value — and user value can't allocate $100K. • A healthy enterprise win rate is 25–35%. If yours is higher, your price is too low.

The five CRM stages were built to weight a forecast — treating them as a sales motion means you're already at step ten before you know it

"Most people think the sales process is five steps," Abel says. "We're already in step ten and we're not even done."

The pipeline every sales team runs — intro, demo, proposal, contracting, close — didn't emerge from studying how enterprise deals close. Abel is blunt about its origins: those stages are buckets for a weighted forecast. A mid-funnel proposal might carry 50% probability weighting; something in contracting, 80%. That's the framework's entire purpose.

Ninety percent of salespeople use these forecast buckets to structure the actual client journey, which means they skip two to five conversations that need to happen inside each stage. Enterprise sales, Abel argues, is mirroring and controlling a buyer's buying process — not dropping them into yours. "It's not plopping these people into your sales process."

The fix isn't abandoning the CRM. It's building a parallel 15-step internal playbook alongside it: who has the intel, which stakeholder hasn't been brought in yet, who might kill the deal at the demo. The CRM tells the CFO what to expect. The 15-step map tells you how to actually get there.

The intro call is the only moment a prospect speaks freely — demo once, and that window closes permanently

Every competitive advantage you will ever have in this deal is available in a single 30-minute call. Abel's instruction: show them nothing. No demo, no slides. Don't record it.

"The information they will tell you on the first call, they will clam up moving forward because it starts to feel like a sales process." Once that shift happens, it's permanent. The prospect becomes polite instead of candid.

Her approach: ask them to go first. Let them describe their role briefly, then push deeper — "What needs to change going into next year?" surfaces the mandate that's come down from above, which is almost always where real budget and urgency live. Keep pulling threads: why now, what does success look like, what's the measurement. The final ten minutes go to a pitch built entirely around what she just heard.

No BANT questions. No scripted frame. "The fastest way to commoditize yourself is to go into some sales script." The pitch at the end of an intro call looks different every single time — and that's the point.

The 15-minute pre-demo call with the champion is the most ignored step in enterprise sales — and none of your competitors are doing it

No competitor you're up against is taking this step — and it takes fifteen minutes.

After the intro call, most salespeople book the group demo. Abel inserts a separate call beforehand with the champion, framed simply: "I want to make sure I'm demoing the right things and we have the right people in the room." She walks them through the product live, asks what will resonate with each attendee, and collects the names of potential blockers before the full group ever gathers.

"For that demo call — who are all these people? What do they care about? And what should I avoid?" The champion, who wants this to succeed, will answer all three. They'll name the skeptic, flag the relevant capability, and warn you which feature makes someone say "we wouldn't use half of this."

By asking the champion to co-script the demo, you give them ownership. "Now they feel part of this journey. Now they trust you." They stop being a contact and start pulling the deal forward — because it now has their fingerprints on it.

Only target the C-suite executive and the N-minus-one — going one level lower trades executive value for user value, and user value can't close a $100K deal

Going below the N-minus-one isn't just inefficient — it wires you into user value instead of executive value, and $100K deals need executive sponsors to allocate budget.

Abel runs two simultaneous outreach tracks — what she calls the Pincer Model. The founder reaches out directly to the C-suite contact. The AE reaches out to the N-minus-one. No other layers. "If you go any further than that, you risk they're not going to be able to communicate your storyline. It's a game of telephone."

One of the two tracks responds. Parity norms do the rest: the person who replied naturally asks "should we bring in so-and-so?" The executive may already recognize the company name when the AE's message lands, creating compound familiarity without a coordinated pitch.

To find both targets: ask ChatGPT or Claude to identify likely candidates at the company and function, then verify on LinkedIn. The message that lands isn't about what the product does. It's about the alpha — what the executive personally unlocks by sponsoring it.

Every AI startup pitches efficiency — executives only fund something that lets them show needle-moving impact to the board

"Alpha" means something specific in Abel's framework. It isn't the problem your product solves — that's "level one," and every competitor makes that case. Alpha is what the executive personally uncovers by bringing in the tool: the narrative they carry into the next board meeting.

"What would they say about the product? 'This product will allow me to do what' — that's like the litmus test." Reducing headcount or cutting costs doesn't clear the bar. What lands is something that repositions how the team is structured, creates a capability the executive can claim credit for, or lets them show needle-moving impact to the COO or CEO.

Executives are mini-founders of their business units, Abel argues. They want the vision, not just the ROI spreadsheet.

The rewrite test for any cold outreach: if this executive brought your product to a board meeting, what exact sentence would they use to describe what it allowed them to do? That sentence — two or three words — is the only thing worth sending.

A 25–35% enterprise win rate is healthy — and if yours is higher, you've already mispriced the deal

The benchmark most salespeople aim for — 50% or better — is wrong. Abel puts the healthy enterprise win rate at 25–35% from qualified opportunity to signed contract. Below 25% means something is broken upstream. Above 35% means the price is too low.

The logic is structural: enterprise executives talk to each other constantly. "You have to assume the market talks. Especially at the corporate executive level." Charging one team $50K while another pays $500K destroys pricing integrity across an entire segment — and someone in a founders' WhatsApp group will eventually ask what everyone else paid.

Pricing conversations belong in one setting: one-on-one with the champion, post-demo, after the group is already excited. If someone pushes during the demo itself, give a range — "somewhere between $150K and $250K with some dependencies" — and close the specific number in private.

When the champion says they can't go to bat for the number, put the constraint back on them. "I need your help to tell me how to make this work." Don't negotiate with yourself. Let them name the first number — they might ask for $20K off when you would have gone much lower. A two-year deal structure lets year one carry a discount while the full value lands in year two.

Show only 20% of the product — the slice that maps to what you learned — because every irrelevant feature unravels the narrative you spent weeks building

Showing a full product in a group demo is one of the fastest ways to lose a deal already won. Abel is direct: "80% of the value comes from 20% of the product, and you have learned on these previous calls what that 20% is."

When stakeholders see capabilities they'll never use, the internal calculus shifts from "this solves our problem" to "we'd be paying for half a tool." That pivot happens in the room, in real time. "You've just unraveled all the work you've just done."

Write down in advance which two or three capabilities appear in the demo — and which don't. The deliberate omissions matter as much as the inclusions. When someone leans in and asks "can it also do X?", the response becomes a gift: "It's so funny you say that, we just released this." Now the product feels built for them.

Enterprise sales is "super super super tight narrative and framing," Abel says. Every call before the demo exists to narrow the frame until the group demo feels inevitable — the product arriving at exactly the problem they described, in exactly the language they used.

Run a two-to-three day pilot with three named users, co-authored success criteria, and a close date agreed before anyone logs in

Seventy-two hours. That's Abel's preferred pilot window — not two weeks, not an open-ended evaluation. Time-boxing to 48–72 hours shortens the sales cycle by two weeks and prevents what she considers fatal: users logging in and "meandering" without a defined task, spending half a day in the product without reaching the magic moment.

Before access is granted, co-author a one-pager with the champion: three specific tasks, three to four named users (not the C-suite executive — they're not the user), defined success metrics, and the projected close date. "What does success look like?" needs an answer in writing before the pilot starts, not in the debrief after.

If the product requires meaningful integration, charge for a longer pilot and credit it back on signing. "If they're willing to pay, that is a huge, huge signal." Payment converts a passive evaluation into an active commitment — they've already won the internal argument.

Abel's post-pilot benchmark: 80% success rate. Below that, the product isn't ready, or the upstream qualification was too optimistic.

The information gap is the moat — and accumulating it is still deeply human work

What Abel describes isn't really a sales process. It's a discipline of deliberate information accumulation — each call, each pre-call, each text sent five minutes after a demo exists to widen the gap between what you know and what every competitor walking in cold will ever know. That gap is the actual product being sold: not the software, but the vendor's demonstrated understanding of the organization. That's what earns the trust needed to move real budget.

Draft the outreach with AI. Earn the intel the old-fashioned way.

---

Topics: enterprise sales, B2B sales, founder sales, sales process, sales playbook, outbound, deal closing, pilot programs, procurement, pricing strategy, demo strategy, sales benchmarks, champion building, information advantage