Dashboard for the owner
Every number that matters assembles itself and is current whenever you open it. Decisions get made on facts, not on a feeling.
- Buildfrom $1,700
- Timeline2–4 weeks
- Supportfrom $420/mo
Who this suits: Owners who read the business off a spreadsheet somebody rebuilds by hand, and learn about a bad week once it is over.
What is in the first version
- data collection
- key metrics
- filters and comparison
- scheduled digest
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
The sources are agreed first
Which system is the truth for revenue, and which for orders, because two answers to one question kill trust.
- 02
Collection runs without anybody
On a schedule, with retries, and with a visible mark when a source does not answer.
- 03
The screen answers in one look
A few numbers with a comparison beside each, and the detail underneath the one that moved.
What decides whether this works or annoys people
Agree the metric before building it
«Revenue» means different things to different departments, and the written formula is what survives the first argument.
Freshness must be visible
Every number carries its collection time, because deciding on yesterday’s figure believing it is today’s is the failure this prevents.
Nobody opens a dashboard daily
The digest is what gets read; the screen is where you go after it says something moved.
What to measure once it is live
- sources collected without gaps
- hours of manual assembly removed
- digests opened
- same-day decisions
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.
- Collection and storagePythonFastAPIPostgreSQLClickHousePlaywrightS3
- The screenTypeScriptReactNext.js
- Schedule and watchingn8nTemporalRedisDockerGrafana
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
- hosting and servers, invoiced by the provider
- paid API tiers on your source systems
- the domain, if the screen gets one
- mail delivery for the digest
Asked before the first call
- Why not Power BI or Metabase?
- Often you should, and we will say so. Those need data already collected and clean; collecting and matching it is usually the actual job, and that is what this is.
- What if some of our systems have no API?
- Then the number is read the way a person reads it off the screen, and that is its own line in the estimate. Dropping a source is also an option.
- Can we add a metric later?
- Periods, segments and what sits on the screen you change yourselves. A new metric means a new source and a new formula, so it goes through us and is priced separately.