Skip to content
02Applications

The numbers, live, on one screen

A dashboard that reads from the systems you already run and shows the figures the business is actually managed by. No spreadsheet on a Monday morning.

Get a quote
See the catalogue
Build time
3–16 weeks
Per project
Quoted
Data, not exports
Live
01Client Portals02Internal Dashboards03Inventory Systems04Custom Databases05Workflow Tools06Management Systems
Who it is for

You will knowif this is you.

01Somebody spends the first hours of the week pulling numbers from four places into one spreadsheet.
02The figures the team argues about are different depending on who ran the report.
03You find out about a problem, a stock-out, a late job, a missed target, after the customer does.
04Managers ask for the same report every month and it is rebuilt by hand every month.
What it does

Everything the systemtakes off your desk.

Each capability is built to your process and shipped with its own controls. Nothing generic is bolted on.

01

Connected sources

Reads from where the data already lives. Nothing is retyped.

  • Accounting, CRM, till and booking systems
  • Spreadsheets and Google Sheets
  • Databases and APIs
  • Scheduled and real-time refresh
02

The metrics you manage by

Each figure defined once, in writing, so everyone means the same thing by it.

  • KPI tiles with targets
  • Definitions shown on hover
  • Period comparison
  • Traffic-light thresholds
03

Charts that answer questions

Trend, breakdown and comparison, drawn for the question, not the chart type.

  • Trends over time
  • Breakdown by team, site, product
  • Drill from total to transaction
  • Mobile layouts
04

Filters and views

One dashboard, many audiences. A manager and a director see the same truth at different depths.

  • Date ranges and comparison periods
  • Saved views per role
  • Site, team and product filters
  • Sharable links
05

Alerts

The dashboard tells you when a figure crosses a line, so nobody has to watch it.

  • Threshold alerts by email or message
  • Daily or weekly digests
  • Anomaly flags
  • Escalation to a person
06

Reports and exports

The board pack, produced on schedule, from the same figures.

  • Scheduled PDF reports
  • Excel and CSV export
  • Presentation mode
  • Embedding in other tools
How it is put together

From the sourceto the screen.

Four layers. Getting the first two right is most of the work, and it is the part nobody sees.

01ConnectionsRead-only links into each system: accounting, CRM, till, bookings, sheets. Each on its own schedule, each logged, none able to write back.
02The modelOne place where 'revenue', 'a job' and 'a customer' are defined. This is what makes two departments' numbers agree.
03The screensDashboards per audience: the daily operations view, the weekly management view, the monthly board view. Same model, different depth.
04Alerts and reportsWhat leaves the dashboard on its own: the threshold alert, the Monday digest, the board pack PDF.
Scope and timeline

Sized to the job,quoted per project.

The four dashboard tiers from the catalogue. The operations dashboard is the one most businesses need first.

01

Analytics dashboard

Quoted

3–5 weeks

  • Custom KPI widgets
  • Interactive charts
  • Real-time updates
  • Data source connections
  • Export
  • Date range filtering
Get a quote
02Most popular

Operations dashboard

Quoted

5–8 weeks

  • Multi-source aggregation
  • Real-time status monitoring
  • Alerts and notifications
  • Team performance metrics
  • Historical trends
  • Custom reports
Get a quote
03

BI dashboard suite

Quoted

8–12 weeks

  • Cross-department views
  • Advanced filtering
  • Scheduled report automation
  • Embedded analytics
  • Custom metric calculations
  • Data governance controls
Get a quote
04

Executive dashboard

Quoted

10–16 weeks

  • Cross-departmental metrics
  • Financial KPI tracking
  • Automated report scheduling
  • Presentation mode
  • Secure access controls
  • White-label options
Get a quote

Timelines are the ones in the catalogue. The quote fixes the scope, the price and the delivery date before work starts.

Built on the platform

Your Loungealready has one.

Every Quooro customer's dashboard opens on figures from their own platform: enquiries, bookings, invoices, jobs. A custom dashboard extends that to the systems outside the platform, and can sit inside the Lounge as a page of its own.

What you own

Yours outright, on the day it launches.

  • The complete dashboard, its data model and every connection, as source code
  • The definitions document: what each metric means and where it comes from
  • Integration documentation for each connected system
  • A training session for the people who will read it and the person who will own it
  • A support period written into the quote

The same terms as every build: read ownership and handover.

How it is built

Four stages, no surprises.

Whole buildSet in your proposal

01

Discover

Starts when you say go

We map how the work gets done today.

What happens

  • Workshops with the people who will use it
  • Your current process mapped, step by step
  • Your data and the systems it lives in audited
  • A written specification of what to build first

What you get

  • The specification
  • A staged plan and a fixed quote

What we need from you

  • Time with the team who do the work
  • Access to the tools you use now
02

Design

After you approve the specification

A clickable prototype before a line of code is written.

What happens

  • Screens and user journeys for each role
  • A clickable prototype the team can try
  • The data model and the integrations agreed
  • Permissions: who can see and change what

What you get

  • The prototype
  • The agreed data model

What we need from you

  • Feedback from real users
  • Sign-off on the prototype
03

Build

After you approve the prototype

Built in stages, with a working demo at the end of each.

What happens

  • Features built in the agreed order
  • A working demo at the end of every stage
  • Your existing data moved across and checked
  • Tested against the real process, not a script

What you get

  • A working system at each stage
  • A test environment to try it in

What we need from you

  • Testing time from your team
  • Decisions when questions come up
04

Launch

After you approve the finished build

Rolled out, taught and supported.

What happens

  • Rolled out to the team, in stages if that suits
  • Training for each role
  • Documentation for how it works and how to run it
  • Support after go-live, with a retainer if you want one

What you get

  • The live system
  • Full ownership of the code and data

What we need from you

  • A go-live date that works for the business
Straight answers

Asked beforeyou ask.

01Does it need a data warehouse?Not to start. Most businesses' data fits in one database we build and refresh on a schedule. A warehouse becomes worth it at many sources or very high volume, and the model carries across if it does.
02How live is live?As live as the source allows. A till or booking system can update in seconds; an accounting package usually exposes changes every few minutes; a spreadsheet updates when it is saved.
03Can it write back to the systems it reads?By default no, deliberately. A dashboard that changes records is a management system, and that is a different build with different controls. If you need actions from the dashboard, we scope them explicitly.
04Who can see what?Roles decide it. A site manager sees their site, a director sees all of them, the accountant sees the finance views. The same dashboard, filtered by who signed in.

Retire theMonday spreadsheet.

Send us the report somebody builds by hand every week. We will tell you what it takes to have it build itself.

Get a quote
Talk it through first
01 · PreviousClient Portals03 · NextInventory Systems