Business Problems I Have Solved

Every new customer needed their own build of the product, so the team was maintaining separate codebases that slowly drifted apart.

One SaaS product delivered on three surfaces — web console, mobile app and installable PWA — all served by a single API with a super-admin layer that provisions each customer's workspace.

Customers, branch staff and admins each worked from a different system, so balances and pending requests were constantly out of sync between them.

A banking system split into three separate portals — customer, staff and admin — running on one core API, where a transaction posted in any portal updates the others in real time.

Each department kept its own spreadsheet, so stock, purchase and sales figures never agreed at month end and nobody could say which was correct.

A connected ERP where inventory, purchase, sales and resource data live on shared master records, so every department reads the same numbers instead of keeping its own sheet.

The books were maintained by hand, so entry errors only surfaced at period close — the point where they are hardest and most expensive to trace.

A books-of-accounts system covering ledgers, vouchers, invoices and statements, built so the balances stay reconciled without an accountant re-checking every entry by hand.

Billing at the counter was slow during rush hours, and stock counts drifted far enough that staff were selling items that had already run out.

A counter billing system tuned for speed — the cashier can complete a sale entirely from the keyboard while stock and day totals update behind the screen.

Contracts were emailed around for signatures with no way to see who had signed, who was holding it up, or whether the final copy was the right version.

A digital signing platform where one document travels through several approvers — each signer gets a secure link, and the sender watches the flow move stage by stage.

Hosted cart platforms could not handle the client’s discount and reward rules, and could not be run on the servers they were required to host on.

A custom online store built and deployed on the client's own Windows Server rather than a hosted cart, paired with an admin panel and a shopping app for customers.

Maintaining separate Android and iOS apps doubled the cost and delivery time of every single feature, and the two versions kept falling out of step.

Android and iOS apps built from a single React Native codebase, talking to the same Node.js backends that power the web portals so data never drifts between them.

Collection agents recorded instalments on paper, so the office saw payments days late and had no reliable record when a customer disputed one.

A field-collection finance system: agents record instalment collections on the mobile app, and the back office sees the same status update on the web console immediately.

Bookings were taken over the phone with no live view of where vehicles were, and fares were agreed verbally — which led to arguments at drop-off.

A booking platform with separate passenger and driver experiences sharing one live trip engine, from fare quote through pickup, tracking and trip close.

The company had no web presence that converted, and the enquiries that did arrive came by phone with nothing recorded for the sales team to follow up.

Marketing landing pages and a corporate business portal — fast, hand-coded pages that load quickly and hand qualified enquiries straight to the sales team.

Organisers built teams and fixtures by hand before every event. It took hours, and the matchups came out unbalanced often enough to cause complaints.

A game tournament platform that takes registered players, shuffles them into balanced teams and runs the whole bracket automatically without an organiser drawing fixtures by hand.

The agency could show clients static design files, but nothing a client could actually click through and feel during a pitch.

Front-end delivery inside a brand agency — turning designer files into responsive, pitch-ready interfaces their clients could click through before any backend existed.

Off-the-shelf templates force a business to change how it works in order to fit the software, instead of the other way round.

Work that starts from your idea rather than a template — you describe what the business needs to do, and I design the screens, the data model and the app around it.