84 minutes of enterprise sales alpha | Jen Abel
In a Nutshell
Enterprise sales succeeds through 15 micro-steps rather than the standard 5-stage pipeline, with the intro call being the single most important meeting to extract priorities and build internal champions before any demo. The alpha comes from controlling the process—pre-demo calls, 2-3 day pilots, and post-demo debriefs with champions to gather intel competitors never get. Win rates of 30-35% are healthy; higher rates mean pricing is too low.
These notes were generated by AI and may contain inaccuracies.
The conversation covers the full enterprise sales lifecycle step by step, which is closer to 15 steps rather than the commonly assumed 5 steps. Most people ignore many of these steps. The process is identical whether selling a $100,000 solution or a $1 million solution. Enterprise organizations are more sensitive to the sales process than to product demonstrations.
Enterprise win rate is typically 30-35%. If win rate exceeds this range, pricing is too low. The most successful salespeople are not formally trained salespeople. Using traditional frameworks like BANT (Budget, Authority, Need, Timing) commoditizes the seller. Approximately 90% of salespeople are executing the process incorrectly.
SpaceX serves as the case study, specifically targeting the legal function. Legal represents the largest budget line item in enterprise budgets, sometimes 3-4 times other budgets. Legal budgets are perpetual with always available additional funding. The target is a non-technical team within a technical organization.
Two valid entry points exist: the chief legal officer (or equivalent title) or N-1 (one step removed, typically VP or director level). Targeting anyone below N-1 risks communication breakdown through telephone game effects and learning user value rather than executive value.
A compressed storyline must land immediately to the objective they want to solve. Beyond AI mandates, the alpha represents what the executive uncovers and unlocks by bringing in a net new tool. Bringing net new tools is inherently risky, so the value proposition must be substantial enough to justify executive sponsorship.
The Pinsir model involves simultaneous outreach from two directions: founder reaches out directly to the chief legal officer, while the AE reaches out to the N-1 contact. The goal is that at least one responds, and the contacted person loops in the other party. This creates a parity of rule where each can reference the other's outreach.
Use AI tools like ChatGPT to identify potential N-1 targets by querying for the chief legal officer and their deputy at target companies. Verify results through LinkedIn searches. Everyone is likely targeting the same executive names, making differentiation critical.
Cold calling works for non-technical roles. Email, LinkedIn, and Twitter are viable channels. Enrichment tools like Lenlist provide email addresses. The critical factor is crafting a message that stands out among hundreds of incoming emails.
The pitch must focus on how the product helps executives rethink their business model and team structure, not merely reduce resources. The litmus test is whether bringing the product to a board meeting would allow the executive to demonstrate needle-moving impact to their COO or CEO.
The intro call is the most important call because it sets the tone for how prospects perceive the seller and their craft. All information edge is gained on this first call. Keep it super informal with no demos or slides. Conduct a 30-minute one-on-one dialogue.
Open by stating the call will be kept super informal and may not require the full 30 minutes. Request to swap intros and offer to schedule a deeper follow-up if appropriate. Always let the prospect speak first to gain information before framing responses.
Ask whether they have an AI mandate and how they're thinking about their current work processes. Inquire what they want to achieve by 2027 and whether anything needs to change. Ask if there's measurement for their goals and why the timing matters now versus waiting another year.
Continue probing with questions about what matters most, what they want to own, and chronological priorities. The more digging occurs, the more information prospects provide. Balance question volume with reading the prospect's openness—some are poker faces while others are more forthcoming.
Never bring a recorder to the intro call. Recording prevents prospects from being open and vulnerable. Even without explicit recording, assume prospects operate under the assumption that calls might be recorded.
Some people are poker faces and some people are not. You will be able to go much deeper with some and not deeper than others. You just have to improv. After you have that intel and can understand the frame you're going to take, you can give them the pitch. Every single conversation has a storyline that looks slightly different. There is no scripted pitch or frame for any call because it feels artificial. They feel it. It feels like you're putting them into a square box.
The best thing you can do is listen actively and then feel confident enough to craft the pitch around what they just shared. In enterprise sales, it's so hard to hire for because the more someone is trained in sales, the less natural it feels. The most successful salespeople are not trained salespeople. That's why founders are so good at this. They don't give themselves enough credit. What are they not good at? Probably following the process. What are they great at? Pulling out information, pulling on strings, getting people excited by vision. No one can do that better than they can.
Two to three out of every four calls there's something real. One out of every four calls requires disqualification based on maturity. If you're an enterprise executive or enterprise account executive, your job is to know who to talk to. Your job is also to quickly disqualify someone. The qualification question is most people are not going to be qualified, not because you're talking to the wrong person, but simply because of maturity.
Getting them to share a bunch may feel tricky like you're tricking them into sharing, but really they have problems they want to solve and you're there to help them solve a problem. Why would they not want to share what they need help with, the problem, and their priority? Their job is to buy solutions to these problems. That's why they have budgets. The fastest way to commoditize yourself is to go into a sales script like budget, authority, need, timing. That should be in the back of your brain. You never actually ask those questions.
The core lesson is focus on learning and extracting their priorities. Push them to get more real and pressure test how big of a deal these priorities are. Why are these important? You want them to ask you questions because that's when you know you're building a relationship. A client asked what the biggest learning the team has had this year. Every product needs to get better. Every product has a bug. Every product isn't able to do X or Y as well as they said. That's a really good question. They just want to know you're vulnerable because then it doesn't feel like sales.
In pricing, there's usually going to be two motions. Either they need the lowest cost way to do X because it's low on the totem pole and they really don't care if it's 60% of the way there. No one's getting fired over it. They'd rather just save budget. Or you're solving a problem that you can charge $250,000 to $500,000 because it is high risk. If you're dealing with legal, there's high risk to it. Missing information, being delayed on something, not having people understand the importance of some new regulation or law, not being buttoned up. Every organization looks different. Marketing and sales need numbers to drive them. For legal, they need to stomp out risk.
This comes back to the idea of alpha and upside. The more you can be in that bucket, the more you can charge, the easier everything gets.
Step one is the most important meeting. People spend so much time talking about themselves and miss all the competitive advantage to win the deal. As a buyer, it's so low pressure at that point. You're just exploring. Their openness to share more starts to clam up a little bit more once they're in the funnel and have to actually make a decision.
The stages most people have are intro, demo, proposal, contracting, close one or close loss. There are five stages. They're very basic. People usually go from an intro call straight to a demo. The demo is the carrot in the process. Everyone wants to see this amazing thing you just spoke about. The job is to make sure that when you do the formal demo, you have the right people on the call. If you don't, you lost your leverage to organize that group and rally them. More importantly, you never want it to feel like one person's baby. If you're selling to that director or that VP, you need to make sure that executive feels like they're part of it. They're helping craft it. They have their fingerprints on it. Vice versa, you want the C-suite if they want the actual users to feel like they were bought in on this too.
You want it to be a group effort. The person you had the intro call with is the champion. Most champions are one step removed. The C-suite executive has delegated this to the champion to navigate. Before you do the demo, get on another call with them. This call should be 15 minutes. Say you had so much fun on the first call and think there's a great opportunity to support them. You'd love to do a demo, but before doing the demo, you want to make sure you have the right people in the room and are demoing the right things. Ask them to help understand from the conversation what would resonate with the team.
Now you're collecting more intel. It starts to feel like they get to put their fingerprints on this. When demoing to this group, you want certain questions to be asked. They can ask questions in the meeting because they want them to understand the value. You're building this demo alongside this internal executive. None of your competitors are doing this. No other startup is taking these extra steps. You have the alpha of the intel they're giving from these conversations. They feel part of this journey. They trust you.
Spend 15 minutes trying to figure out or 30 minutes. Sometimes they won't give that much more time, but ask for 30. Do 15 and say here are the five different things that can be gone into. From the first conversation, it sounds like these two things matter, but show all five. They might say to do those two that were spoken about, but also show something else because it's part of their mandate. This will make it feel holistic. You've now mapped out the storyline with an internal partner on their end. You have the names of the right people. Close that call by asking if there's a time to look at everyone's calendar and put this on the calendar. Make the meeting an hour. The demo should be an hour.
Ask before this meeting if they want to do a pre-demo to maybe someone else on the team that would be excited by this before racing to the group demo, or should they just do the group demo. They know their organization better than anyone else and how pressing this need is. If they're less mature in knowing if they want something like this, they probably want to bring in someone else before the big group. If they're ready to really move into this, they probably are ready to go into a group. Figure out where they are on that maturity arc of their decision.
Push for pre-demo because it's more intel. If there's a pre-demo, there's a new colleague on the phone. For five minutes, catch them up on the things just learned from someone. Ask what they can add to that. What do they think? You're just collecting more and more intel along the way. You're building the business case for them. They feel like they're buying, not being sold to. You have two or three people already excited for the big group demo.
The worst thing you can do in the sales process when moving into demo is go into one straight demo with no problem. An enterprise organization might reach out because they're going through due diligence to see what was built. They'll ask to present to four or five people. Don't do it. You're either a checkbox and you want to remove yourself from being a checkbox. Or you're about to demo the product with no competitive intel. You've just lost the deal at that point.
Enterprise deals feel so close to who they are. It feels like it was built specifically for them. That's the whole game. The theme is alpha. The alpha comes from the team. It's information edge. Whoever is being competed against is not getting that information edge. In enterprise, you're always up against something. You're up against not doing anything at all, or you're up against a competitor who does something, or an incumbent. Most likely the incumbent. So many people just spew out a pitch with no informal and fun approach. People buy from people they like.
It feels very doable, not that difficult. It doesn't feel like it takes that much time to do any of these steps. Time is spent thinking about what to read between the lines of what they were saying. That's when follow-up happens. Those pre-demo calls before a big demo clarify all those questions. Ask if interpretation was correct. Is that the priority? They'll go deeper. The more questions that are inferred, the more prompting happens. It's like prompting humans at this point. Go deeper and deeper and deeper. The answers get so much more refined. The whole game is to slow down to go fast. All of this should be within a 90-day sales cycle based on their maturity.
To some people, this may sound like a lot of work. This is what separates companies and products that win deals versus not. You could have a better product, a better price, but just not executing through the sales process is shooting yourself in the foot. Or you're stuck having sold the enterprise on a $15,000 solution. How do you expand that? The whole game is expansion. If you're not going from $100,000 or $250,000 to $350,000 or $500,000 the following year, it's not an enterprise motion.
Step one is landing the meeting. Then running the intro call. Then the follow-up intro call, which is often ignored and a big opportunity to improve the demo. The demo is the carrot that's held that can be used to extract more. Step four is prepping the pitch and framing the demo. Now running a big demo. All the people involved in the demo are gathered. There might be somebody from their AI team that's going to support some rollout. All the people involved in this decision need to be at that table for the demo. That's how important it is to not rush it.
Before that demo on one of those calls, know who all these people are, what they care about, and what to avoid. The person built a relationship with can give all the intel. At this point, they want this to go forward. This is a great story for them. They found this amazing tool that's going to solve problems and get to put their name on it alongside one or two other people. For that demo, make sure exactly who's involved, what these people care about, and what a successful demo looks like for them. Ask them what looks good. People do demos all the time. What looks good? 30 minutes of discussion, maybe 10 minutes of showing, 10 minutes of discussion, 40 minutes in the product. What does the organization like?
On that demo, there are going to be people that were not a part of any of these calls. The job is to take a step back and restart with here is who we are, here is why we are doing what we are doing. It's fully in their frame. All the context is available to put this in their frame. For these net new people, they're thinking this was built for us. They're leaning in, being like this is very aligned with what is needed.
They have no idea you've talked to all these people. No idea you've learned what their challenges are. They're leaning in, being like this feels different. This is the whole part of being different. Not only is the product different, not only is the pitch different, the way the sales process is gone through is different. These guys are good. Let them talk. Let these net new people talk. Ask what they want to get out of the demo today to make sure focus happens for them. Lean a little bit more into these net new people so they feel the love.
When demoing the product, 80% of the value comes from 20% of the product. Learned on previous calls what that 20% is. Do not demo everything unless there's some reason to. The tight frame, the tight narrative crafted and spent all this time with just gets thrown out the door. It's like, I wouldn't use that. I wouldn't use that. Everything shared is really only over here. The whole thing could be blown up. Enterprises are like they don't know if they want to spend this much money for half the tool that wouldn't be used. All the work just unraveled. Enterprise sales is super tight project management and super tight narrative and framing. Owning that frame to exactly who these people are. That's why this role is so hard. It's a lot of improv. It's a lot of leaning in. It's a lot of reading between the lines. It's stuff that is doable. It's just psychology.
Most senior people it's very hard to get to that title if verbose, long-winded, and take things off track. That's the good thing about going after executives. Those people are really dialed in. No one takes a meeting off track at an executive level. Sometimes there are people that meander. Say love this conversation, can we park it because another call dedicated to that is wanted. If that needs to happen, then run with it.
There are two people that might be leading this. Might be the founder if still doing founder sales. Could be the AE or VP of sales. Signs that a salesperson is not doing a great job include the timeline from intro call to demo. How many conversations have happened between those two buckets of when people advance stages in the sales pipeline? Can the salesperson articulate exactly what they are going to be demoing, why they're going to be demoing it, and how they're going to open it? The demo looks different every single time. Never run a demo that looks the same. When everyone comes back to what's the scaled playbook, what's the scaled approach with this? When selling $100,000 minimum, it's the same effort as selling a million dollars. It could be selling a million dollar deal. It's hard. Cracking some of the largest logos that every single startup goes after. Have to be different. Have to take a different approach. It is not cram the pitch down their throat and hope that they want to buy something.
Feels like a job AI will not replace anytime soon. Not worried about AI replacing because there's so much about it that's just human. Do you vibe with this person? Taken intro calls with people probably did not appreciate how it was run. That's okay. It happens. When demoing, demo as narrow a slice of the product as possible that addresses their priorities and needs. They may feel like why do we need all this stuff? We just want this one problem. That's shooting yourself in the foot. Or let them guide. They might ask if it can also do this. It's so funny you say that. Just released this. Now it feels like it's built for them. They want to feel like it was built for them. They get alpha.
Step six is the post demo discussion. Also something everyone ignores. As soon as the demo closes, text the person that has helped guide to this point. Ask how they think that went. Can a call happen in five minutes for a fresh debrief? They will give a raw reaction. They haven't spoken to anyone. What do they think? How did it go? Do they think going deeper with anyone is needed before anyone solidifies everything that was said? Where do they think someone was lost?
There's always someone in the organization that's going to kill a deal. You need to protect against that as much as possible and make sure everyone is aligned and excited. The more intel you collect on these people, the better positioned you are to handle situations where someone goes quiet for two or three weeks. In those cases, you can prompt with: "Hey, I know you guys are still in the process of thinking through if this makes sense. Do you think it's worthy if I found 15 or 20 minutes with said individual to just hear their thoughts and maybe we can approach this a little bit more closely with how they would want to see it."
The champion is the individual that really wants this to come to life, who was there from day one. This isn't necessarily the C-suite executive - the executive could be the one shepherding it, but they need to make sure the people below them are brought in. The champion may be an executive and they're excited at this point, very excited for this to work out, they're on your side.
The best thing you can do, assuming you've built an incredible solution and you're this far in, is to control the time. You want them to go in for two to three days with specific users. Do not put your C-level executive into the product - they're not the user. You want the users of this to experience the magic and the power of what this is. Run, don't chart.
You could charge them for a pilot if it's an extended period of time, but the preference is to forego the money and do a two to three day pilot so you can control the sales cycle more. If they ask for a month and there's a good reason for it, charge for that. But for two to three days, let them see if they can get the value from it.
There are two different pilots you can run. A pilot that does not require their data to be in the product to get the value, or a pilot that you want to charge for because they need to see some level of integration on their end for the whole product to actually work. The focus here is on something they can get in two to three days that's a pretty light lift.
Time box it to two or three days. Don't make it two weeks. People will go in usually for half a day and get what they need out of it. Shorten your sales cycle by two weeks by doing two to 48 or 72 hours.
If you need something more integrated and it's a far more technical solution, do it for a month or two months, charge them for it, and then use that fee and credit it back to them if they move forward. If they're willing to pay, that is a huge signal. Especially if you're about to put in all this work, they have no problem paying for it. It's usually probably going to come out as services anyway because they're not buying technology, they're buying the services to go through it.
Make it a credit on the back end. Don't start the relationship off on a bad foot. Start the relationship off on a good foot.
When convincing them to do only two to three days, say: "This is what we typically do. Who are the three or four people we want to put in and assess the value from a user perspective." Make sure it's your person or the person closest to them. Don't put your C-suite executive in it - they're not going to go into the product.
Then two or three other people. Say: "We're going to do two or three days. I'm going to onboard you each differently. We're going to do two or three different onboard sessions before those two or three days. And I want you to go in and I want you to do these three specific tasks." Be very thoughtful and explicit and descriptive with what you want them to do.
Here's how we're going to measure success. Define that with them. Co-author that. That's no different than the thing that's a little bit longer where you require integration and buildout. Co-author it with them. What does success look like? What are the specific things they should be doing? They should not just be logging in and meandering. That puts the work back on them. Your job in sales is to take all the work off their plate, 99% of it, and help them discover the magic.
You might have one of those users that's like, "Oh, I didn't like it." In that three-stage process, ask: "What didn't you like? What wasn't clear? What wasn't obvious? Where did you get lost?" The tighter it is, the less people get lost. The more grounded it feels and the more consistent the experiences. You don't want people having different experiences.
Before putting everyone in the pilot, work backwards: if this is successful, how do we get this deal through? One is: when do we want to get signatures on these papers? Let's work backwards from there. Do we think we can get this closed by the end of next month? Who needs to be involved in that? Do you have a procurement lead that we should be educated in this process? Push them a little bit - you're project managing it. Is there a security lead we should be working with to run due diligence on the product? Is there someone in legal or is there a way for me to draft the paper to make this make sense now?
You would have already gone through pricing discussions with them post-demo. Try to hold out on talking about pricing until post-demo because they might assume this is three times what I'm spending and not know why it's three times, because there's all these other people that might not have been involved in those initial discussions. Talk through pricing post-pilot once everyone's excited.
If they're this far along, if they're really concerned about pricing, they would have brought it up by now. These are the little cues like, "Okay, I think I could probably push them a little bit here." If they ask and they push, give them a ballpark: "Well, it depends, but let's say it's somewhere between 150 and 250 and there's a lot of dependence on that."
Work with your champion to say: "Listen, here's what the price is. I know you know why we price it this way. Before you put this in front of anybody, how are you going to make the case? Where are you going to cut? How are you going to defend it? How can I build out a slide to defend this for you and show you the ROI?" Let them tell you. You don't have to go blind into it.
If they come and push back and say, "Listen, I don't know if I can go to bat for this," respond with: "I hear you. Let's work on this together. How can what do you feel comfortable going to bat with? And can we do a step up for year two to get to the actual full value of what we know we charge?"
Do pricing one-on-one with the individual you've been working with because they will help. They might say, "Okay, I think we're all aligned." This is what's usually going to happen. There are three answers: we're all aligned, I'm not too concerned about this, or I don't know if I feel comfortable going to bat with this number.
When they say they don't feel comfortable, say: "Okay, I hear you. Let's take a step back. Let's figure out how to make this work." Don't say you're going to discount. Don't throw out numbers. Be like, "I want you to tell me how to make this work." This is the one part where you want to put it on them because they might come back and say, "Is there any way we can cut 20K?" And you might have been willing to go much lower than that. You don't want to negotiate with yourself. But work with them. You've gotten to this point. You've shown so many people. Everyone's excited. This is when you know you can win them over through the co-authorship. And remember, you can always do the full value in year two and sign a two-year deal.
Give access to three to four people. Very small. Very tight. Who are the power users? Who are the people that are going to be in on a daily level? You don't want everyone in there. You want it to feel like they're buying into it too. You do want your champion, that one individual that's been giving you all this intel, to be part of the pilot because you want them to get you prepped for everything.
If your product is going to take a month to even get onboarded, that's when the two different pilots come into play: show you the value in two to three days, or show you the value in 30 days for a 30-day value charge and credit it back to them. But know that your sales cycle is going to probably be a month longer because of that. But that's okay because you're probably charging more anyway.
Your price should be predicated on your sales cycle. If you can get a deal done in 90 days for 100K, do that all the time. If it takes nine months to get a deal done, you probably should be charging 250-300K.
Opinions on forward deployed engineers sway back and forth. Is an FDE there because the product's super hard to navigate or is it there because you're taking the work off their plate? It's good if it's taking the work off their plate and accelerating and controlling the situation. But if you're using an FDE because your product's so gnarly and hard to do that they can't do it on their own, that's a bad sign.
The original idea of forward deployed engineers was they work at a company inside of your company building custom software for you to solve your problems and then they figure out how to make that a broad product they can sell to other people. An FDE is great for an expansion or a land, especially if you're talking about something like Palantir where it's much more complex. But they're also charging multi-million dollar deals. If you're selling a 100,000 dollar deal and you're pulling a forward deployed engineer, your economics are going to get messy. You will not make money if you have a full-time engineer salesperson sitting there working on this.
There's a lot of folks in account management whose job is to service and expand and upsell and they just take on the title of FDE so they're just another salesperson. Palantir people called FDEs at most companies "sparkling sales engineers."
Because you've talked about the timeline to if this is successful, what does that look like? Run this before you put everyone in it because you might want to push out the pilot. If they're like, "Hey, listen, this is probably going to be another quarter," put the people in the pilot now because now you've lost all the momentum you need to continue. You need the steps to happen. So use that: "Hey, if this is a successful pilot, how far out are we from a commitment from you guys?" If they're not ready in a month to roll this out if this is a huge success, then wait on doing the pilot. You may lose that momentum. You've already exhausted all the stages. You don't want to do that. You want the stages to align with how they're thinking, but you want to project manage as tightly as you can.
Everyone knows the traditional five steps: intro, demo, proposal, contracting, and then closed won or closed loss. Those are the typical buckets. But that's not how you run the sales. Those are buckets to understand how to understand a weighted forecast. A proposal or something mid-funnel might be weighted at 50% of the deal value for the pipeline. Something in contracting might be weighted at 80% and something in intro might be weighted at 10%. That's what those stages are for. That's not the stages you take a client through. Those are just the broad buckets.
A lot of people use those buckets to say, "Okay, there's about five different meetings that need to happen" when it's like, no, there's like three meetings, maybe up to five meetings in each of those buckets that are critical to get the deal done. For a million-dollar deal, you want to have more of those upfront meetings. You always want to know who the executive sponsor is. For a 100K deal, you probably can accelerate it a little faster, again ensuring that they're qualified.
90% of founders and salespeople are doing it wrong, treating it like this five-step process. Enterprise sales is mirroring their buying process. It's trying to control their buying process. It's not plopping these people into your sales process.
You can send a survey. They might want to send a survey. Get the intel or do one-on-one to each of these users. Or you can have your champion internally discuss and say, "Hey, how was that?" You need to make sure that you are mirroring their experience from a technical perspective - how much time did they spend in the product? Did they run into any bugs? What were they using the most of? Because you need to be prepared going into that call to say, "Hey, I know we gave everyone those three things, but most people only spent it on two. Why?" That might be okay, but you don't want them to be like, "Oh, well, you know, we wish it did this." Well, yeah, but no one spent time on that. We do do that, but no one spent time on that. So you just need to control also that you're capturing what they did in those pilots and making sure that you're syncing up.
Or you could go to your champion and be like, "Hey, I know so and so logged in for like 15 minutes today. They didn't get past step one. Don't tell them what they're doing. You shouldn't even be, but they didn't get past step one. Do you want to check in on them and make sure they're having a good experience?" Use your champion to guide them with where they should be focused as well because at the end of the day getting a deal done at the enterprise, it is set up to have as much friction as possible. There's people that will kill the deal, then you got to deal with procurement, then you got to deal with legal, then you got to deal with finding the executive sponsor, which usually comes in the very top of the funnel. But there's so much friction to get a deal on the project management and the individual on the inside. That's your key.
Many people naturally want to avoid confrontation. They won't want to say this is not going to work, we don't want this. They're going to probably be like, "It's fine. It's good. It's good. Oh yeah. Everything's PCs." So a lot of this process is to pull out: "Okay, here's the concern. Here's the problem." When you're in this, this is why your internal champion is so important. When they go quiet on you, that's when you know. This individual, if they've spent enough time with you, they will call you and be like, "Listen, if I'm reading the tea leaves, we should sit on this for a minute. Let's repick this back up." That's why having someone on the inside is so critical. The easier approach is just to stop responding and just hope that the salesperson understands they're not excited.
Once something is qualified, meaning you're speaking to the right person, they are excited by the alpha, they admit that there's change that needs to happen. Notice the emphasis on change rather than problem. People get so fixated on problems which are important, but everyone speaks to the same problem and it commoditizes you, which is why it's better not to overly emphasize it.
A healthy win rate for enterprise is actually probably going to surprise you. It's not 50%. Of all sales qualified leads or opportunities, a healthy win rate is usually around 30 to 35%. From qualified lead to qualified signed contract, you're closing anywhere between 30 to 35%, maybe slightly less, maybe 25 to 30%. If your win rate is higher than that, your price is too low. There's a lot of part of the market that's just not in a maturity perspective to take you on. And that's healthy. Those are all the chasms. It's better off keeping your price high than winning more often because the market talks. The worst thing you can do is charge somebody's friend 50 and somebody else 500K. They talk. People talk. The market talks. You have to assume that.
The amount of deals that come that boomerang a year later of the ones that have lost, that's probably another 25%. So it is totally normal and natural for deals to not advance, but a healthy win rate in the enterprise is typically between 25 and 35%.
From qualified lead to coming out of demo, you'd lose half. From demo, that gets you to 30%. From demo to post-demo, the more you move down the funnel, the less wide those numbers are. If you're doing a really good job targeting the right people, maybe 50 to 75% of those people move to a qualified lead. Of that, then another half move to demo, and then from there...
Post-pilot success rates should reach 80% when proper deal qualification has occurred. If success rates fall below this threshold, either the pilot itself has issues or qualification was inadequate. Smart buyers consistently request pilots as part of their evaluation process.
After a successful pilot, document the agreed timeline in an email for the champion to forward to procurement. Include pricing details predicated on signing by a specific date, along with incentives for meeting that deadline. Create urgency through time-bound offers such as free months of service.
Send contracts as Word documents rather than PDFs, since procurement teams will always redline documents. Provide the option to use either your paper or theirs, recognizing that using their paper may be faster for meeting deadlines. Most enterprise environments use Microsoft Word exclusively and cannot access Google Docs.
Procurement represents a potential deal killer even when internal stakeholders love the product. Business unit leaders cannot authorize payments directly - all funding must flow through finance teams pulling from approved budgets. Never begin implementation, onboarding, or any work until contracts are fully signed.
Procurement is frequently used as an excuse to avoid delivering negative feedback. The actual procurement process typically spans 30 days of legal back-and-forth, with procurement's role being alignment with purchasing requirements rather than deal termination.
When receiving redlines, accept straightforward changes immediately. For extensive redlines, arrange a live call with legal teams to work through issues rather than engaging in lengthy email exchanges. Focus negotiations on business-critical terms while releasing less important concessions.
When procurement provides their paper, expect extensive terms requiring redlines - this is standard practice. All terms remain negotiable, but prioritize battles carefully. The deal will not collapse over reasonable negotiation points at this stage.
Identify the actual signatory before routing documents, as this may be the CFO rather than the executive sponsor. Ensure all internal stakeholders know who holds signing authority to prevent delays. Once signed, celebrate the win but recognize that pipeline generation must immediately resume.
Expansion opportunities fall into two categories: known product extensions that emerged during the sales process, and new use cases discovered through deeper customer engagement. For early-stage companies closing their first 10 enterprise customers, founder involvement becomes essential for identifying custom product needs and potential service offerings.
Despite the focus on ARR and recurring revenue, services represent the largest budget line item for most organizations. Buyers are accustomed to purchasing services alongside software, including consulting and professional services. Budget allocation for services remains consistently available.
When prospects indicate the timing is not right, buyers should communicate this directly and immediately rather than prolonging uncertainty. Timing issues or organizational maturity gaps represent the most common reasons for hesitation. Sometimes selling services first provides a pathway to technology adoption later.
Sales professionals may challenge hesitation by referencing earlier stated needs and pushing for creative solutions. However, legitimate barriers such as ongoing acquisitions or competing priorities must be respected. When prospects express uncertainty about organizational readiness, direct acknowledgment of the gap can sometimes prompt internal action to address it.
Enterprise sales processes share significant similarities with product management approaches, particularly in systematic problem-solving and stakeholder management. Both disciplines require deep understanding of customer pain points and collaborative solution development.
Personalized, authentic communication outperforms AI-generated content in sales contexts. Recipients can detect when emails are read aloud versus generated, making genuine voice and perspective essential for relationship building. Avoid boilerplate templates and AI-generated communications in favor of crafted, individual messages.
State Affairs is actively hiring multiple enterprise sales roles with direct training from experienced practitioners. This represents an opportunity to learn enterprise sales methodology through hands-on mentorship.
Keep Lenny's Podcast in your library
Save the videos and channels worth coming back to, and find them again in one place.
