Field service software: what you are buying, and when you outgrow a calendar

Worth saying at the top: CodeWords is an automation platform, so this article has an interest in the answer. What follows tries to be useful anyway, including about where a full field service platform is the right purchase and where nothing we make would be.

The question "is this software overkill?" is usually asked about price and is really about fit. A platform built for a company with a dispatch office, twenty vans and a call centre will not feel wrong to a sole trader because it costs too much. It will feel wrong because two thirds of it describes a business they do not run.

What we'll cover

• What a field service platform is actually for
• The costs nobody puts in the comparison
• What one person actually needs
• The signals you have outgrown a calendar
• Building it with CodeWords
• Where a full platform is genuinely the right answer
• Where a lighter setup wins
• The questions to ask any vendor
• Leaving, which is the part to check first
• Making it survive
• Limits worth knowing about
• What to do first
• Frequently asked questions

What a field service platform is actually for

The large platforms solve a coordination problem that appears at a particular size.

Allocating work across people. Who goes where, with which skills, in which order. With one technician this is a list. With fifteen it is a genuine optimisation problem.

Keeping a dispatcher and the field in sync. Somebody in an office needs to know where everyone is without ringing them. That role does not exist in a one-van business.

Standardising work across technicians. Forms, checklists, pricing books, so the newest person does the job the same way as the most experienced. Irrelevant when there is one person.

Reporting for management decisions. Technician-level margin, job-type profitability, conversion by salesperson. Useful when somebody's job is to look at it.

None of that is wasted functionality. It is functionality for a business with staff to coordinate, and a sole trader buying it is paying for the coordination of a team they do not employ.

The costs nobody puts in the comparison

Several vendors in this space do not publish pricing, which makes comparison difficult and is itself informative: software that has to be quoted is usually software sold with an implementation attached.

The subscription is rarely the whole figure. Ask about setup and data migration, per-user pricing as you add anybody, minimum contract terms, payment processing if it is bundled, and whether the modules you actually want are in the tier you were quoted.

Then count the costs that never appear on an invoice.

Learning it. Evenings, and there is only one of you.

Entering your history. Customers, equipment, pricing. The unglamorous week that determines whether the thing works at all.

The parts you will not use. Complexity has an ongoing cost even when ignored, because it is in every screen.

Getting out. Dealt with below, and it is the one people skip.

What one person actually needs

Strip it back and the list is short.

A diary you trust, that you can see on a phone with no signal in a plant room.

Customer and equipment history. What you did last time, on which machine, and what you charged.

A quote that goes out the same day, because the ones that wait until the evening frequently do not go at all.

An invoice you can issue from the doorstep, with a way to take payment there.

Something that answers enquiries when your hands are full, and collects enough to triage later.

Reminders that happen without you remembering.

That set is achievable in a general calendar, a decent invoicing tool and a messaging automation, for a small fraction of a platform subscription. It is also perfectly achievable inside a proper field service platform, which is the honest point: the capability is not the differentiator at this size, the fit is.

The signals you have outgrown a calendar

Not about revenue. Four things, and when two appear the calendar is done.

Somebody other than you allocates work. The moment a second person needs to see and change the schedule, shared visibility stops being optional.

You cannot answer "what did we do for them last time?" without searching a thread. That is a history problem, and history is the thing loose setups handle worst.

Jobs are getting lost. Parts on order, quotes unchased, second visits never booked. An invisible pile of open work is the clearest signal there is.

You are reconstructing invoices from memory. If what happened on site is not captured on site, the billing is already leaking.

Revenue, van count and customer count are all poor signals by comparison. Plenty of one-person businesses turn over a great deal on a calendar and a notebook, perfectly well.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: what happens to an enquiry, what gets booked automatically, what is held for you, and which reminders fire.
3. Authorize the connections to whatever you already use, which for most sole traders is a calendar, an invoicing tool and a messaging account. There is no requirement to adopt a new system of record.
4. Describe the exceptions: emergencies, jobs you do not take, areas you do not cover, anything needing a price you have not set.
5. Run it for a month before deciding whether the gap you were trying to fill was a software gap at all.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Where a full platform is genuinely the right answer

Worth stating clearly rather than dismissing the category.

Several technicians whose days need coordinating. This is the core problem those systems solve and they solve it well.

Contract and maintenance work at volume. Recurring visits, asset registers, service histories across hundreds of sites. Assembling that from parts is miserable.

Compliance-heavy trades needing standard forms and certificates produced consistently by different people.

Commercial clients demanding portals, SLAs and structured reporting. If your customers require it, that requirement decides the question.

A business being prepared for sale. Clean, systemised records in one place are worth real money at that point.

If two or more of those describe you, the platform is not overkill. It is the tool for the job and the subscription is the smaller part of the decision.

Where a lighter setup wins

One or two people, where coordination is a conversation rather than a system.

Mostly reactive domestic work, which is short, varied and hard to standardise.

A strong preference for your existing tools. Replacing a diary that works is a cost, not a benefit.

Wanting one specific thing automated, usually enquiry handling or reminders, rather than a whole operating system.

No appetite for a migration. Entirely legitimate. The best system is the one that gets used.

The questions to ask any vendor

What does it cost in year one, everything included? Subscription, setup, migration, training, payment processing.

What happens when I add somebody?

Can I export everything, in a usable format, whenever I want?

What is the minimum term, and what happens at renewal?

Which of the features I was shown are in the tier I was quoted?

Who actually uses it at my size? Ask for a reference from a business your size, not their flagship customer.

Leaving, which is the part to check first

Nobody evaluates software on how easy it is to stop using, which is why so many businesses stay on something that no longer fits.

Ask before signing: can you export customers, job history, quotes, invoices and equipment records, in a format another system can read, without paying for the privilege. If the answer is vague, that is the answer.

The question matters most for the data you cannot recreate. Pricing can be retyped. Ten years of what you did on which boiler at which address cannot.

Making it survive

Write down your requirements before any demo, or you will be sold somebody else's.

Price year one in full, not the monthly headline.

Check the export route before signing.

Give it a trial with real jobs, not a sandbox.

Revisit annually, because the right answer at two vans differs from the right answer at six.

Limits worth knowing about

No software adds capacity. A full diary is a staffing question.

Migration always takes longer than quoted, and the quote is usually the vendor's.

A tool nobody uses is worse than no tool, because the data is now split in two.

Integrations break. Anything stitched together needs somebody to notice when it stops.

Cheaper is not automatically right. If you are losing jobs for lack of coordination, a subscription is not the expensive part.

What to do first

Write down the five things you actually need, before looking at anything. Most people discover two of the five are not software problems at all: they are a pricing decision and a habit.

Two habits make the difference. Judge the fit by whether you have outgrown a calendar rather than by revenue, since the signals are about coordination and visibility and not about size. And check how you would leave before you decide how you would join, because the history you cannot recreate is the thing that ends up holding you in place.

Frequently asked questions

Is a full field service platform overkill for a sole trader?

Usually a poor fit rather than an expensive one. Much of what those platforms do is coordinate work across several technicians, which is not a problem one person has.

What does field service software actually cost?

More than the headline, and several vendors do not publish figures at all. Ask for a full year-one number including setup, migration, per-user pricing, minimum term and payment processing.

What does a one-person business genuinely need?

A diary you trust on a phone, customer and equipment history, same-day quotes, doorstep invoicing with payment, something that answers enquiries when your hands are full, and reminders that fire without you.

How do I know I have outgrown a calendar?

Somebody else allocates work, you cannot answer what you did for a customer last time without searching a thread, jobs are getting lost, or invoices are being reconstructed from memory. Two of those and it is time.

Is revenue a good signal?

No. Plenty of one-person businesses turn over a great deal on a calendar and a notebook. The signals are about coordination and visibility.

When is a full platform the right purchase?

Several technicians to coordinate, contract and maintenance work at volume, compliance-heavy trades needing consistent certificates, commercial clients demanding portals and reporting, or a business being prepared for sale.

What should I ask a vendor before signing?

Full year-one cost, what happens when you add a user, whether you can export everything freely, the minimum term and renewal behaviour, which features are in your tier, and for a reference at your size.

Why does the export question matter?

Because the data you cannot recreate is what keeps you on a system that no longer fits. Pricing can be retyped; years of equipment history at particular addresses cannot.

Can I keep the tools I already use?

Often, yes. Automation can sit on top of a calendar and an invoicing tool without replacing either, which suits people who have no appetite for a migration.

What is the most common mistake?

Choosing after the demos rather than before. Write your five requirements down first, and expect to find that two of them are a pricing decision and a habit rather than a software gap.

Related reading

• Dispatch, routes and arrival windows
• The jobs that are not finished
• Setting up as a regulated trade