Here is a story, invented but built from a very ordinary pattern. Rohan sells workflow software to mid-sized insurers. In January he is working a deal with a general insurer in Mumbai, around ₹1.2 crore over three years. His contact is Anita, an assistant vice president in operations. She is enthusiastic, answers messages within the hour, and has told him twice, “I want this, it will fix our claims backlog.”

Rohan marks the deal as Commit. Why wouldn’t he? Anita is the sponsor, she has budget in her plan, and the demo went well. He never meets anyone else, partly because Anita says she will “take it forward internally”, partly because chasing others feels like going around her.

In March, Anita accepts an offer from another company and gives notice. Her replacement, who arrives in April, has a different priority list, has never seen the demo and has been told to review all pending vendor commitments. Nobody else at the insurer knows Rohan. By June the deal has been pushed to “next financial year”. Rohan did nothing wrong in the conversations he had. His mistake was in the conversations he never had.

Threads, not a thread

Multi-threading means building relationships with several people at the buyer, across roles, so that a deal does not depend on any one of them. The word comes from the image of a rope: one strand snaps easily, several together hold.

Who would Rohan have wanted to know? Start with the people who matter in a typical purchase of this size. The economic buyer, who controls the money: here perhaps the chief operating officer. The users, the claims team leads who would live with the tool every day. The technical evaluators, from IT and information security. Someone from procurement and one from legal or compliance, since insurers are regulated and will ask serious questions. And possibly a sceptic, the person who liked the old way, whom it is better to meet in March than to be surprised by in June.

Why reps avoid it

It is uncomfortable. Asking your friendly contact to introduce you to her boss feels like implying she cannot manage the process. Reaching a senior person risks a rejection. And a single contact is efficient: one phone number, one thread of email, one story. Efficiency is the trap, because it feels like progress.

The way through is to make it Anita’s idea, or at least obviously useful to her. Imagine Rohan had said in January: “To put together a business case your COO will accept, I need to understand how he measures the claims function. Could we spend thirty minutes with him, with you in the room?” That request is a favour to Anita. It protects her proposal. Most sponsors who genuinely want the project say yes, and if she hesitates, that is itself a finding, because it suggests her influence is weaker than she let on.

Reading the threads you have

A quick test, worth running every week on your top deals. Write the names of the people who will decide or influence the purchase. Beside each name write: have I spoken to them directly, and what do they think of us? If you have two names with nothing beside them, you do not yet know your deal. If your only strong relationship is with someone junior to the economic buyer, your forecast probably deserves a haircut.

Notice also what kind of relationship it is. A friendly contact is not necessarily a champion. A champion has influence in their company, a personal stake in the outcome, and is willing to spend their own credibility for you, for example by presenting your case in a meeting you are not in. Someone who simply likes you, but cannot influence a decision, is a coach at best.

How to build the other threads

  • Use your own seniors. A sales director calling a COO is a peer conversation; a salesperson calling a COO is a cold call. Bring your executive in with a specific purpose, not just “to say hello”.
  • Offer something to each role. Users want to see their workflow; IT wants an architecture session; finance wants the business case; legal wants the data-handling terms early.
  • Put them in the plan. A joint plan of dated steps, with a named person on the customer side for each, quietly forces the introductions.
  • Ask directly, as a normal part of the job: “Who else should we be talking to about this?”

Back in June

Suppose Rohan had done this. When Anita left, the claims leads already wanted the tool, the COO had seen the business case, and the information security review was half complete. The new head of operations would have found a project with momentum and several voices behind it. Replacing the sponsor might still have cost a few weeks, but not the deal.

One limit, to be fair about it: multi-threading takes time, and in a small, fast purchase of a few lakh there may genuinely be one decision-maker. Do not turn a three-week deal into a three-month tour. Match the effort to the size of the deal and the number of people who will have an opinion.

Figures and names in the examples are illustrative.

Leave a Reply

Trending