Key takeaways
- Map the stack to the life of a job: call, book, dispatch, work, invoice, pay, review, follow up.
- Most shops are small: about 77% of plumbing, heating and AC establishments had fewer than 10 employees in 2023[1], so a lean stack is the norm.
- Field-service software is the hub; phones, accounting, payments and texting should connect to it with one customer record.
- Security is part of the stack: multi-factor authentication, a password manager and named logins for everyone.
Start from the job, not the software
Plumbing software is sold by category: field-service management, CRM, accounting, phones, marketing. That makes it easy to buy tools one at a time and end up with five systems that do not talk to each other. A better starting point is the life of a single job, because every system you own should serve one or more steps in it:
- A customer calls, texts, chats or fills in a form.
- Someone books the job or routes an emergency.
- Dispatch assigns a tech and a truck.
- The tech does the work, records notes and photos, and presents options.
- The customer approves an estimate or the work, and signs off.
- The office invoices and takes payment.
- The job hits the books.
- The customer is asked for a review and offered maintenance.
For each step, ask: which system holds the information, who enters it, and where does it go next? Gaps and double entry show up quickly.
The core systems and what each does
| System | Main job | Connects to | Usual owner |
|---|---|---|---|
| Phone system | Business numbers, routing, recording, call records | Field-service software, AI call handling | Office manager |
| AI call handling | Answers, takes job details, books routine work, routes urgent calls | Phone system, schedule, inbox | Office manager |
| Field-service software | Customers, scheduling, dispatch, estimates, invoices | Almost everything | Operations manager |
| Accounting | Books, payroll, taxes, reports | Field-service software, bank, payments | Bookkeeper |
| Payments | Card and bank payments, deposits, financing | Field-service software, accounting | Bookkeeper |
| Texting and email | Confirmations, updates, two-way messages | Field-service software, phones | Office manager |
| Website and listings | Bookings, chat, reviews, local search | Field-service software, review tools | Owner or marketing lead |
| File storage | Photos, permits, warranties, policies | Field-service software | Office manager |
| Security tools | Password manager, multi-factor authentication, device management | Every system | Owner |
Field-service software is the hub
In most plumbing companies, the field-service platform holds the customer record, the schedule, the job history, estimates and invoices. Everything else should feed it or draw from it. When you choose or review other tools, the first question is whether they connect to it reliably. Our comparison of field-service software for plumbers covers the platforms and what to test.
Keep one customer record. If the phone system, texting tool and accounting package each create their own version of the customer, someone will spend hours reconciling them, and customers will be asked the same questions twice.
Phones and intake
The phone system is still where most plumbing revenue starts. It should give you business numbers that stay with the company, routing for business hours and after hours, call recording with a proper notice, and call records you can export. Intake channels around it include website forms, chat and texting; each should land in the same queue.
AI call handling sits on top of the phone system. Ava, for example, answers calls in your business name, takes down the job, books routine work into a tested schedule, reaches the on-call tech and sends a summary with the recording to your inbox; direct connections to field-service platforms are Planned, so today booked work is copied across from that summary.
Money: accounting and payments
Invoices created in field-service software should flow into accounting without retyping, and payments taken in the field should match to those invoices automatically. Test the sync with a handful of jobs each month, including a refund and a partial payment, because those are the cases integrations get wrong. Keep payment card data out of every other system: no card numbers in job notes, emails or call summaries.
Sizing the stack to the shop
Most plumbing businesses are small. About 58% of plumbing, heating and air-conditioning contractor establishments had fewer than 5 employees in 2023, about 77% had fewer than 10 and about 89% had fewer than 20[1]. Enterprise-grade stacks built for 50-truck operations often cost more in setup and attention than a small shop can give them.
- One to four people: a field-service app with scheduling and invoicing, accounting software, card payments, a business phone number with call recording, a password manager.
- Five to ten: add dispatch features, two-way texting, after-hours call handling, review requests and basic reporting.
- Ten to twenty and beyond: add membership management, inventory, a phone system with routing and reporting, device management for tech phones and tablets, and defined owners for each system.
Small businesses expect to keep adding tools: 84% plan to increase their use of technology platforms[2]. That makes it more important, not less, to decide what each tool is for before buying the next one.
Where AI fits
AI is arriving in two ways: as separate tools, such as AI call handling, and as features inside software you already own, such as estimate drafting in a field-service app or transaction categorizing in accounting software. In the Census Bureau's October 2026 survey, 24.2% of US businesses said they used AI in a business function[3]. Treat each AI feature like any other system: know what it does, who checks its output, and where its data goes.
Security belongs in the stack
- Multi-factor authentication on email, field-service software, accounting, payments and the phone system.
- A password manager, with shared passwords kept in it rather than on sticky notes.
- Named logins for every person; never one shared office account.
- Device management or at least screen locks and remote wipe on tech phones and tablets; 91% of US adults own a smartphone[4], and most techs carry customer data on theirs.
- A written list of who has admin access to each system, reviewed when anyone leaves.
Buying principles for every new tool
Before adding anything to the stack, run it through the same short set of tests. They take ten minutes and prevent most regrets:
- It solves a problem you can name and measure, at a specific step in the job.
- It connects to your field-service software, or you have accepted the cost of not connecting.
- You can export your data in a usable format at any time, including after you cancel.
- It supports named logins, roles and multi-factor authentication.
- The vendor can tell you which features are live today and which are planned.
- Someone in the business has agreed to own it, including setup, training and reviewing whether it is still needed.
- You have tried it on real jobs, with real staff, before committing to a long contract.
Own your data, whatever you buy
Software changes; your customer history should not disappear with it. Keep a quarterly export of the records that matter most: customers and service addresses, job history with notes, equipment installed and warranty dates, open estimates, and memberships. Store it somewhere you control, protected like any other sensitive file. If a vendor is acquired, raises prices sharply or shuts down, that export is what lets you move without losing years of service history. It is also useful for reporting, because you can analyze it without the limits of the software's own reports.
Audit your stack in an afternoon
List every system
Include free tools and personal accounts staff use for work.
Map each to job steps
Write which step of the job each system serves. Anything that serves no step is a candidate to cancel.
Find double entry
Ask the office where they type the same information twice. Each answer is a missing or broken connection.
Check owners and access
Name an owner for each system and check who has admin rights.
Prioritize one fix
Choose the single change that removes the most double entry or risk, and do that first.
Example: a six-person shop's map
Example: a shop with four techs and two office staff lists eleven tools. Mapping them to job steps shows two texting tools doing the same job, a scheduling spreadsheet duplicating the field-service calendar, and after-hours calls going to the owner's cell with no record. The owner cancels one texting tool, retires the spreadsheet, adds AI after-hours call handling that sends summaries to the office inbox, and turns on multi-factor authentication everywhere. The office estimates it has removed about an hour a day of retyping.
Frequently asked questions
What software does a plumbing company need?
At minimum: field-service software for scheduling and invoicing, accounting, card payments, a business phone system and a password manager. Add texting, after-hours call handling and reporting as you grow.
Should everything connect to the field-service software?
Ideally, yes. It usually holds the customer record, schedule and invoices, so other systems should feed or draw from it to avoid double entry.
How often should we review our tech stack?
Once a year, and whenever you add a system or someone with admin access leaves.
Where does AI fit in?
Most often in call handling and as features inside existing software. Treat each AI feature like any system: clear purpose, a person who checks output and known data handling.
References
U.S. Census Bureau (2023). County Business Patterns 2023, U.S. national file (cbp23us) (opens in a new tab) โ
U.S. Chamber of Commerce Technology Engagement Center (2025). Empowering Small Business: The Impact of Technology on U.S. Small Business (2025) (opens in a new tab) โ
U.S. Census Bureau (2026). Business Trends and Outlook Survey (BTOS), national response estimates (opens in a new tab) โ
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) โ