Operations dashboard

The numbers from five tools in one view, always up to date.

For
SMEs and operations, Founders and startups
Service
Build + Automate
Case study
Reference system

Figures from five tools brought together in one up-to-date view, with an alert when something goes off track.

Reference system: a need I come across often, documented with the exact architecture I would put in place. Other client work is presented in meetings.

Problem

The data sits in the CRM, invoicing, support and several spreadsheets.

Reporting is done by hand, late, and everyone turns up to meetings with their own figures.

Context

Users
Management, team leads, operations.
Current process
Manual exports, consolidation in a spreadsheet, sent by email.
Constraints
No change to the source tools, shared metric definitions, fresh data with no manual step.
Tools in place
  • CRM
  • Invoicing
  • Support
  • Spreadsheets

Solution

The sources are synced into Supabase by scheduled n8n workflows. Metrics are calculated once, in the database, and the dashboard displays them by period and by team.

Thresholds trigger alerts before the problem starts costing money.

Why this approach. Calculate metrics in the database, not in the interface: everyone reads the same figure, and it stays reusable elsewhere.

Architecture

Input

  • CRM Opportunities, clients, sales activity.
  • Invoicing Revenue invoiced, collected, overdue.
  • Support Requests, response times, satisfaction.

Automation

  • Scheduled n8n Syncs each source at regular intervals, via API.

Data

  • Supabase Raw tables, then SQL views that define each metric once and for all.

Interface

  • Dashboard Views by period and by team, role-based access.

Output

  • Alerts A crossed threshold triggers a Slack message or an email to the person in charge.
Hover over or tap a block to see its role in the system.

Features

  • Scheduled syncData arrives on its own, as often as is useful.
  • Metrics defined onceOne definition per figure, shared by everyone.
  • Views by period and by team7, 30 or 90 days, the whole company or a single team.
  • Threshold alertsYou are notified when a metric leaves its normal range.
  • Role-based accessEveryone sees the figures that concern them.
  • ExportThe data stays exportable for one-off analyses.

Target result

  • One figure per metric.
  • Reporting with no manual handling.
  • Being alerted before the problem starts costing money.

How it is measured

  • Time spent on reporting
  • Data freshness
  • Alerts handled and reaction time

What I do

  1. Defining metrics with management
  2. API connectors
  3. Data model and SQL views
  4. Dashboard design
  5. Alerts
  6. Production launch

Try it.

A working version of the system, with sample data. Nothing is pre-recorded: it all runs in your browser.

Dashboard · Operations Sample data
Requests handled per day