Insights · The thinking behind the architecture
What the architectural shift in field service actually looks like.
A series of articles on the move from job-led to contract-led service delivery, what "operating system" actually means in field service software, and why the architecture matters more than the AI features that get bolted on top of it. Written for operators who already feel the ceiling of job-led platforms — and the people advising them.
The articles
Six anchor articles. Two reserves.
In publication order — the cluster reads as a single argument from Article 01 through 06. The two reserves publish in Phase 2 amplification or as needed for sales air-cover.
The job is no longer the unit of work in field service.
Why contract-led service delivery is making job-led software architecturally obsolete.
By [CONFIRM AUTHOR — Jim or Subha]
What "operating system" actually means in field service software.
Most software is a tool. An operating system is a foundation. Here's the architectural difference.
By [CONFIRM AUTHOR — Subha]
The compliance regime that broke job-led software.
Gas Safe, F-Gas, BSA, SFG20, Legionella, asbestos, fire safety. The regulatory map for UK Hard FM.
By [CONFIRM AUTHOR — Subha + named compliance lead]
Why your contract is the unit of operation, not the job.
An operator's view: managing forty commercial contracts on software designed for one.
By [CONFIRM AUTHOR — Operator-led, ghost-written]
The personalisation problem in field service.
Service contractors win on personalisation. They lose margin trying to scale it. The architectural answer.
By [CONFIRM AUTHOR — Jim]
What persona activation actually looks like in field service operations.
Helpdesk, scheduler, contract manager, engineer, SDM. What changes for each role, day by day.
By [CONFIRM AUTHOR — Operations director with internal CSM voice]
In reserve
Two reserves for Phase 2 amplification.
Publishing as the cluster extends — or as sales air-cover requires.
The end customer's experience of an operating system.
What changes for building owners and FM clients when their contractor's software stops being a cost centre and starts being a service capability.
The audit that should never have been a project.
Why audit prep takes weeks — and what changes when compliance is woven into the architecture instead of bolted on as a module.