Buying Guides

What to look for in field service software if you have 2–10 technicians

The features that matter when you have 2–10 technicians, the features you don't need yet, and how to avoid per-user pricing traps that punish you for growing.

By WorkOrderPro Team

The 2–10 technician range is the hardest range to manage in field service. You are too big for a WhatsApp group and a mental to-do list. You are too small to justify enterprise software that costs R5 000 a month and needs a dedicated implementation team.

Most software in this market is built for either the one-person sole trader or the 50-person fleet operation. If you are in the middle, you need to be deliberate about what you buy — and what you ignore.


Why this scale is different

One tech is simple: you are the tech. You know every job because you did every job.

Three techs adds coordination — who goes where, who has which parts, which jobs are running late. You are no longer doing the work; you are managing the people doing the work.

Ten techs adds a different kind of complexity: you cannot know the detail of every job. You need systems that surface problems to you rather than you finding them manually. You need to trust that jobs are being documented, quoted, and invoiced without you checking every one individually.

The software needs to change with you across that range. The wrong choice is buying a tool that works great at two techs and breaks down at eight.


Features that matter at this scale

Job dispatch with real visibility

At two or three techs, you can manage dispatch via WhatsApp and a phone call. At five or more, you need a visual system — something that shows you who is assigned to what, what time, and what the current status of each job is.

A dispatch board that updates in real time when a tech's job status changes is not a luxury at this scale — it is the difference between proactive management and reactive firefighting. When a job runs over, you need to see it and respond before it creates a cascade of late arrivals.

Basic list-view dispatch is enough to get started. As your team grows, a calendar view with drag-and-drop assignment and live GPS positions is what makes managing five-plus techs manageable without being on the phone constantly.

Mobile job cards that work offline

Your techs do not work in an office. They work in someone's ceiling, under a kitchen sink, or in a factory that loses signal every time the power cycles. The app they use on-site needs to work without a data connection.

"Works offline" means something specific: the job record, the photo storage, the time tracking, and the note-taking all happen locally on the device and sync when signal returns. It does not mean "loads faster on a good connection." It means the tech can complete a full job — including capturing photos, clocking out, and building a quote — without a single byte of data moving.

This matters everywhere in South Africa, but it matters most during load shedding, when mobile network towers and routers lose power and signal becomes unreliable.

Quote builder on mobile

At this scale, your techs are probably building quotes on-site. That might be a written quote on a paper job card, a WhatsApp voice note, or an informal verbal discussion that leads to a disputed invoice.

A mobile quote builder that pulls from your service catalog, builds line items, and gets the customer to approve by signing on the screen closes a huge gap. The quote is the same format every time, it is linked to the specific job card, and the approval is captured before the tech leaves the site.

This is not about looking fancy. It is about having a record that matches what was agreed, available to both you and the customer, without any manual re-entry.

Job photos with proper structure

A photo taken on a phone and shared to a WhatsApp group is not the same as a job photo. A job photo is linked to a specific job record, taken at a specific stage (arrival, work in progress, completion), and time-stamped and GPS-tagged automatically.

When a customer disputes a job three weeks later, a WhatsApp photo is almost useless — you have to find it, prove it was from that job, and explain when it was taken. A structured job photo is attached to the job card, labelled by stage, and carries its own evidence.

At this scale, you will have a customer dispute a job at some point. The question is whether you can resolve it in five minutes or in two weeks.

Auto-invoicing on job completion

Invoicing delays are a cash flow problem, not an admin problem. If your techs complete jobs and the invoices go out two days later because someone has to sit down and create them manually, you are carrying unnecessary receivables.

Software that auto-generates an invoice the moment a tech marks a job complete — and sends it to the customer via email and WhatsApp — removes that delay entirely. The customer gets the invoice while the job is still fresh. You get paid faster.


Features you do not need yet

Advanced SLA management

SLA (Service Level Agreement) tracking is essential for facilities management contractors who have contractual response times and need to document compliance. For a residential plumbing or electrical business serving individual homeowners, it adds complexity without benefit.

You do not need to measure your average response time to the minute if your customers are not contractually requiring it. If that changes as you win commercial contracts, revisit this.

Equipment registry

Tracking make, model, serial number, and service history for every piece of customer equipment is essential for HVAC businesses servicing commercial air conditioning units. For a plumber or electrician doing primarily repair work, it is overhead.

If more than 20% of your work involves servicing the same equipment repeatedly — the same air conditioner units at the same commercial client, the same CCTV cameras at the same property — then equipment tracking earns its keep. Otherwise, skip it for now.

API integration and custom development

Any software vendor that leads their pitch with API access is selling to a different customer. You do not need to integrate your job card software with a custom data warehouse at this scale. You need to dispatch jobs, capture photos, build quotes, and send invoices.

Look for software that does those four things well. The API is a feature for the future, not a selection criterion for a 5-tech operation.

Job costing and profitability analysis

Knowing which jobs are profitable and which are losing money is genuinely useful — but it requires you to first have consistent data on labour hours, parts usage, and quoted vs actual prices. Building that data discipline takes time.

Get the basics right first: consistent job documentation, accurate quoting, on-time invoicing. Once those are habits across the whole team, job costing makes sense. Bolting job costing onto an undisciplined job management process produces misleading numbers.


The pricing trap: per-user billing vs base + per-technician plans

This is the single most important pricing consideration for a 2–10 tech operation, and most buyers do not notice it until they are in the middle of it.

Per-user billing means you pay a fee for each technician on the platform. At R349 per user per month, a team of five techs costs R1 745/month. A team of eight costs R2 792/month. Every time you hire, your software bill goes up. That is a disincentive to grow, and it makes software feel like a tax on hiring.

Base + per-technician billing means you pay a fixed base fee for your plan tier plus a per-technician fee. When you grow from three techs to five, your base fee stays the same — only the per-tech portion increases. This keeps costs predictable and proportional to your team size.

When evaluating software, calculate the total monthly cost at your current team size and at the next likely team size. A tool that looks cheaper at three techs may cost significantly more at seven.

WorkOrderPro uses base + per-technician pricing: Starter at R999/mo base + R349/technician (up to 5 technicians, 250 work orders/month), Professional at R1 999/mo base + R499/technician (up to 25 technicians, 500 work orders/month), all excl. VAT. Your base fee stays fixed — costs scale proportionally with team size.


South Africa-specific requirements you cannot skip

ZAR pricing and a local payment gateway

Software priced in USD is a hidden cost. The USD/ZAR exchange rate means your monthly bill fluctuates even if the software price does not change. In a business where margins are tight, a R300 swing on your software subscription when the rand weakens is money you did not budget for.

PayFast is the standard SA payment gateway. Software that bills via PayFast in ZAR means no forex exposure, no international bank fees, and no declined payment when your bank flags an overseas transaction.

POPIA compliance

POPIA (the Protection of Personal Information Act) is South African data protection law. Your field service software holds customer data, GPS locations of your technicians, job site addresses, and potentially photos of people's homes and belongings.

Before you sign up for any platform, check: how do they handle GPS consent for technicians? How long do they retain GPS data? Can a customer request deletion of their data? Is data stored on South African or international servers?

These are not abstract compliance questions — the Information Regulator can impose significant penalties for POPIA non-compliance. Choose software that takes this seriously.

Full Android support

Approximately 85–90% of smartphones in South Africa run Android [ESTIMATE — based on general SA market data]. Software with an iOS-only full-featured mobile app is not fit for purpose in the SA market.

Before committing to any platform, confirm that the Android app has feature parity with iOS. Not a "lite" version, not a mobile web browser. A native Android app with full functionality.


How to evaluate before you commit

Most field service software offers a free trial. Use it properly: create a handful of real jobs, have one of your techs try the mobile app on their actual Android phone, and run through a real quote-and-invoice workflow. If the tech finds it confusing within ten minutes, the rest of your team will too.

The right software for a 5-tech plumbing business in Johannesburg and the right software for a 5-tech HVAC business in Cape Town may not be the same product. Understand your own job mix — whether you are mostly reactive repair callouts or mostly scheduled maintenance visits — and evaluate software against that reality.


Not sure where to start? WorkOrderPro is built for South African field service businesses with 2–25 technicians. Start your free 14-day trial — no credit card required — and see whether it fits how your team works.


Title Variations

  1. "What to look for in field service software if you have 2–10 technicians" (72 characters)
  2. "Field service software for small teams: what matters at 2–10 techs" (67 characters)
  3. "How to choose field service management software for a small SA business" (71 characters)
  4. "The honest buyer's guide to field service software for growing SA businesses" (76 characters)
  5. "Field service software for 2–10 techs: features that matter, features that don't" (81 characters)

Meta Description

The features that matter at 2–10 technicians, what you can skip, and how per-user pricing traps punish SA service businesses that grow. (136 characters)

Key Takeaways

  • Dispatch visibility, mobile offline capability, on-site quoting, structured job photos, and auto-invoicing are the non-negotiable features for a 2–10 tech operation.
  • SLA tracking, equipment registry, and API integration are features to revisit once your business has grown and the basics are under control.
  • Per-user pricing means your software bill goes up every time you hire. Base + per-technician plans keep your base fee fixed while costs scale proportionally.
  • Full Android support is mandatory in the SA market, where approximately 85–90% of smartphones run Android.
  • Test software with a real tech on their actual phone before committing — not just in a demo environment.

Internal Linking Suggestions

  • Anchor: "dispatch board", Target: /features/dispatch-board, Context: Supports the dispatch visibility section with a direct feature deep-dive.
  • Anchor: "works offline", Target: /features/mobile-app, Context: Links to the mobile app feature page which explains offline-first architecture.
  • Anchor: "base + per-technician pricing", Target: /pricing, Context: Natural link from the per-user vs base + per-technician pricing section.
  • Anchor: "best field service software in South Africa", Target: /compare/best-field-service-software-south-africa, Context: Gives readers a comparison resource for evaluating all options.
  • Anchor: "POPIA compliance", Target: /popia, Context: Supports the POPIA section with a dedicated policy page for readers who want detail.

FAQ Section

Q: What is the most important feature for a 5-technician field service business? A: Real-time dispatch visibility — knowing which tech is assigned to which job, at what time, and what the current job status is — matters more than any other feature at this scale. Without it, managing five techs requires constant phone calls, and jobs fall through the cracks when things run over schedule.

Q: Is per-user pricing bad for small field service businesses? A: Not inherently, but it creates a financial disincentive to hire. Every new technician increases your software bill. Base + per-technician plans (a fixed base fee plus a per-tech fee) keep the base cost fixed and make it easier to model costs as you grow.

Q: Do I need SLA tracking for a residential plumbing or electrical business? A: Probably not at this stage. SLA tracking is most valuable for businesses that have contractual response time commitments — facilities management contractors, commercial security companies, HVAC businesses on service contracts. For primarily residential repair work, the added complexity does not pay its way.

Q: Why does offline capability matter if my techs have mobile data? A: Load shedding, network congestion, and rural job sites all create connectivity gaps. An app that requires a data connection to function can leave a tech unable to complete a job card, capture photos, or build a quote. Offline-first means the app works regardless of connectivity and syncs when signal returns.

Q: How do I know if a field service app has full Android support? A: Download the Android app and test it yourself before signing up. Look specifically for: the ability to take and upload photos, build and send a quote, clock in and out, and view the full job detail. If any of those require the desktop or are limited in the Android version, look for a different product.

Ready to run your jobs on WorkOrderPro?

Start a free trial. No credit card required. Set up your first job card in under 10 minutes.