Most growing service businesses pay for five or six software subscriptions and get real value from one of them. The rest are half-configured, half-adopted, and quietly billing a card nobody checks.
That is not a character flaw. It is what happens when a business grows by solving one problem at a time. You needed invoicing, so you bought an invoicing app. Then scheduling. Then a form builder because the website form was bad. Then a CRM because the spreadsheet broke. Each one was the right call on the day. Together they are a system nobody designed.
This is the expanded version of a post we published last year. It covers what the typical stack looks like, what it actually costs once you count time, how to audit it on one page, when consolidation into a single system makes sense, when off-the-shelf still wins, how to keep ownership of your data, and how to move without taking the business offline.
The typical stack
The usual six are a CRM, a scheduler, an invoicing tool, a form builder, an email platform, and a project or job-tracking tool. Almost every service business between three and thirty people has some version of this, and almost none of them chose it on purpose.
Here is how it tends to accumulate, using an invented example: a twelve-person landscaping and hardscape company in the Gold Coast.
- Year one: an invoicing app, because the accountant insisted. This is the one that gets used, because money depends on it.
- Year two: a scheduling tool so crews know where to be. Adopted by the office, resisted by the crews, who still get their day by text.
- Year three: a form builder, because the website's contact form sent inquiries into a void. Now inquiries land in an inbox instead of a void, which is better and still not good.
- Year three, later: an email marketing platform, set up by a freelancer for a spring promotion that ran once. The list has not been emailed since. The subscription continues.
- Year four: a CRM, bought after a lost quote nobody could find. Three of twelve people log into it. Quotes still live in the owner's email.
- Year five: a project tool, because the hardscape jobs got bigger and someone needed to track materials and stages. It works for the one person who set it up.
Six tools. One used fully. Two used partly. Three paid for and ignored. And none of them talk to each other, so the inquiry in the form tool is retyped into the CRM, the CRM quote is retyped into the invoicing app, and the schedule is a fourth copy of the same job.
Replace landscaping with electrical, cleaning, physio, a design studio or a regional logistics firm and the picture barely changes. The named products change by country and trade. The shape does not.
The real cost, including time
The subscription line on your card statement is the smallest part of the cost. The larger parts are the time spent retyping between tools, the decisions made on incomplete information because the data is split across six places, and the leads and invoices that fall between them.
Start with the obvious number. Six tools at somewhere between US$30 and US$150 a month each, plus per-user fees that climb as you hire, lands most small businesses somewhere between US$300 and US$1,000 a month before anyone counts the add-ons. That is US$3,600 to US$12,000 a year, for a stack where three of the six are unused.
For context on how common this is at the top end: Zylo's 2025 SaaS Management Index, which draws on more than 40 million licenses and US$40 billion of software spend under its management, reports that the organizations it covers waste an average of US$21 million a year on unused licenses (Zylo, January 2025). Those are large enterprises and the figure is theirs, not yours. We mention it because the pattern of paying for seats nobody uses holds at every size, and it is worth knowing it is not just you.
Now the number that matters more. Count the retyping.
If the office person spends 20 minutes a day moving inquiries from the form tool into the CRM, 30 minutes turning CRM quotes into invoices, and 20 minutes updating the schedule from the job list, that is over an hour a day, or roughly 25 hours a month. At any realistic loaded hourly cost, that is more than the subscriptions. And it is only one person. Add the crew lead who re-enters job notes, the owner who reconciles at month end, and the bookkeeper who chases the gaps.
Then count the errors. Every retyping is a chance for a wrong address, a wrong price, a job scheduled for the wrong day. Every one of those costs a phone call, a drive, a credit note or an apology.
Then count what you cannot see. With data in six places, you cannot answer simple questions without a spreadsheet exercise: which service is most profitable, which inquiry source actually converts, which customers are overdue and also due for a repeat visit. You run the business on feel because the facts are scattered.
That last cost is the one owners underestimate most, and it is the one that compounds as you grow.
The one-page software audit
You can audit your stack in an afternoon on a single page. List every tool, what it was bought to do, who actually uses it, what it costs, where its data lives, and whether it talks to anything else. The result is almost always clear enough to act on without further analysis.
Here is the format. One row per tool, six columns.
- Tool. The name and the plan you are on.
- Job. One sentence: what you bought it to do.
- Users. Who logs in at least weekly. Names, not roles.
- Cost. Monthly, including per-user fees and add-ons. Check the card statement, not your memory.
- Data. What lives only in this tool. Customer records, quotes, job history, invoices, email list, form submissions.
- Connections. What it is connected to, if anything, and whether the connection is a real integration or a person retyping.
Then add three questions at the bottom of the page.
- Which tool would hurt most if it vanished tomorrow? That is your core, and it is usually invoicing or scheduling.
- Which tools contain data that exists nowhere else? Those need an export before anything is cancelled.
- Which tools would nobody notice were gone? Cancel those this week. You will be surprised how many there are.
Most businesses finish the page with one tool they cannot live without, two they use partly, and two or three they can cancel immediately. That alone usually recovers a few hundred dollars a month. The bigger decision is what to do about the partly-used ones and the retyping between them.
If you want to know where you stand first, book a call and we will walk through your site, listings and search with you.
Consolidating into one system
Consolidation means replacing the partly-used tools and the retyping between them with one system where an inquiry becomes a quote becomes a job becomes an invoice without anyone re-entering it. The gain is not fewer logins. It is one record per customer that everyone works from.
The test for whether you need it is simple: draw the path of one job from first inquiry to paid invoice and count the tools and the retypings. If the answer is more than two tools and more than one manual handoff, you are a candidate.
What a consolidated system looks like for a service business:
- Inquiries from every channel (form, phone, Business Profile, email, WhatsApp) land in one place as lead records.
- A lead becomes a quote with one click, using your price list.
- An accepted quote becomes a job with a schedule slot, a crew, and a materials list.
- The job generates the invoice when it is marked complete, and the invoice syncs to your accounting package.
- The customer sees all of this in a portal: their quote, their appointment, their invoice, their history.
- Every stage has a timestamp, so you can finally answer "how long do quotes sit before they are accepted" and "which crew finishes on time."
That is one system doing the work of a form builder, a CRM, a scheduler, a project tool, and the customer-facing half of invoicing. The accounting package usually stays, because tax and payroll are a specialist job and the integration is well-trodden.
The common mistake is to try to consolidate by buying a seventh tool that promises to do everything. Sometimes that works. Often it becomes a seventh thing that three people use. The difference between a tool and a system is whether it was shaped to your process or whether your process was shaped to it.
When buying off-the-shelf beats building
Buy off-the-shelf when your process is standard, your team is small, and the tool's default workflow is close to how you already work. Build when the workflow is the business, the off-the-shelf tool makes you do things its way, or the per-seat pricing is punishing you for growing.
We build systems for a living and we still tell a meaningful share of businesses to buy instead. Here is how we decide.
Buy when:
- Your process matches a well-served category. A single-chair barbershop should use a booking app. A freelance designer should use an off-the-shelf invoicing tool. The category tools are good and cheap because thousands of near-identical businesses use them.
- You have fewer than five staff and nobody in the office. The overhead of a custom system is not worth it until there is enough volume for retyping to hurt.
- You are not sure yet what your process is. A new business should use cheap tools for a year and learn what it actually needs before committing to a build.
- The tool's export is clean and complete. If you can get everything out in a usable format whenever you want, the risk of buying is low.
Build when:
- Your workflow is unusual enough that every off-the-shelf tool makes you compromise. Multi-stage jobs with deposits, subcontractors and inspections. Service areas that change by season. Pricing that depends on three variables the tool only has a field for one of.
- You are paying per seat and growing. Ten seats on three tools at US$40 each is US$1,200 a month and rising. A built system has no per-seat tax.
- The customer experience is the differentiator. If a portal where clients see their job, approve changes and pay is part of why people choose you, you want to own it.
- You have tried the seventh tool and it became the seventh unused subscription.
There is a middle path, which is to build a system on a proven architecture rather than from a blank page. That is what we do with Ørigin 1.0, and it is why a Command System build is a 45-day project inside Mission ALPHA or BRAVO rather than a year-long software project. The architecture (leads, quotes, jobs, schedule, invoices, portal, automation rules) is already built and tested. The shaping to your business is the work.
Data ownership and export
You should be able to export every customer record, quote, job, invoice and message from any tool you use, in a format another system can read, without asking permission. If you cannot, you do not own your data; you rent access to it, and the rent goes up when you try to leave.
This is the question most businesses never ask until the day they want to switch. Then they discover that the CRM exports contacts but not the notes, the scheduler exports upcoming jobs but not history, the form builder exports submissions as a PDF, and the email platform will give you the list but not the engagement data that made the list useful.
Before you buy anything, and certainly before you build, ask:
- Can I export everything, not just contacts? Every object: leads, quotes, jobs, invoices, messages, attachments, timestamps.
- In what format? CSV or JSON with a documented structure is fine. A PDF is not an export.
- Can I do it myself, any time, from the interface? Or do I have to email support and wait?
- Is there an API? Not because you will use it tomorrow, but because the next system will need to pull from it during migration.
- What happens to my data when I cancel? Some vendors delete it within 30 days. Know that before you stop paying.
Note that the data protection laws most countries now have give individuals rights over their own personal data, but they do not give a business a general right to bulk-export its operational records from a vendor. Your export rights are whatever the contract says. Read the contract.
For anything we build, the rule is simple. The system runs on infrastructure you control or can take with you, the database is yours, and a complete export is a button, not a request. We describe how that works for the Command System in Custom CRM and ERP for home service businesses. If a vendor cannot give you an equivalent answer in one sentence, that is the answer.
Migrating without downtime
You migrate without downtime by running the old and new systems side by side for a short, defined period, moving history first and live work second, and cutting over one process at a time rather than all at once. The business should never have a day where it cannot quote, schedule or invoice.
The order we use:
1. Export and clean
Export everything from every tool, before anything is cancelled. Then clean it: merge duplicate customers, standardize addresses and phone formats, archive customers you have not worked with in three years into a separate file rather than importing them. This is the step businesses skip, and it is why migrations drag. Dirty data in the old system becomes dirty data in the new one, now with more confidence.
2. Import history into the new system
Customers, past jobs, past invoices, notes. Verify a sample by hand: pick twenty customers and check that their history looks right in the new system. If it does not, fix the import before going further.
3. Run both for two weeks
New inquiries go into the new system. Existing open jobs stay in the old one until they close. Staff use both, which is annoying for two weeks and far less annoying than a hard cutover that loses a job mid-flight.
4. Cut over one process at a time
Inquiries and quotes first, because they are the top of the funnel and the easiest to verify. Then scheduling. Then invoicing, which is last because it touches the accountant and the bank. Each cutover gets a week to settle before the next.
5. Freeze the old tools, then cancel
Set the old tools to read-only (or just stop entering anything new) for 30 days. If nobody needs to look something up in that time, cancel. Keep the final export somewhere safe regardless.
If the migration includes a new website on a new domain or new URLs, the same principle applies to search: map every old URL to its new one with redirects, keep the old domain until the new one is fully indexed, and use Google's documented process for a move (How to move a site, Google Search Central). A business that loses its rankings during a migration has lost something that took years to build, and it usually happens because nobody mapped the URLs.
Two more rules that save grief. Migrate in a quiet period, not the week before your busiest season. And name one person who owns the migration end to end, with the authority to pause it. Migrations with no owner stall at step three and leave the business running two systems indefinitely, which is the worst outcome of all.
What we build on Ørigin 1.0
Ørigin 1.0 is the architecture under every Command System we deliver: a single system that handles leads, quotes, jobs, scheduling, invoicing and a client portal, with automation rules shaped to the business and a database the business owns. It replaces the typical six-tool stack with one, and it is built in weeks rather than months because the core is already proven.
What a Command System includes as standard:
- A CRM with every inquiry channel feeding one lead list, with timestamps and owners.
- Quoting from a price list, with approval by the customer in the portal.
- Jobs and scheduling, with crews, materials and stages.
- Invoicing that syncs to your accounting package, which stays.
- A client portal where customers see their quotes, appointments, invoices and history, and message you in one place.
- Automation rules: acknowledgement on new inquiries, escalation on untouched leads, quote follow-ups, review requests after completion. The follow-up part is covered in detail in The follow-up gap.
- Reporting you can read without a spreadsheet: conversion by source, time in each stage, revenue by service, overdue invoices.
- Full export, any time, from the interface.
What it does not try to be: an accounting package, a payroll system, or a marketing automation platform. Those categories are well served and the integrations are mature. Consolidation means fewer systems, not one system that does everything badly.
For businesses rebuilding their whole presence, the Command System comes inside Mission ALPHA with the website, operations automation, brand kit, listings and demo video. For businesses that only need the website and the system, that is Mission BRAVO. After launch, HyperCare+ keeps the web presence managed runs it with you every month, done for you or by you, so the six-tool problem does not quietly rebuild itself.
What to do this quarter
Do the one-page audit this week, cancel what nobody uses, export what matters, and decide whether the retyping between the rest is a problem worth solving properly.
- Fill in the one-page audit. Every tool, one row. Use the card statement for costs, not memory.
- Cancel the tools nobody would notice. Export their data first, even if you think it is worthless.
- Draw the path of one job from inquiry to paid invoice. Count the tools and the manual handoffs. Put an hourly figure on the retyping.
- Check the export on each tool you are keeping. If you cannot get a complete export yourself from the interface, note it as a risk.
- Decide. If the path has two tools and no retyping, you are fine; stop here. If it has four tools and three handoffs, you are paying for a system in time that you could own in software. Talk to someone who builds them, or read the Systems page to see how we think about it.
The six-apps problem is not that you bought the wrong tools. It is that nobody was ever asked to design the whole. Once someone does, the subscriptions you actually need turn out to be fewer, and the one that matters turns out to be the one that holds everything together.
Si esto describe tu negocio, una llamada te mostrará qué parte te está costando más.
