It’s not about having more tools. It’s about using the right one.
When I first visited the shop, nothing really felt broken. Customers were coming in, sales were happening, and the owner seemed confident. But the more time I spent there, I noticed everything was running on memory, notebooks, and experience, with no clear view of sales, stock, or daily performance.
This wasn’t about building something for thousands of shops. It was about solving real problems for one shop, within its reality.
Working with the shop team, I replaced their manual system with a simple digital solution that fits into their daily routine and needs no training.
Rajesh had been running this hardware business for years. He knew every product, every regular customer, and could handle three things at once during rush hour.
But his confidence came from habit not data.
His workflow was built entirely on memory and instinct:
What stood out to me immediately was this:
He didn’t need more information. He needed better control with less effort.
Rajesh
Shop Owner
Anil
Sale Executive
Suresh
Inventory
Three people. One shop. No shared view of what was happening.
The pattern was clear:
Instead of jumping to solutions, I spent time with Rajesh, Anil, and Suresh watching how the shop actually ran.
Manually logged every transaction. Stock checks meant physically asking Suresh or walking over no instant answer.
Updated stock only at end of day. Items were sometimes sold after they’d run out, simply because no one knew in time.
Couldn’t answer “how much did we sell today?” without flipping through a notebook.
At first, it looked like an inventory issue. But the more I observed, the clearer it became This was not just about tracking products. It was about lack of visibility and control in daily operations.
The owner was making decisions based on experience, not data. And while that worked to some extent, it created gaps that kept growing over time.
This created three major issues:
This project came with very real limitations. I wasn’t designing for a tech-savvy user sitting in a relaxed environment. I was designing for someone who:
This flow shows how a shop owner moves through the app from creating bills and managing stock to tracking expenses and handling customers. Each step follows a clear and logical path to ensure tasks are completed quickly and without confusion.
Initially, I focused on making the system powerful, adding detailed analytics, charts, and insights. While it looked complete, it didn’t match the user’s reality it required time and attention the shop owner didn’t have.
I shifted from asking “What features should I include?” to “What is the fastest thing the user needs right now?” This changed the direction from adding more to removing friction.
Translating research insights into clear flows, information hierarchy, and functional layouts before moving into visual design.
Every decision came from one constraint: the user had no time to think.
Card-based layout: Similar hardware products look nearly identical. Cards let staff see the image, brand, and key details at a glance without opening each item.
Daily revenue front and centre: Rajesh’s first question every day was “How much did we sell today?” So that number is the first thing he sees. Clear, large, immediate no graphs, no noise.
Fewer steps, everywhere: One extra tap is one too many. I stripped every screen back until only what was necessary remained. Rajesh confirmed it: “I don’t want graphs and reports. Just show me the amount.”
The final solution focused on clarity and speed rather than complexity.
After implementing this approach, the system felt more aligned with real usage.
45%
Revenue Growth
Milestone reached within 30 days of app adoption.
100%
Real-Time Visibility
Accurate stock tracking, eliminating manual errors.
100%
Digital Accountability
Every payment and Credits deal is now tracked digitally.
This project changed the way I think about design.
I learned that designing for one user can be more challenging than designing for many. Because it forces you to deal with real behaviour, not assumptions.
Most importantly, I learned that: Good design is not what looks impressive, but what works quietly in the background.