Trade businesses — plumbers, electricians, builders, HVAC technicians, pest controllers — have some of the most specific app requirements of any industry. The work happens in the field, often without reliable internet. Jobs get dispatched, changed, and completed across a scattered team. Invoices need to be generated on-site. Customers need to know when someone's coming.

Off-the-shelf tools like ServiceM8, Fergus, and AroFlo solve a lot of this — and for many trades, they're the right answer. But once you have specific workflows, pricing logic, or integration requirements they don't support, a custom app starts to make sense.

Here's what a tradie app typically needs to do well.

Job management and scheduling

The core of any field service app is resource and staff scheduling — assigning jobs to technicians, managing their availability, and showing each person their work queue for the day. This sits on top of a booking system that handles customer-facing scheduling: letting customers book a call-out online, picking from available slots, and receiving confirmation automatically.

For trade businesses with multiple technicians, the scheduling logic needs to handle individual availability, travel time between jobs, and emergency call-outs that jump the queue.

GPS tracking and field visibility

Dispatchers need to know where their team is. Customers want to know when their technician is arriving. GPS tracking solves both — live location for the dispatch view, and "your technician is 10 minutes away" notifications for customers.

For businesses running a fleet, GPS also provides a record of where vehicles have been, which is useful for job verification and insurance purposes.

Invoicing on-site

One of the biggest wins in a tradie app is invoicing and PDF generation that happens at the job, not back at the office. A technician completes a job, marks materials and labour, and a tax-compliant invoice goes to the customer immediately. For businesses that currently invoice days or weeks after the job, this compresses the cash flow cycle significantly.

This ties directly to GST calculation — the invoice needs to correctly handle GST, show the ABN, and meet ATO requirements for a valid tax invoice.

Payments in the field

Collecting payment on-site — card payments via a physical reader, or a payment link sent by SMS — reduces outstanding invoices dramatically. One-off payment processing via Stripe integrates with the invoice to create a complete job-to-payment flow without manual reconciliation.

Offline mode

Job sites, crawl spaces, rural properties — mobile reception is unreliable. Offline mode means the app keeps working: technicians can view job details, complete checklists, add notes, and collect signatures without a connection. Data syncs automatically when the device comes back online.

This is one of the most important features for trades specifically, and one that's often underestimated in scoping.

Notifications and updates

Push notifications keep the team updated — new job assigned, job details changed, customer running late. SMS notifications keep customers in the loop — booking confirmation, technician on the way, invoice sent. Both reduce inbound calls to the office significantly.

Role-based access

Office staff, technicians, and customers all need different access. Role-based permissions ensures technicians only see their own jobs, customers only see their own history, and admins can manage everything. Without this, everyone sees everything — which is both a security issue and a usability one.

What does it cost?

A core tradie app — job management, GPS tracking, on-site invoicing, payments, offline mode, push notifications — typically runs $25,000–$50,000 AUD depending on the number of features, complexity of scheduling logic, and integrations required (Xero, MYOB, parts suppliers).

The app cost calculator lets you pick your specific feature set and see a rough estimate.

Questions to ask before you build

Do you actually need a custom app, or would ServiceM8 / Fergus work with some configuration? Custom makes sense when your workflows are genuinely different, or when you need deep integration with systems those tools don't connect to.

How many technicians does the scheduling logic need to handle? The complexity (and cost) of scheduling increases significantly past ~5 concurrent technicians.

Does the app need to work offline, and how much data needs to be available offline? Job details, customer history, parts lists — define this clearly before build.

What integrations are non-negotiable? Xero, MYOB, a parts supplier API, or a CRM system can each add $2,000–$5,000 to the build.

---

See also: GPS tracking costs · Invoicing & PDF generation · Offline mode & PWA · App cost calculator