From Spreadsheets to a Full Operations Platform: 14 Weeks to Build a Crane Hire System in NZ

Most crane hire companies in New Zealand are running their operations on some version of the same stack: a collection of spreadsheets, a generic accounting tool, email threads, and a shared drive full of PDFs that nobody can find when they need them. It works — until the business hits the point where it does not.

R&O is a New Zealand crane hire business. They were at that point. The business had reached a scale where spreadsheets were no longer just inconvenient — they were a genuine operational risk. Quotes were taking too long to produce and too easy to get wrong. Job records were fragmented across multiple tools. Health and Safety compliance documentation — licences, incident records, personnel certifications — was managed manually with no alerting for expiry dates. Every invoice had to be manually re-entered into Xero.

We built them a full operations platform from scratch. Here is what we built, how we built it, and why the approach we used made it possible to deliver at approximately 80% less than a comparable traditional agency project.

What the system needed to do

Before writing a line of code, we spent two weeks in discovery — mapping every manual process, every spreadsheet, every email handoff, and every piece of compliance documentation the business was managing. The scope that came out of that process covered six interconnected modules.

• Lead pipeline — a shared kanban board replacing individual inboxes and tracking every enquiry from first contact through to quote sent
• Quote builder — generating professional PDF quotes from line-item rate cards, with full variation history so nothing is ever overwritten
• Job lifecycle management — converting accepted quotes into job records, tracking every job from booked through to invoiced and closed
• Client and supplier management — a single source of truth for every contact, with full job and document history attached
• Xero integration — accepted quotes auto-generate draft invoices in Xero; supplier purchase orders auto-push as Bills. Zero manual re-entry.
• Health and Safety compliance — a dedicated module covering personnel records, licence and certification tracking (with expiry alerts), incident recording, and a compliance dashboard showing the status of every licence across the team

All documents — lift studies, site plans, compliance certificates, signed authorisations — are stored in Supabase Storage, attached directly to the relevant job or personnel record. Access to the entire system is restricted via VPN, so sensitive client, site, and compliance data never travels over an open network. Email notifications (via Resend) alert the right people when licences are approaching expiry, jobs are updated, or quotes need action.

The stack

• Next.js and React (TypeScript) — fast, statically optimised where possible, fully type-safe
• Supabase — PostgreSQL database hosted in the Sydney region for NZ data residency, with row-level security and Storage for documents
• Vercel — deployment and hosting, preview environments for every feature branch
• Xero API — bidirectional integration for invoices and bills
• Resend — transactional email for notifications and alerts
• VPN-restricted access — the system is not publicly accessible; only authorised team members can reach it

What phase 1 delivered in 14 weeks

Phase 1 covered the full commercial workflow — from first lead through to invoiced job — plus the complete H&S compliance module. It went live in 14 weeks from the discovery kickoff. The system includes a full audit log: every create, update, and delete is recorded with the user and timestamp, giving the business a permanent, queryable record of every change ever made.

The H&S module was a significant part of Phase 1 scope. For a crane hire business operating in New Zealand, Health and Safety compliance is not optional — licence expiries, incident records, and personnel certification all need to be actively managed, not discovered after the fact. The compliance dashboard gives the operations team a single view of every team member's certification status, with automatic alerts as expiry dates approach.

Built to grow: the Phase 2 roadmap

The Phase 1 architecture was designed from the start to support Phase 2 without a rebuild. The data model, API structure, and access control layer are all built around extensibility. Phase 2 — currently in scoping — adds:

• Scheduling and dispatch — visual scheduling of cranes and operators against confirmed jobs
• SMS dispatch — automatic job briefings sent to field operators on job confirmation
• Staff and asset management — full equipment register with service history and availability
• AI-powered dashboards — natural language queries over job history, revenue by client, utilisation rates
• Client portal — self-service access for clients to view job status and download documents

Phase 2 slots directly onto Phase 1 — no rewrites, no migrations, no architectural compromises. That is what 'built to grow' actually means: not a marketing phrase, but a deliberate decision made in discovery about how the data model is structured.

How AI-augmented delivery changes the cost equation

A system of this scope — six interconnected modules, two-way Xero integration, custom H&S compliance engine, VPN-secured infrastructure, document management, and full audit logging — would cost a NZ business considerably more at a traditional agency. We delivered Phase 1 at approximately 80% less than comparable agency quotes for equivalent scope.

That gap is not because we cut corners. It is because of how we work. We use Claude and Cursor as core tools throughout every project — AI-augmented development that lets one senior developer deliver at the output of a larger team, without the project management overhead, account management layers, or agency margin that inflate traditional quotes.

The approach also changes the risk profile. We scope everything before writing a line of code and sign a scope document with the client — fixed price, fixed scope, fixed timeline. No day-rate billing, no 'out of scope' emails when a feature takes longer than estimated, no invoice surprises. The client knows exactly what they are getting and what it costs before the project starts.

What the client owns after handover

• Full IP and source code — transferred to the client's GitHub repository
• All cloud accounts — Supabase, Vercel, Resend — under the client's own billing
• Complete documentation — architecture, data model, deployment guide, and module-by-module technical notes
• No lock-in — the client can hand the codebase to any developer to extend or maintain

What to look for when considering a custom platform for your NZ business

A custom operations platform is the right choice when off-the-shelf software genuinely cannot handle your workflow — not just when you want something bespoke. The question is not 'what could we build?' but 'what is the cheapest solution that actually solves the problem?'

For R&O, the combination of custom quoting logic, crane-specific H&S compliance requirements, and the need for everything to connect to Xero without manual entry put the business past the point where a generic job management tool could work. That is a genuine case for custom software.

If you are running your operations across spreadsheets and want to understand whether a custom platform makes sense for your business, a 30-minute discovery call is the right place to start. We will tell you honestly whether custom software is the answer — or whether there is a cheaper solution you have not considered yet.