Field Operations Visibility via a Native Android App

The challenge

Towerstream operated wireless internet service from hundreds of locations, supported by a team of field technicians who installed and maintained equipment at client sites. The field tech manager had a persistent blind spot: where were techs at any given moment? How much time were they spending at each site? What were they actually doing during those hours?

The data didn't exist anywhere. Techs filed paperwork after the fact — sometimes. Schedules were planned without visibility into what was happening on the ground. The manager couldn't optimize routing, couldn't catch sites where techs were getting stuck, and couldn't accurately reconcile field hours against operations.

What we considered

The instinctive consultant response would have been to solve this inside NetSuite — a custom form for techs to fill out after each visit, or a daily summary email. That would have failed for an obvious reason: field techs aren't sitting at NetSuite. They're on rooftops and in mechanical closets with phones in their pockets, not laptops in their hands. Any solution that required them to log into the ERP after a long day would have been ignored.

I proposed something different: build a native Android app the techs would actually use in the field, then have it log everything back to NetSuite via the integration layer.

The judgment wasn't a technical one — it was recognizing that the problem needed a solution outside of NetSuite. NetSuite is a great system of record. It's not a field tool. Forcing the workflow into the wrong system would have produced a feature nobody used.

I came up with the approach myself after talking with the field tech manager about what was actually broken. Sometimes the right response to "we need this in NetSuite" isn't more NetSuite.

What we built

• A native Android application for field technicians, deployed on company-issued phones
• Check-in / check-out at client sites with GPS location tagging and timestamps
• Status updates (in transit, on-site, working, completed) logged in real-time
• C# Windows service that synced field data from the app back into NetSuite via SuiteTalk web services
• Custom NetSuite records capturing the full field-visit history, queryable like any other NetSuite data
• Reports for the field tech manager — time per site, time per technician, schedule actuals vs. plan

The result

The field tech manager finally had visibility into operations that had been invisible before. Schedule optimization based on real time-on-site data, not estimates. Sites where techs were getting stuck got attention before they became chronic problems. The full field-time-to-NetSuite pipeline gave operations and finance a complete record of where field hours actually went.

"I was amazed at what Jaime has been able to do with the Field Tech App." — Field Tech Manager, Towerstream

Why it worked

The decision to build outside NetSuite is what made it work. A NetSuite-only solution would have been ignored by the techs, who needed something that worked in the field — not at a desk. Recognizing that boundary — when to use NetSuite and when to build alongside it — is the kind of judgment that's hard to articulate but obvious in hindsight.

It still shapes how I scope custom work today. The right answer to "we need this in NetSuite" isn't always more NetSuite. Sometimes it's a tool that lives where the work actually happens, with NetSuite as the system of record on the back end.