Building simple systems for small businesses

I worked with small businesses and operational teams that needed practical systems without enterprise-level complexity.

The work included websites, booking journeys, content structures, supplier records, request trackers, product information, customer-facing forms, and internal follow-up workflows.

Projects typically began with a loosely defined need and ended with something the team could operate, update, and hand over.

The value was not only in building the interface. It was in clarifying what information was needed, who would maintain it, how work would move through the system, and what would happen after launch.

The common problem was rarely a lack of tools. It was fragmented information, unclear ownership, manual follow-up, and systems that were hard to maintain after delivery.

Small-business systems often look simple from the outside, but the work sits across several constraints. Requirements may be incomplete. The person requesting the system may not be the person using it every day. Information may live across spreadsheets, messages, notebooks, websites, and individual memory. And a business may need a useful solution quickly, without the time or technical capability to maintain something complicated.

The challenge was deciding what needed to be built, what could stay manual, and how to make the final system usable after handover.

At Gandharva Loka Dublin, supplier requests, pending stock, product information, and follow-up activity could become difficult to track across conversations and individual memory.

I created a coded request tracker that connected open requests, supplier follow-ups, pending stock, ownership, next actions, and completion status.

The system did not replace every existing tool. It created a clearer operating layer around the work, making it easier to see what was open, who needed to act, and what could be closed.

This mattered in an environment involving approximately 50 suppliers and a catalogue of more than 3,000 products.

Small organisations do not need scaled-down enterprise systems. They need tools and workflows designed around their actual capacity, habits, and operating constraints.

The best solution is often not the one with the most features. It is the one that makes the next action clear, reduces avoidable follow-up, and remains usable after the person who built it steps away.

That principle still shapes how I approach product work: start with the real workflow, reduce friction, make ownership visible, and design for continued use.

"A useful system does not need to be complex. It needs to make the next action obvious."