Blinco.tech/What we build/Operations dashboards

Operations dashboards

The business already produces the numbers. They are just scattered across a job app, a bank feed, four spreadsheets and three people's heads. A dashboard is what happens when they are put back together and kept live.

Live · refreshed every 60 s Open jobs Overdue A$ Crew on tools Lands this week Invoiced by week Exceptions

Fig A · The shape of the thing: one readout strip, the money trend, and the leak report, one screen

Fig B

Drive one

Dash 01 · live · fictional business

Below is not a screenshot. Each of these five boards is running live inside this page: pick one, work its filters, open its panels, watch the numbers agree with the clock. Five fictional businesses, five different screens. The code is what we ship.

Dash 01 · Corridor Freight · truck logistics · the corridor drawn as the live map, gauges, a slot-mapped trailer, ETA derived from the clock

Fig B · Embedded live demonstrations · all data invented and internally consistent · scrolling inside the frame scrolls the board

Open the Corridor Freight fleet board full screen

What goes on it

Yours will differ
D-01JobsEvery open job with age, stage, owner and margin. The stuck ones surface themselves instead of hiding in a list.
D-02CashInvoiced, paid, overdue, and what lands this week if nothing changes. Pulled from the ledger, not typed into a cell.
D-03Crew & fleetWho and what is on the tools right now, and the utilisation trend that tells you when to hire or park.
D-04ExceptionsCompleted work not yet invoiced, deliveries missing PODs, quotes past their use-by date. The leak report.
D-05The wall screenA cut for the workshop TV: today's board, no controls, readable from four metres.
Build

How it's built

Fed, not typed

The dashboard is fed by the systems you already run: the job platform, Xero or MYOB, bank feeds, timesheets, even a spreadsheet if that is where the data lives today. Each source lands in one data model, on infrastructure you control, and the screen reads from that.

Where a source can push events, the numbers move in seconds. Where it can only be polled, they move in minutes. Either way, nobody types a number into the dashboard. Every tile drills through to the records behind it, so a strange number is two clicks from its cause.

  • Any screen. Office monitor, phone, workshop TV. It is a fast, plain web app, not an installed program.
  • Your infrastructure. The data model and the app live on hosting you own. Turning us off does not turn it off.
  • Exports stay possible. Anything on screen can land in a spreadsheet, because sometimes a spreadsheet is the right tool.
Note

What it replaces

The weekly assembly

The weekend spreadsheet assembly, the Monday "where are we at" meeting that runs on memory, and the quick questions that interrupt whoever holds the numbers in their head. The information stops being a chore someone performs and starts being a place everyone looks.

Q

Asked every time

Common questions
Our data is a mess. Does that sink it?

No, it changes the first fortnight. Dirty data is normal; the build starts by agreeing what the source of truth is for each number and cleaning on the way through. The dashboard then becomes the thing that keeps it clean, because a wrong number is suddenly visible.

How live is live?

Per source. Systems with webhooks or APIs update in seconds to a minute. Bank data moves at the speed banks move. The refresh age is printed on the screen so nobody has to wonder.

We only have spreadsheets. Too early for this?

Spreadsheets are a fine starting source; many builds begin there. The dashboard reads them where they sit, and sources can be upgraded behind it later without changing the screen people already trust.

Want the whole business on one screen?
Tell us which numbers you assemble by hand today. That is the scope talk started.
Start a project