Field notes / Field operations
The case against pooled tablets
Pooled tablets — devices kept on a charging shelf and signed out per shift — look efficient on a spreadsheet. Fewer units per crew, lower hardware spend, theoretical resilience. In practice, we have watched three or four customers attempt this model and one of them sustain it past six months.
The problem is the half-hour at the start of every shift. Crews spend it logging in, syncing the inspection app, fixing yesterday's offline-cached form, and discovering that someone has installed a battery-killing app overnight. Multiplied across a hundred crews, that is a meaningful slice of the working day, and it gets billed back to the customer as overtime or productivity loss in places nobody attributes to the device strategy.
Assigned tablets, with offline-first imaging and a kiosk profile, eliminate most of that overhead. The trade is a slightly higher device count and a small attrition allowance for the tablets that get genuinely lost — which we publish, with a formula, in the master agreement. We have found the assigned model wins on total cost in roughly nine of ten field-services scenarios. The exception is summer-only seasonal crews where the device only lives twelve weeks and the math does, in fact, work the other way.
Three more notes worth opening.
- September 11, 2025
Why we stopped quoting per-device prices below twenty-five seats
A quiet decision we made last summer that has improved both our renewal rates and, surprisingly, the relationships with our smallest customers.
- August 3, 2025
A refresh cadence is a forecasting tool, not an upgrade pitch
How we use eighteen-month refresh windows to give CFOs the only thing they actually want from device subscriptions: a number that does not move.
- July 17, 2025
Same-day swap, and what we will not promise
Notes on the operational reality behind a same-day swap window — and the regions where we deliberately do not commit to it.