Walk into almost any residential solar business in Australia and you’ll find the same setup. There’s a design and proposal tool for the quote. There’s a job management tool for the field side. There’s an accounting package for the money. Three tools, three logins, three monthly bills, and not one of them talks to the others in a way you can trust.
Each one is good at its own job. That’s the trap. You didn’t make a bad decision picking any of them. You made three reasonable decisions, and the gap between them is where your time and your margin quietly leak out.
I’ve watched this play out across hundreds of solar businesses over twenty years, from the supplier side, the admin side, and the sales side. The pattern is so consistent it’s almost a law. So let me name the problem properly, explain why the market built it this way, and show you exactly where the data falls through the cracks.
The standard three-tool stack
If you run residential solar in this country, your stack probably looks like this.
A design and proposal tool: Pylon, SolarPlus, OpenSolar or Aurora. This is where the system gets designed, the roof gets laid out, the string sizing happens, and the customer-facing proposal gets generated.
A job management tool: ServiceM8 is the common one, though plenty of operators are still running this part on spreadsheets and a shared calendar. This is where the job card lives, the scheduling happens, and the installer crew gets their run sheet.
An accounting package: Xero, or MYOB. This is where invoices, bills, payroll and BAS live.
And then there’s a fourth track that nobody designed into the stack at all: STC paperwork. The Small-scale Technology Certificates created from the system’s deemed generation get handled by email, a spreadsheet, or a separate trader portal, sitting off to the side of everything else.
That’s the dominant pattern. Not because anyone chose it as a system, but because each tool solved one urgent problem at a time.
Why no single tool covers the whole job
Here’s the part most people never stop to think about. These tools were built by different people, for different buyers, starting from different ends of the problem.
Design tools are built by engineers who understand solar physics. They start from the panel, the inverter, the roof and the shading. They’re brilliant at the technical proposal and weak on what happens after the customer says yes.
Job management tools like ServiceM8 are built for general trades: plumbers, sparkies, locksmiths, anyone with a van and a calendar. Their entry point is the work order, full stop. STCs, deeming periods, and the mechanics of a solar quote are simply outside their world (SPS Energy, n.d.).
Accounting tools are built for bookkeepers and accountants. They start from the ledger. They care about a clean set of books, not about whether the panel count on the invoice matches the panel count on the roof.
None of them start from the installer’s actual workflow, which runs lead to quote to job to install to STC lodgement to invoice to follow-up. So none of them own the whole thing. Each one owns a slice, and you are the integration layer holding the slices together by hand.
The handoff points where data goes missing
The cost of this stack isn’t in any single tool. It’s in the seams between them. Walk the job through and you can see every place a human has to retype something that already exists.
Quote accepted to job created. The customer signs off in your design tool. Now someone opens the job management tool and re-keys the customer name, the address, the contact number, the panel count and the system size into a fresh job card. Same data, entered a second time.
Job completed to invoice raised. The install’s done, the job’s closed in the field tool. Now someone opens Xero and creates the invoice, re-entering the customer and the line items. Same data, entered a third time.
STC lodgement, running in parallel. The compliance paperwork, the photos, the CES, the assignment form, all of it gets pulled together separately, often from email threads and a folder of phone photos. This is the fourth entry, and it’s the one most likely to stall and tie up cash.
Every one of those handoffs is a manual copy. Every manual copy is a chance to fat-finger an address, transpose a panel count, or miss a job entirely when it gets busy. And it does get busy.
The one real integration, and what it doesn’t cover
To be fair to the market, there is one explicitly built connection that gets talked about a lot: the link between Pylon and ServiceM8. It’s real, not hypothetical, and Pylon names it on its own comparison material as a differentiator. If you run that exact pairing, it does take some of the sting out of the quote-to-job handoff.
But look closely at what it doesn’t do. It doesn’t handle your STC documentation. It doesn’t give you subcontractor visibility across jobs. It doesn’t carry job costing back to the original quote so you can see whether you actually made money on the install. And it only helps if you happen to be running those two specific tools. The moment your stack is OpenSolar plus spreadsheets plus Xero, you’re back to hand-keying everything.
One bridge between two of the four tracks is not a connected business. It’s a connected corner of one.
What the re-entry actually costs you
The obvious cost is errors. The wrong address on a job card sends a crew to the wrong street. The wrong panel count on an invoice means a billing query, or worse, an STC claim that doesn’t match the install. Every retype is a fresh chance to get it wrong, and the error usually surfaces at the worst possible moment.
The less obvious cost is time. I won’t put a hard figure on it because it varies with how messy your handoffs are, but in my experience the manual re-entry across those handoffs can easily add twenty to forty minutes of pure admin to every single job. That’s not selling, designing or installing. That’s a person retyping data a computer already has. Multiply it across a month of jobs and you’re paying for a part-time role that exists only because your tools won’t speak to each other.
This isn’t just my read. ServiceM8 reviewers on platforms like G2 and GetApp consistently call out the integration burden and the need to run other tools separately as a top frustration. The complaint isn’t that the tool is bad. It’s that it’s an island.
The reporting void nobody mentions
Here’s the cost that hurts most and gets noticed least. Each tool reports beautifully on its own little world, and on nothing else.
Xero tells you about money. The field tool tells you about jobs. The design tool tells you about proposals. Not one of them tells you the things you actually need to run the business:
What’s my quote-to-job conversion rate? What’s the real margin on a completed job once I cost it back against the quote? How much STC cash am I owed against jobs already installed? How long does it take me to go from quote to install?
Those numbers live across all three tools at once, so they live in none of them. To get them you export to a spreadsheet on a Sunday night and stitch it together by hand, which means most owners never get them at all. You end up flying the business on gut feel because the dashboard you need was never built, because no single tool can see the whole picture.
Why this is a growth ceiling, not just an annoyance
At five jobs a month, this stack is survivable. You can hold the seams together yourself, eat the admin, and the errors are rare enough to clean up.
At fifty jobs a month, it breaks. The manual handoffs that were a nuisance become a full-time problem. Jobs slip through. STC cash gets stuck behind late paperwork. The reporting blind spot means you can’t even see where the business is bleeding, so you can’t fix it.
That’s the cruel part. Scattered tools put a hard ceiling on how far your business can grow, and you’ll often hit that ceiling before you can even pinpoint the cause. The result is a nagging feeling of being flat-out busy without actually becoming more profitable (Monday.com, n.d.). If you’ve already moved off spreadsheets onto a couple of tools and still feel the squeeze, the next bottleneck is almost always the gaps between them, not the tools themselves. I dug into that earlier transition in moving past spreadsheets to real solar business software.
This three-tool problem is exactly why I’m building CurrentFlow. The idea is one system where quoting, scheduling, job management and STC compliance share the same data, so the customer and the job get entered once and flow through. It isn’t live yet, and I’m not going to pretend it is. But the gap is real, I’ve lived it from every side of this trade, and it’s worth naming clearly whether or not the thing I’m building ever ships.
For now, if you take one thing away: the problem isn’t your design tool, your field tool or your accounting package. It’s the empty space between them, and that space is costing you more than any single subscription.
References
Clean Energy Regulator. (n.d.). Small-scale Technology Certificates and the Small-scale Renewable Energy Scheme. https://www.cleanenergyregulator.gov.au
G2. (n.d.). ServiceM8 reviews. https://www.g2.com
GetApp. (n.d.). ServiceM8 reviews and pricing. https://www.getapp.com
ServiceM8. (n.d.). Job management software for trades and services businesses. https://www.servicem8.com
Xero. (n.d.). Accounting software for small business. https://www.xero.com
FAQ
What is the typical software stack for an Australian solar install business?
Most residential solar businesses run three tools that each cover one part of the job: a design and proposal tool (such as Pylon, SolarPlus, OpenSolar or Aurora), a job management tool (commonly ServiceM8, or spreadsheets), and an accounting package (usually Xero or MYOB). STC paperwork tends to sit on a fourth, separate track handled by email or a trader portal.
Why don’t these solar software tools just integrate with each other?
Because they were built by different people for different buyers. Design tools start from solar engineering, job management tools are built for general trades, and accounting tools are built for bookkeepers. None of them start from the installer’s end-to-end workflow, so each owns one slice and leaves the handoffs between them to you. The Pylon to ServiceM8 link is the main exception, and even that covers only part of the quote-to-job step.
How much time does manual data re-entry actually cost per job?
It depends on how messy your handoffs are, so be wary of anyone quoting a hard universal figure. In my experience, re-keying the same customer and job details across the design tool, the field tool and accounting can easily add twenty to forty minutes of admin per job. Across a busy month that adds up to a part-time role that exists only because the tools don’t share data.
Are STCs a government rebate?
No, and it’s worth getting right. Small-scale Technology Certificates (STCs) are tradeable certificates created from a system’s deemed generation. Liable entities, mainly electricity retailers carrying obligations under the federal Renewable Energy Target, must buy and surrender them to the Clean Energy Regulator. The customer usually assigns their right to create the certificates to the installer in exchange for an up-front discount, which is why it feels like a rebate to the buyer but technically is not one.
Does running fewer tools really matter if my current stack works?
At low volume you can hold three or four disconnected tools together by hand. The trouble shows up as you scale: manual handoffs cause errors and dropped jobs, STC cash gets stuck behind late paperwork, and no single tool can report on conversion rate, true job margin or quote-to-install time. The fragmentation becomes a growth ceiling well before most owners can clearly see what is capping them.