One written definition per number
Agreed in advance, so that active client and closed job mean the same thing on the screen as they do in the meeting.
Web apps
The report your team rebuilds by hand every Monday
Internal dashboards and admin screens that show the current number without an export, a lookup and a copy and paste. For operations and finance teams running several branches off one spreadsheet that somebody has to assemble first.
Who this is for
For operations, finance and service teams whose data is already being recorded somewhere and who lose hours every week turning it into the same report. Where the numbers are not captured reliably yet, a dashboard only spreads bad data faster and with more confidence.
What you get
What we deliver
The screen that answers the standing question
The handful of figures your team currently assembles by hand, on one page that is correct the moment it loads.
Filters shaped like your organisation
By branch, team, product line and period, with each person's choice remembered so nobody resets it every morning.
Drill down to the underlying rows
Every total opens into the records behind it, because the first thing anyone does with a surprising number is ask which entries made it.
Admin screens for the routine fixes
The internal tools for jobs that currently need a developer: correcting a record, reissuing a document, changing someone's access.
Scheduled sends for the people who never log in
The same figures pushed out as an email or a chat message on a schedule, with the time they were last refreshed attached.
Peso, VAT and a calendar that is not flat
Money has to read the way your finance team reads it: peso amounts, with a clear line between VAT inclusive and VAT exclusive figures, because a chart that quietly mixes the two gets argued about instead of used. Time is not flat here either. Demand moves with the pay cycle, lifting after the fifteenth and again after the last working day, so a week-on-week comparison can show a collapse that is really just the calendar. The holiday list is long and partly local, which means a regional holiday can close one branch while the rest of the country trades normally, and a naive branch ranking will read that as underperformance. Comparisons get built to account for both, so a soft week reads as a soft week and a public holiday reads as a public holiday.
Questions
What people ask before they buy this
Could we just use a spreadsheet or a free reporting tool?
Often yes, and that is the first thing we check. If the data already lives in one place and the question is really a chart, an off-the-shelf reporting tool is cheaper and faster than anything we would build. A custom dashboard earns its place when figures have to be pulled from several systems, when the definition of a metric is contested internally, or when people need to act on the screen rather than only look at it.
Our data is spread across three systems. Is that a problem?
It is the normal case, and it is the part that takes the time. Before any screen is designed we agree where each number comes from and which system wins when two of them disagree. That is usually a business decision rather than a technical one, so it gets made with you and written down.
How up to date do the numbers need to be?
Less up to date than most people first say. Live to the second is expensive and rarely changes a decision, while hourly or overnight is enough for almost every operational report. We ask what you would do differently if a figure were an hour old, and when the answer is nothing, we refresh on a schedule and show plainly when it last ran.
Will our branch managers be able to use it on a phone?
That is the assumption we design on. A branch or area manager reads a number standing on the floor, not sitting at a desk, so the phone layout leads with the few figures that drive a decision. The desktop view then has room for the detail, instead of the phone being a squeezed copy of a desktop screen.
Can we control who sees which numbers?
Yes, by role and, where it matters, by branch, so an area manager sees their own area and the finance view is not open to everyone with a login. Cost and payroll figures are usually the sensitive part and get their own permission rather than riding along with sales. We agree that grid before the build, because adding it afterwards is harder than it looks.
Web apps
Related services
Ready when you are
Tell us what you are building and we will tell you honestly how we would approach it.