Path to Close: budget, pain and the close

Path to Close tracks five closing steps on every MSP deal — pain, budget, decision maker, offer, open objections — with one budget record and a pain ladder.

Path to Close

A normal CRM asks the rep whether the deal is qualified. This one shows its working.

Most CRMs hold qualification as a handful of checkboxes the rep ticks when they remember to. MADDOX stores a Path to Close on every deal: five closing steps — pain, budget, decision maker, offer, and no open objections — each met, unmet or honestly unknown, all judged by one rule set. Behind it sit one budget record per deal with the gap between what the customer can spend and what you quoted worked out for you, a four-level ladder for how deeply each pain has been explored, and a set of reads around the deal that say what is missing before a forecast call has to.

How it works

Five steps, one rule set, every surface

The steps, the two records that feed them, and the reads that use them.

Five closing steps in one place

Pain, Budget, Decision maker, Offer, No open objections. The rules that decide each one live in exactly one place, and every surface that shows a step — the panel, the readiness reads, the advice shown when a deal moves — asks that one place. A deal with no qualification history reads unknown, never unmet: nobody gets marked down for a question that was never recorded.

One budget record, one pain ladder

Was money discussed, what range did the customer name, what did we quote, how did they take it — one record per deal, read by every budget surface, with the gap computed fresh each time it is shown. Each pain carries a depth: mentioned, explored, quantified, or personal — the last meaning the buyer said what the problem costs them. Depth only ever goes up.

Reads that say what is missing

A close-picture strip across the top of the deal, a deal spotlight of what to ask and what to watch, a scan of meeting transcripts for things the rep said that cut against your sales process, and a second probability argued from evidence beside the rep’s own. Each one says what it is based on.

In the product

Where the deal actually stands, in one strip.

closing_steps: 5 budget_gap: computed per view pain_depth: 4 levels Sample data — illustrative product UI, not a performance claim.

The two records

Budget and pain, recorded once and read everywhere

Four scattered budget fields with four provenances is how one deal comes to say five different things about one conversation. So each of these is one record, and every surface reads it.

The budget record

One row per deal holds the budget conversation: whether money was discussed, the low and high the customer named, the amount and cadence we quoted, their reaction, notes, and the quote from the conversation that supports it. The Path to Close budget step, the deal sheet’s budget block, the 1:1 prep sheet and the pipeline card all read this one row.

The gap between quote and budget is computed every time it is shown rather than stored, so a correction to any of its inputs is reflected immediately and there is no stale figure to explain. The record is drafted from conversations, but a rep who edits it outranks the draft from that moment on: later passes propose a change for review instead of overwriting what somebody wrote.

The pain ladder

A pain is not just a line of text. It carries how far it has been explored: mentioned (named only), explored (cause, consequence or scope discussed), quantified (a cost or impact figure attached), and personal (the buyer said what it costs them, personally). Depth is never downgraded by a later, shallower mention, which is what lets a manager trust that “quantified” means somebody really did get to a number.

Filled from the conversation, not from memory

An AI pass reads the deal’s conversations and fills the deal sheet — the fields behind pain, budget and the rest — with each value traceable to what was said. It is on by default with a small daily spend ceiling per workspace. What a rep has typed is theirs: the pass fills and proposes, it does not overwrite a person.

The reads

What sits around the deal

Each of these answers one question a manager would otherwise have to ask in a pipeline review.

The close-picture strip and the deal spotlight

Across the top of the deal page, on every tab, a compact strip shows five readings in a fixed order — buyer intent, path, budget, pains, readiness — and each one jumps to the card that holds the full reading. The order never reshuffles as readings arrive, because the most valuable strip on the page should not move under your eye.

The deal spotlight puts the rest in one place: what to ask on the next call, whether the deal has stalled and for how many days in its stage, what to watch out for, what the client promised and has not yet done, and the playbook checklist for the step the deal is on.

The AE risk scan, against your own guidance

Meeting transcripts are scanned for the things an account executive says that contradict your sales process or hurt future revenue — and what counts is written by your workspace, versioned, and published, not hard-coded by us. Publishing a new version re-opens the corpus so old and new findings never share a sheet claiming to mean the same thing. It is on by default, reads meeting tape only, and the 1:1 sheet shows how much of that tape it has actually covered rather than implying it read everything.

A second probability, argued from evidence

Beside the rep’s own probability sits a second number, built from evidence already on the deal and starting from your own trailing win rate for deals that reached the same step. It never writes over the rep’s figure. Where your history is too thin to measure a starting point, there is no number at all rather than a made-up default, and the pipeline board flags a deal where the two disagree by a wide margin.

Conversations that have not been read yet

If conversations on a deal have not been through the read, the deal page says how many and offers to process them now. The count and the button ask the same question of the same data, so the banner can never promise work the button will not do.

Battle cards and the incumbent IT provider

Every company record has a field for who supports the account’s IT today, which you can set by hand, import, and see in the company list. A value a person entered or imported is final: no automated pass will overwrite it.

For workspaces running the IT audit module — which is off until a workspace turns it on — a further pass reads each transcript for outside organisations the buyer named. The incumbent fills that company field with the sentence it came from; a competitor nobody has met before gets a draft battle card; and findings accumulate on existing cards as additions, never as rewrites of what a rep wrote.

Who it is for

For MSPs whose forecast depends on qualification

If “is this deal real?” is the question every pipeline review comes down to, this is the answer laid out step by step.

  • A sales manager running a forecast call who wants the budget gap and the open objections on screen, not recalled.
  • An account executive who wants to know which closing step is missing before the proposal meeting.
  • An owner who wants to see how deeply pain was explored before a managed-services price was put in front of a buyer.
  • A team displacing an incumbent provider who wants that provider recorded on the account.

Questions

The things people actually ask.

What are the five closing steps?

Pain, Budget, Decision maker, Offer, and No open objections. Each is met, unmet or unknown, decided by one rule set that every screen shares.

How is the budget gap calculated?

From the deal’s one budget record: the range the customer named against what you quoted, computed each time it is shown rather than stored, so it is never out of date.

Will the AI overwrite what my rep entered?

No. Once a rep edits the budget record or a deal-sheet field, later passes propose changes for review instead of writing over them. A company’s incumbent provider entered by a person is never overwritten either.

Does it read Outlook sent mail?

Only if you switch it on. The Microsoft 365 Sent Items sweep ships off. Without it, the email threads read are the ones your team files on the deal.

Is Path to Close the same as the stage gate?

No. The stage gate checks the evidence a pipeline step requires. Path to Close tracks the five steps that decide whether a deal can actually close, and its advice appears when a deal moves rather than blocking the move.

Open your biggest open deal.

Then look at which of the five steps is still unknown.