Workflow software for 5–25 person NZ plumbing & electrical crews
You're past the one-tradie-plus-a-van size, but not yet at the point where a dedicated ops manager owns the workflow. This post is the 5-minute version of why the spreadsheet-plus-WhatsApp stack stops scaling at the 8-to-15 person band, what workflow software consolidates instead, and how a same-week rollout trades the Monday admin pile-up for a single job note that drafts the quote, the record, and the roster together.
The pain
Four ways a spreadsheet stops being the workflow at the 8-to-15 person band
Every cross-vertical NZ trade crew recognises at least two of these. They aren't catastrophic failures — they're the slow stand-up of admin overhead that nobody scheduled time to fix because the founder has been the integration layer all along.
A spreadsheet stops scaling past ~8 people
At a one-or-two-tradie size, a Google Sheet plus a phone each is fine — the same admin owner is also the person doing the work, and the sheet is the single source of truth. The moment you add a third crew member, then a fourth, then a second van, the sheet forks. Rows stop lining up with reality, the owner becomes the integration layer, and the Monday admin pile-up is the visible symptom of a system that has silently lost its authority.
Messages, photos, and notes scattered across three apps
Job brief comes in on email or a Messenger thread. Photos of the install or the board land in a separate camera roll. The note-to-self about what was actually done sits in someone's phone. Three apps, three owners, no shared ledger — and the question "what was agreed for job #2179" gets answered from memory because it's faster than digging.
Quote, install, and invoice drift apart over the week
A quote goes out Monday. The install adds a part that wasn't on the original line list. The invoice lands Friday with a margin the owner didn't intend, and the client questions the line they didn't know was added. The drift isn't visible at any single point — it's the gap between three events that should have shared one record, but didn't.
Record-finding is a Monday admin pile-up
Most 5–25 person NZ trade crews run a Monday ritual: reconciling the week, filing the certificates, restoring the photos, chasing the missing test log for the job EWRB or PGDB is going to ask about. It takes half a day per week, falls on the founder, and is rarely charged to a job — it's the cost of running a business on a stack that wasn't designed for the size.
The scope split
What a 5–25 person crew runs on today — and what runs after workflow software lands
This is a cohort-level swerve, not a board-specific rewrite. Whether the crew is licensed under PGDB (plumbers, gasfitters, drainlayers), EWRB (sparkies), or both sides running in parallel, the same workflow consolidation applies to the way the week is run.
What a 5–25 person crew runs on now
- A Google Sheet (or two) acting as the job ledger — quotes, install notes, and invoice status across tabs that someone owns in their head.
- Three messaging apps doing what a real crew feed should — email for client comms, WhatsApp or Messenger for the team, photos in a personal camera roll.
- Quotes drafted by hand on a template, then re-keyed into accounting when the invoice goes out.
- Certificates and compliance paperwork stored in a folder nobody owns, with retention dependent on whichever laptop has the file open.
- The founder as integration layer — answering "what's happening on job #2187" by tapping through three apps to reconstruct what everyone else already knows.
What runs after workflow software lands
- One job note per install — the same place, every job, written once on the device already in the van. Captured by whoever is on the tools, not by the founder at midnight.
- Quote, record, and compliance paperwork drafted in one pass against the same source note. Line items and the compliance record share provenance, so invoice drift and missing test logs stop being separate failure modes.
- A crew feed that replaces the three messaging apps — every photo, note, and message attached to the source job, searchable, with the line items and the records attached.
- Approvals that run on the dashboard, not in the founder's head. The sparky's draft lands next to the plumber's draft, queued for the one approval that signs off the job.
- Records filed with the install behind them — exportable, retention-aware, and ready for the EWRB or PGDB request when it arrives, instead of rebuilt over the Monday morning coffee.
What's at stake
The four failure modes a 15-person crew can't keep absorbing
Treated at a cohort level — no specific dollar-per-hour claims, no fake multipliers. The framing is durable across boards because the underlying failure pattern is the same: a single founder absorbing operational overhead that, at the next headcount rung, becomes a margin problem the team can't keep carrying.
Invoice queue creep as the founder absorbs the admin
When everything runs through the founder's memory, a missed quote or a delayed invoice isn't an operational delay — it's a margin leak. At a 15-person crew, that leak shows up as a doubling in days-sales-outstanding on a quarterly review, and the recovery work lands back on the same person who didn't have time to send the invoice in the first place.
Compliance rosters that quietly miss a renewal
The 5–25 person band is where a second plumber needs their practising licence check, or someone needs an ESR refresh, or the PGDB supervising-licence holder is on leave. None of this is dramatic in a single week — but the missed renewal shows up at the next audit, and the cost is the gap where a record should have been.
Quote-to-margin drift when records stop lining up
A quote goes out at margin X. The install adds a fitting that wasn't on the quote. The invoice lands at margin Y, and the client disputes the line they didn't authorise. The deeper failure isn't the dispute — it's that the quote, the install record, and the invoice didn't share the same source, so the drift was inevitable and invisible until the client asked.
Crew retention when the founder IS the admin
The best tradies leave businesses where they can't get a clean invoice out the door in two weeks, where they're answering WhatsApp queries about job status instead of doing the next job. Workflow software that surfaces queued work to the team removes the founder as the only person who knows what's happening — and removes the bottleneck that drives the good people out.
ROI for a 15-person crew
What the consolidation is actually worth at the cohort band
The honest framing: workflow software at the 15-person cohort is a margin recovery, not a new revenue stream. The founder gets their Monday back. The line items stop drifting because quote, install, and invoice share provenance. Compliance renewals stop going missing because the record sits with the install. Crew retention improves because the team can see what's queued without asking the founder. None of this is a single-source-of-truth miracle — it's one workflow that pulls the four failure modes above into a single dashboard, with board-specific certificates drafted alongside the quote.
The cross-vertical positioning is deliberate — KoruAI covers PGDB (plumbing, gasfitting, drainlaying) and EWRB (electrical) compliance record-keeping against the same workflow, so a mixed-trade crew gets one stack, two board templates. If you're weighing it board-by-board first, the PGDB and EWRB-specific pillar posts go deeper on the records themselves.
The workflow
One job note. Quote, record, and roster drafted in one pass.
The same workflow that drafts a job summary becomes the workflow that drafts the quote AND the compliance record AND the next-week roster. The crew member on the tools writes one note — KoruAI drafts against the right record-keeping frame (PGDB or EWRB, depending on the install), you approve, the quote goes out the door and the record is filed with provenance. No re-keying, no reconstructing the bundle the night before a follow-up call.
Capture the job note in one place
A sparky or plumber writes a brief note after the install — same place, every job. What was done, the parts used, the photos from the van, the client's quote. Captured once, on the device already in the van, by the person on the tools, not the founder at midnight.
AI drafts the quote, the record, and the roster
KoruAI reads the note and drafts the matching paperwork in one pass: the quote you send the client, the compliance record your board expects (CoC / ESC for a sparky, gas certificate or drainage record for a plumber), the next-week roster, and the bill-out to the supplier. Drafted against your templates, mapped to whichever board applies to the crew who actually did the work.
You approve the draft
The draft lands in your dashboard with the source note, the photos, and the crew feed attached. You read, edit if anything is off, and approve. One approval per job — and the quote, the record, and the roster all go out the door together.
Filed with the install record behind it
Every approved quote, compliance record, roster, and test result is stored with its draft history, the source job note, and the revision timestamps. When EWRB, PGDB, or WorkSafe asks for the bundle behind a job, you produce it in seconds — the same record the inspector will read.
Why KoruAI
Built for the cross-vertical crew workflow, not a generic job board
NZ-based
A team that has worked with NZ trade businesses understands PGDB, EWRB, and the way a 5–25 person crew actually runs its week. Built in Christchurch, supported in business hours NZST.
Built for the cross-vertical crew workflow
Cover both boards (PGDB for plumbing / gasfitting / drainlaying, EWRB for electrical) without doubling up the admin. The same record-keeping workflow that files the gas certificate also files the next job's quote — and the crew feed keeps the sparky's install note visible to the plumber scheduled for the second visit.
Reach a real person
You can email the team behind the build at hello@koruaitrades.com. Replies come from a real person, usually the same day. No support-ticket queue, no chatbot intermediary.
Common questions
FAQ for 5–25 person NZ plumbing & electrical crews
Next step
See what the rollout looks like for your 5–25 person crew
The diagnostic, the 30-day sprint, and the ongoing managed plan all ship the same cross-vertical workflow — applied to your PGDB / EWRB templates, your rate card, your board scope, and the compliance frame your crew actually works under. Browse the pricing page when you're ready to compare, or grab the AI-readiness checklist first.