Dashboard
Reference buildSignal
An analytics surface for a business operating on several systems: the few numbers that matter, the trend behind them, and the one thing to act on today.
- Dated
- 2025
- Product type
- Dashboard
- Technologies
- 4
Revenue
$72.8k
Orders
423
Average
$172
Revenue over time
30 daysWhere it came from
Needs attention
1Working interface — not a screenshot
The short version
Why it exists.
Every build here answers a specific operational problem. This is the one it answers.
- 01
What was wrong
Numbers living in four tools and reconciled into a spreadsheet every Monday. By the time the report existed the week had moved on, and two people could produce two different revenue figures for the same month.
- 02
What we built
One surface reading from the systems directly, with every figure defined once so it means the same thing everywhere, trends over a chosen period, and alerts on the movements worth interrupting someone for.
- 03
What changes
Decisions get made on this week rather than last month, and there is one revenue figure instead of an argument.
What it does
The parts that matter.
Not a feature list — the four things this product is actually for.
One definition per number
Revenue means one thing. Every screen that shows it is reading the same definition.
Alerts worth having
Raised on movements that need a decision, not on every change the data makes.
Who, not just how many
New against returning, by period — so growth can be explained rather than just reported.
Takes your numbers with you
Any view exports, so the figures can go into a board pack without being retyped.
What it took
The disciplines behind it.
How it is built
The technologies.
Chosen because they suit the problem and because a team other than ours can maintain them.
- Next.js
- TypeScript
- PostgreSQL
- ClickHouse
Start a project
You have seen what we build. Now let us build yours.
Tell us which part of the business you want to run better. We will come back with how we would approach it, what it would take, and whether we are the right people for it.
- 01An engineer reads the brief — not a sales inbox.
- 02You get a written response on approach, risk and rough shape of effort.
- 03If it looks like a fit, a call to pressure-test the scope.