Stout IntelStout Intel
Stout Intel

Dashboards That Fill Themselves

A sales cockpit nobody has to update.

Live, in daily useFastify + SQLiteReactscheduled collectorsCRM and inbox sources

What it is

The dashboard I run my week from: pipeline health with stalled-deal detection, a client touch map showing who has gone quiet, overdue activity surfacing, and passive capture that reads the money traffic instead of asking anyone to log it.

How it works

Collectors sweep the connected systems on a schedule and write into a local store, so every number is current without a refresh ritual. The rot detection is the useful part: it ranks by silence rather than by stage, because the deals that die are the ones nobody touched.

Development to deployment

Every CRM dashboard I have used was accurate for about a day after someone spent a morning cleaning it. The fix was to give up on discipline and build collectors instead. The numbers are right because nobody maintains them.

Value delivered

Hundreds of open opportunities monitored continuously, with stalled deals and overdue follow-ups surfaced automatically instead of discovered during a quarterly review.

Every dashboard rots, and it always rots the same way

A dashboard is only as true as the data entry behind it. Somebody spends a morning cleaning the CRM before the quarterly review, the charts look sharp for about a week, and then reality drifts away from the record one un logged call at a time. Six weeks later the numbers are wrong, everyone privately knows they are wrong, and decisions get made off gut feel while the dashboard sits there being decorative.

The usual response is to demand better discipline. Log your calls. Update your stages. Fill in the close date. This never works, and it does not work for a structural reason: you are asking the highest value people in the business to spend time transcribing what they just did into a system that gives them nothing back.

The fix is to stop asking. If the data can be observed, observe it. People should not be the input device for facts the systems already have.

Collectors instead of discipline

Scheduled collectors sweep the connected systems and write into a local store. The CRM, the inbox, the calendar, the money traffic. Every number on the dashboard is derived from something that actually happened rather than something somebody remembered to record.

This inverts the usual relationship. Instead of the dashboard being a report on how well the team maintained the CRM, the dashboard is a report on the business. Those are extremely different things and most companies have only ever seen the first one.

It also means the dashboard is correct on a Monday morning with nobody having touched it over the weekend. That property, being trustworthy without a preparation ritual, is the whole reason it gets used.

Rank by silence, not by stage

The most useful thing on the whole board is not the pipeline total. It is the stalled deal detection, and the reason is a small insight that took me a long time to get to.

Deals do not die at a stage. They die in silence. A deal sitting in Proposal for three weeks with an active thread is healthy. A deal sitting in Negotiation for three weeks with nothing since is nearly gone, and a stage based report shows the second one as further along. Sorting by stage systematically hides the deals that need you.

So the ranking is by time since real contact, drawn from actual message and activity traffic rather than from a logged note. The board surfaces who has gone quiet and how long it has been. That single reordering changes what you do on a Monday more than any other number on the page.

Local first, and why that was the right call

The whole thing runs locally rather than as a hosted service. That sounds like a limitation and it bought three real things. There is no per seat subscription, so the marginal cost of another view or another metric is zero. Sensitive commercial data never leaves the machine. And query speed is instant because nothing crosses a network.

The trade is that it is one operator sized. This is not a multi tenant analytics platform and does not try to be. For a small business where two or three people need the truth and nobody needs a login system, that is exactly the right shape, and it is a shape almost nobody sells because it is hard to charge monthly for.

If you have ever priced business intelligence tooling for a small team and concluded the numbers do not work, this is the alternative. The reporting most small businesses actually need is a scheduled collector and a well chosen sort order, not a platform.

Common questions

Why do our dashboards and CRM reports stop being accurate?

Because they depend on people manually logging what they did. That discipline decays predictably within weeks. The structural fix is to collect the data from systems that already have it, the inbox, the calendar, the money traffic, rather than asking humans to transcribe it.

Can this replace the spreadsheet our team currently reports from?

That is normally exactly what it replaces. A reporting spreadsheet is a dashboard with a manual refresh step and a single person who understands the formulas. Moving it to scheduled collectors removes both the refresh ritual and the key person risk.

What is the single most useful metric on it?

Time since real contact, not pipeline stage. Deals die in silence rather than at a stage, so ranking by how long an opportunity has been quiet surfaces the ones that need attention today. Stage based reports systematically hide those.

Does this require replacing our CRM?

No. It reads from whatever you already run. The point is to stop depending on the CRM being lovingly maintained, not to swap it for a different system that will have the same problem.

Get the full build doc

The deep documentation on my builds, architecture, guardrails, and lessons included, lives in the client portal. A free account gets you in, and the docs land in your files.