Services
The tool your team stopped asking for.
Somebody asked for it twice, was told it was too expensive, and built a spreadsheet instead. We build the real thing.
Free · Ten minutes · The report is yours either way
The part everybody dreads
Type it once. The report writes itself.
One screen for the record that used to be typed twice, and a report that is finished before anybody asks for it.
Typed once, not twice
The record goes in on one screen and both systems have it. Nobody opens the second window and types it again.
Monday's number, already made
The figure somebody rebuilt by hand every month is a screen that is current when you open it.
Eleven tabs, one screen
We start with the spreadsheet — it describes the process better than a brief would — and build the screen it was pretending to be.
The yes is on the record
Who asked, who approved, and when. Not a chain of forwarded email.
Two people, one record
The thing a shared file never managed. Nobody has to ask who has it open.
Not everyone sees everything
Pay, margins, client notes. Permissions are part of the build, not a promise.
A wrong click is not the end
Changes are recorded and reversible. A spreadsheet forgives nothing.
What the screens above show
- Example of a screen headed “New job”, opened at the front desk: Client — Chosen from the list; Site — Address already on file; Starts — Monday, 8:00; Assigned — The team on duty. Lands in: The job list and The schedule. Beside it a second window, “the other system”, typed in again, slides away and is gone. Beneath it, “Typed here, then typed again over there.” struck out and replaced with “one entry, both places”.
- Example of a report headed “This month”, updated a minute ago: Finished 43; In progress 18; Not started 6. Beneath it, “Two hours in a spreadsheet, every month.” struck out and replaced with “made itself · Monday 8:00”.
- Example of a spreadsheet with the tabs Jobs, Jobs v2, Jobs final, Do not touch, Old, +5, turned into a table with the columns Job, Stage, Updated: 1042, In progress, today; 1041, Waiting on a yes, yesterday; 1039, Finished, Friday. Beneath it, “Eleven tabs, three colours that mean something.” struck out and replaced with “one screen anybody can read”.
- Example of an approval trail: Tue 09:04 asked; Tue 11:20 approved — on the record.
- Example of one record, Job 1042 · open, in use in two places at once: front desk and workshop, both typing — both at once.
- Example of a record where Job 1042 is shown and Pay and Margin are covered by a padlock — managers only.
- Example: “Row deleted · 10:12”, then “Put back · 10:13” — change history.
Nobody keys the same job into a second system, so the two can never disagree. The month's figure is on a screen that is already right, and it is the same figure for everyone reading it. Who asked, who said yes and what changed stays on the record — and a wrong click can be put back.
Forty-five minutes on a screen share. You keep the written plan either way.
There is a spreadsheet. It has eleven tabs, three colours that mean something, and one person who understands it.
That person is on holiday next week. Everyone is quietly nervous about it.
Weeks
to something you can use
Yours
the code, and the data
In pieces
shipped so you can use them
If you hire us
How the first build goes.
01First weeks
We read what is there
Whatever runs your work today keeps running while we learn how it is actually used.
02The first piece
Something you can use
One useful part, shipped early, instead of one delivery at the end you cannot see until it lands.
03After that
The people who built it
The same team keeps it running, so a change is a conversation rather than a project.
Ten minutes on a call. You keep the plan either way.
What we handle
What that actually covers.
Not a list of products — the things that change for you.
We start with the spreadsheet
It already describes the process better than any brief would. We read it and ask why.
The number, without the export
The figure somebody rebuilds by hand every Monday becomes a screen that is always right.
Approvals that leave a trail
Who asked, who said yes, and when. Not a chain of forwarded email.
Two people can use it at once
The thing a shared file has never managed. No more "are you in it?" across the office.
Not everyone sees everything
Pay, margins, client notes. Permissions are part of the build, not a promise.
Nothing is lost by a wrong click
Changes are recorded and reversible. A spreadsheet forgives nothing.
Start with the review. Ten minutes.
Start with a scoping call: ten minutes, then a written plan with what it does, what it costs and how long it takes.
Or ten minutes on the phone first
About half the reports say you’re in decent shape. If that’s you, we say so and leave.