Jimmy de GrootBy Jimmy de Groot··5 min read

Multi-Threading in Sales Starts With the Person Nobody Emails

Multi-threading in sales fails when you only go to the top. GovTech advisor John Kitsmiller on mapping every persona, and how to scale it.

Outbound

Multi-threading in sales means building relationships with several people in one account instead of betting the deal on a single contact. John Kitsmiller, founder of the GovTech go-to-market practice energizeGTM, learned it in two decades of government sales: deals are decided by everyone below the top, including the people other vendors never email.

Key takeaways

  • The classic multi-threading mistake is going straight to the top and skipping everyone below, says John Kitsmiller of energizeGTM.
  • The person the org chart overlooks can tip the deal when your outreach shows you understand their job.
  • Buyers decide before they call you: 6sense's 2025 Buyer Experience Report found 95% of winning vendors were already on the day-one shortlist.
  • Reps are stretched: 48% of sellers lack bandwidth for adequate cold outreach, according to Salesforce's 2026 State of Sales report.
  • Multi-threading scales when every contact gets their own message and their own page, without extra rep work.

What is multi-threading in sales?

Multi-threading in sales is engaging several stakeholders in the same account at the same time, each with a message about their own role. A single-threaded deal depends on one champion. If that person goes quiet or changes jobs, the deal goes with them.

John Kitsmiller has sold to government for more than 20 years, most recently SaaS for prosecutors' offices. He sees the same failure again and again. A vendor reaches an elected official or a department head, assumes the job is done and skips everyone below. Then the vendor loses and does not understand why. The people they ignored were part of the decision.

Today John helps early-stage GovTech and LegalTech founders avoid exactly that, through his go-to-market services at energizeGTM.

Why does the person nobody emails decide so many deals?

The overlooked stakeholder decides deals because they are close to the work, and every other vendor ignored them. John's favourite example is the victim advocate in a prosecutor's office: the person who helps crime victims understand their rights. Most vendors of case management software do not know the role exists.

It cuts both ways. In his article on WIIFM in government sales, John describes an evaluation at a county DA's office that stalled after a victim advocate raised usability concerns with the chief deputy. Nobody had asked what that user needed.

He has also seen the opposite. A so-called nobody becomes the loudest internal voice for a vendor, simply because that vendor spoke to their real problems.

How do you map every persona in an account?

You map every persona by narrowing your ICP first, then listing every role that touches the problem. John starts every client engagement this way, and he explains why in his piece on niching down your SaaS GTM.

For a prosecutor's office, his list is long: the elected prosecutor, managing attorneys, paralegals, legal assistants, office administration, investigators, victim advocates, IT and procurement. Each has a different stake. Send an IT person a message about managing cases and you get deleted, because that is an attorney's concern.

Single-threaded outreachMulti-threaded outreach
Who you contactOne senior decision makerEvery role that touches the problem
MessageOne pitch for the organisationOne argument per role
If your contact goes quietThe deal stallsOther threads keep it alive
Without repliesNothing happensStakeholders discuss you internally

That last row matters. Even when people do not reply, relevant outreach gets talked about inside the account.

How do you multi-thread without burying your reps?

You multi-thread without burying reps by automating the role-specific part. Five tailored arguments for five stakeholders in fifty accounts is 250 pieces of custom work. That is where outbound breaks, especially when Salesforce finds the average seller spends only 40% of their time selling.

This is what Neuropage was built for. Every lead gets a page built around who they are, generated automatically from public role data. Put the IT director, the operations lead and the department head of one account in the same sequence, and each gets a page that opens with their own concerns, on your domain and in your brand. Reps write nothing extra. See how teams use personalized pages in outbound sequences, and how this works for B2B SaaS teams selling into committees.

Per-lead analytics then show which threads are warm. If IT and procurement opened their pages but the department head did not, you know where your next call goes. More on that in our lessons from personalized pages.

My take: one email was never enough

I started Neuropage because of this exact problem. In my previous sales job I kept trying to fit everything into one email, and it never fit. Different people in the same company needed different information to say yes. So I asked: why not send each of them to a page built for them?

When John told me about the victim advocate, I recognised it immediately. The deal is never one person. If you want to see how John thinks about this in practice, listen to his podcast Built for Government. It is one of the most honest looks at selling into complex organisations I know.

Frequently asked questions

What is the difference between single-threaded and multi-threaded deals?

A single-threaded deal relies on one contact. A multi-threaded deal has relationships with several stakeholders, such as the economic buyer, IT, finance and daily users. Multi-threaded deals survive when one contact goes quiet, and they show you where the whole account stands.

Should you contact the decision maker first?

Not only the decision maker. Contacting just the top is the mistake John Kitsmiller of energizeGTM sees most in government sales. Senior leaders rely on the people below them to judge fit and risk. Reach them alongside the operational roles, each with a message about their own work.

How many people should you contact per account?

Contact every role that genuinely touches the problem your product solves, and nobody else. In a prosecutor's office that can be six or more roles. In a smaller B2B company it might be three. What matters is that each contact gets an argument written for their role.

Multi-threading in sales is a relevance problem

Multi-threading in sales works because committee deals are decided in conversations you are not part of. John Kitsmiller's rule applies everywhere: do not skip the people below the top, and do not send them someone else's pitch. Want his full approach? Start with his free GTM readiness assessment. Then see how Neuropage builds a page for every lead and turn one account into five warm threads.

Read us first on Google

Pick Neuropage as a preferred source and Google can show our articles more often in your Top Stories and AI Overviews.

Add as preferred source

Jimmy de Groot · Founder of NeuroPage

Jimmy ran outbound before he built NeuroPage. He started it because personalization was never a belief problem but a cost problem: half an hour of research per lead, so it only ever reached a shortlist.

Built for teams like yours

Turn every lead into a personalised landing page, automatically

NeuroPage connects to your outbound, paid, or organic workflow and generates unique pages for every prospect.

See how it works

Continue reading

10 new teams every week

See personalization in action, with your own data

Book a 15-min demo. We'll build a personalized page for one of your actual leads during the call.