A legal tech sales leader opens the forecast on a Monday. Four deals have sat in “Contract sent” for six weeks. By the pipeline’s math, they are 90% likely to close this quarter. By the rep’s account, they are fine — they are in the buyer’s security review, which always takes a while. Both are describing the same four deals, and it is the pipeline that is wrong.
HubSpot ships with seven deal stages: appointment scheduled, qualified to buy, presentation scheduled, decision maker bought-in, contract sent, closed won, and closed lost. Per HubSpot’s documentation, each one carries a default close probability, and those probabilities drive the weighted pipeline number the company reports to its board. Decision maker bought-in sits at 80%. Contract sent sits at 90%.
For a fast, transactional sale, that is a reasonable curve. In legal tech, “decision maker bought-in” is often where the hard part starts. Intapp said as much in its annual report to the SEC, describing a sales cycle that is “lengthy and unpredictable and often requires pre-purchase evaluation by a significant number of employees in our clients’ organizations.” That is a public legal software company describing its own sales motion, in a document it can be held to.
Forrester’s 2026 buyer research puts procurement in a decision-making role in about half of business purchases. So in roughly half your deals, a function that appears nowhere in the default pipeline is making a call at exactly the point the model has already scored at 80 or 90%.
Two things break at once. The forecast inflates, because deals sitting in procurement carry near-certain weights. And reps look stalled when they are not, because a deal that has not changed stage in six weeks reads as neglected — even when it is moving through legal review right on schedule. Managers then coach against a picture the system drew wrong.
The reps have been telling the truth. The pipeline just has no field for it.
| Default stage | What's usually happening in legal tech | Stage worth adding |
|---|---|---|
| Decision maker bought-in | The champion is sold; the committee isn't yet | Committee or partner approval |
| (nothing) | Security questionnaire, SOC 2 request | Security and vendor risk review |
| Contract sent | Redlines, procurement terms, legal review | Procurement and legal |
In a law firm sale, the committee stage often means a partners’ meeting that happens once a month. Model it as a stage, and a six-week gap stops looking like a stall.
Then reset the probabilities to what actually converts from each stage, not what the defaults assume. And turn on time-in-stage reporting, which HubSpot calculates automatically once the stages exist.
The payoff is bigger than a cleaner forecast. Once security review is its own stage, it has an average length you can see — and a cost you can see is a cost someone will own. That is usually when a company builds its security questionnaire library and has its SOC 2 report ready before a buyer asks for it.
Pull every open deal older than sixty days. For each one, ask the rep a single question: what is actually happening right now? Count how many answers do not match a stage in your pipeline. Most teams find the answers cluster around the same two or three missing stages. If it is more than a handful of deals, your forecast is describing a sale you don’t run.
So the forecast isn’t wrong because reps are optimistic. It’s wrong because the pipeline has no words for the longest part of the sale. Give it the words, and the number starts meaning something again.
If you find this content insightful, consider subscribing to our LinkedIn Newsletter and following our company page for our latest articles!