There is a quiet moment that follows almost every software purchase in a trade business. The invoice is paid, the welcome email lands, the login works - and then nothing much happens. Three weeks later the new CRM has four contacts in it, the automation platform has one half-built workflow, and everyone has drifted back to the whiteboard and the group chat. Nobody talks about this moment in the sales demo, but if you have bought business software before, you have probably lived it.
That moment is not a discipline problem. It is a model problem. Most business software is sold as SaaS - software as a service - and the honest, unspoken deal of SaaS is this: we build the tool, you build the system. This post is about the difference between those two things, and about the alternative model we run at Pipereply, which we call SWaS - software with a service.
What SaaS is, and what it is honest about
SaaS is a genuinely brilliant model, and it is worth being fair to it. You pay monthly instead of buying servers. Updates arrive automatically. You can start small and add seats as you grow. The entire modern software economy runs on it, and for good reason.
But the model has a boundary, and it sits exactly where most trade businesses need the most help. SaaS gives you capability, not outcomes. The pipeline exists, but it is empty. The automation builder exists, but the workflows are yours to design. The integrations page lists fifty logos, but connecting your actual OpenSolar account to your actual pipeline, with your actual field names, is an exercise left to the reader. When something breaks, there is a help centre and a ticket queue.
None of that is a scam. It is just the deal. The subscription price is low precisely because the configuration work has been shifted onto you.
The hidden line item: your hours
Here is the maths nobody puts on the pricing page. A capable off-the-shelf CRM might cost a modest monthly fee per seat. Sounds cheap next to a built-for-you system - until you count the owner's evenings spent watching setup tutorials, the workflows that fire twice or not at all, the integration that silently stopped syncing in March, and the slow bleed of a team that never quite trusted the system and went back to doing things by hand.
For a business whose actual job is installing solar or wiring switchboards, that configuration burden does not compete with other software projects for attention. It competes with quoting, installing and invoicing - and it loses every time. The software was not bad. It was just never going to build itself into a system.
What SWaS means
SWaS - software with a service - is the model we run at Pipereply, and the name describes the deal precisely. You are not buying a login. You are buying a working system, plus the team that builds it, connects it, tunes it and keeps it improving. The software matters, but the service is the product.
At Pipereply, that word "service" is specific, not decorative:
- The build is done for you. Core includes three structured 2-hour onboarding sessions plus approximately 12 hours of back-end build and customisation by our team. Complete includes four sessions and approximately 24 hours. What goes live is your system - your pipelines, your automations, your reporting - not a template with your logo on it.
- The integrations are wired in, not listed. Your proposal software (OpenSolar or Pylon), your job management platform (Simpro, AroFlo or ServiceM8), your lead providers and your payments - connected by the people who built the integration layer, then tested against your live accounts.
- The AI team is trained on your business. Piper, Sarah and the rest of the agent roster are tuned to your offers, your pricing and your way of speaking to customers - not left as a generic bot with your name pasted in.
- Someone keeps it running. Support is identical in every package: a dedicated Slack channel, a video and guide library, and weekly group training. When an upstream tool changes something, it gets fixed before it costs you a lead, not after.
The incentive is the point. Every Pipereply package is a one-time setup plus a month-to-month subscription with no lock-in contract. That structure means the service has to keep earning its place every single month - which is exactly why we hold a 98% client retention rate. Nothing keeps a client on board except the system working.
SaaS and SWaS, side by side
| What happens | Typical SaaS | SWaS at Pipereply |
|---|---|---|
| Day one | A login email and a setup checklist | A kickoff session and a build plan |
| Integrations | A marketplace and the API docs | Wired to your live accounts by our team |
| AI | A generic assistant you configure | Agents trained on your offers and tone |
| When things drift | You notice, eventually, then raise a ticket | We monitor, tune and fix as part of the deal |
| The bet you are making | That someone in your team becomes the software person | That the system pays for its own management |
When plain SaaS is the right call
Honesty matters more than winning the comparison. Plain SaaS is genuinely the better fit if you enjoy building systems and have the hours to do it, if your workflow is simple enough that a template covers it, or if your volume is so small that a leaked lead here and there does not sting. A sole trader doing a handful of jobs a month, happy in the settings menu, does not need a built-for-you operating system - and we would rather tell you that on a Strategy Call than sell you one.
The equation flips the moment your business lives on enquiries, quotes and jobs moving between tools. Once a slow reply costs you real installs, once the same details are being typed into three systems, once quotes sit unchased because everyone is on the tools - the cheapest thing about your software stops being the subscription price.
What the difference feels like in practice
A lead lands at 9pm through your website. Under the SaaS deal, that lead waits for someone to remember to check the inbox tomorrow. Under SWaS, Piper has already answered it, qualified it and booked Thursday 4:15pm into your calendar - because the system was built, connected and switched on for you from day one. The quote that gets viewed twice on Saturday gets chased by Andy on Saturday, referencing the actual site-visit notes. The won job appears in your job management platform without anyone re-typing it. That is not a feature list. It is what "with a service" buys.
The full picture of what gets built, connected and managed lives on the Solar AI-Q platform page, and every package and price is published on the pricing page - because a model built on earning its keep monthly has nothing to hide. Results vary by business, but the pattern is consistent - a system that is actually built and actually managed gets actually used.