enterprise sales
Is Your Sales Team Killing Deals in the First 30 Seconds?
How many times has a stranger called you or filled your inbox with a message that starts with their name and a generic company intro? Did it make you want to pay attention, or did you immediately hit “delete”?
For executives overseeing high-stakes enterprise sales, this isn’t just an annoyance—it’s a performance barrier. If your team is stuck in a “Me and We” mentality, they are burning valuable leads before discovery even begins.
The Problem: You Can’t Win if You Don’t Get to Play
Most sales and marketing teams default to talking about themselves. They lead with their history and their product features. In enterprise sales, this is a fatal error.
Unless you are a dominant market leader, your prospects don’t care who you are or where you work; they care what you can do for them. Every second spent on your “About Us” slide is a second lost in identifying the prospect’s pain points.
The Cost of Misaligned Messaging
When your team uses “me-focused” messaging, the consequences are immediate:
· Low Engagement: Cold calls and emails are ignored because they lack immediate relevance.
· Stalled Demos: Prospects tune out during the “logo slide,” reducing the probability of real engagement and follow-on from this point on.
· Failed Discovery: Without quickly developing rapport and a focus on the prospect’s specific business and terminology, your team will never uncover the deep-seated issues required to close a complex deal.
The Solution: Use a “Prospect-First” Framework
To fix your pipeline performance, your team needs to pivot to a PIE-based approach that leverages your perspectives, insights, and expertise to prioritize the prospect’s desired outcomes. Help them visualize that better outcome, using their terminology and scenarios, with your solution.
1. Establish Immediate Rapport
Before the call, find a “hook”—a shared hobby, a mutual connection, or a specific business challenge they’ve mentioned in forums or job postings. Connection builds the rapport necessary for a successful discovery.
2. Lead with PIE (Perspective, Insight, Experience)
Instead of introducing your company, lead with the problems you solve. Help them answer the “why you?” question by demonstrating expertise and a proven solution.
· The Shift: Instead of saying “We are the leading Kubernetes platform,” try: “About half of the executives I meet are concerned about unplanned outages, spiraling costs, and security exposure. Have these been concerns for you?”
· The Result: This adds instant credibility without making the conversation about you. It forces the prospect to engage with their own problems if they are truly interested in finding a solution. And if not, you both agree that there is no fit at this time and move on.
3. Skip the Ego, Show the Success
In your next demo, skip the logo page and the multiple feature pages. Move directly to a relevant customer case study from a similar industry. Discuss their specific issues and the measurable outcomes that must be achieved. This makes your solution relatable and positions your team as experts who can help, rather than just another vendor. Build rapport and earn that next meeting.
Audit your team’s outreach today. Are they leading with “We” or with “You”? If your messaging needs a strategic overhaul to better reach your future customers, contact me here. Let’s turn your sales messaging into a competitive advantage.
How is your team changing its approach to meet today’s better-informed yet more skeptical enterprise buyers? Let me know in the comments below.
Sales Discussions that Work
Selling is challenging work, and often, “we” (sales and marketing teams) make it even more challenging than it has to be. How many times have you seen a selling script, elevator pitch, or initial presentation that is long, boring, and undifferentiated? People have a short attention span, and nobody wants to interact with someone who does not listen to them or is pushy.

Your initial discussion is crucial to your success. Instead of going over a list of features, reading a slide deck, and telling why you and your product are so great, let’s try something else.
1. Understand why people buy. Any change has the potential to be difficult, risky, and painful. So, the pain they are facing has to be even greater, or they won’t bother changing. Your main job early on is to listen and try to understand their concerns. You may have a perfect solution, but if it doesn’t solve their pain, it holds little value to your prospect. This initial meeting is all about them.
2. At the start of the meeting, ask, “What would make this time well spent for you? What would you like to walk away from this meeting with?” Get them thinking about their problems and the value you may be able to provide, even if they don’t fully articulate them to you.
3. Ask questions and follow-up questions. People don’t lead with their significant issues, and someone unwilling to divulge anything likely isn’t a buyer. The more the prospect talks, the more you learn. So many sellers do not understand this simple concept. They want to dazzle you with features and demos – even if those things are not what the prospect needs.
4. Once you think that you have identified a pain, qualify and quantify it. For example, “You mentioned that your product release cycles are too long and complex. What is the business impact of that, and what would the impact be if you could reduce that time and effort by 50%?” Write that down, in their own words, because it could be vital later. If you manage to identify several pain points, review them and ask the prospect to identify the top three issues from the list, and ask why those three?
5. If you are giving a presentation, pull up the most relevant slide (customer problem/benefit slides work well here) and ask if this sounds similar to the problem they are facing. It can be a good starting point for getting the discussion moving in the right direction.
6. Don’t worry if you are not able to cover everything you intended, as long as the meeting is productive. I’ve also seen salespeople cut someone off and move on to a new slide rather than discussing something of substance. I was actually told once by a sales leader that five minutes of discussion is all that is required in an initial 30-minute meeting, because our goal is to pique their interest. That just doesn’t work.
7. Next steps. Keep in mind that your time is valuable, and qualifying out a prospect who is not a good fit is essential – it helps you avoid false hopes and lets you focus on people who might genuinely need your help. There are many ways the next meeting could go, but it’s best to ask the prospect. Would they like to expand the audience? Is there a specific issue they would like to address? Would they like a product demo or a technical discussion? Is something like a non-disclosure agreement (NDA) keeping them from opening up? Lack of engagement on their part is a huge clue. Be direct and ask the tough questions now to avoid wasting valuable time and effort later.
Here is a mini success story. In 2010, my team and I began selling the first commercial vector high-performance analytics database. There were several products already out that claimed to be 70x-100x faster than other products. Our pitch was supposed to be that we were 70 times faster than other products. That was self-limiting from the start and likely prevented people from contacting us.
After two months of minimal success (I closed a deal with a small hedge fund, which was the only sale in all regions), we started a weekly webinar called “Why Fast Matters.” The focus was on positive business outcomes rather than specific technology and features (“speeds and feeds”). We opened with some “What if?” statements, such as: What if you get answers from complex queries faster than your competitors? What if you could do that without the cost, complexity, delays, and limitations of a Star Schema or pre-aggregated data? What if you could do this on commodity x86 hardware? We would then briefly cover the breakthrough technology (which was a precursor to Snowflake) and offer a free half-day meeting with a consultant.
Within the first two weeks, we met with a company that was later acquired by PayPal shortly before eBay acquired PayPal. This company was about to spend $500K on a proprietary hardware expansion that would have only provided additional capacity for the following year. Their customers bought advertising based on queries against the last six months of their data. I asked the question, “What if they could query against five years of data and get answers faster than they do today? Do you think that would help them buy more advertising? Do your customers ever ask for this?” The response was that their customers frequently ask for 12 months of data and would be willing to pay more for these capabilities. Still, they did not have a way to do this cost-effectively.
I closed a $250K ARR subscription deal in two weeks, and they purchased $140K of commodity Dell hardware for our software to run on. They saved 20% over their planned purchase, and more importantly, they rolled out advanced querying capabilities (against six years of data) in less than a month. There was incredible value to them and their customers, and it generated more business for them. We would not have identified this need if we had primarily focused on features and technology.
As an aside, I was initially chastised for going off message, but after the Australian team adopted our approach and began closing deals, it became the new corporate standard. If something isn’t working, focus on finding ways to improve it. Even incremental change can be meaningful.
In the words of Tony Robbins, “If you do what you’ve always done, you’ll get what you’ve always gotten.”
Lessons Learned from Selling Kubernetes
Cloud-native, containerization, microservices, and Kubernetes have become very popular over the past few years. They are as complex as they are powerful, and for a large, complex organization, these technologies can be a game changer. Kubernetes itself is a partial solution – the foundation for something extraordinary. It can take 20-25 additional products to handle all aspects of the computing environment (e.g., ingress, services mesh, storage, networking, security, observability, continuous delivery, policy management, and more).
Consider the case of a major Financial Services company, one of my clients. They operated with 200 Development teams, each comprising 5-10 members, who were frequently tasked with deploying new applications and application changes. Prior to embracing Kubernetes, their approach involved deploying massive monolithic applications, with changes occurring only 2-3 times per year. However, with the introduction of Kubernetes, they were able to transition to a daily deployment model, maintaining control and swiftly rolling back changes if necessary. This shift in their operations not only allowed them to innovate at a faster pace but also enabled them to respond to opportunities and address needs more promptly.
Most platforms utilize Ansible and Terraform for creating playbooks, configuration management, and other purposes. Those configurations could become very long and complex over time and were prone to errors. For more complicated configurations, such as multi-cloud and hybrid environments, the complexity is further amplified. “Configuration Drift,” or runtime configurations that differ from what was expected for various reasons, leads to problems such as increased costs due to resource misconfiguration, potential security issues resulting from incorrectly applied or missing policies, and issues with identity management.
The surprising thing was that when prospects identified those problems, they would look to new platforms that used the same tools to solve them. Sometimes, things would temporarily improve (after much time and expense for a migration), but then fall back into disarray as the underlying process issues still needed to be addressed.
Our platform used a new technology called Cluster API (or CAPI). It provided a central (declarative) configuration repository, making it quick and easy to create new clusters. More importantly, it would perform regular configuration checks and automatically reconcile incorrect or missing policies. It was an immutable and self-healing Kubernetes infrastructure. It simplified overall cluster management and standardized infrastructure implementation.
All great stuff – who would not want that? This technology was new but proven, but it was different, which scared some people. These were a couple of recurring themes:
- The Platform and DevOps teams had a backlog of work due to existing problems, so there was more fear about falling further behind than confidence in a better alternative.
- Teams focused on their existing investment in a platform or on the sunk costs spent over a long period, attempting to solve their problems. The ROI on a new platform was often only 3-4 months, but that was challenging to believe, given their own experiences on an inferior platform.
- Teams would look at outsourcing the problem to a managed service provider. They could not explain how the problems would be specifically resolved, but did not seem concerned about that lack of clarity.
- There was a lack of consistency on the versions of Kubernetes used, the add-ons and their versions, and one-off changes that were never intended to become permanent. Reconciling those issues or migrating to new, clean clusters both involved time and effort. That became an excuse to maintain the status quo.
- Unplanned outages were common and usually expensive. Using the cost of those outages as justification for something new was typically a last resort, as people did not like acknowledging problems that put a spotlight on themselves.
- Architects had a curiosity about new and different things, but often lacked the gravitas within business leadership to effect change. They were usually unwilling or unable to explain how real changes happen within their company, or introduce you to the actual decision-makers and budget holders.
Focusing on outcomes and working with the Executives most affected by them tended to be the best path forward. Those companies and teams were rewarded with a platform that simplified fleet management, improved observability, and helped them avoid the risky, expensive problems that had plagued them in the past. And, working with satisfied customers who appreciated your efforts and became loyal partners made selling this platform that much more rewarding.
Finding the Right Fit in Sales
I won’t sell a product or service if I don’t believe in it or in the company behind it. But that is only part of the picture. Not all products or services fit everybody, but most are a fit for somebody. Whether you are a seller or leading a sales team, understanding the best-fit use cases helps you create a repeatable sales motion that allows you to:
- Find and prospect the best candidate companies.
- Demonstrate benefits for a credible and relevant use case.
- Find a sponsor who benefits from your offering.
- Accelerate the deal velocity – even in a large enterprise business.
- Close large deals faster – and more of them!
When I started at my last company, I was told that the typical deal size was $75K-$80K, having a 9-12 month sales cycle with a midsize company. I was selling a Kubernetes Fleet Management platform, and I quickly found that most midsize companies lacked the containerization needs that Kubernetes provides. Most also needed to gain the skills required for fairly complex solutions, which can take months.
Large Enterprise companies had the need and the expertise to support Kubernetes, which started my profile development exercise. Large companies with a corporate standard containerization product were less likely candidates with a much longer sales cycle. Financial Services companies require strong end-to-end security and cannot afford breaches (reputationally and actual costs). Therefore, they had larger budgets and immediate needs, so they became a primary focus.
While looking at the environments for these companies, it became clear that an initial deal size could easily be in the $500K – $1 million range. And, if you successfully delivered what you promised, there could be several more significant follow-on deals. The icing on the cake is that by selling those companies what they need, solving significant problems or concerns, and treating them like the valued customers they are, they would reward you with loyalty and long-term business.
Finding the right fit for your product or service takes analysis, investigation, testing, and time. Getting this right provides the perfect opportunity to be successful and scale the results through the entire team. It also provides credibility when new customers are willing to speak with prospects and sing your praises. Success breeds success.



