Skip to content
Software for Trades

A long read

When to switch from spreadsheets to software.

Spreadsheets are the right answer for longer than vendors will admit. Here's how to know it's actually time to switch.

Why spreadsheets work better than they should

Software vendors will tell you spreadsheets are holding you back from day one. They're wrong about that, and they know it.

A two-tab Google Sheet — one for jobs, one for customers — runs a one-truck plumbing operation just fine. You can build a quote in five minutes, copy last week's numbers into this week's invoice template, and pull a rough P&L by sorting a column. The total cost is zero and the learning curve is whatever you already know.

I've seen electricians do $400K a year out of a single spreadsheet and a shared Google Calendar. I've also seen $1.2M HVAC shops drowning in three different SaaS subscriptions because they upgraded too early and never finished the rollout. The tool isn't the bottleneck until it actually is.

What spreadsheets get right:

  • They bend to your workflow instead of forcing you into someone else's
  • You can see everything on one screen
  • Nothing breaks when the internet is slow at a customer's house
  • There's no monthly fee eating into a slow February
  • Training a new admin takes 20 minutes, not two weeks

The trade-off is that spreadsheets don't scale past a certain operational complexity. They don't enforce process, they don't remind anyone to do anything, and they can't be in two places at once. The question isn't whether they'll break — it's when.

The four signals that say it's time to upgrade

Forget revenue thresholds. Some shops outgrow spreadsheets at $250K, others run lean to $1M+. The trigger is operational, not financial. Watch for these four signals.

Signal 1: You're losing money to scheduling friction.

If your dispatcher (or you, at 9 PM, with a beer) is spending more than 30 minutes a day shuffling jobs, you're past it. The specific tell: a tech finishes early, calls in, and you can't tell them what to do next without scrolling through three tabs and texting two people. That's $150 of windshield time you just lost.

Signal 2: Customers are slipping through cracks you can see.

Recall jobs not getting scheduled. Maintenance agreements that lapse without anyone noticing. Estimates sent and never followed up on. If you're saying "I meant to call them back" more than once a week, the spreadsheet has run out of memory — yours.

Signal 3: You can't answer basic questions in under a minute.

How much did we make on water heater installs last quarter? Which tech has the highest callback rate? What's our average revenue per service call? If those questions require an hour of pivot-table work, you're flying blind on decisions that matter.

Signal 4: Your techs are the bottleneck for paperwork.

When invoices go out two days after the job, you get paid two weeks later. When techs hand-write notes and someone retypes them, you're paying twice for the same work. If your AR aging report (you do have one, right?) shows more than 15% over 30 days, that's almost always a paperwork problem, not a customer problem.

One signal is a yellow light. Two means start shopping. Three or four means you're already losing more money to inefficiency than software would cost.

What you'll gain (and what you'll lose) by switching

Most articles about switching only cover the gains. That's how people end up disappointed three months in. Here's the full picture.

What you actually gain:

  • Time back on dispatch. A good scheduling system saves a working dispatcher 1-2 hours a day. Real number, not a marketing promise.
  • Faster invoicing. Techs collecting payment in the driveway means cash hits your account that night, not next Tuesday.
  • Customer history at the tech's fingertips. The tech knows it's a Carrier from 2017 before they knock on the door.
  • Automated follow-ups. Maintenance reminders, review requests, estimate follow-ups — the stuff that grows revenue but never gets done manually.
  • Real reporting. You'll find out which job types actually make money. This will surprise you and probably annoy you.

What you'll lose, and nobody will warn you about:

  • Flexibility. Your spreadsheet bends. Software doesn't. If your process is "we always do it this way except for Mrs. Henderson," software will fight you on the exception.
  • Speed on simple tasks. Booking a job that took 30 seconds on paper might take 90 seconds in software because there are required fields. Multiply that by 200 jobs a month.
  • Money. Plan on $80-200 per user per month for anything decent. A four-person shop is looking at $400-800/month plus payment processing fees.
  • A month of productivity. Anyone who tells you implementation is "easy" hasn't done it. Plan for 4-6 weeks where things are slower, not faster.
  • Some of your team. Not everyone makes the jump. I've watched two good techs quit over software rollouts because they hated using the app. Budget for that risk.

The math still works for most shops past the four-signal threshold. But go in knowing you're trading one set of problems for a different, smaller set of problems — not eliminating problems entirely.

Solo, small crew, scaling: the right move at each stage

Different shops need different answers. Here's what I tell people based on where they actually are.

Solo operator (just you, maybe a spouse helping with books)

Stay on spreadsheets longer than you think. Add a free or cheap CRM if customer follow-up is the weak spot — something like a $15/month tool that sends reminders. Skip the field-service platforms entirely until you hire your first tech.

The exception: if you're doing recurring service contracts (lawn care, pool service, pest control), get software earlier. Recurring billing and route optimization pay for themselves fast in those trades.

Small crew (2-5 techs)

This is the sweet spot for switching. You've got enough volume that scheduling and invoicing friction is real money, but you're small enough to actually finish a rollout in a quarter. Look for software priced per user, not flat-rate enterprise pricing.

At this stage, the goal is the boring stuff: scheduling, dispatching, invoicing, customer history, basic reporting. Don't pay for marketing automation, advanced analytics, or "AI-powered" anything. You won't use it and it'll distract from getting the basics right.

Scaling crew (6-15 techs, multiple service lines or locations)

You probably needed to switch nine months ago. At this size, the cost of staying on spreadsheets isn't just inefficiency — it's that you literally cannot see what's happening in your business in real time. You're managing by anecdote.

Budget for a real implementation: 2-3 months, possibly a part-time project lead, and a chunk of your own time you weren't planning to spend. The platforms that fit this size are pricier and more complex. The cheapest option is almost always the most expensive option because you'll outgrow it in 18 months and have to migrate again.

Past 15 techs

You're outside this article's scope. You need someone in your business looking at this full-time, not a buyer's guide.

How to migrate without losing a week of revenue

Migration is where most shops mess this up. They pick a Monday, flip the switch, and spend the next two weeks fielding panicked calls from techs who can't find anything. Don't do that.

Pick your slow season. Actually pick it.

If you're in HVAC in the Southeast, that's October or March, not July. Roofers, late winter. Landscapers, January. Trying to migrate during peak season is how shops lose real money — I've seen a roofing company drop $40K in lost bookings during a July rollout because the office couldn't keep up with calls.

Run parallel for two weeks minimum.

Keep the spreadsheet alive while the new system comes online. Yes, it's double work. Yes, you'll hate it. Do it anyway. The first time the new system has a sync issue or someone enters a customer wrong, you'll be glad the old system is still warm.

Migrate customers, not history.

Don't try to import five years of job history. Import your active customer list — names, addresses, phone numbers, equipment if you have it — and call it done. Old job history can stay in the spreadsheet for reference. Trying to clean and import 8,000 historical records is a six-week project that adds almost no operational value.

Train in the right order:

  1. Office/dispatch first, two weeks before techs go live
  2. Your best tech next, one week early, as a pilot
  3. The rest of the team on a single day, with the office and the pilot tech available to help
  4. The skeptic on the team last — pair them with the pilot tech, not with you

Set a real go-live date and a real fallback.

Pick a date. Tell everyone. If three days before go-live you're not ready, push it two weeks. Don't push it three days. Either you're ready or you're not, and a 72-hour delay just means people stop trusting the date.

Have a clear fallback plan: if the new system isn't working by end of week two, what's the trigger to roll back? Most shops never use the fallback, but having it written down keeps the panic level manageable.

Eat the cost of a slow week.

Plan to do 20-30% less work the first week. Block out the schedule, tell customers you're doing system upgrades and booking starts the following week. The shops that try to migrate at full capacity are the ones that lose techs and customers.

The mistakes most first-time buyers make

I've watched dozens of shops buy field-service software, and the failures cluster around the same five mistakes.

Buying on the demo, not on the daily use.

Demos are designed to look good. The salesperson knows exactly which buttons to click in which order. Your dispatcher on a Tuesday morning with three techs on hold and a customer yelling about a no-show does not. Before you buy, get a 14-day trial and have your actual office person use it for actual jobs. If they hate it on day three, they'll hate it on day 300.

Picking the platform with the most features.

You will use maybe 40% of any platform's features. The other 60% will clutter the interface and make every screen slower for your team. Match the tool to your workflow, not the other way around. A simpler platform that fits is worth more than a powerful one that doesn't.

Underestimating the integration tax.

Your software needs to talk to QuickBooks (or whatever you use). It needs to handle your payment processor. Maybe it needs to push to your phone system. Each integration is a place where things break. Ask the vendor to show you the actual integration working with your actual accounting setup before you sign. Not a screenshot. A live demo with your data.

Negotiating like it's a one-time purchase.

Software vendors are running an annuity, not selling you a truck. The list price is rarely the real price. Ask for an annual deal instead of monthly, ask for the implementation fee to be waived, ask what they'll do for a two-year commitment. Most vendors will move 15-25% on price if you push. They will not volunteer this.

Not assigning a project owner.

If "we" are rolling out the software, nobody is. Pick one person — you, your office manager, your lead tech — and make it their job. They get to make decisions, set deadlines, and tell other people they're behind. Without an owner, the rollout drags six months and never quite finishes.

Bonus mistake: switching too often.

If you're on your third platform in two years, the platform isn't the problem. Either your process isn't defined or you're chasing features that don't matter. Pick one, commit for 24 months, and make it work before you start shopping again.

What to do next

If you read this and recognized two or more of the four signals, you're ready to start shopping — not buying, shopping. Two concrete next steps:

  1. Spend an hour with your spreadsheet and your calendar. Write down every place you said "I meant to do that" or "I forgot" in the last 30 days. That list is your real requirements doc, more useful than any vendor checklist.
  1. Get trial accounts on two or three platforms in your trade. Don't watch demos — actually book three real jobs through each one this week. The one that feels least bad after a real workweek is probably your answer.

If you only recognized one signal, or none, stay where you are. Tighten up the spreadsheet, add a follow-up reminder system, and revisit this in six months. Switching too early costs more than switching too late, and the vendors selling you on urgency are the ones who get paid when you sign — not when it works.