VECTOR
guide

Level Selling: Why You Need More Than One Person Inside the Account

Running enterprise sales like a product team - one owner, one lead - is why deep tech deals stall at month four. Here's how level selling fixes single-threaded accounts.

Nick Black · · 4 min read
Architectural cross-section illustration of two buildings on opposite cliffs — a glass corporate office on the left with an executive at a boardroom, and an industrial workshop on the right with engineers at a desk — connected by a single magenta suspension bridge spanning the gap between them.

Level Selling: Why You Need More Than One Person Inside the Account

When I first started scaling enterprise sales, I ran it the way I had run my product teams. One owner per problem. One lead per project. I led the charge from the front, worked the relationship with the most engaged person at the customer, and treated that contact as my way into the account.

Turns out that doesn’t work for selling.

The relationship felt productive. The POC was going well. The technical champion loved us. And then somewhere around month four the deal would go quiet, and I couldn’t work out why.

Here is what my project-owner instinct was hiding from me: nobody decides to buy your product alone. Gartner’s research on B2B buying groups, written up by Brent Adamson and his colleagues in HBR, puts the typical decision group at 6 to 10 stakeholders, and in genuine enterprise it is higher. If you are running the account through one contact, you are flying blind on everybody else who has a vote.

The Principle

The way around this is called level selling, or multi-threading. You stop running the account through a single contact and start pairing functional areas across the two companies. Engineers to engineers. Commercial to commercial. Founder to senior executive.

Why it works is simple. People are most honest with their peers. Your customer’s lead engineer will raise a real architectural concern with a senior engineer on your side in a way they will not raise it with your CTO, who they may find intimidating. Their COO or department head will tell your founder whether the project actually sits on the executive priority list, or whether you are being kept warm by a champion whose own boss isn’t bought in.

Pairing creates honesty. Honesty surfaces friction earlier in the cycle, when you can still do something about it.

The Hardest Move: The Founder Has to Level Up

If you’re the founder leading sales, the trickiest part of all of this is not hiring the team. It is getting yourself out of the tactical seat.

While it feels productive to be the one chasing the technical conversation - because you know the product, you can answer any question, you’ve been doing this since day one - it is the wrong place for you to be once the deal is maturing. Your job is the executive room. The EVP, the VP, the CTO whose budget this lands in. The strategic conversation about what your product means for their three-year roadmap, not the tactical one about whether the API handles their throughput.

This is where the value crystallises. A senior buyer needs to see your product as a game-changer that reshapes what their company can do, not as another vendor on the procurement list. They will only see that from a peer-level conversation with you - and you can only have that conversation if you have stopped doing the technical demos.

Meanwhile, push the engineering questions down. Your customer’s engineers will be more comfortable raising their actual concerns with one of your more junior engineers than with your CTO. That is where you learn what is going on underneath the polite technical conversation.

What Level Selling Buys You

When you multi-thread an account properly, four things start to happen at once:

  • More deals close, because the senior buyer is bought in alongside the technical champion, not informed about them at the end.
  • Problems surface earlier, because peers tell each other things they will not tell up the chain.
  • Consensus builds inside the customer, because multiple people across functions are now talking about you internally without you in the room.
  • Hidden anxieties and frictions get smoked out: the legal review nobody mentioned, the political resistance nobody named, the budget cycle nobody flagged.

You get to the truth of the deal faster. That is the prize.

What to Do This Week

  1. List every active deal. For each one, write down every customer contact you have, what function they sit in, and what seniority level they hold.
  2. Mark the deals where you only have one contact, or where every contact sits in the same function. These are your single-threaded deals. They are the ones most likely to go quiet.
  3. For each single-threaded deal, draft the bridging move. Who on your team needs to meet who on theirs, and what specifically gets discussed in that meeting.
  4. As founder, identify the most senior person you have met in each account. If it is not the EVP, VP, or P&L owner, plan how you reach them. Usually you ask your existing champion for an executive sponsor introduction, and you frame it as helping them build the internal case.

If you have read our discovery playbook, this is the natural extension of it: discovery is what you learn from a single conversation; level selling is what you learn from the right conversations happening across the account in parallel. It also pairs cleanly with the qualification work in our MEDDIC piece - you cannot qualify a deal you are only seeing through one window.


Watching a technically-validated deal go quiet at month four? That is almost always the signature of a single-threaded account. Apply to VECTOR and we will pressure-test your live deals with you and rebuild the engagement plan one level at a time.