Field service software: what you are buying, and when you outgrow a calendar
A candid look at what platforms like ServiceTitan are actually for, the costs nobody quotes, and the signals that you have outgrown a spreadsheet.
On this page
- What we'll cover
- Key takeaways
- 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
- Related reading
Yes, for most sole repair technicians a full field service platform such as ServiceTitan is a poor fit, and the reason is fit, not price. A platform built for a company with a dispatch office, twenty vans and a call centre mostly describes a business a sole trader does not run.
CodeWords is an automation platform, so this article has an interest in the answer. It also covers where a full field service platform is the right purchase and where nothing we make would be.
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
Key takeaways
- A full field service platform mainly solves the problem of coordinating several technicians, which one person does not have.
- Count year-one cost in full: subscription, setup, data migration, training and payment processing.
- A sole trader needs six things: a trusted diary, job history, same-day quotes, doorstep invoicing, enquiry handling and reminders.
- Two signals show you have outgrown a calendar: somebody else allocates work, or jobs are getting lost.
- Check how you can export your data before you sign anything.
What a field service platform is actually for
Field service platforms exist to coordinate work across several people, a problem that appears at a particular business 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
The full cost of a field service platform is more than the subscription. Several vendors in this space do not publish pricing, which makes comparison difficult, and software that has to be quoted is usually sold with an implementation attached.
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
A sole trader needs six things from field service software.
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 quotes that wait until the evening often do not go out 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.
A general calendar, an invoicing tool and a messaging automation can cover these six needs for a small fraction of a platform subscription. A field service platform can cover them too, so at this size fit decides the choice, not capability.
The signals you have outgrown a calendar
You have outgrown a calendar when two of four signals appear. Revenue is not one of them.
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, billing is already leaking.
Revenue, van count and customer count are all poor signals by comparison. Some one-person businesses run a large turnover on a calendar and a notebook.
Building it with CodeWords
CodeWords connects to 3,000+ integrations (CodeWords, 2026), and each connection is made once and reused.
- Open CodeWords and start a new automation.
- 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.
- Authorize the connections to whatever you already use, which for most sole traders is a calendar, an invoicing tool and a messaging account. You do not need to adopt a new system of record.
- Describe the exceptions: emergencies, jobs you do not take, areas you do not cover, anything needing a price you have not set.
- 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 ($0) covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026); details are on the pricing page.
Where a full platform is genuinely the right answer
A full platform is the right answer in five situations.
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 these describe you, the platform is not overkill. It is the right tool, and the subscription is the smaller part of the decision.
Where a lighter setup wins
A lighter setup wins in five situations.
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
Check the export route before you sign. Few people evaluate software on how easy it is to stop using, so many businesses stay on a system that no longer fits.
Ask before signing whether you can export customers, job history, quotes, invoices and equipment records in a format another system can read, without paying extra. A vague answer means you cannot.
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 takes longer than the vendor's quote.
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, the subscription is not the expensive part.
What to do first
Write down the five things you need before looking at any product. Some of the five will turn out not to be software problems: they are a pricing decision or a habit.
Then judge fit by whether you have outgrown a calendar, not by revenue, because the signals are about coordination and visibility. And check how you would leave before you decide to join, because history you cannot recreate is what holds you in place.
Frequently asked questions
Is a full field service platform overkill for a sole trader?
Yes, a full field service platform is usually overkill for a sole trader, as a poor fit more than an expensive one. Much of what these platforms do is coordinate work across several technicians, which is not a problem one person has. A calendar, invoicing tool and messaging automation can cover the essentials.
What does field service software actually cost?
Field service software costs more than the headline subscription, and several vendors do not publish figures at all. Ask each vendor for a full year-one number that includes setup, migration, per-user pricing, minimum term and payment processing, so you can compare offers on the same basis.
What does a one-person business genuinely need?
A one-person business needs six things: a diary you trust on a phone, customer and equipment history, same-day quotes, doorstep invoicing with payment, an automated reply for enquiries when your hands are full, and reminders that fire without you. None of these requires a full platform.
How do I know I have outgrown a calendar?
You have outgrown a calendar when two of four signals appear: somebody else allocates work, you cannot recall what you did for a customer last time without searching a thread, jobs are getting lost, or you reconstruct invoices from memory. Any two together mean it is time to change.
Is revenue a good signal?
No, revenue is a poor signal. Some one-person businesses run a large turnover on a calendar and a notebook. The better signals are about coordination and visibility: whether others need to see the schedule, whether jobs get lost, and whether history is easy to find.
When is a full platform the right purchase?
A full platform is the right purchase in five cases: 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. Two or more of these make the subscription the smaller part of the decision.
What should I ask a vendor before signing?
Ask six things: the full year-one cost, what happens when you add a user, whether you can export everything freely, the minimum term and renewal terms, which features are in your quoted tier, and for a reference customer of your size. Written answers protect you later.
Why does the export question matter?
The export question matters because data you cannot recreate keeps you on a system that no longer fits. You can retype pricing, but you cannot rebuild years of equipment history at particular addresses. Confirm in writing that you can export customers, jobs, quotes, invoices and equipment records.
Can I keep the tools I already use?
Yes, in most cases you can keep your current tools. Automation can sit on top of a calendar and an invoicing tool without replacing either, which suits people who do not want a migration. CodeWords connects to the tools you already use through its integrations.
What is the most common mistake?
The most common mistake is choosing after the demos instead of before. Write your five requirements down first, then compare. Some requirements usually turn out to be a pricing decision or a habit, not a software gap.