Building the operating layer small businesses were missing
Across 8+ SME engagements, I rebuilt supplier records, booking workflows and request tracking into systems small teams could run without me, including a 50-supplier, 3,000-product records rebuild at a Dublin music retailer.
Independent engagements · multiple small businesses · 2021 – 2026
Context
Small businesses where the work was happening but the system around it wasn't: records, requests and follow-ups living in memory, conversations and inboxes.
The problem
Requests were missed, product details were slow to retrieve, and follow-ups depended on whoever remembered them. The job each time: find the smallest tool that would hold under daily pressure. And still hold after I left.
"I came in where the tools were not. Each engagement started with understanding how the business actually ran, then building something specific enough to work, and simple enough to last."
Brief
Small businesses often have the work happening, but not the system around the work. Customer requests sit in conversations. Product details sit inside slow systems. Follow-ups depend on whoever remembers them that day.
Across 8+ engagements (a Dublin music retailer, a numerology practice, a tyre business, a fashion studio, a steel engineering firm, a water brand, a chartered accountant, and Mast Service Station), I was the person who walked in unfamiliar, worked out how the business actually ran, and shipped the missing piece: request trackers, supplier records, booking journeys, calculators, content systems. Different businesses, different tools; the same judgment call each time about what was worth building.
The constraint that shaped every decision: no budget for platforms, no appetite for training, and no me after handover. Whatever I built had to be useful enough to be adopted and light enough to be maintained.
The real problem
The repeated issue was not effort. It was visibility and ownership.
At Gandharva Loka, a specialist music retailer in Dublin, the team of 5–6 managed a catalogue of 3,000+ products across around 50 suppliers. Customer requests were often logged with minimal contact detail, and there was no reliable way to link an open request back to stock when the item arrived. Follow-up depended heavily on memory.
At Renumerology, the business had no structured digital journey at all: no proper website, no booking flow, no analytics, no way for a new client to understand the service and take the next step.
At Mast Service Station (one of these engagements too, covered in depth in its own case studies) the same pattern showed up as a visibility and retention problem.
Different businesses, same underlying problem: the workflow depended on memory, manual effort and scattered channels. And each one needed a different-sized answer.
Approach
I treated each engagement as a workflow problem before treating it as a digital build.
At Gandharva Loka, I started with the records: built a product and supplier master sheet from scratch, capturing product and supplier context, supplier contact details, communication notes, paid orders, order tracking and stock-arrival context: a single reference point for product and supplier lookup. I then updated the customer request tracker so open requests could be reviewed against stock arrival, with ownership made clearer through visible status, comments and responsibility fields. Where the POS needed specific product details to return useful results, the tracker let staff search on broader or vaguer keywords, reducing friction during live service.
At Renumerology, I shaped the digital journey from the ground up: brand, website, booking flow, Google Analytics, Instagram support and six numerology calculators, including destiny-number and life-path tools. Alongside the site I also built an internal numerology report generator, giving the practitioner base calculations from a client's name and date of birth to build on.
Mast Service Station was one of these engagements too. Its brand, UX and web work has its own case study, and its operating-layer rebuild another; this one is about the pattern across all of them, not a repeat of either.
The last step was the same everywhere: hand it over. Feedback rounds until it fit how the team actually worked, and no dependency on me being in the room.
What the work enabled
The work improved visibility, follow-up and digital readiness across different SME contexts.
At Gandharva Loka, product and request details became easier to retrieve, open follow-ups were more visible, and ownership was clearer through status, comments and responsibility fields. This was not measured as a formal analytics exercise, but the operational improvement was visible in daily use: fewer missed loops, faster responses and less dependence on memory. The system is still used by the business today because it is lightweight, practical and built around the way the team actually works.
At Renumerology, the business moved from almost no structured web presence to a clearer digital service journey. Visitors could understand the service, use simple calculators, book more easily and leave a data trail through analytics.
Supplier and product records restructured across ~50 suppliers and a 3,000+ product catalogue at Gandharva Loka.
A status-coded customer request tracker replaced inbox-and-memory handling — every open request linked to an owner, a supplier action and a next step, still in use today.
Six numerology calculators and an internal report generator shipped for Renumerology, alongside the brand, site, booking flow and analytics.
What it taught me
The best small-business systems are not always the most sophisticated. They are the ones that make work visible, reduce dependence on memory and help people act faster under daily pressure.
This work strengthened how I think about product and business analysis: start with the real workflow, find where ownership breaks down, then shape a system that is useful enough to be adopted and light enough to be maintained.
What I'd do differently: baseline the simple numbers on day one (open requests per week, time to find a product) so the improvement isn't only visible in daily use. The systems earned the team's trust; the case for them shouldn't have to rest on anyone's memory, including mine.
"Small teams do not always need heavy platforms. They need systems light enough to use under pressure and clear enough to maintain after the novelty wears off."