Field Service Management
Field software is judged on a bad day: no signal, cold hands, a job that is not what the notes said. We design for that day.
What this covers
Scheduling
Work assigned against skills, parts and travel rather than a best guess.
Mobile capture
Job records, photographs and signatures taken on site, offline.
Parts and stock
What is on the van and what has to be ordered.
Evidence
Proof of work, retained and retrievable when a job is disputed.
Customer contact
Appointment windows and arrival notifications that hold up.
Reporting
First-time fix, travel and utilisation measured honestly.
Who this is for
Maintenance providers
Planned and reactive work against contracts.
Installers
Scheduled work with parts and sign-off.
Utilities and networks
Distributed assets and statutory inspection.
Facilities management
Multi-site work with service levels.
How we work
People who have done it before
Teams that have worked in this setting, not a generic squad reading the brief for the first time.
One team, start to finish
The people who design it are the people who build it and the people who answer for it afterwards.
Working software early
Something running in weeks, so the direction is judged against a real thing rather than a document.
Bought once, owned by you
What you keep at the end
The code, the documentation and the accounts are yours throughout. Nothing here depends on us staying, and any arrangement that continues does so because it is worth continuing.
Talk to us
What we promise
- A named team you can reach, not an account manager relaying questions
- A working version early, and every fortnight after that
- Written estimates with the assumptions and the risks stated
- Your code, your data and your accounts, yours throughout
- A direct answer when something is late or will not work
How it runs
Scope
What the solution has to do, what it must integrate with, and what is deliberately out.
Pilot
A working configuration with one team or one process, measured against how it works today.
Roll out
Extended in stages, each with a way back if it does not hold.
Improve
Measured after launch and changed on evidence, which is when most of the value arrives.
Common questions
Yes. Offline is the default assumption, with sync on reconnection.
If it is faster than paper. Screen count and typing are the things to design out.
It can propose, and a dispatcher decides. Fully automatic scheduling rarely survives contact with reality.
Whatever the team already carries, within reason.
Would this work here?
A short conversation is usually enough to tell whether this fits your situation. If it does not, we will say so.
Get in touch