Priority sector
Operating consulting for trade & field service businesses.
Mid-market mechanical, electrical, plumbing, fire safety and facilities services across Australia.
Field service businesses do not have abstract operating-model problems. They have specific, structural problems that compound across every job the business is dispatching. Technicians sit idle while jobs sit unscheduled. Margin on maintenance contracts is thinner than it looks once the true cost of dispatch and rework is counted. The systems are partially deployed, the spreadsheets are still load-bearing, and the leadership team is spending too much time chasing visibility into operations that should be self-evident.
We work specifically with mid-market commercial field service businesses where the operating model has not yet caught up with the size and complexity of running hundreds of jobs simultaneously across multiple technicians, customers and sites. The Infinikey Operating Method adapts to the realities of dispatch-based work: scheduling and utilisation, job-to-invoice flow, contract management, technician credentials, and the operational discipline that high-volume field delivery requires.
01
The Situation
What's actually happening in the sector right now.
Australian mid-market commercial field service is operating under a set of compounding pressures that have become structural rather than cyclical, and the businesses that thrive will be the ones whose operating model can absorb them. The patterns that bring field service leadership to this practice.
01
Technician scarcity has become the rate-limiting constraint on the business.
Tradespeople, qualified technicians and senior service engineers are scarce, and the cost of attracting and keeping them is rising faster than the rates the business can charge. Revenue ceilings are increasingly determined not by demand but by how many qualified technicians the business can credibly deploy at any given week. Operating-model decisions around utilisation, dispatch, scheduling and credentials management are no longer back-office questions. They are the levers that determine whether the business can grow at all.
02
Margin compression on maintenance contracts has become structural.
Commercial customers, particularly facilities groups and property managers, have sharpened procurement on recurring contracts. Margins available on reactive call-outs and quoted work have not kept pace with rising labour, parts and vehicle costs. The leadership team senses margin is leaking but cannot see exactly where, because the data sits across job management, scheduling, finance and contract systems and never quite reconciles in real time. Profitable jobs and unprofitable jobs are not being distinguished week to week.
03
The systems landscape has fragmented across multiple disconnected platforms.
Most mid-market field service businesses are running a job management system, a scheduling and dispatch tool, a quoting system, an invoicing platform, a customer database, and increasingly an asset or IoT layer. These are partially integrated at best. A technician completing a job triggers a chain of system updates that often happens in arrears, with manual reconciliation in between. The total cost of integration friction is now larger than the original problem any single platform was bought to solve.
04
Customers are buying data, not just service delivery.
Commercial customers increasingly expect more than the service itself. They expect asset registers, condition reports, compliance evidence, predictive maintenance recommendations, and structured reporting tied to their service-level agreements. Field service businesses that can produce this data become strategic partners. Those that cannot get squeezed on price and treated as commodity providers. The operating-model question is whether the business is built to capture, structure and deliver this data as a by-product of service delivery, or whether it has to be assembled retroactively each month.
05
The shift from reactive to recurring revenue is an operating-model question.
The strongest mid-market field service businesses are deliberately shifting their revenue mix away from purely reactive call-outs toward maintenance contracts, service-level agreements and longer-term customer relationships. This shift is a commercial strategy, but it is delivered through the operating model: different scheduling logic, different technician deployment, different reporting cadence, different customer management. Businesses that grow recurring revenue without rebuilding the operating model around it usually find the new revenue is less profitable than expected.
Some field service businesses arrive at this practice with one of these patterns. Most arrive with three or four, and the patterns are usually compounding on each other. The work is rebuilding the operating model so the business can absorb the pressures the sector is now operating under.
02
The Work
What operating-model work looks like in field service.
The Infinikey Operating Method runs through every engagement: Diagnose, Redesign, Implement, Hold. The structure is consistent across sectors. The work inside the structure adapts to the realities of how a field service business actually runs. Five questions that shape field service engagements specifically.
01
How does the business actually deploy its workforce, and where is utilisation leaking?
Most field service businesses can tell you their billed hours. Far fewer can tell you their utilisation by technician, by team, by week, with confidence. Idle technician hours, travel-heavy job sequencing, mismatched skills-to-job allocations, and rework all show up as utilisation leakage that the business is paying for. We rebuild the operating model so leadership can see, in real time, where utilisation is genuinely productive and where it is not, and design the scheduling and dispatch logic that closes the gap.
02
How does a job actually flow from quote to dispatch to completion to invoice?
The lifecycle of a single job touches estimating, scheduling, technician dispatch, parts and materials, on-site execution, completion documentation, invoicing, and customer follow-up. Mid-market field service businesses have grown past the size where this flow can run on informal handovers. We map the actual flow as it currently runs, identify where information is being lost between stages, and rebuild the workflow so each stage produces what the next stage needs without rework or chase. Same-day or next-day invoicing becomes the default rather than the exception.
03
How is contract margin actually managed, contract by contract?
Recurring maintenance contracts are the most strategic revenue stream for most mid-market field service businesses, and also the easiest to lose money on without realising it. We rebuild the contract-margin architecture so leadership can see, contract by contract, which agreements are profitable and which are silently consuming margin through overservice, scope creep, or under-pricing. Renewal decisions become evidence-based rather than relationship-based.
04
How do the systems support the work rather than gate it?
Most mid-market field service businesses have made significant investment in job management, scheduling, and customer-facing platforms, and are not getting full value from them. We work alongside the existing systems rather than replacing them, to close the deployment gaps, build the integrations between job management, finance and field execution, and create the reporting layer that makes the systems trustworthy. Where the systems genuinely cannot meet the need, we build the targeted automation or workflow tools that fill the gap.
05
How does the business deliver the data that customers now expect?
Asset registers, condition reports, compliance evidence and structured reporting against service-level agreements are no longer optional for businesses serving sophisticated commercial customers. We design the operating model so this data is captured at the point of service delivery rather than reconstructed retroactively, and reported to customers in the formats they expect. The businesses that thrive are those whose data layer is a by-product of how the work runs, not a separate reporting project each month.
The output is not a dispatch manual or a technology strategy document. It is a working operating model that the business runs on, with utilisation visibility, contract-margin discipline, job-flow integrity and customer data architecture that hold across every job, every team and every contract.
03
The Methodology
How the four phases adapt to field service.
Operating-model engagements with field service businesses run through all four phases of the Infinikey Operating Method. The work inside each phase is shaped by the rhythm of high-volume, dispatch-based service delivery.
PHASE 01
Diagnose
Sector-anchored
We map how work flows through the business: from inbound enquiry or contracted job to scheduling to dispatch to execution to invoicing. We score the Control Index with weight on utilisation visibility, contract-margin discipline, job-to-invoice flow, systems integration, and the quality of customer-facing data. The Priority Register names which structural issues are most acute and what to fix first across the operations.
PHASE 02
Redesign
Centre of gravity
Operating Model Blueprint, Decision Rights Matrix, Governance Cadence Charter and KPI Architecture, all built for high-volume dispatch-based work rather than for a generic business. The redesign typically focuses on utilisation and scheduling logic, the job-to-invoice workflow, the contract-margin architecture, and the reporting layer that gives leadership real-time operational visibility.
PHASE 03
Implement
Sequenced around live operations
Implementation in field service is shaped by the reality that the business cannot stop dispatching jobs while we improve them. We sequence the changes so the operating model is rebuilt across live operations without disrupting service delivery. New scheduling logic is introduced job type by job type. Workflow changes are piloted with one team before being rolled out broadly. Operational continuity is non-negotiable.
PHASE 04
Hold
Critical at high job volume
Field service businesses are uniquely prone to operating-model reversion under daily operational pressure. Dispatchers fall back to old habits when a busy week hits. Technicians revert to familiar scheduling patterns. New reporting gets quietly worked around. We run monthly Operating Cadence Reviews for the first quarter, then quarterly check-ins, with structured re-scoring against the original Control Index baseline. The Hold phase is what protects the work from the constant erosive pressure of high-volume daily operations.
Field service operating-model work without a Hold phase fragments fast under daily dispatch pressure. We have structured our practice around this conviction.
04
Selected Engagements
What this looks like in the field.
A selection of recent field service engagements. Client identities anonymised at request. Outcomes will be quantified as case studies are released.
Commercial HVAC
Utilisation, dispatch and field-to-office data flow
A commercial HVAC business in NSW with mobile technicians servicing commercial property across the metro area. Job data was being captured on paper and re-keyed at the office, with significant lag and error rates. Technician utilisation was visible monthly, after the fact, with no clear view of where time was being lost. We rebuilt the dispatch and scheduling logic around real-time utilisation visibility, designed the field-to-office data flow so completion data captured on site flowed cleanly into invoicing and reporting, and integrated the job management and finance systems. Same-day invoicing became the default, and weekly utilisation visibility gave leadership the lever to address the genuine bottlenecks.
Commercial Electrical Services
Contract-margin discipline and renewal architecture
A multi-state commercial electrical services business with a portfolio of recurring maintenance contracts alongside reactive work. Contract margin was being assessed only annually, at renewal, with limited visibility into which contracts were genuinely profitable versus which were silently consuming margin through overservice and scope creep. We rebuilt the contract-margin architecture so margin became visible contract by contract, monthly, and designed the renewal decision framework so commercial conversations with customers were grounded in evidence. Several loss-making contracts were either repriced or exited, and the recurring revenue mix shifted toward profitable agreements over the following two quarters.
Multi-Trade Facilities Services
Job-to-invoice flow and customer data delivery
A multi-trade facilities services business in Victoria servicing commercial property portfolios across multiple disciplines. Customer data delivery (asset registers, condition reports, compliance evidence) was being assembled retroactively each month from multiple sources, taking significant senior time and increasingly being asked for in formats the business could not easily produce. We redesigned the operating model so customer-facing data was captured as a by-product of service delivery rather than reconstructed retroactively, integrated the data layer with the existing job management system, and built the reporting templates customers were actually requesting. Customer data delivery shifted from forensic assembly to automated output.
All engagements anonymised at client request. Detailed metrics released alongside named case studies as clients approve disclosure.
05
The Buyer
Who in the business engages this practice.
Field service operating-model engagements typically come from one of three buyer roles. Each carries a slightly different version of the problem.
01 · Founder / MD
The Founder or Managing Director.
Often a tradesperson or service engineer who built the business from one team or a small base. Increasingly aware that the structure that worked at twenty technicians is breaking down at eighty or one hundred and twenty. The founder is still the most credible person in the business about the work itself, but cannot be the dispatcher, the operations manager, the contract negotiator and the relationship lead simultaneously. Engages us when they sense the business has outgrown how they personally run it, and they need an operating model that lets them lead rather than chase.
02 · Operations Manager
The Operations Manager or General Manager.
The senior operator running dispatch, scheduling and technician coordination day to day. Often the person closest to the operational pain because they see utilisation gaps, mismatched dispatching, customer escalations and rework most directly. Engages us when they need leadership-level support to redesign the dispatch-and-scheduling architecture, not just to tighten the next week's roster.
03 · CFO / Finance Manager
The Chief Financial Officer or Finance Manager.
Often the role that first surfaces "something structural is wrong" because they see the lag between job completion and invoicing, the contract margins that vary unpredictably, and the technician utilisation that is lower than what the business needs more clearly than anyone else. Engages us when reporting has become a forensic monthly exercise and they need an operating model where the data flows naturally rather than being reconstructed each month.
The Diagnostic is structured to give all three buyer types a shared view of what is actually happening, what to fix first, and who needs to own which piece of the work.
06
The Fit
When we are the right firm for a construction business, and when we are not.
We are the right firm when:
- The business is mid-market: typically 50 to 300 staff, $20M to $100M revenue, dispatch-based service delivery rather than project-led work.
- The work is commercial mechanical, electrical, plumbing, fire safety, or multi-trade facilities services. Sectors where utilisation, dispatch, contract margin and customer data are operating-model questions.
- The leadership team senses the operating model has not kept pace with how the business has grown.
- The business has invested in job management or scheduling systems but is not getting full value from them.
- Utilisation visibility, contract-margin discipline, job-to-invoice flow, or customer data delivery are recognised gaps.
- The leadership team is willing to commit two to four hours per week to the active engagement and to engage operations and field staff in the work.
We are not the right firm when:
- The business is a national or enterprise field service operator where the operating-model questions sit at enterprise scale rather than mid-market.
- The business is a residential trade or owner-operator business below the scale where formal operating-model work makes economic sense.
- The need is for field service software selection or implementation as the primary deliverable. We work alongside existing systems, but we are not a systems integrator and we do not lead software selection projects.
- The leadership team cannot give meaningful time to the engagement. Field service operating-model work cannot be done at arm's length from the people running operations.
- The need is for operational management resourcing rather than for a structural rethink of the operating model.
If you are not sure whether your situation fits, the Diagnostic is built to answer that question. Two to four weeks. Senior-led. Honest about whether we are the right firm for your business.
07 · How to Start
Start with a Diagnostic.
Every field service engagement begins with a Diagnostic. Two to four weeks of structured discovery across leadership, operations, dispatch, field execution, and contract management. You walk away with a clear view of where the operating model is straining, a 90-day plan for what to fix first, and a working sense of how we think about field service businesses.