How Do You Flag Single-Threaded Deals in HubSpot?

How do you flag single-threaded deals in HubSpot?

Use HubSpot's default deal property, Number of associated contacts, which HubSpot updates automatically. Build a saved deal view that shows open deals where that number is below two, past a stage you choose. Then add a weekly review or an automated task so someone acts on the list before those deals stall.

A single-threaded deal is one where your whole relationship rests on one person at the buyer. If that person goes quiet, changes jobs, or loses an internal argument, the deal dies and you often do not know why. Most small sales teams know this risk in theory. Very few can see it in their CRM at a glance.

This tutorial is for a founder or a two to five person sales team running deals in HubSpot. It takes under an hour to set up, and it turns a vague worry into a list you can work every week.

Why does single-threading matter enough to track?

Because one contact is one point of failure. Deals with several engaged people at the buyer have more paths to a signature: a second champion, a budget owner who already knows you, a technical evaluator who has seen the product. Tracking the contact count makes that risk visible early, while you can still fix it.

I think of contact count as a leading indicator, not a guarantee. A deal with four associated contacts can still be single-threaded if three of them never opened an email. But a deal with one associated contact is almost always single-threaded. Starting with the simple count catches the most obvious risk with almost no setup.

If you want the strategy side of how to add people to a deal once you spot the gap, I wrote about how to multi-thread a deal with a two-person sales team. This article is the CRM setup that tells you which deals need it.

What does HubSpot already track for you?

HubSpot's default deal properties include Number of associated contacts, which its knowledge base describes as the number of contacts associated with the deal, updated automatically by HubSpot. That means you do not need a custom calculation to start. You only need to make sure reps actually associate the right contacts.

That last point is where most setups fail. The property can only count what is associated. If a rep emails three people at the buyer but only links one contact to the deal, HubSpot will count one. So before you build anything, agree on one rule with your team: every person who joins a call or replies to an email gets associated with the deal.

Also check your association settings. HubSpot lets admins set limits on how many records can be associated, so confirm that no limit is blocking reps from adding contacts. HubSpot's knowledge base has a page on setting limits for record associations if you need to review it.

Step one: which deals should the flag cover?

Only open deals past an early stage should be flagged. A brand new deal with one contact is normal. A deal at proposal stage with one contact is a risk. Pick the stage where you expect at least two people involved, often after discovery, and flag only deals at or beyond it.

Write this down before you touch HubSpot. Look at your deal pipeline and choose the earliest stage where a healthy deal should have a second person. For many B2B SaaS teams, that is the stage after the first demo, because a serious buyer usually brings in a colleague for the second conversation.

Also decide on the threshold. Fewer than two contacts is the simplest rule and the one I recommend starting with. If your deals usually involve a committee, you might raise it to fewer than three for late stages.

Step two: how do you build the saved view?

In the deals index, filter by pipeline, then by deal stage to include your chosen stages, then by Number of associated contacts less than two. Save the view with a plain name like "Single-threaded deals past discovery" and share it with the sales team so everyone sees the same list.

The exact clicks change as HubSpot updates its interface, so follow the current HubSpot knowledge base article on creating and saving views if the menus look different. The logic stays the same. Three filters: the right pipeline, the right stages, and a contact count under your threshold.

Add a few columns to the view that help with action. Deal owner, close date, amount, and last activity date are the ones I find most useful. With those, a rep can scan the list and see which single-threaded deals are both valuable and close to their expected close date.

Step three: how do you make sure someone acts on it?

A saved view nobody opens does nothing. Either review it in a weekly pipeline meeting, or create a workflow that assigns a task to the deal owner when a deal enters a flagged stage with fewer than two contacts. The task should ask for one specific action, such as adding the economic buyer.

The weekly review is the simplest version and works well for small teams. Open the view at the start of your pipeline meeting and ask each owner one question for each flagged deal: who else at this company needs to be in the next conversation?

The automated version uses a deal-based workflow. Set enrollment to deals at your chosen stages where Number of associated contacts is less than two, and have it create a task for the deal owner. Workflow availability depends on your HubSpot subscription, so check HubSpot's current documentation for which plans include deal-based workflows before you plan around it. If you already use stage-based automation, my tutorial on building a stale deal alert in HubSpot follows the same pattern.

Step four: how do you report on single-threading over time?

Build a simple report that counts open deals by stage and splits them by whether they have fewer than two associated contacts. Track the share of single-threaded deals at late stages each month. If that share falls, your team is multi-threading earlier, which usually shows up later as steadier close rates.

I would keep the report to one chart. Stages along one axis, deal count on the other, with single-threaded and multi-threaded deals shown separately. It is easy to read in a meeting and hard to argue with.

You can also compare closed won and closed lost deals by their contact count at the time they closed. Over a few quarters, that comparison tells you whether multi-threading actually matters for your sales motion, instead of relying on general advice.

What are the common mistakes with this setup?

The biggest mistake is trusting the count without checking association habits. Others include flagging deals too early in the pipeline, which creates noise, and never assigning an owner to act on the list. A flag works only when the data is clean and someone is responsible for each flagged deal.

A quieter mistake is counting contacts who do not matter. Associating a generic billing contact or an assistant who scheduled the call can push a deal over the threshold without adding real influence. Ask reps to associate the people who will actually shape the decision.

Finally, do not make required fields do this job. You could force reps to add two contacts before moving a stage, and I covered stage requirements in setting required properties on HubSpot deal stages. But forcing a second contact often leads to fake associations. A visible flag and a real conversation work better.

What should you do next?

Agree on the association rule with your team, pick the stage where a healthy deal has two people involved, and build the saved view with three filters. Review it every week for a month. Once the habit sticks, add the automated task and the monthly report to see whether multi-threading improves your close rates.

Start small. One saved view and one weekly question can change how your team thinks about deal risk. The automation and reporting can come later.

I build CRM workflows, lead routing, and pipeline reporting for B2B SaaS teams, mostly in HubSpot. If you want help setting up single-threaded deal flags and the reporting behind them, reach out at pravinkumar.co. Let's chat.