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.

I ask him one question: how many deals do you need to get there?

Silence. I let it hang.

Then we do the math out loud. Average ticket €45K ACV. To close a €2M gap, he needs 45 new enterprise clients in 9 months. With an 8-month sales cycle. So he needs 5 new Enterprise clients every month, for the next 9 months.

With 10 deals in pipeline today for a total amount of 550K.

The conversation changes completely.

I work with a small number of founders building complex B2B tech — AI-driven SaaS, deep tech, vertical software, AI agents — selling into mid-market and enterprise. ARR between €500K and €10M. Different geographies. Different products.

They are post-product-market fit, but pre-scale. The hardest moment in the journey.

Over the last six months I started tracking what kept repeating — across operational meetings, live pipeline reviews, hiring decisions, deal post-mortems. Hundreds of hours of deep work. I later used AI on top of those transcripts to surface what was repeating. The logos changed. The patterns didn’t.

They have the product. They have customers. They have proof the market exists. The early deals came through relationships, instinct, sheer founder energy. It worked. Until it didn’t.

When the commercial engine stalls in B2B AI SaaS, the instinctive reaction is always the same. Look at the product. Add a feature. Hire a superhero rep. Wait for the market to “get it.”

The problem is almost never the product. It’s almost always how the founder interprets what they see, and the gap between instinct-driven selling and the architecture that scaling actually requires.

The Revenue Math Nobody Does

The opening scene is not an isolated case. It’s systematic. Almost every founder I work with has a clear target and a math that doesn’t add up. Not because they’re naive, because nobody has ever forced them to do the calculation out loud. When they do, priorities shift immediately.

The question is never “what’s your target?” The question is “what does hitting that target actually require: in deals, in meetings, in weeks?” That calculation, done honestly, is one of the most disorienting things a founder can experience. It exposes the distance between the narrative they carry and the reality they’re operating in. And it changes every decision that follows.

The Bottleneck Has A Name

In every company the commercial bottleneck has a name.

• Sometimes it’s a long-standing team member who knows the product inside out but can’t qualify a prospect.
• Sometimes it’s an external hire who produces theoretical go-to-market plans instead of getting in front of customers.
• In other cases it’s the Board, especially the lead investor, who pushes the founder to hire a pedigreed CRO when the company is not ready yet.

The founder already knows. They’ve always known. The work isn’t identifying the problem. It’s confronting the cost of inaction.

I’ve recently watched a salesperson lose a significant enterprise deal after two hours of technical demo without ever reaching the economic buyer and without understanding that the concern was about implementation and change management, not the product.

The problem wasn’t the demo. It was that nobody had ever defined what needed to happen in the first 20 minutes of that meeting. And nobody had held anyone accountable for it. The founder knew the meeting had gone wrong. They let it go anyway. That pattern, repeated across five or six deals, is what a stalled pipeline looks like from the inside.

The Founder Who Needs To Stop Being The Best Salesman In The Room

The founder is almost always the best salesperson in the company. That’s also the reason the machine doesn’t scale. As long as the first meeting choreography lives only in their head, the company depends on them for every deal that matters.

The work is first of all to codify that method: the opening, the qualification questions, the structure of the conversation, the next step, and transfer it. Not in theory. In practice, meeting by meeting.

I’ve seen a founder rebuild their entire approach to the first meeting from scratch, put it on paper, test it, then hand it to a newly hired Account Executive. Three months later the team was closing deals that previously required the founder’s direct presence. The founder was still in the room sometimes, but not as the salesperson anymore.

That’s the transition. It’s slower than it sounds and more important than almost anything else on the GTM agenda.

The Product As Refuge

When the commercial conversation becomes uncomfortable, founders retreat to the product. It’s human. It’s also dangerous.

I’ve seen pipelines blocked not because of missing features but because average ticket sizes were too low for the target segment, account profiles were wrong, and sales cycles were too short to indicate real enterprise engagement. The numbers said all of this clearly. The founder was looking at the roadmap.

I looked at a pipeline recently with an average ticket of €1,300 and a 50-day closing cycle. SMB numbers inside an Enterprise strategy. The founder’s diagnosis was that the product needed agentic AI integration before it could compete and justify higher pricing.

The actual diagnosis was simpler and harder to hear: the team was selling to the wrong accounts with the wrong motion. The product wasn’t the problem. The product was the excuse.

The Architecture That Never Ends

There’s a moment in every engagement where structural work needs to give way to execution. Revenue model, account list, ideal customer profile, first meeting choreography. All necessary, all worth the investment. But I’ve seen founders stay in “let’s build the system” mode for months while the pipeline sits empty.

A founding team once spent several months building what I’d consider a genuinely solid GTM architecture. Revenue model finalized. ICP defined. First meeting choreography on paper. Account list enriched. SOA ready. Every session produced a new layer of structure.

Then I asked a simple question: how many first meetings have you had this month? Four. I asked the same question the following month.

Six.

The architecture was immaculate. The pipeline was empty. At some point I stopped asking about the architecture and asked a different question: what are you afraid of?

The market doesn’t wait for perfect. At some point, you have to pick up the phone.

The Pattern That Divides Everything

This isn’t a pattern among others. It’s the variable that determines the speed of everything else — and the one that’s hardest to talk about directly.

Exposed to the same inputs — revenue math that doesn’t work, pipeline that isn’t moving, a sales motion that depends entirely on the founder — founders react in radically different ways.

Some upgrade fast. They take the feedback, kill the old deck overnight, rewrite the pitch, raise their prices, and are executing the new motion the next morning. The discomfort of seeing reality clearly is visceral, but brief. The action follows immediately.

Others resist quietly. They protect their existing worldview. They find reasons why their market is “different”, why the timing isn’t right, why the product needs one more thing before the commercial motion can really work. They schedule another product review. This week ends. The next week starts. Nothing has moved.

This isn’t a question of intelligence. It isn’t a question of experience. It’s the capacity to update your mental model when the data says something different from what you expected. It is GTM Cognitive Elasticity.

Take two founders with the same structural problem: pitch too technical, deals lost because the conversation never reached the economic buyer. One rebuilds the entire approach in a week, tests it on the next meeting, closes. The other spends the same week thinking about how to improve the product to make the pitch easier.

Same diagnosis. Opposite reactions. Very different outcomes three months later.

Cognitive elasticity can’t be taught directly. But it can be pressured. Weekly work — inside the real numbers, inside the live deals, inside the decisions that can’t be postponed — is one of the few environments where this update happens under conditions that actually matter.

The Market Timeline

Founders absorb GTM reality at different speeds. That’s normal. What isn’t normal is assuming the market will adjust to that pace.

I’ve worked with founders at €500K ARR and founders approaching €10M in the same period. Different revenue, different geographies, different products, different teams. The same patterns. The same delays. The same resistance in the same places.

The difference between those who scale and those who stall is almost never the product, the market, or the size of the opportunity. It’s the speed at which the founder can see what they don’t want to see, and act on it before the window closes.

Go-to-market was intuitive when the early customers came through relationships and conviction. It stops being intuitive the moment you need a machine, not a founder. That transition, from instinct to architecture and how you phase it, is where most of the game is won or lost.

The market has no patience for the gap.

Picture on pexels by Ali Borgiba

The post Scaling Complex B2B Tech: When GTM Instinct Ends and Architecture Begins appeared first on Luigi Mallardo.

It feels safer to go wide. But in crowded B2B SaaS markets, “wide” is where startups go to die.

A few days ago, I sat down with Greg Head on the Practical Founders podcast to deconstruct the journey of Woffu, the B2B SaaS we scaled from €2K MRR to a strategic exit to Visma.

We didn’t raise a massive Series A. We didn’t chase unicorn valuation metrics. Instead, we made a series of uncomfortable decisions to reduce our market optionality.

The result? We increased our business optionality.

Market optionality reduces business optionality. Business optionality comes from dominance, not diffusion. Here is the blueprint behind that paradox, and why “sequencing” growth beats chasing it.

The “Optionality Trap”

There was a fascinating debate in the comments of Greg’s LinkedIn post about our episode. Some founders argued that niching down too early is risky because technology changes fast.

I understand the fear. But the biggest risk for a sub-$10M ARR company isn’t missing the next wave. It’s fragmenting its energy before it masters the current one.

At Woffu, we had the “HR Suite” temptation. We could have built an ATS, a Performance Review module, and a Payroll system all at once. If we had done that, we would have been a mediocre “All-in-One” player fighting a capital war we couldn’t win.

Instead, we chose Time & Attendance. A boring, unsexy, specific wedge. We became dominant in that specific problem for a specific Mid-Market segment.

The Lesson: Real optionality isn’t having 10 lottery tickets. It’s having one dominant cash-flow engine that buys you the freedom to purchase the next ticket later.

Growth is a Sequence, Not a Buffet

One of the best comments on the episode came from a founder who noted: “It’s about sequencing growth so today’s traction funds tomorrow’s options.”

This is the “Operator” definition of strategy.

At Woffu, we didn’t launch Inbound, Outbound, and Partners on Day 1. That would have broken us.

• Phase 1: We nailed Inbound.
• Phase 2: Once Inbound was predictable, we used that cash flow to build the Outbound machine (raising ARPA).
• Phase 3: Only when we had a repeatable sales motion did we layer in Partners.

By sequencing these layers, we grew Average Revenue Per Account (ARPA) by 7x. If we had tried to do all three simultaneously, our CAC would have spiked, and our focus would have fractured.

The Takeaway: You don’t say “no” to new channels or products forever. You say “no” for now.

The Hidden “Operational Tax” of Going Wide

Founders often view new opportunities as simple addition. “If we add this vertical, we add €X in revenue.”

But operationally, addition is division. Every new vertical divides your product team’s attention. It forces your CS team to learn a new playbook. It dilutes your marketing message.

As another CEO brilliantly put it in the discussion: “Operationally, they are division. Every new vertical divides the attention of the product team and dilutes the GTM motion.”

We avoided this tax by adhering to the 80/20 Rule of Focus:

• 75-80% (All-in on Core ICP): Pipeline mix, resource allocation, and management attention went to where we were already monetizing and winning.

• 20-25% (Structured Experiments): Reserved for new verticals with clear hypotheses and clear kill criteria.

This ratio allowed us to innovate without risking the ship.

Exit Value is Created Years Before the Exit

Why did Visma buy Woffu? They didn’t buy a roadmap of “potential features.” They bought a machine. Acquirers don’t pay for ambition. They pay for predictability.

They bought:

1. Dominance in a specific segment.
2. Unit economics that proved efficiency.
3. A predictable GTM engine, not a founder-led magic trick.

Because we had focused so intensely on healthy growth and efficiency, we had leverage. We didn’t need to sell. As I told Greg: “Clarity about your endgame determines your strategy early on.”

We warmed up potential acquirers for years, treating them like strategic prospects. By the time we were ready to exit, it wasn’t a distressed sale; it was a strategic alignment.

Final Thought: The Builder’s Duty

In 2026, with AI lowering the barrier to build anything, the temptation to build everything is higher than ever.

Don’t do it. Differentiation today comes from depth, not breadth.

Focus feels restrictive. It feels like you are leaving money on the table. But as our journey at Woffu showed, from €2K MRR to a strategic exit, focus is the only leverage you actually have.

Want the full backstory?

Listen: The full episode on Practical Founders.

Read: My previous deep dive into [step-by-step GTM mechanics of the Woffu journey here].

The post The Focus Paradox: Why Reducing Market Optionality Increased Exit Value appeared first on Luigi Mallardo.

Every week a new “AI Revenue Orchestration Platform” appears. Our feed is a parade of promises. “The #1 AI Agent for Sales.” “Revenue Superintelligence.” “Fully Autonomous Outbound.” Everyone claims they can replace half your team with AI agents.

The Wrong Question

Founders end up asking: “Which AI tool should we use?”

If you start there, you’re already lost. Tools come and go. The real question is: “Where would AI actually move the needle in my revenue engine without creating chaos?”

This piece is for founders and CEOs who want grounded, operational clarity. No hype, no futurism, no promises of an “autonomous GTM team by Q3”. Just the reality of where AI delivers value today for companies with real customers and real ACV.

I’m talking about AI-driven B2B SaaS and deep tech companies with €5–15M ARR selling into traditional industries, mid-market and enterprise cycles, multiple stakeholders, ACVs from €20-30k to several hundred thousand. Mature enough to have systems. Early enough that every decision still matters.

Before going deeper, let me make something explicit: AI is a system-level shift. Not a tools game.

I’ve been experimenting with this long before AI became fashionable. Salesforce since 2010. Outreach and Drift since 2017. The Pavilion work on GTM tech stacks in 2019-2021. And the last 24 months spent researching and testing how AI actually embeds into GTM motions.

The conclusion hasn’t changed. If you rebuild your GTM around tools, you get chaos. If you rebuild around systems, AI becomes leverage.

Do not start from the tools

Strategy first. Technology second.

Teams keep buying tools hoping they’ll “fix” pipeline, qualification, outbound, forecasting.

They won’t, not if the underlying GTM motion is unclear.

Start from the revenue reality.

• Where are you losing time?

• Where are you losing deals?

• Where do reps guess instead of knowing?

• Where is your pipeline lying to you?

Only once you answer these questions does AI for GTM become useful.

The field of possibilities

Yes, the landscape is huge. This matrix from CopyAI is a reasonable map of what’s possible today. Dozens of workflows fully automatable.

But abundance creates confusion. The point is not “What can AI do?”. The point is “What should you do first?”.

For a €5–15M ARR company with enterprise motions, the priorities are clear. There are five areas where AI delivers real, fast, high-leverage gains.

And let me be clear: AI does not replace the human. It removes the robot work so humans can focus on judgment work. Not automation. Augmentation. A “Cyborg GTM” team where the machine handles inputs and the human handles trust.

Let’s get into what actually moves the needle today.

From Manual Hunting to Sniper Targeting (Surgical ICP)

A healthy GTM engine knows exactly where it wins. It doesn’t “go broad”. It hunts with precision.

A few years ago, building an ICP-aligned list was slow, manual, and error-prone. Offshore teams scraping LinkedIn, graduates guessing emails, random signals.

Now it’s a different world: one operator with the right workflow can do the work of ten. Faster, cheaper, and with much higher accuracy. Signals, enrichment, timing — all available instantly.

But here’s the part most people miss: the hard work isn’t generating the list. It’s knowing exactly who belongs on it.

Accuracy is the new efficiency. If your ICP is not christal clear, AI amplifies the chaos. If it’s sharp, this becomes your fastest quick win. You move from “carpet bombing” to “sniper targeting”.

This is the first real quick win for a post-PMF scaleup.

A warning: Don’t get dragged into the “GTM engineering” hype where agencies try to rebuild your entire system overnight. At €5–15M ARR, you need leverage and momentum, not disruption. Start with precision. Unblock value fast. Evolve later.

From Templates to Hyper-Relevance (First Meetings)

If you’re still using templates and generic scripts, you’re leaving pipeline on the table. Buyers have built immunity.

The old world: “Hi {Name}, I saw on LinkedIn that…”. Some light research. A standardized script.

The AI world: Context-rich relevance. The AI can digest a prospect’s annual financial report, podcast interview, hiring pattern, and recent news. It turns that into a hook that actually earns a reply. Then the human adjusts tone and judgment.

You no longer have to choose between Quantity and Quality. It’s not “less work”. It’s better work. And it compounds.

One clarification: I remain skeptical of fully automated outbound cannons unless you sell a commodity. In enterprise motions, AI gives humans leverage; it doesn’t replace them.

AI for GTM as a sparring partner (The Coaching Lever)

This is where the leap becomes obvious.

Before AI, you relied on AE reports. You trusted their interpretation. You reviewed random call recordings. You hoped qualification happened as prescribed. Then came transcription. Useful, but shallow.

Now? AI analyzes every meeting. It contrasts it with your playbook, surfaces red flags, highlights missed questions and suggests next actions.

For the AE, it’s coaching. For the Manager, it’s clarity. For the CRO, it’s truth.

And truth is what GTM has been missing for years. We’ve left the persuasion era. We’re in the qualification era.

AI becomes your Sparring Partner. It forces rigor. It removes wishful thinking. It exposes reality. And reality is what drives forecast accuracy.

The Pipeline Notary (Forecast Integrity)

Let’s be honest: forecast calls used to be a negotiation between reality and optimism. Reps had “happy ears”. Managers had little visibility.

AI changes this dynamic completely. If the evidence isn’t in the data, the deal is not qualified. End of the story.

AI checks transcripts against your qualification framework (MEDDPIC or similar):

• Did the rep identify the Economic Buyer? No?
• Did they clarify the Decision Process? No?
• Did they confirm compelling event, competition, metrics? No?

If it’s not there, it’s flagged. Immediately. This is not surveillance. It’s discipline. Forecasting stops being storytelling. It becomes revenue.

Data Integrity and Leadership Visibility 

This is the simplest and most misunderstood shift. Everyone talks about “saving reps time”. That’s irrelevant.

The real shift is CRM truth. AI captures what actually happened, not what the AE remembers, or chooses to report. Next steps, risks, objections, stakeholders, alignment: all surfaced and structured.

The CRM becomes reality and a strategic asset, not a fiction. Leadership finally operates with visibility:

• Are meetings following the intended choreography?
• Are opportunities meeting stage criteria?
• Where are reps skipping critical questions?
• Where is risk emerging?
• Where is coaching needed immediately?

This is leverage. This is operating with your eyes open.

The Vision: The GTM AI Operating System

If you implement a few of the points above, you’re already ahead of most of the market. But the real game is bigger.

The future of GTM isn’t a collection of AI tools. It’s a GTM AI Operating System.

You don’t need to rebuild everything. You don’t need a “GTM engineer” tomorrow. You don’t need a 6-month transformation.

You need clarity.

Start with one workflow where AI creates immediate value. Experiment. Codify. Scale what works.

The real frontier is not the toolset. It’s the operating model behind it. The best companies are already redesigning their GTM engines as unified systems. An AI-enabled operating layer that connects marketing, sales, CS and product into one motion.

Not more tools. Better systems. Faster signal-to-action loops. Less friction. More truth.

This is the real GTM AI Operating System.

Final Thought

There are no “AI experts” yet. We’re all learning in real time. The companies winning aren’t the ones waiting for clarity. They’re the ones already experimenting.

AI won’t replace your team. But a team that learns to use AI will outperform the one that doesn’t.

The threat isn’t AI. The threat is standing still.

If you enjoyed this post, you might also like:

 [The GTM Playbook Behind Woffu’s 9-Year SaaS Journey and Exit]

 Subscribe to SaaSification for no-fluff GTM insights, frameworks, and real stories for AI-driven SaaS leaders.

The post AI for GTM: Tools Are Not the Point. What’s Real, What’s Hype, and Where It Actually Helps appeared first on Luigi Mallardo.

The post ERR vs. ARR: The Founder’s Guide to SaaS Pilot Discipline in the AI Era appeared first on Luigi Mallardo.

This leaves founders with a crucial question: if you’re not ready for a full-time VP or CRO and wary of the fractional model, how do you get the senior strategic and tactical guidance you need to scale?

The answer isn’t to go it alone. It’s to be incredibly precise about the kind of help you need. Your network is cluttered with options: mentors, advisors, consultants, coaches. They can all be useful, but only if you know who you need and when. You wouldn’t hire an electrician to fix a leaky pipe. Let’s bring some clarity.

Deconstructing the GTM Support Landscape

The Full-Time VP or Chief Revenue Officer (CRO)

Think of this person as the captain for your transatlantic journey. You hire them when the ship is built, tested on shorter voyages, and ready for the open ocean. As we’ve discussed, if your GTM fundamentals aren’t in place, bringing on a full-time CRO is a premature and costly move. A great CRO is a vitamin that accelerates a healthy system, not a medicine to cure a sick one.

The Mentor

A mentor is like a friend who has successfully navigated the path before you. They offer advice, connections, and inspiration. The relationship is often informal and free of charge; mentorship is a state of being, not a structured activity. Expect a boost to your confidence and a trusted sounding board, but don’t expect them to provide hands-on GTM leadership or drive defined outcomes.

The Strategic Advisor

This is often a former operator or industry veteran who watches your “games” from the outside and shares high-level perspective. You might speak occasionally, meet for lunch, or have semi-regular catch-ups without a rigid agenda or expected deliverables. They provide valuable external viewpoints but are not designed to get their hands dirty in your day-to-day GTM execution.

The Consultant

Photo by Soloman Soh on Pexels

A consultant is a specialist you hire to solve a specific, well-defined problem. Think of them as the expert you call to install new windows in your home. They are incredibly valuable when you know exactly what you need: setting up a better sales process, optimizing your pricing, or deploying a targeted training program. You should expect and demand hands-on work on that specific topic. They deliver a solution to a known issue, not a comprehensive GTM strategy.

These roles all serve a purpose. But what if you don’t need a full-time captain, an informal guide, a high-level spectator, or a single-problem specialist?

What if you’re a hands-on founder, still acting as the de facto CRO, who needs consistent, structured, strategic guidance to make better decisions yourself?

This calls for a new, hybrid model.

The Third Path: The GTM Sparring Partner (Advisor & Coach)

This is the evolution of the fractional model, moving away from part-time operations and towards focused, high-impact strategic partnership. It’s not about doing the work for the founder; it’s about working with the founder to ensure they are making the best possible GTM decisions.

Think of it as the blueprint for your home renovation, combined with the expert who checks in weekly to make sure you’re building it right.

A GTM Sparring Partner is for the hands-on founder who doesn’t need another manager, but a world-class strategic partner in their corner. The engagement is designed for maximum clarity and impact with minimum operational friction.

How a GTM Sparring Partner Works:

• Structured & Consistent: This isn’t an ad-hoc call. It’s a disciplined, weekly (e.g., 1 hour/week) engagement focused on your most pressing strategic and tactical GTM challenges.

• Strategic Sounding Board: They help you pressure-test your assumptions on everything from positioning and pricing to channel strategy and team structure.

• Framework-Driven: They bring proven GTM frameworks (like my SaaSup model) and help you adapt them to your specific business, providing a clear system for growth.

• Coach & Enabler: They help you and your team grow. A great sparring partner helps you develop your own GTM leadership, find the right full-time CRO when the time comes, and manage that critical onboarding process.

Where an Advisor tells you what they would do, a Sparring Partner helps you figure out what you should do, and holds you accountable for executing it.

Conclusion: What Kind of Help Do You Really Need?

The post GTM Leader, Mentor, Advisor, or Sparring Partner? A Founder’s Guide to Choosing the Right Help appeared first on Luigi Mallardo.

The economic risk is immense. For an early-stage company, a senior GTM hire represents hundreds of thousands of euros in direct and opportunity cost.

When this critical hire fails, a shockingly common outcome, the consequences are severe: founder dreams are put at risk, valuations drop, and boards often enter a “circle of hell,” cycling through one failed VP after another.

So, it’s not surprising that many founders turned to a new model: the fractional CRO.

It promises:

• A lower-commitment way to get senior leadership.
• A flexible way to de-risk a critical hire.
• A tactical fix for strategic pain.

I was one of the first in Europe to embrace this model back in 2018. I ran full-stack GTM engagements for companies like Tiendeo and Wide Eyes, helping them scale and reach successful exits.

I wasn’t an advisor or a consultant. I was a fractional revenue leader, in the trenches.

Over time, after nearly seven years of seeing the model evolve, and seeing its cracks, here’s what I now believe: the classic fractional model is a temporary fix, not a durable strategy.

It was born as a reaction to a problem. Yet, it often creates a new set of challenges.

Let me explain why.

The Fractional Leader’s Dilemma: The Illusion of Impact

The idea behind the fractional model is solid:

“Let’s get an experienced operator to lead GTM for 1-2 days a week. We save cash and stay flexible.”

But here’s the truth nobody tells you: you can’t drive deep transformation in 1-2 days a week.

You often operate without real authority, missing critical context, and are too stretched to go deep into people, process, and culture. As a result, you become an expensive “doer” rather than a true transformer.

For the leader, it can become a comfort zone.

For the company, a dangerous illusion.

And importantly, for an ambitious, hungry leader who wants to truly shape a company’s destiny, it’s rarely the right long-term path.

The Founder’s Trap: The Illusion of Outsourcing GTM

Here’s the biggest trap I’ve seen again and again: founders believe they’ve “outsourced” GTM to the fractional CRO.

So they step back. They focus on product, ops, or fundraising. But GTM is not something you can outsource in the early stages.

You can’t outsource conviction.

You can’t delegate positioning.

You can’t hand off the core sales motion.

In short, this is what I call “Founder Abdication“, and when it happens, the GTM machine stalls. No matter who’s at the wheel.

The Real Choice: Full-Time Partner or Founder-Led GTM?

This brings us to a crucial, binary choice every founder must make.

Either you are ready to bring a true GTM partner on board, or you are not.

If you are, you’re not just hiring a CRO. Instead, you’re bringing on a GTM co-founder.

This person must be fully integrated, empowered with a clear mandate, and trusted to shape the company’s future alongside you.

They are all in.

But if you’re not ready, the answer isn’t a halfway measure.

Instead, the answer is to own your role as the company’s GTM leader.

This is where the fractional model can become a trap.

It creates a false sense of security, delaying the hard but necessary work of building a GTM foundation that only a founder can truly lead.

What Do Hands-On Founders Really Need?

So what does a founder who is still the de facto CRO really need?

Not a part-time operator.

Not a manager.+

Rather, a strategic sparring partner.

This became crystal clear in my work with companies like Cloud Academy.

The CEO was brilliant and deeply involved in his GTM, but he needed a high-level sounding board to challenge assumptions, de-risk key decisions, and inject external perspective.

My role wasn’t to run his sales team. It was to ensure he was equipped to lead it more effectively.

It wasn’t a fractional CRO engagement.

It wasn’t classic advisory.

It was something else: more focused, and ultimately, more impactful.

What Comes Next

The classic fractional model was a necessary innovation.

But now, it’s time to evolve:

• From execution bandwidth to strategic and tactical depth.

• From outsourcing GTM to owning it, with the right partner.

• From fractional leadership to a more agile model of strategic GTM coaching and advisory.

Is there still a place for the fractional model? Sure.

It can be a short-term fix to plug a gap, or a way to “date before you marry” a future GTM leader.

But it’s not a long-term strategy for building a scalable revenue engine.

In my next article, I’ll break down what this “third path” really looks like, and how a GTM Sparring Partner is built for hands-on founders in the new era of capital-efficient, AI-driven SaaS.

If you enjoyed this post, you might also like:

[The GTM Playbook Behind Woffu’s 9-Year SaaS Journey and Exit]

Subscribe to SaaSification for no-fluff GTM insights, frameworks, and real stories for AI-driven SaaS leaders.

The post The Fractional CRO Fix: A Temporary Solution or Another Trap? appeared first on Luigi Mallardo.

The story is about a few mice; the mouse that does well is the one who (1) realizes the early signs that the “cheese” is going to finish soon and (2) finds the courage and common sense to identify the right things to do, then finally (3) she can make it happen.

In B2B SaaS in mainland Europe an interesting tale could be about 3 CEOs that share the same ambitions (grow the company, work hard, enjoy the journey, become multimillionaires), but they are 3 different characters and they act differently.

BOTTLENECK CEO

The Bottleneck CEO tends to micromanage too much.

In B2B SaaS, scaleups with Bottleneck Founders, who can be good salespeople as well, can grow well at the beginning but at some point, by 3-5 million € in ARR at the latest, the revenue growth start to decline sharply and in 1-2 years it can go to zero.

An “enlightened” Bottleneck CEO recognizes not too late that the company go-to-market approach needs to be professionalized and starts to build teams and processes with the appropriate experience and focus.

Many Bottleneck CEOs unfortunately delay too much the needed transformation and then it becomes a real issue or, worst case scenario, they mutate in a MARADONA CEO once they get close to a burnout for accumulating too much stuff on their shoulders.

MARADONA CEO

Why Maradona? Because she’s looking all the time for that superstar Go-To-Market Leader (CRO or VP of Sales) that will sort things out so she can focus on the things she likes the most: the product, the press, raising money, whatever.

As soon as the company raises a decent round, the MARADONA CEO recruits the GTM Leader and most of the times it’s a failure. After one year nothing has happened, the Leader vanished, got fired or resigned and things are again on the CEO shoulders.

What is the cost of this? Founder dilution on the next round plus hundreds of thousands € in management, operational and opportunity costs.

Read more here about the common mistakes (link):

• Timing
• Profile
• Expectations
• Onboarding

A typical case is the Maradona CEO who gives one or two shots of CRO or VP. If none works then the Bottleneck soul takes the lead again and the CEO may lose faith in the VP formula.

DOWN-TO-EARTH CEO

The Down-To-Earth CEO does not want to reinvent the wheel on sales scaling best practices.

She knows that to scale healthily she needs:

• Strict strategic focus and a solid value proposition and product marketing
• Obsession for sales process and funnel KPI’s
• The right sales people with the appropriate experience, in the right roles, at the right time.
• An experienced hands-on GTM Leader after the team has already a few high performers.

The Down-To-Earth CEO knows that the biggest threat to scalability is not executing on time a set of Go-To-Market Fundamentals for a healthy and sustainable revenue growth. There would most likely be slow down of revenue growth for one or a combination of the following reasons:

• Raw sales process and Playbook (eg every deal is different and new sales reps struggle to learn)
• Value proposition and Outbound sales struggling on bigger deals
• Biggest mistake – the VP Sales or CRO

Her Go-To-Market vision for B2B SaaS

She knows the biggest driver of customer loyalty is the Sales Experience she’s able to build into the organisation.

The Down-To-Earth CEO will scale the team, including an experienced GTM Leader, after having reached concrete signals of revenue predictability.

I’ve seen many CEOs living their Bottleneck “childhood” too long, and then moving all of a sudden into a “Maradona” mode, looking for the great VP/CRO.

It doesn’t work 90% of the times, especially when they have high revenue expectation not backed up by a working engine and they need to start from scratch a sales team or have an existing team with specific issues and wrong “postures”.

Other CEOs, on the contrary, as soon as they decide to professionalize the sales engine, become too perfectionists about sales process, CRM, tracking or other techie stuff. Wrong focus.

The Down-To-Earth CEO knows that the Process is just one of the 4 Pillars needed for a healthy go-to-market execution, it’s just one leg in a long journey.

To scale healthily you need two legs and two arms, well harmonised.

Can you imagine someone running a race with only one leg, without the other leg, and with no arms?

CONCLUSIONS

VCs have been investing a lot of money and there is a general concern about the exits.

Many B2B SaaS Scaleups are injured and at risk of future devaluation or extinction for a combination of inappropriate go-to-market execution and for the impact of the storm we have been experiencing after the pandemic.

Many of these companies can be recuperated if we:

• Calm down and stop wasting energy on unicorn infatuation
• Stop believing in ‘growth at all cost´mindset
• Focus on exits based on revenue and process engineering
• Stop thinking that hiring a better GTM Leader is always the solution

Why do you think the average tenure of a Revenue Leader (VP Sales and CRO) is less than a year and a half, everywhere?

If you enjoyed this post, you might also like:

[A Founder Guide to Choosing the Right Help]

[The GTM Playbook Behind Woffu’s 9-Year SaaS Journey and Exit]

Subscribe to SaaSification for no-fluff GTM insights, frameworks, and real stories for AI-driven SaaS leaders.

The post As a CEO are you Bottleneck, Maradona or Down-To-Earth? appeared first on Luigi Mallardo.