Fast forward to today. Buyers are highly informed. Categories are crowded. CFOs fiercely guard budgets. Multiple stakeholders are involved in almost every meaningful enterprise deal.

A decade ago, a good enterprise seller could create conviction where there was only interest. Today, in mature B2B categories, the more critical skill is often determining whether enough internal conviction already exists to build upon.

The fundamental question is increasingly not: How do I convince this prospect to buy?

It is: Is there enough here to justify trying to convince them at all?

Welcome to the era of qualification.

Why the “Challenger Sale” Became Good Wine

This does not mean persuasion is dead. Methodologies like the Challenger Sale still hold immense value. Teaching, tailoring, and taking control absolutely work. But you shouldn’t act like a professor with a buyer who already knows the category, the competitors, the pricing and the alternatives inside out.

I increasingly think of Challenger as good wine. It is still valuable. Yet, it is not water. The approach is powerful when the situation calls for it. Consequently, it becomes counterproductive when you pour it into every conversation.

Persuasion has become selective. Qualification has become foundational.

And modern qualification is not discovery. Furthermore, it is not BANT. Nor is it a MEDDPICC checklist properly updated in the CRM.

The new era of qualification seeks evidence, not just answers. Here is what in my experience it looks like in practice.

Evidence #1: Language Is Not Commitment

A CEO I’m working with recently came to me frustrated. “They said we were the preferred vendor. They said they wanted to sign before the quarter ended. Then they didn’t sign.”

There is a massive gap between: “We want to sign.” and: “We will sign.”

But even “we will sign” is not enough. Who exactly is signing? Is Legal fully aligned? Has Procurement approved the vendor? Are all the necessary stakeholders on board? What still needs to happen internally between today’s conversation and the signature? And who owns each of those steps?

This is where “happy ears” become expensive. We hear a positive statement and unconsciously convert it into evidence supporting what we already want to believe. Modern qualification requires almost the opposite reflex.

Every positive statement should trigger the next qualification question, not the next forecast increase.

The buyer probably isn’t lying. The person telling you they want to sign may genuinely want to sign. But wanting something to happen and having an organization capable of making it happen are two completely different things.

Your job is to understand the difference.

Evidence #2: Make the Buyer Work

In another case, we were discussing how to present ROI to a key Prospect Account. He proudly noted: “We already have a business case simulator that we build for them.”

My question was: How central is it to the conversation?

If you are the one asking for the data, running the numbers, and building the business case alone, you have lost a massive qualification opportunity.

A business case simulator can do much more than calculate ROI. It can qualify the customer. Make it a collaborative process. Ask the prospect to bring their own numbers. Agree on the assumptions together. Understand what happens if a particular metric improves by 5%, 10% or 20%. Bring whoever owns the underlying data into the conversation.

Suddenly, you are learning things that no discovery checklist will tell you. Will they give you the data? Will they invest the time? Can your champion bring other stakeholders into the room? Do people internally agree on the problem? Does anyone actually own the metric you’re proposing to improve?

Most importantly: Will the customer do some work?

Because commitment is easier to observe than intent. Good qualification doesn’t only ask better questions. It creates small commitments that generate evidence.

The prospect doesn’t just tell you the project matters. They behave as though it matters. That is a very different signal.

Evidence #3: Qualify the Future They Want

I recently reviewed a stalled deal with a large retailer. On the surface, the scale-up’s product had proven value, clear ROI, and a strong historical relationship with the customer.

Yet something had changed. The customer organization had increasingly become attracted to what we started calling the Holy Grail: one integrated platform capable of solving most of the problems currently addressed by several specialized solutions.

At that point, you don’t simply need to convince them that your specific best-of-breed product is superior. You need to ask a different question: Are they psychologically and organizationally available to buy the kind of specialized solution we actually sell?

Around the same time, I spoke with an experienced seller from a competing specialized vendor. He had learned to recognize the pattern. Whenever he realized that the customer was pursuing the Holy Grail of an all-in-one platform, he knew his probability of winning had dropped dramatically.

Not necessarily because the competing product was better. The customer was buying a philosophy: integration, consolidation, fewer vendors, one platform.

That is sophisticated qualification. Not: Do they have budget? Not: Do they like our product? Not even: Can we demonstrate ROI?

But: What kind of solution has this organization already decided it wants to buy?

Sometimes you are not losing a feature comparison. You are on the wrong side of a strategic conviction. And when the answers don’t align, sometimes the right thing to do is to bless the loss.

Walking away early can create more value than dragging a fundamentally misaligned deal through your pipeline for another six months.

Evidence #4: Your Champion Isn’t Your Decision System

A friendly contact who loves your product is great. But that doesn’t necessarily make them a champion. Modern qualification demands knowing whether that person can actually move the decision system.

Do they share internal information a vendor normally wouldn’t have? Will they consistently keep their commitments? Can they introduce you to the stakeholders you need? Furthermore, do they have influence inside the organization? Are they willing to spend some of their internal political capital moving the project forward? Ultimately, do they personally have something to gain if the change succeeds?

A friendly contact gives you access. A real champion creates movement.

And in complex enterprise sales, even that may not be enough. You are rarely selling to one person. You are selling into a decision system.

So the question isn’t simply: Is my champion convinced? It is: Can this person mobilize the organization required to make the decision?

Tailoring for group consensus becomes more important than tailoring only for individual buy-in.

A champion saying “yes” is information. A champion mobilizing others is evidence.

Qualification Is Not a Stage in the Funnel

This is perhaps the biggest shift. Qualification is often treated as something you do at the beginning of a deal. You qualify the opportunity, enter the information into the CRM, move it to the next stage and start selling.

But in complex B2B, qualification should become progressively deeper as the deal moves forward.

At the beginning, you may be qualifying pain. Is there actually a meaningful problem? Then priority. Is solving it important enough compared with everything else competing for attention? Then commitment. Will the customer invest time, data and internal resources? Then mobilization. Can your champion bring the decision system with them? Then buying philosophy. Does the organization actually want the kind of solution you sell? And ultimately, organizational readiness. Can this company absorb the change required to produce the outcome you’re promising?

Pain → Priority → Commitment → Mobilization → Buying Philosophy → Organizational Readiness.

The deeper you move into a complex deal, the less useful stated intent becomes. You need behavioral evidence.

The Hidden Cost of Bad Qualification

This is why a badly qualified opportunity does more damage than simply wasting a salesperson’s time.

Every additional meeting consumes resources. Likewise, every unnecessary pilot burns time. Each Solution Engineer pulled into the wrong opportunity carries an opportunity cost. Furthermore, every founder spending three months chasing the wrong enterprise logo is not doing something else. And ultimately, any badly qualified opportunity sitting in the pipeline corrupts your understanding of the business.

This illusion makes pipeline coverage look healthier than it is. It contaminates your forecast. Consequently, it can make you think you have a conversion problem when you actually have a qualification problem. And eventually, such noise can influence hiring and investment decisions based on demand that was never really there.

Knowing When Not To Sell

For years, enterprise sales culture celebrated persuasion. Overcoming objections. Creating urgency. Handling resistance. Never taking no for an answer.

There is still a place for all of that. But persuasion is expensive.

The modern enterprise seller needs to be skilled enough to create conviction when a real opportunity exists, and disciplined enough to recognize quickly when it doesn’t.

That means stopping the instinct to ask: How can I keep this deal alive?

And asking instead: What evidence would make this deal deserve to stay alive?

That distinction matters. Because the objective of qualification isn’t to kill opportunities. It is to concentrate your organization’s persuasion, expertise and energy where they have the highest probability of creating value.

The best enterprise sellers are still persuasive. They just know that persuasion is expensive. Qualification tells them where it is worth spending it.

Featured image: Jahra Tasfia Reza

The post The Era of Persuasion Is Over. Welcome to the Era of Qualification appeared first on Luigi Mallardo.

• First lane: automate the SMB motion, reduce friction, make it self-service, clean up the unit economics.
• Second lane: go deep into enterprise, land and expand, build an advisory board with the biggest players in the industry.
• Third lane: use the IP they had built to go to the top of the value chain — become a data infrastructure provider for the large channel partners facing an existential threat from AI.

I liked the metaphor. But I thought the CEO was asking the wrong question.

His question was: how do we execute across all three? The question that actually mattered was: which lane deserves the company’s next hire, next euro, and next year of management attention?

This is the swim lane trap. And I have seen it destroy more growth potential than bad product, bad timing, or bad luck combined.

One company. Different businesses.

A swim lane is not just a customer segment. It is not simply SMB versus mid-market versus enterprise. It is a complete combination of economics, GTM motion, people, metrics, and retention model. When you change lane, you are not adjusting your targeting. You are running a fundamentally different business.

When you look at this table, something becomes obvious. These are not two customer segments you can serve with the same team, the same funnel, and the same definition of success. They are two different businesses that happen to be sold under the same product name.

The swim lane trap begins the moment you treat them as the same race.

Trap 1 — Swimming in two lanes with the same team

I sat down with that founder some time ago. Recruitment space. Solid product. Real traction. Around 2M in ARR: A customer base that included five of the top twenty staffing companies in the world.

The numbers were interesting. SMB net dollar retention was around 82-85%. Enterprise net dollar retention was 145%.

Seven enterprise accounts represented roughly 40% of total ARR. The whitespace inside those accounts was enormous — same buying center, multiple countries, multiple divisions, years of potential expansion.

At the same time, the SMB base was churning at a rate that made it structurally expensive to maintain.

The business had two sets of customers. One set was telling them, clearly, that they were worth far more than what they were being charged. The other set was telling them, just as clearly, that the unit economics did not work.

The founder knew this. He could see both signals. And yet, the company was trying to serve both with the same commercial team, the same funnel, the same customer success motion, the same management attention. The same energy.

The insight that changed the conversation was simple.

These are not two customer segments. They are two different GTM businesses. The enterprise motion requires different sellers, different choreography, different success criteria, a different relationship model. The SMB motion requires automation, low touch, product-led growth. You cannot ask the same people to do both.

You can run multiple swim lanes but you cannot pretend they are the same race.

The trap here is not having multiple lanes. It is putting everyone in the same pool and expecting them to swim in different directions at the same time.

Trap 2 — Optimizing a lane that has reached its ceiling

The second case is different in context, but the trap operates by the same mechanism.

Ten years in the market. Two solid functional use cases with tangible ROI. €6M ARR. Approximately 2,000 customers. 90+% inbound. Average ARR per customer somewhere between €3K and €4K. Growth: flat.

In the years since the company was founded, the competitive landscape had changed completely. Well-funded all-in-one suites had entered the market, raised hundreds of millions, and were now competing for the same customers. The inbound channel that had built the business was producing diminishing returns. Marketing budget was the same. The output was less.

When I started working with the CEO, the internal conversation was still largely about inbound optimization. How do we improve conversion on the landing pages? How do we reduce the drop rate between demo scheduled and demo done? How do we make the customer journey cleaner?

These are legitimate questions. They are also the wrong questions.

At some point, improving conversion from 13% to 15% becomes strategically irrelevant when you do not have hundreds of millions in revenue. You are optimizing traffic flow inside a road that does not lead where you want to go.

The lane that built the business

The lane that built this company was the original specific use case for small and medium businesses, acquired through inbound, at low ticket sizes. That lane still exists. It still generates cash. It is a real business.

But it is not the business that produces growth in a market where competitors with 100 times the marketing budget are competing for the same customers.

The question was never how to optimize the existing lane. The question was what lane to build next, and how to protect the resources required to build it without cannibalizing the engine that was keeping the lights on.

What became clear was that this couldn’t be solved at funnel level. Before designing the next GTM motion, the company had to decide what business it wanted to become.

Only then could we start defining the next lane: going back to the original product strength, narrowing the ICP around the verticals where it had proven depth, moving toward higher-value accounts, and building outbound and partnership motions alongside the historical inbound engine.

This was not a pivot. The existing lane continued to operate. But it required building a second lane with protected resources, a different funnel, different people, and a different definition of success.

This second trap is subtler than the first case. The company knew the existing lane had reached its ceiling. The leadership knew a new lane was needed. But the gravity of the existing motion—the team trained on inbound, the metrics built around small tickets, the habits of a decade—kept pulling resources back toward the old lane.

The switch from optimizing what exists to building what comes next is the hardest organizational transition in Complex B2B tech. Not because the strategy is unclear. Because the existing lane is still alive, still generating revenue, and still demanding attention.

The hardest part: resource allocation

This is where most companies fail, not in the strategic choice, but in the operational consequence.

Deciding to build a new swim lane is easy. Every leadership team can draw a box on a slide. The decision that actually matters is what you are willing to stop feeding in order to give the new lane a real chance.

If you put all your commercial resources on the historical lane because that is where 90% of your revenue comes from, the new lane will never receive the attention it needs to develop its own momentum. The same applies when you ask the head of sales to optimize inbound conversion and simultaneously build an enterprise outbound motion, one of the two will die. Almost always the new one. Measuring both lanes with the same dashboard compounds the problem. A €300 MRR inbound conversion and a €50K enterprise opportunity are not comparable units. Treating them as if they were produces noise, not insight.

Every strategic swim lane needs protected resources, its own funnel, and its own definition of success.

This is not a principle. It is a precondition. Without it, the new lane exists only on paper.

Five questions before adding a lane

Before committing to a new swim lane, there is an important caveat: there is an opposite trap here too. Inventing a new swim lane because execution in the existing one has become uncomfortable.

A new lane is not a substitute for fixing poor execution. If the current market still has headroom, the economics work, and customers are pulling — adding another motion may simply multiply your problems.

With that said, five questions help separate the real strategic decision from the escape hatch.

One. Is the current lane still structurally capable of delivering the growth you need?
If the answer is yes, the priority is execution, not diversification. If the answer is no, the conversation changes entirely.

Two. Does the new lane have materially different economics?
Different ACV, different sales cycle, different retention model, different expansion potential. If the economics are not materially different, you are not adding a lane. You are adding complexity inside the same lane.

Three. Does it require a different buying and selling motion?
If the answer is yes, you may need different people, and you certainly need different choreography, incentives and metrics. You cannot simply bolt the new motion onto everyone’s existing job.

Four. Do you have evidence of pull, not strategic wish?
Retention data, expansion signals, inbound from the new segment, reference customers who expanded significantly. The new lane should already be whispering to you before you commit to building it.

Five. What are you genuinely willing to take away from the old lane to give the new one a chance?
This is the question that separates decisions from declarations. Every company says they are committed to the new direction. Very few are willing to visibly reallocate resources from something that is working to something that is not yet proven.

The fifth question is the one that determines whether the new lane actually gets built.

The GTM motion that got you here

Most B2B tech companies that reach €2M, €5M, or €10M ARR have built a real, working GTM motion. It is not glamorous. It is not the motion they will use forever. But it produced real results in real markets with real customers.

The mistake is not having that motion. The mistake is assuming it will scale indefinitely.

Every GTM motion has a ceiling.

The inbound engine that gets you to €5M may struggle in a saturated market. The founder-led enterprise motion that wins your first ten accounts may collapse when you need a hundred without the founder in every room.

Recognizing that ceiling is not failure. Staying inside it because that’s where the organization feels comfortable is.

The GTM motion that got you here may still be a perfectly good business.

It just may not be the business that gets you to the next stage.

 Subscribe to my newsletter for practical GTM insights, frameworks, and real stories for complex B2B tech leaders.

Featured image: Jan van der Wolf

The post The Swim Lane Trap: When Your Existing GTM Motion Becomes Your Growth Ceiling appeared first on Luigi Mallardo.

Picture a promising AI-native startup. They have a product that actually works. Solid seed investors. Two SDRs consistently booking 20+ meetings a month. Target deal sizes ranging from €30K to €120K. The founders are deeply involved, leading the GTM motion personally.

They are raising a new round of a few million, getting ready to scale. Everything looks exactly how a high-growth startup should look. Until you scratch the surface.

They haven’t crossed the €1M ARR mark yet. Still missing a few hundred thousands. The founders have already diluted their equity down to 50% before Series A.

Then, you look at the conversion rate from first meeting to closed-won: 3%.

The number itself didn’t worry me. What worried me was everything it implied.

The Pattern of Pipelines Not Converting 

If you enjoyed this post, you might also like:

 [AI Doesn’t Just Change The Product. It Changes The Business Case]

 [What to do when a competitor is in trouble]

 [The CEO-CRO Nobody Wants To Be]

 Subscribe to my newsletter for practical GTM insights, frameworks, and real stories for complex B2B tech leaders.

Featured image: Engin Akyurt

The post Why Too Many AI-Native Startups Destroy Value Before They Even Reach €1M ARR appeared first on Luigi Mallardo.

The more I work with AI companies, the more I realise they are not just competing with software. They are competing with human work.

For more than twenty years, enterprise software has helped people do their jobs better. Faster, more precise, more scalable. SaaS was built on a simple premise: give specialists better tools and they will produce better outcomes.

Today, AI is increasingly starting to do the job itself.

That changes something far more fundamental than the product. It changes the business case. And I think many AI founders are still selling as if they were selling SaaS. Same qualification, same pricing, same demo, same buyer.

Clearly, the product has changed. Yet, the GTM conversation often hasn’t.

That is the mistake.

The hidden mismatch

A typical enterprise AI deal looks healthy from the outside.

The champion is engaged. All goes well during the demo. The budget exists. Also the use case is clear. And the timeline is reasonable.

Inevitably, six months later the relationship becomes difficult. Because the vendor was selling one business case while the customer was preparing for another.

Two business cases. One product.

Most AI founders think the complexity of their enterprise deals comes from the product, the integration, or the change management. In my experience, the deeper complexity comes from something less visible.

Not two products. Not two buyers. Two business cases.

Business Case A — Augmentation

AI helps existing specialists do their work better.

For example, consultants use it. Engineers use it. Compliance teams uses it. Auditors use it. Ergonomic analysts use it. The process remains human. AI accelerates, improves, automates parts of it.

In this case the ROI is productivity, quality, speed. The internal champion is the operational lead or the functional manager. The budget is operational and can often be approved without direct C-suite involvement.

Business Case B — Transformation

Exactly the same product. Completely different economic logic.

The question is no longer “how much faster can my specialists work?”. The question becomes “how much specialist work will eventually disappear?”

In this case the ROI is labour substitution, reduced headcount growth, lower outsourced spend, or the elimination of entire categories of manual work. The internal sponsor is no longer the operational lead. It is the CFO. The COO. Sometimes the CEO. The budget is strategic, significantly larger, and requires a completely different approval process.

Nothing changed in the software. Everything changed in the business case.

Here is where the vendor was selling productivity. The customer was planning transformation. And in the gap between those two realities, deals quietly fall apart, contracts fail to expand, and relationships that started well become difficult.

I saw this recently with a deep tech company selling AI into a large industrial group. The prospect described Business Case A in every conversation. As a result, the champion was enthusiastic. Their use case was concrete. Consequently, the vendor qualified accordingly, priced accordingly, and structured the contract accordingly.

Six months after signing, the internal conversation shifted. The executive sponsor changed. Success metrics changed. The renewal conversation looked nothing like the original deal. What had started as an augmentation purchase was now being evaluated as a transformation programme.

The product had not changed. The business case had.

Four conversations inside every enterprise AI deal

Inside a large enterprise, the same AI product creates four parallel conversations.

The champion talks about usability, adoption and features.

Operations talks about productivity.

The CFO talks about labour costs.

Then the board talks about organisational redesign.

The vendor often hears mainly the first conversation. The other three happen behind closed doors, in rooms the vendor never enters, with stakeholders the vendor has never met, using a business case the vendor never built.

That is not a communication problem. It is a GTM problem.

And it is a problem that traditional qualification frameworks were not designed to surface.

Why Traditional Enterprise AI GTM Qualification Breaks

Traditional enterprise qualification was built around pain, budget, authority and timeline. It assumed that buyer and seller were, more or less, qualifying the same opportunity.

In AI, increasingly, they are not.

The customer is buying tomorrow. The vendor is qualifying today.

While the pain described in that first conversation is real, it is often not the pain driving the strategic decision. The budget that exists for Business Case A is not the budget available for Business Case B. The champion who is enthusiastic about augmentation may have personal incentives to resist transformation, because transformation changes their role, their team, their relevance.

Traditional qualification captures what the customer is ready to discuss. It may completely miss what the board is already considering.

There is a question that surfaces the gap. One question. And it is almost never asked.

“If this works exactly as expected over the next three years, are your specialists still doing the same work, only faster? Or are they doing something fundamentally different?”

That answer changes everything: the stakeholders you need to involve, the business case you need to build, the ROI you need to demonstrate, the pricing logic you can defend, the contract structure that will hold, and the expansion path that actually exists.

If you do not ask it, you are not qualifying an enterprise opportunity. You are qualifying the version of the opportunity your customer is comfortable describing in the initial meetings.

Why AI Companies Risk Pricing The Wrong Business Case

Many AI vendors still price as if they were selling conventional software.

Per seat, per user, or per volume of data processed. The logic comes directly from SaaS — and in Business Case A, it often makes sense.

But many enterprise buyers are valuing something different: not access to software, but the amount of human work it can replace.

Fundamentally, those are completely different economic models.

If the customer is buying productivity, seat pricing captures the value reasonably well. If the customer is buying organisational transformation — if the perceived value is the elimination of consulting spend, the reduction of specialist headcount, the removal of an outsourced function — seat pricing captures only a fraction of the value being created.

An ergonomic consultant costs X per year. If your AI eliminates the need for that consultant in 70% of cases across a manufacturing group with operations in twelve countries, the value is not the cost of the software. It is a fraction of the consultant’s annual cost multiplied across every site where the workload, external spend or required headcount is materially reduced.

This does not mean every AI company should jump to outcome-based pricing. It means the pricing model should follow the business case.

You cannot choose the right pricing model if you do not understand which business case your customer is actually buying. When the buyer is doing labour economics and the vendor is still using SaaS logic, the product is likely to be materially underpriced.

Qualifying The Business Case, Not Just The Opportunity

One of the biggest risks in enterprise AI is qualifying one business case while the customer is already preparing for another.

The software has not changed. Neither has the demo. Even the buyer may be the same person.

But the business case has.

And if your qualification framework does not uncover that shift, you are not qualifying an enterprise opportunity.

You are qualifying yesterday’s buying logic.

The question every AI founder selling into enterprise should be asking is no longer:

Is my product good enough?

It is this:

Do I understand the business case my customer is actually buying?

Because in AI, the product may stay exactly the same.

The economics rarely do.

If you enjoyed this post, you might also like:

 [What to do when a competitor is in trouble]

 [The CEO-CRO Nobody Wants To Be]

 Subscribe to my newsletter for practical GTM insights, frameworks, and real stories for complex B2B tech leaders.

Featured image: Evgeniya Koniukhova

The post AI Doesn’t Just Change The Product. It Changes The Business Case. appeared first on Luigi Mallardo.

One competitor gets acquired by a Private Equity firm and everyone knows that their new mantra will be “cost cutting”.

Another raises a large funding round but starts burning enterprise pilots that are poorly managed and do not convert.

A third begins losing key people while product execution slows down.

Most founders read the news. Some even congratulate the team on LinkedIn for the funding or the exit. Then they move on.

I don’t.

Whenever I see a competitor losing control of its narrative, my first question is: “Which of their enterprise customers just became more willing to have a conversation?”

Good GTM leaders don’t wait for demand to arrive. They capture it in the exact moment a competitor loses control of their narrative. And that moment is not a news event. It is a window.

That window is usually short. Sometimes a few weeks. Rarely more than a few months.

Miss it, and the market resets.

Capture it, and you can accelerate deals that would otherwise have taken another year.

This is about recognising GTM windows to act on, now

There is an unspoken assumption in B2B tech that competition is a game with rules. You build your pipeline, they build theirs. You earn your deals, they earn theirs. When a competitor struggles, the polite thing is to wait your turn.

I don’t agree with that “peaceful” perspective. The market does not reward patience. It rewards presence. And the founder who is closest to the moment of vulnerability, with the right message, the right list, and the right choreography, is the one who captures the demand that was never going to come through inbound.

There are three scenarios where a competitor creates a window. Each one requires a completely different approach.

Before getting there, let’s get something clear.

I’m not talking about attacking competitors. And I’m certainly not talking about celebrating someone else’s problems.

What I’m talking about is recognising moments when the market becomes unusually receptive to change.

In reality, enterprise customers don’t wake up looking for new software or AI agent. They move when something disrupts the status quo. Competitor disruption is one of those moments.

Window #1 — Competitor Acquisition

A well-funded competitor gets acquired. Maybe by a Private Equity firm looking for financial returns. Maybe by a legacy industrial player expanding into software or AI. The press release is optimistic. The LinkedIn posts are congratulatory.

Underneath the surface, something different is happening.

The internal focus of the acquired company shifts immediately to financial hygiene, cost rationalisation, and synergies. The product roadmap freezes or slows. The sales team is distracted, uncertain about their future, and often partially replaced. The customer success teams often become the first casualties of post-acquisition chaos.

Their enterprise clients notice. Not immediately, but within a few months, the signals start appearing. Support tickets take longer. The champion who sold them the solution is suddenly unavailable. The roadmap conversation at the QBR is vague in ways it never was before.

This window lasts 60 to 120 days from the announcement. After that, the new ownership consolidates the narrative and the moment closes.

The playbook is simple and requires no creativity. Build a closed list of their top fifteen to twenty enterprise clients. No spray and pray. Precision. Identify the accounts that fit your ICP and where the timing of a conversation makes commercial sense.

The message does not attack the competitor. It acknowledges the moment.

“You’ve probably seen the news about the acquisition. These transitions usually come with a period of uncertainty around roadmap, support, and strategic focus. We’ve been through this with clients who’ve navigated similar situations. Would it make sense to have a conversation?”

You are not selling a better product. You are selling stability in a moment of operational uncertainty. That is a completely different conversation, and a much more timely one to have.

Window #2 — Onboarding Disaster

The second opportunity is shorter. And far more counterintuitive.

A competitor has raised a significant round and is deploying capital aggressively. They are signing enterprise pilot agreements they know will not convert. The pilots go live. The pilots struggle. The clients are frustrated.

The founder’s instinct is almost always the same. “Let’s wait. Let the pain accumulate. Let the contract expire. Then approach.”

That’s exactly what I challenge. Working with a CEO some months ago I used an analogy that everyone immediately understood.

Like training a puppy.

If you don’t correct behaviour at the exact moment it happens, the puppy learns the wrong pattern. Later becomes much harder.

Complex tech enterprise buying works in surprisingly similar ways. At first, customers blame the vendor. “This implementation is terrible.” A few months later, something much more dangerous happens. They stop blaming the vendor. They start blaming the category.

“AI forecasting doesn’t work.”

“Retail planning software never delivers.”

“We’ve already tried this.”

The original business problem hasn’t disappeared. Their belief has changed. And once that happens, you’ve lost far more than one opportunity. You’ve lost the category.

That’s why timing matters.

You need a list of accounts that are in or just coming out of troubled pilot phases with the competitor. Your commercial intelligence sources — a former competitor employee, a partner in the ecosystem, a client who knows other clients — are more valuable here than any database.

The message goes directly to the pain without being aggressive.

“We know what happens when companies with strong funding and limited operational depth run enterprise pilots at scale. We’ve seen it. We know what goes wrong and why. And we know how to offer a controlled path out of it.”

The pricing structure and the SOW becomes a weapon. I’ve executed that playbook several times and it works. No payment until their current contract expires. A defined exit clause at three months. A controlled, low-risk transition that removes the financial objection before it is raised.

You are not selling your software or AI agent. You are selling a way out of the pain they are feeling right now.

Window #3 — Previous Vendor Trauma

This scenario does not involve a competitor in difficulty. It involves a prospect who was burned, not by the competitor you are displacing, but by a previous vendor. Six months to one year lost. Budget burned. An integration that became a permanent war story.

The competitor is already gone. The prospect has reverted to their old status quo, but they know it’s unsustainable.

Your champion internally loves your product. The qualification is strong. The use case is perfect.

You think you have won because of the champion’s feedback. You have not.

Because the budget is not approved by your champion. It is approved by the board. And the board’s memory does not work the way your champion’s memory works.

Your champion sees: “This new vendor has better architecture, stronger support, and a track record with companies like ours.”

The board sees: “We burned six months and significant budget on the last software decision. Now someone is asking us to trust again.”

That is not a commercial objection. That is organisational trauma. And you cannot treat organisational trauma with enthusiasm.

I have watched founders lose deals at this exact moment, not because the product was wrong, not because the pricing was wrong, but because they brought promises to a board that was asking for guarantees.

The playbook here is not commercial. It is architectural.

You need an integration formal discussion. Bring a specific document or one-pager, that is contractually meaningful. You need a written exit clause. You need to show the board that you have already anticipated the scenario where this goes wrong and built a structured path out of it.

The key business conversation here is that you are focusing on de-risking their past.

If you get in front of a board that has been burned and you talk about your product, you lose. If you get in front of that same board and talk about how you have structured the engagement to protect them in case of failure, you win.

Different windows require different playbook and choreography

One of the biggest mistakes I see is treating every competitive campaign the same way.

An acquisition requires one narrative. A failed pilot requires another. A product crisis, executive departures or operational instability each require something different again.

Consequently, the triggers change. So should the choreography. One campaign, one message, one sequence is rarely enough.

The companies that consistently displace competitors are the ones that recognise buying psychology before everyone else does.

The most expensive mistake: Waiting

Recently I was working with a CEO navigating two competitor situations simultaneously. One competitor had just been acquired by an industrial player. The other was burning enterprise accounts with cheap pilots they couldn’t execute.

However, the founder’s temptation was to do just one thing: wait and see how the situations evolved.

My reaction was immediate. These are two different windows, requiring two different lists, and two completely different choreographies. Launch both campaigns asap.

Instead, waiting wasn’t reducing risk. It was wasting the window. Because the moment a competitor is vulnerable is the only moment when the market is willing to listen to you outside of a normal sales cycle. Outside of an RFP. Outside of a structured evaluation.

This founder saw the window opening and acted with operational authority, winning the first 4 customers and increasing pipeline. They built an entire campaign around it. It worked.

The wrong question

When competitors struggle, most founders ask:

“How long before they recover?”

The better question is:

Which of their customers is experiencing uncertainty today, and how quickly can we start a meaningful conversation?

Competitor disruption releases demand that was already trapped behind inertia.

The best GTM operators don’t wait for that demand to arrive.

They recognise the window.

Then, they build the right choreography.

And they move before it closes.

If you enjoyed this post, you might also like:

 [The CEO-CRO Nobody Wants To Be]

 [You’ve Been Selling the Champion. You Haven’t De-Risked the Decision System]

 Subscribe to my newsletter for practical GTM insights, frameworks, and real stories for complex B2B tech leaders.

Featured image: Tom Fisk

The post When a Competitor Bleeds: The Opportunistic GTM Playbook appeared first on Luigi Mallardo.

The uncomfortable answer is: You are the CRO.

Most founders believe their core problem is: “We just haven’t found the GTM leader yet.” The actual problem is: “Nobody has built the Go-To-Market system yet.”

You cannot delegate a system that does not exist.

Until that system is built, codified, and generating predictable outcomes, the CRO is you, the founder CEO. Even at €2M ARR. Even at €5M ARR. And especially after your Series A. Even when the board is impatient and you are mentally exhausted.

But here is the point. Most technical and product-native founders think acting as the CRO means doing more product demos, closing more deals and running forecast calls. Updating the CRM. Hiring and firing.

What the job actually is

That is not being a CRO. That is being a Sales Manager. Your job in this phase is not just to sell and manage people. Your job is to build.

What does building a GTM system actually look like for a CEO? It looks like managing friction.

The real job is creating the conditions under which revenue becomes predictable. And in early stage, those conditions don’t exist yet. Someone has to build them. You.

In many B2B complex tech companies, the CEO must act as the CRO long before the company is ready to hire one.

Here are four real scenes from the trenches of startups navigating this exact phase.

Scene 1. The board wants a superhero CRO. Your job is to reframe the question.

The board sees pipeline starting to move. Their pattern-matching kicks in immediately: now is the time to hire a serious GTM leader, someone who has done this before, someone who can convert this demand.

It’s not wrong instinct. It’s just the wrong question for this moment.

A founder I work with was heading into exactly this board conversation. His investors were pushing for a VP of Sales — experienced, expensive, traditional profile.

He had a different view, built on something more nuanced: a framework of four hiring profiles, mapped against fit, cost, and probability of success for his specific stage and motion.

The insight wasn’t just analytical. It was strategic.

If you walk into a board meeting with an open question — who should we hire? — the board will answer it for you. And their answer will be shaped by pattern recognition from companies that looked nothing like yours.

If you walk in with a structured view — here are the four options, here is why three of them fail at our stage, here is the profile that fits our next twelve months — you’re not asking for permission. You’re guiding a decision.

Be ready to push back if they insist: “how often have you seen hiring a senior CRO in a situation like ours to work well? None of our Account Executives are consistently hitting quota. Our sales choreography is not yet fully codified. If we hire an experienced VP right now, we will burn six months of their salary just to watch them fail in a structural vacuum. I will hold the wheel until the fundamentals are green.”

They know the answer. 99% of the time, it fails.

That’s GTM leadership. It looks nothing like closing a deal. You don’t just report to the board. You coach the board.

Scene 2. Sales and marketing don’t align by themselves. You are the alignment.

In another company, there was a tension that had been simmering for months. The sales rep in a key market didn’t trust marketing. Not personally, professionally. Every time marketing proposed a campaign, the response was some version of this is not going to work.

The temptation in this situation is to call a meeting. Get everyone in a room. Talk about alignment.

That meeting will not work. An open brief, let’s build a plan together, in a low-trust environment doesn’t create alignment. It creates more surface area for conflict.

A traditional CRO expects alignment to already exist. The CEO-CRO has to create it in the mud.

They don’t host motivational team-building meetings. They use closed briefs. Instead of giving Marketing an open mandate to “do lead gen,” the CEO intervenes surgically: “Marketing will organize two highly targeted events in the UK for these 10 specific accounts, and Sales will attend.”

You align warring departments by forcing execution and building trust through delivery.

One deliverable. One owner. Clear enough that success and failure are both visible.

The CEO as CRO doesn’t manage pipeline. They manage the conditions that make pipeline possible. In early stage, that often means getting into the room, sometimes separately, before putting people in the same room together.

Scene 3. The market sends signals, if you listen. 

News breaks out. A well-funded, direct competitor just got acquired by a massive legacy conglomerate, or they are rapidly burning cash and losing key talent. Even better, they are having serious product gaps and issues.

A standard sales manager might wait for the quarter to end to analyze the impact. A CEO who is doing the GTM job sees it differently and immediately turns this into a weapon.

This is a demand generation window. Customers who chose that competitor are now uncertain. They launch a surgical campaign the very next morning, reaching out directly to the competitor’s enterprise clients. They leverage the market uncertainty, offering creative pricing models to rip and replace the competitor’s product. That is pure Go-To-Market agility, driven by someone who understands the product, the cash flow, and the market intimately.

This kind of opportunistic strike requires someone who is close enough to the market to see the window, and has enough authority to move immediately. In most early-stage companies, that person is the CEO.

Scene 4. Don’t let the board rush you past the foundations.

Pipeline is starting to appear. Inbound is working. A few outbound sequences are converting. The board is energized.

And now the pressure shifts: let’s accelerate. Let’s add headcount. Let’s scale what’s working.

The CEO as CRO has to protect something in this moment that is genuinely difficult to protect: the discipline of building correctly before building fast.

Because what looks like a working pipeline is often a founder-dependent pipeline. The CEO is in the deals. The qualification is happening in their head, not in a process. The conversion is driven by relationships that don’t transfer.

Scale that, and you don’t accelerate. You expose it.

The job in this moment is not to resist growth. It’s to make sure that what you’re about to replicate is actually replicable, that the qualification criteria exist, that the stages in the CRM reflect reality, that the behaviours you want from your team are trained and documented before you add more people to carry them forward.

This is unglamorous work. It is also the difference between a GTM system and a GTM dependency.

The Wrong Question

Eventually, the fatigue sets in, and every founder asks the same question: “When should I finally hire a CRO?”

It is the wrong question.

The better question is: “Have I already done the CRO job myself?”

Because the best revenue leaders on the market do not create GTM systems from scratch. Unless they are one of the founders. They inherit ones that already kind of work, they optimize and scale them.

If the system doesn’t exist yet, no hire will create it. The board won’t create it. The advisor with the impressive network won’t create it.

You will. Reluctantly, imperfectly, while doing twelve other things.

That’s the job nobody announces and everybody eventually does. The CEO-CRO nobody wants to be, until they look back and realize it was the most important role they ever played.

And until that system exists, the title is yours.

The post The CEO-CRO Nobody Wants To Be appeared first on Luigi Mallardo.

They had funding. Customers were signing. A sales team was in place. Some were hunting for an experienced CRO.

From the outside, everything looked promising. Revenue was growing. The board was supportive. The pipeline looked healthy.

But when you looked underneath the surface, the foundations were still missing. Not the product or the vision. Not the ambition. The GTM foundations: the unglamorous, unsexy infrastructure that determines whether growth compounds or collapses.

What looked like an operating system was merely a series of uncoordinated heroic acts performed daily by the founding team to keep the illusion of traction alive.

Today, the problem is getting worse. Most founders I meet are benchmarking against Cursor, Lovable or the latest AI-native rocketship growing faster than anyone thought possible. And they are asking themselves what to do to expand at that exact same velocity. The comparison feels natural. The pressure is real. The board is asking questions.

The problem is not a lack of ambition or talent. The problem is a fundamentally broken benchmark.

Cursor built a product-led growth motion in a market of tens of millions of developers. Adoption is viral, frictionless, individual. They are selling convenience to a user base that can adopt a tool with a single click.

Your company is selling to a VP of HSE (Health, Safety, and Environment) at a German manufacturing group with a nine-month sales cycle, three approval committees, a procurement process, and a legal team that has never heard of you. That is not the same game. It is not even the same sport.

Benchmarking your GTM readiness against PLG rocketships when you are selling complex B2B software into mid-market and enterprise is not just misleading. It is dangerous. Because it makes you believe you are behind when you are actually just playing a different game, one that requires a completely different kind of machine.

Scaling is not a reward. It is an amplifier.

When legendary basketball coach Phil Jackson took leadership of the Chicago Bulls, and later the Los Angeles Lakers, he did not begin his tenure by designing complex, spectacular offensive plays to highlight the individual genius of Michael Jordan or Kobe Bryant.

Instead, he systematically forced his teams back to the absolute basics of basketball mechanics. He installed the Triangle Offense, a highly structured, repetitive framework that completely relied on non-negotiable fundamentals: spacing, passing precision, acute situational awareness, and split-second defensive reading.

The system itself was intentionally boring to practice. It replaced the reliance on chaotic individual brilliance with a predictable, repeatable rhythm.

Coach Jackson understood an absolute truth that applies directly to GTM organisational engineering: if your players cannot maintain precise four-foot spacing or execute a textbook chest pass under pressure, any advanced playbook you design is entirely useless. You cannot scale individual heroism; you can only scale structural discipline.

The Bulls didn’t win six championships because Jordan invented a new way to score every night. They won because the underlying system was executed with such mechanical perfection that the opposing defense was completely starved of options.

The same logic applies to complex enterprise Go-To-Market strategy.

Founders constantly mistake the injection of venture capital as a validation of their readiness to accelerate.

They treat scaling as a reward for past survival. It is not. Scaling is an amplifier.

It takes whatever organisational architecture you currently have and multiplies its volume by a factor of ten. If your sales process is structurally sound, scaling amplifies your revenue efficiency. But if your GTM fundamentals are broken, scaling simply amplifies your structural flaws at an unsustainable velocity.

Hiring ten more Account Executives or bringing in an expensive corporate CRO before your fundamentals are codified does not accelerate growth.

It merely accelerates your burn rate and scales your internal chaos.

PMF is not GTM readiness. Most founders confuse the two.

Here is the mistake I see most often, and it is an honest one, because the signal is genuinely confusing.

The company closes a massive logo. Can be BP. Santander. A global retailer with hundreds of stores. 6-digit ARR. The product delivers real, measurable value. Excitement spreads to the CEO. The case study is written, the logo is proudly displayed on the sales deck. Investors are satisfied and read this signal as definitive. The machine is ready to be scaled. Build out an outbound sales apparatus, scale up the headcount, build partnerships.

Then you look at what actually happened and start to see the truth.

The deal took fourteen months. Every critical alignment call had one of the founders in the room. The pricing model was rebuilt from scratch three times to navigate the client’s internal budget constraints.

Onboarding required three weeks of on-site work that was never scoped. The champion was incredible, but without that specific champion, the deal would not have survived month four.

That is not a scalable motion. That is heroic intervention dressed up as commercial momentum.

Product-market fit means your product solves a real problem for a real segment. It is necessary. It is not sufficient.

Being ready to scale means your go-to-market machine can operate without heroic intervention. That it can replicate, that it can survive personnel changes, that it produces predictable output.

Product-Market Fit merely gives your startup the right to exist. It is Go-To-Market readiness that gives you the right to scale.

As a matter of fact, the pattern I have seen more times than I can count goes like this. The company has PMF. The founder, energized by the signal, starts building the team. First SDRs. Then AEs. Then a Sales Manager or VP. Eventually, under board pressure, under the weight of investor expectations, they start interviewing CROs.

Each hire is made before the previous layer is working. SDRs generate meetings that AEs cannot qualify properly. AEs generates proposals that die in procurement because no one de-risked the decision system. The VP of Sales inherits a pipeline full of wishful thinking and a sales team that learned everything from watching the founder close.

Nine to twelve months later, growth has slowed. The pipeline looks worse than before. The VP of Sales is under review. And the founder is back in every deal.

The problem was never the hire. The problem was that they tried to scale a system that did not yet exist.

Are you really ready to scale? Run this test before your next hire.

What follows is not a checklist. This is a diagnostic of 6 areas that in my experience are the key ones to surface the specific gaps in your GTM foundation before you pour more concrete on top of them.

The six criteria are not independent. They have a hierarchy. The first two are prerequisites. If you fail either of them, the remaining four do not matter yet. Not because they are unimportant. Because building on a broken foundation accelerates the collapse.

Test 1 — ICP Discipline

What is the last deal you actively walked away from because the prospect was outside your ICP?

If you cannot answer that question immediately, you do not have an ICP. You have a wish list.

This matters more than almost anything else at this stage because your ICP is not just a targeting filter. It is a compounding force.

Selling complex technology to a mismatched customer forces your engineering team into a cycle of bespoke product customisation and traps your Customer Success team in an endless cycle of reactive fire-fighting.

Scaling without a rigorous ICP does not accelerate growth. It scales your future churn.

Stop here until you have an honest answer and the courage to say no.

Test 2 — Pipeline Honesty

Do you have a systematic, ruthless, codified mechanism for killing deals that have shown zero meaningful behavioural movement from the customer in sixty days?

Not a gut feeling. Not a quarterly review where you challenge the rep and they tell you it is “still warm.” A mechanism, a defined trigger, a defined action by the customer, a defined outcome.

A false pipeline is worse than an empty one. With an empty pipeline you know exactly where you stand. With a false pipeline you make wrong decisions on hiring, on forecasting, on how you present the business to your board and your investors. You build organisational confidence on a foundation of fiction.

Most founders fall into a trap at this exact point: a pipeline that looks full feels like a signal that it is time to delegate. Time to bring in a sales leader. Time to step back from the deals and focus on the company.

But before you make that move, ask yourself one question. If you removed yourself from the pipeline entirely — no calls, no introductions, no behind-the-scenes interventions — how many of those deals would survive the next sixty days?

If the honest answer is “most of them would stall,” that pipeline is not a pipeline. It is your contact book with a CRM wrapper.

That gap, between a pipeline that looks real and a pipeline that survives without you, is exactly what the next test is designed to expose. And it is where most founders make the most expensive mistake.

Test 3 — Founder Transferability

Could a recently hired AE take a deal from first call to signature, without the founders entering the process to save the close, accelerate the timeline, or rescue the relationship?

This is the test that generates the most resistance, and I understand why. The founder’s involvement feels like an asset. Clients want to talk to the CEO. The founder knows the product better than anyone. The founder can navigate political complexity in ways a junior AE simply cannot.

All of that is true. And none of it is scalable.

The goal at this stage is not to remove the founder from every deal. It is to build a motion that does not depend on the founder to survive. There is a significant difference between a founder who chooses to be involved in strategic deals and a founder who must be involved in every deal or the deal dies.

Test 4 — Codified Choreography

Does a codified playbook exist?

Written down, not living in someone’s head, not a collection of tribal knowledge passed from one rep to the next.

Can a new hire understand who participates in which meetings, what questions to ask in session one versus follow-up sessions, how stakeholder alignment is built progressively, how risk is reduced throughout the buying journey, and how executive sponsorship is secured before the deal reaches the client’s board?

And if that playbook exists on paper, is it actually shaping behaviour in the field, or sitting in a shared folder no one opens?

If the answers live primarily inside someone’s head, you do not have a process. You have a dependency disguised as experience.

Test 5 — Post-Sale Value Governance

What happens after the signature?

This is where many scaling stories quietly break. Customer Success is often asked to compensate for weaknesses elsewhere.

Does your Customer Success team have a framework for governing the transition of value and managing executive relationships at your enterprise accounts, or are they spending most of their time responding to support tickets and defending product gaps?

When a strategic client escalates an issue, it is rarely a technical software failure; it is almost always a breakdown in commercial governance.

If you scale your sales apparatus while your post-sale delivery relies on heroic, chaotic
manual intervention, you are simply accelerating a churn factory.

This test matters because churn is a GTM problem, not just a product problem.

A company that cannot consistently deliver value after the sale has not earned the right to accelerate acquisition.

Test 6 — Quota Attainment Consistency

One question only. How many of your AEs are hitting quota consistently? Not in their best month, not in the quarter where a single large deal inflated the number, but consistently, quarter after quarter?

I am not going to give you a benchmark from any study. The benchmark is simpler than that: if the answer is zero, or one out of three on a good day, the problem is not the next hire. The problem is the system those AEs are operating inside.

Adding a sales leader or more headcount to a broken model simply multiplies the number of people missing their numbers.

The board wants a CRO. The company needs fundamentals.

Recently I was working with a CEO who was under board pressure to hire a senior CRO. The board believed the timing was right. Revenue had been flat for a while and in the meanwhile the company had been put in a position to be EBITDA and cash neutral.

My first question was not about candidate profiles. It was not about compensation structures or equity packages.

It was this: how many of your AEs are consistently hitting quota?

Silence. None.

That one factual answer reframed the entire conversation. Because when no AE is hitting quota, the problem is not leadership. The problem is the system.

And bringing in a VP of Sales or a CRO to lead a system that is not working does not fix the system. It adds an expensive layer of management on top of a broken foundation, and gives the board a human being to blame when the foundation fails.

You Cannot Manage What You Haven’t Built

I told that CEO something that I believe more every year I do this work: you cannot manage what you have not yet built.

The board was not wrong to want a GTM leader. Boards are right to think about scale. The mistake was conflating the desire to scale with the readiness to scale. Those are two different things, and confusing them is one of the most expensive errors an early-stage company can make.

The right response to board pressure at that stage was not defensiveness.

It was, first of all, to prepare the right question from the CEO to the investors at that Board meeting:

In a situation like ours, how often have you seen that hiring an experienced CRO now brought the expected results? 

The answer was unanimous: “Now that you make me think, it never worked! ”

Second, bring to the board a clear and factual argument: here is where we are, what we have built, here is what still needs to be built, and here is the profile of leadership we need when, not before, those foundations are in place.

The wrong question

Most founders eventually ask: “When should I hire a CRO?”

It’s the wrong question.

The better question is: “Have we built a GTM system that someone else can successfully lead?”

If the answer is no, keep building. Strengthen the foundations. Improve transferability. Increase discipline. Remove dependencies. Create repeatability.

Only then does scaling become leverage instead of risk.

Have you earned the right to scale?

Most complex B2B tech startups that think they are ready to scale do not fail because they build a bad product, nor do they fail because their target market doesn’t exist or because they scale too late.

They fail because they scale assumptions before they scale fundamentals. Because they mistake funding for readiness. Often, they confuse a great product with a great go-to-market. Ultimately, they hire for the company they want to be instead of building the system the company needs right now.

The GTM Litmus Test is not a graduation ceremony. Passing it does not mean you are done building. It means you have earned the right to add resources without multiplying your problems.

Before hiring your next CRO. Before pitching your next round, or doubling the sales team.

Ask yourself one question.

Have you earned the right to scale?

Featured image: Steve Lipofsky (Lipofsky.com), CC BY-SA 4.0, via Wikimedia Commons.

The post Ready to Scale? The GTM Litmus Test for Complex B2B Tech Startups appeared first on Luigi Mallardo.

The business case was solid. ROI validated: 5.1x in year one, 9.6x average over three years. The Champion said it clearly: “If the decision were up to me, I would have already made it.”

The deal was not closed.

The Board meets next Monday. And three of the five people who influence or block that decision haven’t yet received what they need to say yes.

The signal nobody was reading

Look at how the deal evolved over ten weeks:

10%. 50%. 25%. 75%. 50%. 90%. 75%.

Every drop happens when a new stakeholder enters unprepared. Every recovery happens when the Champion pulls the conversation back.

That pattern is not noise. It’s the most important diagnostic signal in the deal.

It says one thing precisely: the team has been managing the Champion’s confidence. It has not de-risked the decision system.

These are two different jobs. Confusing them is the most common way to lose a deal that already felt won.

The stakeholder map nobody built

In complex enterprise deals, there’s a fundamental difference between:

• who is convinced
• who needs to feel safe

The Champion belongs to the first category. The decision system belongs to the second.

By session seven, the reality looked like this:

• Champion: fully bought in. Not the signer.
• User: the primary operational user. Engaged from the beginning. Comfortable.
• IT: Interested, but with unresolved integration concerns.
• Finance & Legal: will influence the decision. Never in a live session.
• Integration owner: will be asked directly in the Board. Has no clear answer yet.

The team knew the Champion deeply. They had built a genuine relationship with User. But the bottom three stakeholders on that list, the ones who most directly influence whether the board approves on Friday, were not safe.

Eight sessions. The wrong focus.

When the previous vendor left scars

This deal had an extra layer. The prospect had already been burned. Twice.

Six months of frustration with a previous vendor.

The Champion understood exactly why the previous vendor failed. He could articulate it clearly, it was an architectural problem, not a category problem.

But that understanding belongs to the Champion.

It doesn’t belong to the Board.

When a prospect has been burned by a previous vendor, the decision system has a built-in high-risk flag that no amount of champion management will lower. The Board doesn’t see “this Vendor is different from the previous vendor.” The Board sees: “The last vendor didn’t work. This new Vendor says it’s different.”

That’s not a commercial objection. That’s a risk signal. And no amount of Champion enthusiasm lowers it.

What actually lowers risk

In this kind of deal, three things move the decision system:

1. Integration clarity. Not a vague assurance that integration is manageable. A specific briefing for the person who owns integration internally: what the data requirements are, how they compare to what the previous vendor already ingested, what their role will be, what the timeline looks like. This person needs to be able to answer a direct Board question with confidence, not with “I don’t have enough information yet.”
2. Onboarding structure. Not “we’ll guide you.” A concrete sequence: which sessions, who attends, what gets covered, what the milestones are. The operational stakeholders need to see their investment of time before they commit to it.
3. A specific exit window. Not “we can be flexible on risk-sharing.” A defined clause: three months post-integration go-live, with clear technical criteria. This is the difference between a promise and a position. The Champion can bring enthusiasm to the board. He cannot bring safety on behalf of Finance and Integration. Only a concrete, written commitment does that.

The trap

Every session with the Champion feels like progress.

The business case lands. The demo impresses. The probability goes up. The CRM looks healthy.

But the Champion doesn’t sign alone.

Meanwhile:

• IT still has open questions
• Finance hasn’t engaged
• Integration isn’t ready
• The Board will ask questions no one prepared for

The Champion leaves each session energized. But value and fit and Champion commitment are necessary conditions, not sufficient ones.

The decision system remains unconvinced. That gap is where deals that felt won quietly die.

What de-risking actually means

De-risking the decision system is not a separate phase. It’s a discipline that runs in parallel from the beginning.

It means mapping the full decision system early: not just who the champion is, but who signs, who can block, who will be asked direct questions at the final decision moment, and what each of those people needs to feel safe enough to say yes.

For each stakeholder who isn’t safe, there’s a specific action, not a general impression management plan, but a targeted intervention that addresses their specific concern in concrete terms.

In this deal, three targeted actions in the forty-eight hours before the board meeting could still change the outcome:

• A pre-board structured Q&A (Not a Demo): Bring Finance, Legal, and IT into a room. The agenda is strictly risk-focused: what onboarding looks like in practice, integration clarity, and the specific risk-sharing clause.

• The Integration One-Pager: A briefing document specifically proving that your data requirements mirror what the previous vendor already ingested, defining their exact role, and mapping the timeline. This is their briefing document for the board question.

• A Written Risk-Sharing Clause: Specific, not vague. “A three-month exit window, post-integration go-live. Technical criteria defined.” This gives the Champion a concrete position to defend, rather than a mere promise.

The only question that matters

There’s a simple diagnostic for any enterprise deal at the final stage.

For each person in the decision system, ask: “If they were asked a direct question about their specific concern right now, could they answer it in a way that moves the deal forward?”

Champion: yes.

User: yes.

IT: not yet.

Finance & Legal: not yet.

Integration: not yet.

Three out of five.

That’s not a deal that’s ready to close on Monday. That’s a deal where the Champion has been sold, and the decision system hasn’t been secured.

The fix isn’t another session with the Champion.

The fix is forty-eight hours of targeted, specific work on the three stakeholders who aren’t safe yet.

The lesson that applies beyond this deal

Every complex enterprise deal has a decision system. And in almost every deal that slips at the final stage, the pattern is the same.

The team invested heavily in the Champion. The champion is genuinely committed. The product fit is real. The business case is strong.

But somewhere in the decision system, an IT owner who was never briefed, a finance stakeholder who never saw the product live, a board member who will ask a question nobody prepared for, there’s a gap between champion confidence and decision system safety.

That gap is where deals go to slip.

The team that closes isn’t necessarily the team with the best product or the most compelling business case. It’s the team that maps the full decision system early, identifies every stakeholder who isn’t safe, and executes specific targeted actions to de-risk their specific concerns. Not in theory, in practice, before the decision moment arrives.

Winning the champion is the beginning of the work.

De-risking the decision system is how you finish it.

The post You’ve Been Selling the Champion. You Haven’t De-Risked the Decision System. appeared first on Luigi Mallardo.

A strategic enterprise customer sent eight points to a CEO & Co-Founder I’m working with.

A multi-billion dollar business. Global presence. Seven-figure contract.

Not to the account manager. Not to the Customer Success team. Directly to the CEO, a few days before a scheduled call.

The points were clear. Structured. Legitimate.

Visibility gaps in the platform. Modules that don’t talk to each other. Features that were expected and never arrived.

The team reads the email and reaches an immediate conclusion: we have a product problem.

I read the same email and saw something different.

The most dangerous misdiagnosis

I gave the transcript of the subsequent call to an AI and asked for a summary. It came back with a clean list of technical issues.

Product gaps. Roadmap items. Feature requests.

Accurate. Well structured.

Completely wrong diagnosis.

Complex B2B doesn’t run on algorithms. And the most dangerous misdiagnosis in enterprise customer success isn’t the one that’s technically incorrect.

It’s the one that’s technically correct and strategically wrong.

“This is a product problem” is often the most intelligent wrong answer in the room.

Product gaps are the language. Not the cause.

When an enterprise customer escalates to the vendor CEO, the instinct is to look at the product.

What’s broken? Is there something missing and undelivered?

Almost always, that’s the wrong question.

Enterprise customers don’t escalate because the product has gaps.

They escalate because they no longer trust the team managing the relationship.

The product becomes the vocabulary of the complaint.

Because it’s safer to say:

“This feature doesn’t work”

than to say:

“I don’t trust your team”

One is technical. The other is political.

That eight-point email wasn’t just a list of issues.

It was a political signal, sent to the CEO, timed before a strategic call, with a clear subtext:

“I want you to know what’s really happening.”

The first twenty minutes say everything

In the call that followed, the customer’s leadership spoke for twenty-five minutes before product came up in any meaningful way.

What did they talk about?

• Weekly calls and quarterly strategic reviews that had stopped.
• Having to chase the team for basic information.
• Lack of visibility into their own operations.
• Slow responses. Missing follow-ups.

Almost no real feature discussion.

This wasn’t a product brief.

It was a relationship brief.

A customer running a multi-billion dollar business, scaling aggressively, under real pressure, and the first thing they needed to say was simple:

The human layer isn’t working.

The signals most teams miss

In that same sequence, three things stood out.

The response the customer was waiting for didn’t arrive before the call.

It arrived after.

When it arrived, it was technically solid. Structured. Honest on the roadmap.

But it missed what actually mattered.

No acknowledgment of a critical issue that had been in limbo for over a month.

Zero reference to the weekly cadence that had quietly disappeared.

No sense of ownership of the experience.

The customer received a technically correct answer when they were expecting a human one.

Later in the call, when asked what success would look like in 12 months, the answer wasn’t about software.

It was about:

• speed of resolution

• feeling prioritized

• restoring basic operational rhythm

The product came third.

Before the product was questioned, the relationship was already broken.

The trap inside Customer Success

The enterprise customer success team reads the same situation and reaches a rational conclusion:

“These are product gaps. We’ve escalated. We need the roadmap.”

They’re not wrong.

But they’re missing the point.

Because in that framing, their role becomes passive.

They stop managing the account and start acting as a bridge between the customer and the product.

A messenger. Waiting.

You see it clearly in how responses are written.

Point-by-point. Clean. Professional. Aligned with the roadmap.

But missing the one thing the customer is actually testing:

“Do you see what’s happening on our side, and are you taking ownership of it?”

When that answer is missing, everything else becomes secondary.

“This is a product problem” becomes a comfortable position:

• it protects the team

• it shifts responsibility

• it avoids the hardest part of the job

And in doing so, it leaves the customer alone.

What actually broke

At this stage, the issue is no longer the product.

It’s the absence of a system that makes the customer feel handled.

No rhythm. No anticipation. Lack of ownership. No narrative control.

From the company’s side, the account looks active.

From the customer’s side, it feels different.

Silence between interactions.

Reactive responses.

Uncertainty about what’s happening next.

So they escalate.

Not because the product failed.

Because no one is clearly in control.

The CEO call is not a good sign

A customer who trusts the operational team doesn’t ask for direct access to the CEO of the vendor.

When they do, they’re saying something else:

“I don’t feel safe relying only on your team.”

In this case, the customer closed the call with:

“Even if we can chat once a quarter, it forces us to think about the issues together.”

That’s not a request for access.

It’s a safety net.

A way to compensate for something that’s missing below.

What nobody says out loud

The enterprise customer success team diagnosing everything as a product problem isn’t technically wrong.

They’re strategically wrong.

Because if your value depends entirely on what the product delivers, then when the product doesn’t move, you have no value to offer.

At least in your own frame.

But enterprise customers don’t just buy the product.

They buy the certainty that someone is in control.

That someone understands what’s happening across their business and will show up before problems become escalations.

And that certainty doesn’t come from the roadmap.

It comes from presence.

The product will never be finished. There will always be gaps.

The job is not to wait for perfection.

It’s to manage the relationship through imperfection. And make the customer as happy as possible in the process.

What escalation is really telling you

When a customer bypasses the team and goes directly to the CEO, it’s tempting to see it as a failure.

It’s not.

It’s the system working exactly as designed.

The customer has already run the test:

They reached out. Waited. Then they followed up. At the end they pushed.

When nothing changed, they went higher.

The escalation isn’t the problem.

It’s the diagnosis.

And the question it’s asking is simple:

When was the last time your team showed up proactively?

The answer to that question tells you almost everything.

The only thing that matters

When a customer escalates to the CEO, the first question shouldn’t be:

“What’s missing in the product?”

It should be:

“When was the last time we made them feel handled?”

Customers don’t escalate because of product gaps.

They escalate when they feel alone.

And by the time they do, it’s already late.

The post The Most Dangerous Misdiagnosis in Enterprise Customer Success appeared first on Luigi Mallardo.

It’s also the most dangerous moment in the journey.

From the outside, everything looks right. The founder has sold every significant deal personally. The team is growing. Investors are happy.

From the inside, something doesn’t add up as far as GTM is concerned.

The paradox has three layers

Everything starts moving at once. Hiring. Pipeline. Product. Board pressure.

The first layer of paradox is having enough success to stop questioning anything. An initial base of enterprise clients came in. Founders tend to interprets this as validation of the method. But almost always, those deals came in because of their direct presence, their personal credibility, their ability to read the room in real time, their willingness to do whatever it takes to close.

That’s not a system. That’s them.

And as ACV goes up, friction explodes. More enterprise means more complexity, more stakeholders, longer cycles, harder qualification. The team isn’t ready for that. The founder was.

Then the second layer is having enough resources to make the wrong moves with confidence. With the round in the bank, the temptation is to hire before having a transferable playbook. A senior AE, a head of sales, someone who “knows how it’s done.” But without a codified first meeting choreography, without a surgical ICP, without pipeline architecture, that person arrives in a vacuum and can’t perform. Not because they’re wrong. Because there’s nothing to land on.

The third layer is the most dangerous: traction is not repeatability. Pipeline is moving. Deals are closing. The founder reads this as confirmation that the GTM is working. In reality, the founder is working. The GTM is still them. The difference only becomes visible when the team scales, and by then the cost is already high.

Looks like scaling. It’s not. The founder is still the system.

The founder pitch is never the scalable pitch

The founder runs the first enterprise meetings and closes. Then the team runs the same meetings and doesn’t. The instinctive diagnosis is that the team isn’t strong enough. But the real diagnosis is that nobody has ever codified what needs to happen in the first 20 minutes of that meeting. The founders know how to do it their way, but the founder pitch is never the scalable pitch.

I’ve seen a founder rebuild their entire approach to the first meeting from scratch: map it out, test it, then hand it to a newly hired AE. Three months later the team was closing deals that previously required the founder’s direct presence. The difference wasn’t the team. It was having a “translation” from the founder pitch to a scalable choreography that existed outside the founder’s head.

The revenue math nobody has done

In this window, founders know they’re growing but they don’t know yet what that growth actually requires. The round creates the illusion of runway.

The pipeline math is rarely done out loud.

Take a founder with a €1.5M end-of-year target, a €15K average ticket, and an 8-month sales cycle. The math requires 75 new clients.

At their current pace of meetings, it’s not difficult. It’s impossible.

Nobody had calculated it before. When they do, every decision that follows changes.

Hiring comes too early, or wrong

Post-round pressure is real. Investors want to see hiring, execution, GTM momentum.

Founders hires. But they hire into a structure that doesn’t exist yet.

The first SDRs arrive without a defined prospecting system.

AEs arrives without a codified first meeting choreography and a clear qualification framework.

The first CS hire arrives without a written onboarding playbook.

I’ve watched a founding team hire an SDR with exactly the right criteria: outbound experience, startup background, someone who picks up the phone. Everything correct on paper. But there was no qualified account list. No tested call choreography. No shared definition of what a “connect” actually means. The first weeks were noise. Not because the hire was wrong.

Because there was nothing to plug into.

The pipeline looks alive. It isn’t

The CRM is full. There are deals in every stage. Weekly pipeline reviews feel productive. There’s always something to talk about.

But when you look at the age of the deals, the last meaningful interaction, the actual probability of closing before year end, the picture changes completely.

A pipeline full of deals that haven’t moved in 60 days isn’t a pipeline. It’s a list of conversations the founder doesn’t want to kill because killing them means admitting the math doesn’t work.

The movement is an illusion. The real pipeline is a fraction of what the CRM shows.

Why Product becomes the default diagnosis

In this window, the product is still evolving. Every deal brings feedback, every client asks for something different. When commercial progress stalls, the founder’s instinct is to look at the product roadmap. Something is missing. One more feature and the deals will close.

Almost always, that’s wrong.

I watched a founding team lose a significant enterprise deal after two hours of technical demo. Team’s diagnosis: missing features. Real diagnosis: nobody had qualified the economic buyer, nobody had understood that the real concern was implementation and change management, not the product. The product wasn’t the problem.

It was the easiest place to look.

Founders who navigate this window VS those who don’t.

It’s not resources or product. It’s GTM sequence.

The founders who come through this window intact do one thing before anything else: they codify the method before they scale the team. Then they don’t hire until they have something to transfer. Also, they don’t scale the pipeline until they have a choreography that works without them in the room.

It’s slower. It’s also the only way to build something that holds.

The round doesn’t create the system. It funds the illusion that the system already exists.

The founders who treat the post-round window as a building phase, not a scaling phase, are the ones who actually scale.

The round is not the end of the hard part. It’s the beginning of the harder part.

When money is scarce, the founder is forced to be precise. Every decision counts, every hire counts, every deal counts.

When money is available, precision becomes a choice, and many founders stop choosing it.

The post-round window is where you decide whether you’re building a machine, an architecture, or still selling yourself.

That decision doesn’t depend on the market. It depends on how willing you are to do the unglamorous work of codifying what you know, before the team has to learn it alone.

Post-PMF doesn’t mean you’re ready to scale. It means you’ve run out of excuses.

This is the moment where most companies don’t fail fast.

They lose momentum quietly..

Featured image image from Pexels by Mikhail Nilov

The post The Post-Round Window: Where Startups Don’t Fail. They Lose Momentum Quietly. appeared first on Luigi Mallardo.