Scaling Complex B2B Tech: When GTM Instinct Ends and Architecture Begins

A founder scaling a B2B tech startup shows me the vision, the plan, and the end-of-year target. €4.5 million. He’s sitting at €2.5M today.

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

Recent post

Scaling Complex B2B Tech: When GTM Instinct Ends and Architecture Begins

A founder scaling a B2B tech startup shows me the vision, the plan, and the end-of-year target. €4.5 million. He’s…

The Focus Paradox: Why Reducing Market Optionality Increased Exit Value

Startups are addicted to optionality. We want to keep every door open. Every vertical. Every feature. Every possible revenue stream.…

AI for GTM: Tools Are Not the Point. What’s Real, What’s Hype, and Where It Actually Helps

The AI for GTM space has become a circus. Every week a new “AI Revenue Orchestration Platform” appears. Our feed…

Luigi Mallardo
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.