Fractional CFO vs Controller for Industrial Equipment Repair

Pull a sample of last month's closed tickets and see whether each one shows parts cost, labor cost at the technician's actual loaded rate, and any truck-stock inventory draw, netted against what the customer was billed. If tickets only show revenue with cost buried in a general expense category, you can't tell which service types or which technicians are actually profitable. Fixing this is controller-level work: setting up ticket-level cost tracking and making sure it's populated consistently, not just for the tickets someone remembers to review.

Parts carried on service trucks are notoriously hard to track, since they move without a formal receiving process the way warehouse inventory does. Without regular reconciliation, truck stock quietly becomes a source of unexplained shrink, and ticket-level cost understates the true parts expense because draws never get recorded against the job. Set a fixed cadence, monthly at minimum, for reconciling truck stock against what's been drawn and billed.

Warranty claims against equipment or parts manufacturers should be tracked as their own category, both the cost incurred and any reimbursement received, kept separate from standard billable repair work. Blending the two hides your true billable margin and makes it hard to tell whether a warranty program with a particular manufacturer is actually being honored promptly or becoming a slow-pay problem worth escalating.

Utilization, billable hours against total available hours, is the metric that actually predicts profitability for a field service business, more than ticket count alone. A technician closing many small tickets with long drive times between them can be less profitable than one working fewer, larger jobs. This needs dispatch and job-cost data tied together, which is more of a system and process question than a pure accounting one, but the controller function usually ends up owning the reporting since it needs to be as reliable as any other financial number.

With ticket-level margin, reconciled truck stock, separated warranty tracking, and real utilization data, a fractional CFO can do the higher-value work: deciding whether to add another truck and technician, whether certain service categories should be priced higher or dropped, and how to think about financing the next truck given that borrowing is usually priced off the bank prime rate rather than a fixed number¹. None of that planning is reliable without the ticket-level data from the earlier steps being accurate first.

Before handing strategic decisions to a fractional CFO, confirm that these basics are in place:

• Every closed ticket shows parts cost, labor at the technician's actual loaded rate and any truck-stock draw, netted against what the customer was billed.
• Truck stock is reconciled regularly, so unexplained shrink does not quietly understate ticket-level parts cost.
• Warranty work is tracked as its own category, with costs and manufacturer reimbursements kept apart from billable repair work.
• Technician utilization, billable hours against total available hours, is measured, and service contracts are tracked separately from one-off calls.

A company running a handful of trucks can typically manage with a bookkeeper trained on ticket-level cost tracking, supplemented by fractional CFO time brought in quarterly. Once the fleet grows large enough that dispatch, warranty tracking, and truck-stock reconciliation across many trucks becomes a daily coordination job in its own right, that volume usually justifies bringing the controller function in-house full time, since keeping that many moving pieces synchronized from the outside becomes harder as headcount grows.

Many equipment repair companies mix one-off emergency calls with standing service contracts that bill on a recurring schedule regardless of how many calls a given customer actually needs in a period. Those two revenue types behave differently and should be tracked separately: a service contract customer who calls rarely is more profitable than the contract price alone suggests, while one who calls constantly may be quietly unprofitable at the contracted rate. A controller should be flagging contracts where actual ticket volume has drifted far from what the pricing assumed, since that's exactly the kind of signal a fractional CFO needs before the next round of contract renewals.

Without that visibility, a company can end up quietly cross-subsidizing its highest-maintenance accounts with margin earned elsewhere, discovering the pattern only once profitability across the whole book has drifted lower than expected and nobody can point to which contracts are actually responsible for the slide. Reviewing this ahead of renewal season, rather than after contracts have already auto-renewed at the old price, gives the fractional CFO time to actually act on what the data shows instead of simply noting it for next year's planning cycle.