Reports that show their working
You pick the questions before anything is built. Every number says what it counted, so you can check it.
Built for the teams that run on whiteboards, spreadsheets and WhatsApp
How it works
From one sentence to software your crew uses. The same afternoon.
Start from your files
You don’t have a spec. You have spreadsheets, PDFs and a group chat.
That’s enough to start. It reads them as they are, typos and all, shows you what it found, and adds nothing until you’ve seen it.
CSVstaff_list_FINAL_v3 (2).csv
NAME,Phone#,start dt,team,site
Rosa Delgado,604 555 0143,3/4/22,Nights,Kingsway
K. Nguyen,,2023-01-09,nights ,Oakridge
Marta Ruiz,604-555-0199,09/01/2024,Days,kingsway
What it readCheck before adding
- workers, one row each
- 38
- teams, “nights ” and “Nights” made one
- 3
- sites, proposed before they’re added
- 14
- cells marked for you to check
- 4
Spreadsheets import today. PDFs, Word documents and chats are next.
Everything included
Not a prototype. A system your auditor will accept.
Forms the crew fills on a phone
Short forms with only their boxes, signed on the spot and sent to the office.
Automations you try first
Pick what starts it and what it changes. You try it on a real record before it’s on.
Every change has a name on it
Each value says who changed it, when, and what it was. An automation’s changes say so.
What needs you comes to you
Overdue and due work rises to the top of Home. Nobody has to go looking for it.
The next system starts from the data you already have
Add van checks, certificates or timesheets to the system you run. Same people, same sites, same history. No migration.
Compare
There are three ways to get ops software today. None of them end with software your team likes.
| Off-the-shelfSoftware you bend to | A blank no-code toolFlexible, and empty | A ticket to engineersSpec, build, ship | GobusoBuilt around you | |
|---|---|---|---|---|
| Fits how you work | No. You change to fit it | Yes. If someone designs it | Yes. Eventually | Yes. Describe it, read it back, change it |
| Your existing data | No. Retype it | No. Retype it | No. A migration project | Yes. Import the spreadsheet you keep |
| Working by | Weeks of setup | Never quite finished | Next quarter | Yes. The same afternoon |
| The crew on site | Paper anyway | A desktop form | Another app | Yes. Short forms on their phone |
| The next system | Another tool | Start again | Another project | Yes. Same data underneath |
We already have years of data.
Start with your staff list. Import the spreadsheet as it is: it opens as a sheet with every doubtful cell marked, and nothing is added until you’ve seen it.
Will this survive an audit?
Every value on a record says who last changed it and when, and what it was before. Anything an automation changes says so. Sign-offs are attached to the person who signed.
What if the AI gets it wrong?
It will, sometimes. That’s why it shows you the plan before it builds anything, and why you can tell it what’s wrong and have it redraw. Nothing is built until you say so.
Who can see our records?
Your company’s records are kept apart from every other company’s, and you decide what each person on your team can see and change. Settings say which region they’re stored in.
Do we need a developer?
No. The people who run the work describe it and change it. If you’d like help, write to us and we’ll build the first one with you.