Case studies
Two operations,named.
Both are real businesses you can look up. One drives RouteMate entirely from its own software over the API; the other runs three technicians and a diary’s worth of jobs from the dispatch board. Neither page claims a saving we have not measured.
Case 01EnterpriseAPI-drivenSignage & print
Four companies, one in-house system, and installers whose day arrives already sequenced — with a time allowance per job type so a two-hour fascia install is not treated like a corflute swap.
- Companies
- 4
- Interface
- Their own software
Case 02Team planField serviceCarpet cleaning
Springfield and Ipswich since 1999. Cleans that run from forty minutes to half a day, vacate work tied to a handover time, and a day divided by hours available rather than by suburb.
- Technicians
- 3
- Trading since
- 1999
The two shapes
How the two customers differ across plan, intake and constraints.| Attribute | Gigil | Nu-Look |
|---|
| Industry | Design, print and signage | Carpet and upholstery cleaning |
|---|
| Plan | Enterprise | Team |
|---|
| How work arrives | POST from their own platform | Entered on the dispatch board |
|---|
| Who plans the day | Nobody — the API does | One person, in minutes |
|---|
| Time on site | Set by job type in their system | Set per booking by service |
|---|
| The deadline that binds | Install windows on site access | Vacate handovers |
|---|
Different plans, opposite entry points, the same underlying decision: sequence the work with time on site inside the calculation.
Want to talk to one of them?
Reference calls are available during a trial. We will ask them first, and we will not pretend a courier reference is a field-service one.