← All case files File A · Code

Hours into minutes

A BC municipality spent most of a working day pulling fleet reports for 500–600 vehicles. I built a Geotab add-in that does it in five minutes.

4–8 h → 5 minMunicipal fleet scorecard, one click
12 minTo build a DOT report that replaced 1–2 days of work, twice a year
15–20 minSaved in every biweekly meeting by an order lookup
0Customer data sent to our servers by the safety scorecard

The problem

The municipality's utilization report and fleet scorecard covered 500–600 vehicles. The data was all in MyGeotab, but turning it into the report took someone 4–8 hours of manual work every time. Other customers had the same pattern: a recurring report or lookup that ate a day, or a slice of every meeting.

What I did

Rather than build each tool by hand, I built a tool that builds them: an Add-in Creator that turns a plain-language description into a working MyGeotab add-in. Then I used it for customers:

  • Municipality: an asset report and fleet scorecard that runs in one click.
  • State DOT: an exception time report, deployed to the customer's government tenant. It took 12 minutes to build and replaces 1–2 days of work they did twice a year.
  • Waste management: an order and purchase-order lookup, built in under 30 minutes, that removes 15–20 minutes of manual reconciliation from every biweekly meeting.
  • Driver safety: a 0–100 distance-normalized scorecard with configurable weights and risk bands, Excel/CSV/PDF export, and the customer's own group hierarchy. It runs entirely in the browser, so no customer data touches our servers.

I demoed the Add-in Creator to the whole company at an internal AI showcase, with these as the customer results.

The result

The municipality's report went from 4–8 hours to 5 minutes.

Before4–8 hours
After5 minutes
Drawn to scale against a six-hour day.