\Proof

Systems that exist, not opinions about systems.

Most consultants have a framework. Here’s what got actually built and shipped.

\01

Nationwide Legal Document System

ProblemApplicants had to be tracked through the court system by hand — across dozens of jurisdictions, with no single place holding the full picture.
What was builtA nationwide legal document creation and tracking system: 500 fields per record, tracking applicants across all 63 courts and 250 Police lawyers by where they’re based.
\ ResultProcessed $30m of applicant income recovered by advocating for drivers to get their licences — and earned the respect of Police, the MOJ and NZTA inside one system.
\02

Breath & Blood Alcohol Analysis System

ProblemDrivers and Police had no clear way to see how an evidential breath test translated into the real world — or how a breath reading compared against a later blood test.
What was builtNew Zealand’s first system that evaluates EBA breath tests against the real world and shows drivers and Police exactly where a driver sits and how they compare — paired with a BAC blood-testing system that reverse-engineers the blood result to reveal how the reading degraded or climbed over time. All available online.
\ ResultBreath and blood results, side by side and explained, so drivers understand their own readings and Police work from the same picture.
\03

HubSpot Applicant Tracker

ProblemApplicants were tracked across email, spreadsheets and memory. People fell through the gaps.
What was builtA HubSpot pipeline that captures every applicant and moves them through defined stages automatically.
\ ResultNo applicant lost since launch; each phase clear on a detailed dashboard.
\04

Call Centre Sentiment Dashboard

ProblemNo one knew what was actually inside the thousands of calls coming into the call centre — the real content, the reasons people rang, the patterns underneath them.
What was builtAn AI system that transcribed all 7,000 recorded calls, ranked every one, and broke out the common reasons and questions — then turned that into a triage workflow: the best sequence and exact questions to ask incoming callers, all built on the real data.
\ ResultA call centre that triages from evidence, not guesswork — every incoming call handled with the sequence the data proved works.
\05

Google Ads CGA Recovery

ProblemAn ad account had been quietly overbilled and mismanaged for months.
What was builtA full audit trail and a formal dispute filed under the Consumer Guarantees Act.
\ ResultA five-figure overspend recovered and the account restructured to stop the leak.
\06

Webflow CMS Rebuild

ProblemSite content was locked in a structure nobody could touch without a developer.
What was builtA restructured Webflow CMS the team can edit themselves, built around how they actually publish.
\ ResultUpdates that took a week now take ten minutes, in-house.
\07

FileMaker Automation

ProblemA daily process depended on someone remembering a dozen manual steps in the right order.
What was builtFileMaker scripts that run the whole sequence end to end, on a schedule.
\ ResultA three-hour daily task now runs itself.
\08

Real Estate Anniversary Planner

ProblemA busy agent’s seven years of sales were scattered across dozens of agency PDF reports — no single view of who bought, when, or where.
What was builtCollated every sale across seven years from the agency PDFs, stripped the duplicates, and built an anniversary planner: buyer anniversaries as a clear month-by-month list rather than a hard-to-read calendar, each with distance from base and distance to the nearest other properties.
\ ResultGift drop-offs now planned by proximity to save fuel between addresses — and the whole year visible at a glance, so gifts get bulk-bought in advance. Less driving, less spent.

Yours could be the next line on this page.

Tell me the problem →