Sahadh Fazal Mohamed

Co-founded a UK studio building websites, apps, bespoke software, third-party integrations, HR and operations systems for growing businesses. I lead engineering; my co-founder leads design and brand.

• Built and shipped a multi-site franchise operations platform covering sales, labour, expenses and compliance.
• Delivered an HR mobile application with one structured record per employee, tracking right-to-work, visas and document expiries.
• Client project (TRUKBK): engineered a hallucination-resistant AI sales concierge on a custom RAG pipeline with vector embeddings and cosine similarity search (Supabase pgvector) and Google Gemini for generation, with a 2-layer fallback preventing customer-facing errors.
• Connected existing point-of-sale systems to mobile apps and reporting, so businesses keep the till they already use while data flows into one place.

Stack: Python, TypeScript, React, React Native, Flask, PostgreSQL, Docker, plus LLM and vector database integration.

Engaged as a freelance software engineer to build a booking platform from scratch for a UK community travel operator, replacing a manual booking and reconciliation process.

• Architected a full-stack platform on a serverless pnpm monorepo (React 19, Vite 7, Express v5), choosing serverless specifically to keep hosting costs low for an early-stage business.
• Built a type-safe, end-to-end automated booking pipeline, so a booking made on the site required no manual intervention to process.
• Integrated Stripe with automated payment reconciliation, cutting administrative overhead by 15% by removing manual end-of-period checking.
• Built an interactive trip discovery carousel and custom search widgets, and modelled the data layer in PostgreSQL with Drizzle ORM.

The reconciliation work mattered most commercially: a booking system nobody trusts financially doesn't get used, however good the front end looks.

Started on the shop floor managing daily store operations and high-volume customer service, which is where I first noticed the gap this role was built to close.

• Worked the kitchen-to-counter workflow directly and identified where orders were getting lost, delayed or mismatched between kitchen and till, rather than assuming what the problem was from outside.
• Engineered PhatOps, a custom operations app handling real-time order tracking and staff authentication, built to solve those specific bottlenecks rather than as a generic dashboard.
• Architected the full-stack solution in React, TypeScript, Tailwind CSS and Supabase, with real-time sync so a change made at one station is reflected everywhere immediately.
• Reduced rendering latency by 20% through optimised reusable components and tuned Supabase real-time subscriptions, which mattered directly on the shop floor: a slow screen at the counter during a rush is a queue forming behind it.
• Now used daily by 20 staff across 4 branches, with rollout planned for 16 further sites.

Being on the floor first was the useful part. I wasn't guessing at requirements from a spec document; I was watching the actual failure happen and building the fix for it.

Elected by my cohort to represent their interests to course leaders and academic staff, gathering feedback on teaching, module content and course delivery and raising it through formal university channels.

• Ran regular feedback sessions with students and consolidated concerns into clear, prioritised points for staff meetings, rather than passing on complaints unfiltered.
• Acted as the first point of contact for coursemates settling into university life, helping new students navigate deadlines, module choices and where to get support.
• Followed up on raised issues to confirm they were actually addressed, rather than treating the meeting itself as the outcome.

This was the first role where I had to turn what a group of people vaguely wanted into something specific a decision-maker could act on, which turned out to be most of what requirements gathering actually is.

My first role in the UK, split between the shop floor and the back office of an international supermarket.

• U-Shop later became an Artim Labs client, and I went on to build their ERP and HR system.
• Processed 16-20 supplier invoices a week in Excel: data entry, validation and reconciliation against incoming deliveries.
• Flagged discrepancies between what was ordered and what arrived before payment went out, protecting payment dates and preventing suppliers being paid incorrectly.
• Produced routine stock and invoice summaries for management from the reconciled data.
• Provided front-of-house customer support during trading hours alongside the admin work.

This is where I first saw how much of a business runs on spreadsheets nobody has time to check properly, which is a straight line to the data and BI work I do now.