ProductCompliance

The compliance pipeline

Replaced a monthly spreadsheet reconstruction with a five-stage pipeline an operator finishes in one sitting.

I mapped the audit obligation backwards from what the LABO actually asks for, then split it into stages that a machine and a human each own. The first three stages run unattended; the operator only sees the shifts that need a decision. Defining that hand-off point — what the software is allowed to correct silently versus what a licence holder must sign off — was the core product decision of the whole platform.

ProductOperations

Shift and break review

Operators report roughly 60–70% less administrative time per compliance cycle.

The screen only shows shifts the rule engine could not clear on its own. Severity is encoded in the row itself, so an operator scans for colour rather than reading every line — the difference between reviewing 214 shifts and reviewing the six that matter. Every adjustment is written back as an audit trail entry, because a correction an operator cannot justify later is worse than no correction at all.

• Exceptions-first view
• Immutable audit trail
• Two-tier severity

DataAutomation

Platform data ingestion

Removed the manual download step entirely — including for the platform that offers no API.

Driver activity lives inside the ride-hailing platforms, and not all of them expose it programmatically. I specified an ingestion layer that treats both cases as the same problem: whatever the source, the output is one normalised document per driver-day. That single shape is what lets the rule engine, the dashboard and the report builder each read the same data without knowing where it came from.

• Python · FastAPI
• Headless browser automation
• Firestore · Google Cloud

StrategyGo-to-market

Commercial architecture and positioning

Restructured the offer into a compliance base plus paid modules, and moved the pitch off penalties entirely.

Selling compliance on the threat of fines put the product in the same mental category as an accountant's invoice — a cost to minimise. Reframing it around licence risk moved it into the category of things an operator cannot run without. Pricing followed the same logic: everyone pays for the compliance base, and the modules that create margin rather than obligation are sold separately.

Operators respond to "pass your next audit", not to "avoid a €X penalty". The first is an outcome they already worry about; the second is a number they discount.

• 3 pricing modules
• Full financial model