See where every deal actually stands
Runner holds the opportunity itself — six ready-made stages from prospecting to a won or lost close, the deals in each one and the account each belongs to, and the outcome written down when a deal closes. Every stage is counted against a single denominator, so the numbers reconcile with each other rather than with three different reports.
Built into Runner
- Every stage counted against one denominator, not five different ones
- Open any stage and see the deals inside it, with their accounts
- Outcomes recorded when a deal closes, win or lose
Worth knowing
The counts use six fixed stages and the deals your team records: no predicted close dates and no win probabilities, which is exactly why the numbers reconcile. An inbound lead can carry one labelled suggestion beside it — Runner's reading of a named, versioned qualification policy, with its reasons shown — and that suggestion never moves a stage, a count or a total.
Every deal that closes says why, won or lost
It's the end of the quarter, and someone asks why the last three deals slipped away. In Runner the answer is already on each one, because closing a deal asks what happened. Lost needs a reason from a set list — price, timing, a missing capability, a competitor, no decision, a bad fit, no response, or other — and other needs a note. Won needs the confirmed value, its currency and a short note on what won it.
A deal you're parking can be marked nurture or disqualified instead, with a note, and given either a revisit date or an instruction to wait for a signal. The revisit date is what brings it back as due a second look. Once a deal is won or lost it stays closed: a company that comes back becomes a new deal, and the old one keeps its outcome.
Every stage is counted against the same total
The top of the pipeline is one row, in the order a deal travels: Prospecting, Qualified, Proposal, Negotiation, then Closed won and Closed lost. Each stage shows how many deals are in it, zero included, out of one total rather than a percentage worked against a shifting base. Click a stage and the list narrows to its deals.
Open value is added up only when every valued deal shares one currency. A mix is flagged and never blended into one number, and when some open deals carry no value, the figure says how many it came from.
Picture this
A six-person API company has twelve open deals, and three of them carry a value. The pipeline shows the sum and says it comes from those three, so nobody in Monday's meeting reads a partial figure as the whole pipeline.
The pipeline hands you this morning's worklist
Beside the stages, the page counts four piles of work across every deal in the product, whatever your filter shows: open deals past their expected close date, deals due a second look, open deals with no close date, and deals with no company linked. An empty pile drops off the page; a pile that couldn't be counted stays on it.
New deals arrive from inquiries, and nothing moves them by itself. An inquiry recorded against a company already on your record opens a deal at Prospecting and stops there, with no owner and no next step, because a deal that qualified itself would be the system marking its own homework. If the company already has more than one open deal, the inquiry opens nothing rather than guess which one it belongs to. A move into any open stage needs an owner, a next step and a due date, checked in the database where the stage is written.
Counted, never forecast, which is why the numbers reconcile
The expected close date on a deal is one a person entered. Nothing on the pipeline predicts one, and no stage is weighted by a chance of winning. The timing report looks back instead: how long deals actually sat in each stage, read from the recorded stage moves, with a deal still sitting in a stage counted and kept out of the timing.
Two things reach in from elsewhere. A conversation in the shared inbox can be linked to a deal, and an AI agent your team connects over MCP can look deals up by name, getting back the deal, its company and nothing more.
Questions buyers ask
Can I track why deals are lost?
Yes. Closing a deal as lost needs a reason from a set list, and a reason of other needs a note, so every lost deal says why. A won deal carries its confirmed value and a short note on what won it.
Does the pipeline forecast revenue or predict close dates?
No. The expected close date is the one your team entered, each stage is a plain count, and the timing report measures how long deals sat in each stage. Counting only what is on the record is what lets the numbers reconcile with each other.
Can a closed deal be reopened?
No. A closed stage never changes. If the company comes back, that becomes a new deal, and the closed one keeps the value, reason or note it was closed with.
Can I update many deals at once?
You can reassign the owner of many deals in one go, with a written reason, and any row that fails is named rather than summarised away. Each reassignment adds to the deal's owner history, so a mistake is corrected with a new entry instead of by overwriting the last one.
Use what already works
If your deals also live in Salesforce or HubSpot, keep that workflow in place: this is a view built on the account record Runner already keeps, and nothing is written back to a CRM's opportunity object, so you always know which one you are reading.
How teams often buy this job
Usually bought as Salesforce or HubSpot.
SalesforceHubSpot
Trademarks of their owners. No affiliation or endorsement.