Where the money gets stuck
Most trade businesses we talk to have plenty of work. The problem is the stretch between packing up the van and seeing the money land. The invoice gets written on Sunday night. It gets chased a fortnight later. The customer disputes it because nobody wrote down what was agreed. It gets paid eventually, minus the hours spent chasing.
Every step in that stretch is a place cash leaks out. Closing it takes a few tools joined up so the booking, the quote, the job, the payment and the Xero entry are all one record. Done right, the customer can pay you while you're still standing in their kitchen.
This is the setup we recommend to plumbers, electricians, landscapers, cleaners and anyone else whose work happens somewhere other than a desk. Most of it you can buy. Some of it, once you grow, you're better off building on top of what you've bought.
The pieces
Think of it as a chain from first enquiry to reconciled bank entry. Each link either shortens the wait or stops a leak.
- Online booking with real availability. A form that shows free slots, not a "request a callback" button. The customer picks a time and it lands in your calendar. You haven't spent twenty minutes on the phone locking in a two hour job. The availability has to come from the same calendar your crews use, though, or you'll double book within a week.
- Deposits at booking. For anything bigger than a small callout, take a deposit when the slot is confirmed. No-shows drop. Tyre kickers drop off. The job starts with money already in the account. Stripe, Square and Tyro all handle this well for Australian businesses.
- Quoting on site. Build the quote on your phone from a price list you maintain, and send it before you leave. Line items, GST shown, a button to accept. Once the customer taps accept you have a record of what was agreed, and that's what makes disputes go away.
- Invoicing from the phone. The invoice is the accepted quote plus any variations, generated in a tap. If it takes longer than a minute it gets left for the weekend, and you're back where you started.
- Tap-to-pay and payment links. Tap-to-pay on a phone means no card reader to lose and no "just transfer it when you get a chance". For customers who aren't there, a payment link in the SMS or emailed invoice gets paid much faster than bank details in a PDF.
- SMS reminders and on-my-way messages. A reminder the day before and a text when you're twenty minutes out. Cheap to run. It removes the two usual reasons a job falls over: the customer forgot, or they weren't home.
- Accounting sync. Every invoice and payment flows into Xero or MYOB on its own. Your bookkeeper stops re-keying, reconciliation takes minutes, and you know your position at the end of the month instead of at BAS time.
None of that is exotic. What matters is that it's connected. A booking that doesn't become a job, that doesn't become an invoice, that doesn't show up in Xero, is four separate admin tasks. Admin is what gets skipped.
Buy it off the shelf first
We build custom software, and we'll say it plainly: most trade businesses shouldn't start there. The job management market for trades is mature. ServiceM8, Tradify, simPRO and the rest cover the whole chain above for a monthly fee, and they plug into the payment providers and accounting packages you already use. For a sole operator or a small crew, one of those plus a payment provider plus SMS is the right answer. You can have it running in a weekend.
If an off-the-shelf tool does ninety percent of what you need, use it and bend your process to fit the last ten. Custom software only makes sense when the missing piece is the thing your business competes on.
Where we do get involved early is the glue. The tool has the integration in theory, but the booking widget doesn't match your website, the availability rules are too simple for how you schedule, or the SMS templates can't say what you want. A small amount of integration work fixes that without replacing the tool underneath.
When it's worth building your own layer
Somewhere between the third crew and the first office manager, the off-the-shelf tool starts fighting the business instead of helping it. The signs are pretty consistent.
Scheduling is the big one. You've got crews with different skills, different areas and different vehicles, and jobs need to go to the right one. The tool gives you a calendar and a drag-and-drop board, and someone in the office spends two hours every morning doing by hand what software should do. A scheduling layer that knows your rules and pushes the result back into the app everyone already uses is often the most valuable piece of software a growing trade business can commission.
Then there's the customer portal. Property managers, builders and commercial clients want to log in, see where their jobs are up to, approve quotes, download invoices and raise new requests without ringing you. Most job tools offer a thin version. When it becomes the reason a big client stays or goes, it's worth building properly.
Recurring maintenance is another. Annual servicing, quarterly inspections, test-and-tag. These need to create jobs on their own, invoice on a cycle, chase renewals and report on compliance. It's a different shape of work from the one-off callout, and generic tools handle it badly. It's one of the most common reasons trade and construction clients ask us to build custom web applications.
And reporting. Margin by job type, callback rates by technician, quote conversion by suburb. The data is all sitting in the job tool and the accounting package. Getting it out in a form you can act on usually needs a small purpose-built layer across both.
In every case we leave the job management tool where it is. We build the one piece the business needs, connect it through the tool's API, and the crews keep using the app they know. The custom part stays narrow, which keeps the cost in proportion and the upkeep manageable.
What it costs, roughly
For a sole trader or small crew, the off-the-shelf stack usually runs to a few hundred dollars a month across subscriptions and card fees. Setup is hours, not weeks.
Integration work to join up a stack you already have, like wiring a website booking widget to real availability or an SMS flow that matches how you operate, tends to sit in the low thousands as a one-off. Treat that as a rough guide. It depends a lot on which tools are involved and how well their APIs behave.
A custom layer like the scheduling engine, portal or maintenance system above is a proper software project. Our guide to custom web application cost goes through the ranges. Whatever the number, it should be paid for by something you can measure: office hours saved each week, a contract kept, fewer no-shows and unpaid invoices.
Where to start
Starting from scratch? Do it in this order. Payments first, because that's where the cash actually gets stuck. Then booking with deposits. Then quoting and invoicing from the field. Then SMS. Then accounting sync. Each step pays for itself on its own, so you see the benefit as you go.
Already got a job management tool that mostly works? Don't rip it out. Write down the three things it makes you do by hand every week, and work out whether each is an integration gap or something the tool can't do at all. The first is cheap to fix. The second is where a custom layer starts to make sense.
We've built software for trades and construction businesses for years, from small integration fixes to full scheduling and portal systems. The first conversation is always the same: where does the money get stuck, and what would it take to unstick it. If that's worth having about your business, get in touch.
