The multi-threaded enterprise deal playbook

Liively sells partnership contracts worth several million, on cycles of six to eighteen months, across email, LinkedIn and WhatsApp, with multiple stakeholders on both sides. This playbook is how they stopped losing those deals to one rep's inbox: one thread per deal, a contract value threshold that forces multi-threading, and a note format written for month fourteen rather than for today.

The old setup was a $90 a month HubSpot plan that stored contacts and little else. The CRM was not really the problem. The problem was that the deal's actual history lived in three places, none of which were the CRM.

Where long deals actually die

Not at the pitch. Not on price. They die in the gap between the person who built the relationship and everyone else.

On an eighteen-month deal, the real history is a WhatsApp exchange in month three where the buyer mentioned their fiscal calendar, a LinkedIn message in month seven where a new stakeholder introduced themselves, and an email in month eleven confirming a scope change. Each conversation is visible to exactly one person: whoever sent it.

Then that person takes leave, changes accounts, or simply forgets, and the deal restarts from a blank page. On a contract worth seven figures, that is the single most expensive failure mode in the business, and it is entirely structural.

One thread per deal

The change was mechanical rather than clever: every channel syncs into the deal record. Email, LinkedIn, and WhatsApp land in one chronological thread that any teammate can open.

What that unlocks is less about convenience and more about who can act:

• Anyone can pick up a conversation without asking a colleague what happened
• A new stakeholder appearing on the buyer side is visible to the whole team, not just the rep who got the message
• The commitment made in month four is findable in month fourteen, when it matters and nobody remembers it
• Handover takes five minutes of reading rather than a meeting that reconstructs history from memory

The two hours a week saved per person is real, but it undersells the effect. Those two hours were previously spent asking other people what had been agreed, which means the cost was paid twice: once by the person searching, once by the person interrupted.

Multi-threading the buyer side

Unified history makes a second discipline possible: refusing to run a large deal through one contact.

Their rule is a threshold. Above a certain contract value, a deal cannot progress past early stage with only one named contact on the buyer side. Below it, single-threading is fine and chasing more contacts is wasted effort.

The threshold matters because "always multi-thread" is advice that gets ignored on small deals and then forgotten on the large ones. A number makes it enforceable.

Finding the second contact is easier once history is shared: the people who appear in CC lines, get mentioned in WhatsApp messages, or view the company's LinkedIn are already visible in the thread rather than buried in one rep's inbox.

Log decisions, not meetings

The second habit that made shared history usable: notes record what was agreed, not what happened.

A meeting note that says "good call, discussed timelines, they seem positive" is worthless in month twelve. A decision log entry is not:

Confirmed they cannot sign before the new fiscal year starts in April. Procurement lead is the approver, not the sponsor we have been speaking to. They asked for the multi-year option to be priced separately.

Three facts, each of which changes what happens next. Nobody rereads meeting notes, but everyone searches for what was agreed, and the search only works if somebody wrote the decision down.

What broke and how they fixed it

WhatsApp stayed personal at first. Reps kept using their own accounts for the easy conversations, which rebuilt the exact invisibility they were trying to remove. Syncing WhatsApp into the deal record closed the last gap, and it was the channel carrying most of the informal commitments.

Notes reverted to meeting summaries. They changed the prompt in the note template from "what happened" to "what was decided and what changes because of it". Small edit, most of the value.

Old deals stayed single-threaded. New deals followed the rule; deals already in flight kept running through one contact because nobody went back to fix them. A monthly audit of open deals for single-threading now catches those.

The numbers

Two hours a week saved per person, three channels unified into one thread per deal, a $90 monthly HubSpot bill removed, and a 15% higher close rate on the multi-million dollar contracts where losing context is the most expensive mistake available.