From opportunity / positioningHypothesis
The core insight
Compliance/QMS obligations for regulated trades don’t scale down. A 3-bay mechanic shop has almost the same categories of obligation as a 40-branch chain — track individual technician qualifications and CPD, log and respond to customer complaints, run corrective/improvement actions, be audit-ready — but none of the scale to justify enterprise tooling or a dedicated QA person.
Today their options are:
- Spreadsheets and folders — free, but fragile, no audit trail, dies when the one person who maintains it leaves.
- Enterprise LMS/QMS (Totara and similar) via an implementation partner — built for large, complex org charts; a garage ends up paying for and configuring machinery it doesn’t need, and the partner has no domain fluency in automotive workflows, so it’s “never quite right.”
- Nothing — until an audit or a complaint forces a scramble.
- A first-generation dedicated tool or consultant — updated
2026-08-10: this used to read “nothing dedicated exists,” which desk
research found isn’t true. Two live, NZ-specific, NZTA-approved
products exist (WoFMate, itsallauto.com’s eWOF™), and a solo consultant
(Business Systems Sorted) does paid QMS reviews for small operators —
see
research/nz-specific-trade-compliance-check.mdandresearch/business-systems-sorted-nz-consultant.md. Neither shows signs of having saturated the market, and neither covers the full compliance layer or is agentic — but “dedicated software” is now a real category with real, if early, entrants, not an empty one.
That gap — vertical-specific, right-sized, compliance-native software for small regulated operators — is still the opportunity, sharpened rather than closed by the above: the closest existing competitor (WoFMate) already covers a meaningful chunk of the NZTA master records, so the bar for “why Benchmarq” is the record-linking depth and the agentic layer, not just “a dedicated tool exists at all.” Not “a better Totara,” but a different category: a QMS built around the actual jobs a small trade business has to do (qualification tracking, complaints-to-CAPA, improvement plans, audit packs) rather than a generic learning platform bent into that shape.
Why this team
- Kelvin brings domain credibility and — critically — distribution. In a fragmented market of small owner-operators, trust and relationships (MTA, franchise groups, trade associations, existing training relationships) matter more than a superior feature list.
- Product leadership avoids the classic trap in this space: solving it by cloning enterprise QMS feature-for-feature at small scale.
- Data expertise + agentic-first build is the actual differentiation
lever — see
product/agentic-approach.md— and is what lets a 3-person team compete credibly against implementation partners who need a services team.
Beachhead
Automotive first (NZ), specifically small independent garages and
service shops — not dealership groups, not national chains. Discipline
here matters: resist scoping the MVP for “all regulated trades” before the
beachhead is proven. See opportunity/market-analysis.md for adjacent
verticals once automotive is validated.
Market analysis
The evidence behind that gap — and what's changed since the first pass.
Product & feature set
What we're building because of the above, and why the agentic layer is the differentiator.