Mecwin WorkRoute - Case Study

Revolutionizing Field Service with Tech and Trust

Date: Jan 2025

Header image

It all started on a dusty weekend ride through the outskirts of Bangalore, my bike roaring as I tracked my route, speed, and stats on an app called ESR - Eat Sleep Ride. As a passionate biker, I loved how it gave me realtime insights into my rides—top speed, distance, even inclination. Little did I know, that app would spark a game changing idea for Mecwin. Fast forward a few months, and I’m leading the charge on Mecwin WorkRoute, a field force management platform that’s turned chaos into clarity for our Service Engineers (SEs), Accounts Team, and farmers. Spoiler: it’s saving us millions, and it’s so simple it only needs four screens to work its magic. Ready to hear how we did it? Let’s roll! 🏍️



The Big Why: Turning Chaos into Cash Savings

Mecwin Technologies India Pvt. Ltd. is all about “Empowering the Future” with solar pumps, IoT, and automation to make agriculture smarter. But our field service system? It was a financial black hole. Our 30 SEs were manually logging 150-200 km of daily travel, submitting reimbursements averaging ₹30,000 per month each totaling ₹9,00,000 monthly or ₹1,08,00,000 annually. Problem? These logs were error prone, leading to inflated claims, delayed payments, and a whopping ₹54,00,000 in annual overpayments. Meanwhile, SEs were frustrated, the Accounts Team was drowning in validation work, and farmers were left waiting for service updates.

💡Biker Brainwave: “If I can track my weekend rides with precision, why can’t our SEs do the same for their 200-250 km workdays?”

Mecwin WorkRoute was our answer: a platform to automate tracking, streamline reimbursements, and restore trust across the board. Inspired by my biking app’s real time stats, I envisioned an app that could do the same for our SEs—track their routes, calculate fair reimbursements, and save us a fortune. And here’s the kicker: we kept it so simple that it only takes four screens to get the job done.



The Research Grind: Digging into the Dirt

To build WorkRoute, I dove into UX research with a mission to uncover the mess and map a way out. Here’s the breakdown:

The verdict? Manual processes were bleeding us dry, eroding trust, and slowing everyone down. But automation, transparency, and a biker inspired tracking system could fix it all with a minimalist design that doesn’t overwhelm.



What We Learned: Pain Points and Payoffs

Service Engineers

Accounts Team

Farmers

Management

💡Trust Gap: SEs wanted fairness, Accounts wanted reliability, farmers wanted clarity, and management wanted savings. WorkRoute had to deliver for all.



Building WorkRoute: From Biker Dreams to Reality

With my biking app as inspiration, our team—led by Tejas Tallam (Project Manager), Hemanth Udupa (Backend Developer), Cheran NP (Frontend Developer), Shyam Rithul RS (Frontend Developer) Saneep PP (App Developer), and me as UI/UX Designer got to work. We faced a tight timeline, legacy systems, and no dedicated testers, but we made it happen.

WorkRoute Screens
WorkRoute Screens

Core Features That Delivered

The Workflow: From Mess to Magic

💡Workflow Magic: SEs went from scribbling odometer readings to tapping “Start Tracking”. It’s like swapping a carrier pigeon for email.



The UI: Five Screens, Endless Impact

WorkRoute’s design is simpler than my biking app, because in the field, less is more. We boiled it down to just four screens, making it a breeze for SEs like Ravi to use, even after a 200 km day:

We rolled out iteratively:

💡Simplicity Win Five screens mean Ravi can track his day faster than I can check my biking stats—no clutter, just results.



The Impact: Numbers That Make You Smile

WorkRoute didn’t just streamline processes—it transformed our bottom line and team morale. Here’s the data:

💰Money Talks: ₹54,00,000 in annual savings means we can invest in more solar pumps—and maybe a fancy coffee machine for the office!



User Manual

The following documentation describes the ease of usage and showcases all the major features of the WorkRoute app.



Challenges and Wins: The Startup Hustle

💡 Startup Truth: No testers? Just channel your inner biker—test fast, fix faster, and don’t crash the demo!

Building WorkRoute wasn’t all smooth rides. We battled a tight timeline, legacy systems, and no dedicated testers, I became the unofficial bug hunter, testing on my own phone between bike rides. But the wins were worth it: SEs feel trusted, Accounts has reliable data, farmers are happier, and we’re saving millions.

Test Runs - WorkRoute became by ride analyzer
Test Runs - WorkRoute became by ride analyzer


What I Learned: Lessons from the Road

Here’s my WorkRoute wisdom in bite sized chunks:

Great ideas can come from a weekend ride. Just add tech, heart, and a lot of coffee to make them real.