Field & Operations

Why Work Still Isn't Mobile

We book flights from our phones. We apply for loans, schedule surgeries, move money across borders. But ask someone to update a customer record or close a work order from that same phone, and the answer changes: "I'll enter it in the system when I'm back at the office."

That single sentence is the quietest line item in every enterprise software budget. Companies spend serious money on ERP, CRM and PLM platforms — and the work still ends in front of a desktop screen.

A Workday Chained to a Desk

Watch a field sales rep for a day. They meet the customer, then jot the notes into their phone's notepad or a message to themselves. Later they walk into a café, open a laptop, and start transferring the day's notes into the system. Technical service teams follow the same script: the job finishes on site, the form gets filled in at night.

So what actually became mobile wasn't the work. It was just the person. The data still sits in one fixed place, waiting for the employee to come to it.

Million-Dollar Software, Single-Screen Lives

ERP, CRM and PLM systems were designed around an assumption from fifteen or twenty years ago: the user sits at a desk, has a keyboard, has a 24-inch monitor, and can keep seven tabs open at once. That assumption still holds for finance. It does not hold for anyone working in the field.

A mobile app is not a mobile workflow

Most enterprise platforms do have a mobile app. But those apps are usually a shrunken version of the desktop interface. Squeeze a forty-field screen onto a phone and you don't get a mobile solution — you get a mobile ordeal. The outcome is predictable: the user installs the app, uses it for two weeks, then quietly returns to the old habit.

The Hidden Cost of the "Café Break"

A field team pulling into a café mid-afternoon to open laptops looks like a harmless habit. It isn't free:

• Delayed data: The report a manager reads in the morning reflects yesterday, not today.
• Missing detail: A meeting note recalled six hours later is half the note it could have been.
• Lost appointments: A customer request that arrives while someone is on site goes unanswered — and a competitor replies first.
• Motivation drain: "The real work is done, now I have to type it all in" is a genuinely tiring feeling.

So Why Is This So Hard?

It isn't a technical barrier. It's a habit and interface problem. When a company spots a new need, the reflex is "let's build another app." But every new app asks the employee to learn one more thing on top of their actual job.

Meanwhile, there's already an interface on that phone — one opened dozens of times a day, one nobody needs to be trained on: WhatsApp.

The Real Question: A New Screen, or an Existing Channel?

Treating mobile transformation as "let's hand out tablets" mistakes the problem for a hardware issue. The actual turning point is different: what if, instead of entering data into a system, you could simply record it by talking?

Aspect	Traditional ERP/CRM mobile	Messaging-based automation
Learning curve	Training and adoption needed	Close to zero
Moment of capture	End of day, in batches	Instant, inside the work
Customer side	Separate portal, separate password	The app they already use
Appointment flow	Manual calendar entry	Automatic confirmation and reminders

Frequently Asked Questions