Project, request for a demonstration, or free trial?
Field team sizing: cost a contract before you sign
- 05/10/2026
- 09:37
Reading time : 5 min
CTO, Nomadia
A contract is due to be signed next week. Around the table: "we'll need three people per territory, so fifteen." Nobody knows whether that's true, and the mistake will eat into your margin for the entire life of the contract. Strategic Planning, a Field Service Management AI module available as an option in the major new version of Nomadia Field Service Management, replaces gut-feel estimates with a simulation run on your real operational data.
Contents
What is field team sizing?
Sizing field teams means working out how many technicians you need, with which skills and in which territories, to handle a given volume of jobs. Strategic Planning automates the exercise: the planned jobs are fed into the optimisation engine, which returns the capacity required based on your real operating history (observed durations, travel times, constraints).
Rule of thumb comes at the cost of your margins
Undersize a contract and you face penalties and overstretched teams; oversize it and you sacrifice margin from the day you sign. In between sit the in-house lookup table and the intuition of your longest-serving veteran: respectable methods, but indefensible in front of a client negotiating hard or a finance director making the call.
The engine in reverse: from jobs to resources
An optimisation engine is normally used to schedule with the resources you have. Strategic Planning runs it in reverse: you feed in the planned jobs (the volume of the contract under negotiation, or a simulated shift in activity) and it returns the capacity you actually need, by area and by skill. Based on your own operating history, not a market average. Costing a contract goes from around three days to one hour.
Estimates based on real pre-sales cases; accuracy depends on the depth of your operating history.
Key concept: The engine in reverse
Scheduling means spreading jobs across known resources. Sizing is the opposite: start from the jobs and let the engine say what resources you would need. Same engine, same constraints, question turned on its head, and an answer you can defend in the boardroom.
Annual preventive maintenance: coverable or not, and by how much
The same mechanics answer the question every operations director asks each autumn: can my teams cover next year's maintenance plan while keeping the necessary share of the schedule free for emergencies? The answer comes back territory by territory (coverable or not, and by how many full-time equivalents) before a preventive maintenance backlog has a chance to build up.
Recruit or train? Decided on data
When capacity falls short, the next question isn't "how many people" but "which skills, and where". The engine returns the missing certifications by territory and the volume to cover: the training plan and the hiring plan get sized instead of argued over, often revealing that the pressure comes from how people are distributed, not how many there are.
Use cases by sector
Anywhere the commitment comes before you know the workload:
- Maintenance under multi-year contracts: resources are costed before signing, not during delivery.
- Energy and utilities: large-scale preventive maintenance plans are tested against real capacity, territory by territory.
- Facility management: a multi-site tender response is sized site by site, skill by skill.
- Telecoms: area-by-area rollouts are smoothed over the year, with peaks anticipated.
- Healthcare and home services: patient growth is anticipated by area, with recruitment and training planned ahead.
How to evaluate a sizing tool
Four questions before you commit:
- Does the simulation draw on my real history, or on market benchmarks?
- Are results broken down by territory and by skill, or given as a global volume?
- Can you simulate a localised change (15% in a single region) and not just a national one?
- Is the share of capacity held back for emergencies configurable in the calculation?
Everything that happens after signing (scheduling, optimisation, monitoring) will never make up for a contract that was badly sized from the start. Costing before you commit, on your own data, is the one operational decision you make once and profit from for years. Strategic Planning makes possible a move that simply didn't exist before: it's available as an optional add-on, and its return is measured by the gap between planned sizing and reality.
Bring a contract you're negotiating right now: we'll run it through the engine during the demo.
Book a demo with a Nomadia expert
