Five apps just to see how the business is doing?
Five apps, one screen.
Not with a KPI dashboard built for the decisions you actually make: payroll approvals, member numbers, jobs in progress, money in. Pulled live from your systems onto one screen.
The real thing
My client dashboard, on demo data.
Demo dataThe ND client dashboard
The dashboard I run for clients, shown on demo data: visits, calls, messages and enquiries per client, month by month. No real client appears here.
One screen
The numbers exist. They are in six places.
Revenue is in the accounting system. Jobs are in the CRM. Hours are in a timesheet app. Memberships are in a spreadsheet someone updates on Fridays. Working out how the business is doing means opening all of them, exporting, and building the same report again. The information is there. Nobody can see it without an afternoon of work.
Built for the decision
Start with the question, not the data.
Most dashboards show everything that can be measured, so nobody reads them. I start with what you need to know or approve each week, and build backwards from that.
Read it in ten seconds. Act on it from the same screen.
Each screen pulls live from the tools you already use, so nothing is exported by hand. Where there is a decision to make, the button to make it is on the screen.
Access is by role, so each person sees what they need and nothing else.
What I build
Built for the decision, not the data.
I start with the question you need answered and build backwards. A payroll approval screen that shows what is due, who has signed off, and one button to release it. A member system that shows who is active, who has lapsed and who needs a call. A live view of enquiries, quotes and jobs. Each one pulls from the systems you already use, updates itself, and is designed to be read in ten seconds on a phone.
- Live data from your existing tools, no manual exporting
- Approval and action screens, not just charts: do the thing from the dashboard
- Role-based access so each person sees what they need and nothing else
- Designed for a phone first, because that is where decisions get made
- Hosted, secured and maintained as part of the system
How it works
Four steps. The question first.
01
I find the question
What do you need to know or approve, how often, and what do you do with the answer. That defines the screen.
02
I connect the sources
Accounting, CRM, bookings, timesheets, spreadsheets. Whatever holds the numbers, I read it.
03
I build and iterate
A working first version fast, then refined with you using it. Real use changes what belongs on the screen.
04
I host and maintain
Secure, backed up, monitored. When a source system changes, I keep the dashboard talking to it.
Asked before you did.
Often built alongside
Asked before you did.
Whatever the business needs to see or approve. It might be a payroll approval screen for a business with staff to pay, or a member view for a gym. If the numbers exist somewhere, they can be brought to one screen.
Usually yes. Most accounting, CRM, booking and payroll systems have a way to read data out, and I connect to it directly so the dashboard is always current.
Built for you. Templates show everyone the same generic charts. Yours shows the four numbers you actually check and lets you act on them.
Yes. Access is by role, so a manager sees approvals, a team member sees their jobs, and the owner sees everything.
A first working version is often live within a couple of weeks. The refinements come from using it, so I build fast and adjust rather than plan for months.
A monthly figure covers hosting, security, monitoring and keeping the connections working as your other systems change. I give you that number before I build.
What you get back
You stop building the same spreadsheet every Monday and open one screen instead.
What do you check every Monday?
Tell me the numbers you build by hand each week. I will show you what the screen looks like that builds them for you.