Sales funnel dashboard
It reads deals out of the CRM, measures the moves between stages and finds the ones that have stopped. The forecast is assembled from conversions that actually happen.
- Buildfrom $1,700
- Timeline2–4 weeks
- Supportfrom $420/mo
Who this suits: Sales teams where the CRM funnel looks full and the month closes on something other than the forecast.
What is in the first version
- conversion between stages
- time in stage
- stalled deals
- forecast from actuals
The figures above are the package this sits on: Dashboard and analytics. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
A deal becomes stage history
Conversion is measured on the moves, not on where a card sits, and the history accumulates from day one.
- 02
Each stage gets its own norm
How long a deal normally lives in a stage is computed from closed deals rather than decreed from above.
- 03
The forecast assembles from the moves
Every open deal is weighted by the conversion of its own stage, and the gap to the plan is visible.
What decides whether this works or annoys people
The CRM forgets when stages changed
Conversion computed from current states is a photograph of today, so the move history is written separately from the first day.
Stages move for the report
A stage needs a checkable condition for entering it, or deals travel forward for the report and a loss becomes on hold.
A stalled deal is not dead
One norm for the whole funnel lists every large deal, so the norm is computed per stage and per segment.
What to measure once it is live
- conversion between stages
- average age of the open pipeline
- losses with a reason recorded
- forecast against the closed month
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Reading the CRM and keeping historyPythonFastAPIn8nTemporal
- Storage and computationPostgreSQLClickHouseRedisDocker
- The screen and the nudgesTypeScriptReactNext.jsTelegram Bot APIGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- the paid CRM tier for export and history
- a CRM seat for the service account
- telephony and call recording
- hosting for the screen and the history
Asked before the first call
- Our CRM already has reports, why this?
- Often they are enough, and we say so. This is about what they lack: a deeper move history, a stalling norm per stage, and a forecast from your own conversions.
- Is this another place a manager has to type things into?
- No, entry stays in the CRM and the report only reads. It asks for one thing: a lost reason from a list, on the same card.
- How much can the forecast be trusted?
- Exactly as much as your conversions are stable, and the screen says so: beside the forecast stands how it lands against months already closed.