Overview
Quoting, scheduling and job tracking for contractors and technical businesses, built around how the work actually runs rather than how software thinks it should. Usually replacing a paper diary and a stack of spreadsheets.
Covers
06- Quoting
- Scheduling
- Job tracking
- Invoicing
- Field apps
- Reporting
Who it suits
03- Contractors quoting from documents and a diary
- Firms retyping invoices from job notes
- Engineers phoning the office to report status
What you get.
4 included- Quotes out, and tracked to a decision
- Scheduling against real availability
- A field app engineers can use on site
- Invoices raised from the completed job
How it runs.
2 to 4 weeksShare of the work, by the weight of each stage.
- 14% of the work
Shadow
How the work actually runs today, including the parts nobody wrote down.
Days 1 to 3 - 57% of the work
Build
Quoting, scheduling and tracking shaped around that, not around a template.
Weeks 1 to 3 - 29% of the work
Roll out
Onto the phones your engineers already carry. The paper diary retires last.
Final week
Built with.
5 tools- Next.jsFramework
- PostgresDatabase
- PWAInstallable
- APIsIntegration
- StripePayments
What to check.
Scope, up frontWhat this is not
3 excluded- Accounting software. It hands off to yours
- A CRM with everything in it
- Hardware, beyond the phones you already carry
Seen in the work.
1 project
GOSU
Permanent PUBG match archive with replays rebuilt from telemetry.
- What it proves
- A data source that deletes itself after fourteen days, ingested and kept, then rebuilt into watchable replays from the raw telemetry.
- Outcome
- A record that survives the API deleting it.
Where it is asked for.
6 townsQuestions, answered.
3 questionsWill my engineers actually use it?
That is the whole risk, so it is built for the phone they already carry, works on a bad signal, and asks for as few taps as the job allows.
What happens to the spreadsheets?
They come across, and stay readable for as long as you want them. The paper diary retires last, once nobody is reaching for it.
Can it invoice?
It raises the invoice from the completed job rather than having somebody retype it, and hands it to whatever accounts package you already run.