Skip to content
Superstack

Apps

Field Service App Development

Everything a technician needs on site: jobs, navigation, checklists, parts, photos, signatures and invoicing, with the office watching live.

Synced to accountingJust now

Superstack does field service app development NZ trades and service companies use to keep technicians on the tools instead of driving back for paperwork. Your technicians get the day's jobs, the site history, the checklist and the invoice on one phone. Your office sees every job move in real time and bills the same day.

The problem

the drive back to the office

  • Our plumbers drive back at the end of the day to hand in job sheets: an hour we pay for and cannot bill.
  • A customer rings to ask if the job is done. The office rings the technician, who is under a house and cannot answer.
  • The fittings from the van and the extra hour on site never make the invoice. We find out at stocktake.
  • Invoices go out a week after the job, once someone has read the handwriting. The customer has forgotten what we did.
  • Everything gets written on site and typed again in the office. Two people, one job, and the versions never match.

What Superstack builds

field service app development for the billable hour

A field service mobile app pays for itself in the hours it hands back: no drive back, no retyping, no forgotten parts. We build around your job sheet and your pricing, so a technician does on the phone what they did on paper, once.

Example workflow

The dispatcher drags the job onto a technician and everything after that happens from the phone. The technician gets the notification, the customer gets the ETA text, and check-in starts the clock. The technician works through the checklist, taps the parts used and hands the phone over for a signature. The invoice goes out from the driveway and lands in your accounting software. The office steps in only for a reschedule, a quote approval or a customer query.

  1. 1
    Dispatcher assigns the job
  2. 2
    Technician notified
  3. 3
    Customer gets an ETA text
  4. 4
    Check-in on site
  5. 5
    Checklist completed
  6. 6
    Parts and time logged
  7. 7
    Customer signs
  8. 8
    Invoice sent
  9. 9
    Synced to accounting

Integrations

Your accounting software receives each invoice as it is sent and returns payment status to the job. Google Maps drives navigation and the ETA, Twilio sends the 'on our way' texts, and Stripe takes card payments on site. An existing scheduling or inventory system supplies the jobs and stock, and gets back what was used.

Any system with an API connects. Click a logo to visit them.

Add AI when it actually makes sense

AI is optional. The app captures the job, parts and signature without it. We add AI only where it saves typing or catches a mistake before the invoice. Read how we use AI and where it fits into business process automation.

Web app, mobile app and customer portal

Web app

Dispatchers and the office use the web app: the schedule board, the live dashboard, pricing and checklists, invoicing and reports. It is where the day gets planned and the end-of-day billing check happens.

Mobile app

Technicians use the mobile app on iPhone or Android. It is a technician app built for gloves and glare: today's jobs, navigation, checklists, parts, photos, signature and invoice. A job app for field workers has to be quicker than paper.

Customer portal

Customers log in to see the ETA, approve a quote, view the photos and report, and pay the invoice. All three share one database, so the moment a technician taps done, the portal and the dashboard say so.

Build options

FAQ

Yes. The technician's jobs download before they leave the depot, and everything they capture on site sits on the phone until a connection returns. Checklists, photos, parts, time and signatures work in a basement plant room. When the van is back in range the app syncs, and the office sees the job as if it had happened live.

Yes. We build one app that runs on both, so a plumber on iPhone and an apprentice on Android see the same screens and jobs. It also runs on a tablet mounted in the van. You choose whether to publish it in the app stores under your name or distribute it privately to company phones.

Yes, if it has an API or an export. The app reads the day's jobs from your scheduler and writes back status, times, parts and the signed report, so dispatch keeps working where it always has. If your scheduler cannot do that, we tell you before the build, and often the answer is to bring scheduling into the app itself.

Yes. When the technician taps 'on my way', the customer gets a text with the name, the ETA from Google Maps and a link to track the van. If the technician is running late, the office updates the time and the customer gets a second text. Texts go through Twilio, use your wording, and stop the 'where are you' phone calls.

Fast, because the field worker app is the smallest part of the build. We start with one job type and one technician, usually the person most fed up with paper, and get them running real jobs on the app while the office dashboard is still being finished. What they find in those first jobs shapes the rest of the build.

No per-technician fees. You pay for the build, then hosting and support for the business, so adding a technician means adding a login, not a subscription. That is the opposite of most field service subscriptions, where the monthly bill climbs with every hire. We set out the ongoing costs before the build, and none of them depends on headcount.

Talk to Superstack

Built around the way you work.

Your business shouldn't have to fit someone else's software. Tell us how your business works. We'll show you what Superstack can build around it.

Send us one job sheet, start to finish. We'll show you it running on a phone with no paper.