Gigil runs fourcompanies fromtheir own software.
A Sunshine Coast design, print and signage group with an in-house platform its whole operation already lives in. RouteMate Enterprise sits behind it: jobs are pushed over the API, sequenced with a time allowance per task, and land on the installer's phone ready to drive.
| Business | Gigil — design, print and signage group |
| Companies in the group | Four brands under one operation |
| Based | Sunshine Coast, Queensland |
| Work routed | Signage installs, print delivery, real-estate boards |
| Plan | Enterprise |
| Integration | Their own platform → RouteMate Integration API |
| Who touches RouteMate | The installers, in the app. Dispatch never opens it |
gigil.au · client portal at app.gigil.au · public notification signage at developmentsigns.com.au
The software knew the jobs. Nothing knew the day.
Gigil's platform already held every job across four companies — the artwork, the client, the site address, the install requirements. What it could not do was turn a day's worth of installs and deliveries into a route, so someone did it by hand each morning: pick the jobs, guess the order, guess how long each site would take, then message the installers.
Signage work makes that guess expensive. A corflute swap is minutes; a shopfront install is hours. Order the day wrong and the long job lands at 4pm.
- 01A person ordered each day's installs by hand, from memory of the region.
- 02Time on site was a guess, so long jobs landed late in the day.
- 03Runs were communicated as messages, not as a list the installer could work down.
- 04Four brands meant four slightly different versions of the same morning ritual.
Their platform → RouteMate → the installer
- 01
Jobs are scheduled where they already live
Nothing changes for the office. Work is created in Gigil's own platform, as it always was.
- 02
The platform posts the run
One authenticated call per driver per day carries the stops, each with the address and the expected time on site for that job type.
- 03
RouteMate solves and assigns
Addresses are geocoded, the sequence is optimised around travel and time on site, and the route is assigned to the named installer.
- 04
The installer opens the app
The day is already ordered, with the next stop and the time budget for it. No planning, no phone call.
- 05
Status flows back
Gigil's platform polls job status, so the office sees progress against the schedule it created.
Nobody at Gigil logs into RouteMate to plan. Their own platform is the interface; RouteMate is the routing engine behind it.
POST /v1/integration-import
{
"external_job_id": "GIG-INSTALL-14208",
"title": "Installs — Tue, Sunshine Coast",
"driver_email": "installer@gigil.au",
"timezone": "Australia/Brisbane",
"stops": [
{ "external_stop_id": "JOB-88421",
"address": "Maroochydore QLD 4558",
"label": "Shopfront — fascia install",
"duration_minutes": 120 },
{ "external_stop_id": "JOB-88437",
"address": "Buderim QLD 4556",
"label": "Corflute swap",
"duration_minutes": 15 }
],
"optimize": true
}What the change actually was
No morning planning
The run is built when the jobs are scheduled, not when the installer arrives. Opening the app is the whole handover.
Time on site is planned
A two-hour install and a twenty-minute swap are no longer treated as the same stop, so the day's back end stops collapsing.
Four companies, one method
Every brand in the group pushes jobs the same way. Adding a company is a client credential, not a new process.
Described as operations, not as a percentage. We publish figures for a named customer only once they are measured and the customer has seen them.
Already have software your team lives in?
Keep it. Put the routing behind it — a token, one POST per run, and the driver's day arrives sequenced.