● Work

Completed work, shown anonymously.

Selected examples without client names: the problem, what changed technically, and what became easier afterwards. More detail can be shared in conversation where confidentiality allows.

W.01 Public sector · Reconciliation

Payroll migration reconciliation system for a council

The problem

A council needed confidence that payroll outputs matched after a system migration, with teams working through high-volume differences under time pressure.

What we built

A frontend reconciliation system for comparing legacy and new payroll exports, surfacing exceptions, filtering by issue type and giving reviewers a clear workflow.

What changed

Migration differences made visible and reviewable
Finance and payroll teams had a shared view of exceptions
Manual checking replaced with a repeatable reconciliation process

W.02 Consumer SaaS · Food planning

Meal planning SaaS product, built full stack

The problem

A meal-planning product needed to move from concept into a usable web application with real grocery data, generated plans and the product plumbing to support users.

What we built

A full-stack SaaS web application with grocery scrapers, recipe and meal-plan logic, account flows, data storage, admin tooling and the frontend experience.

What changed

Product moved from idea to working platform
Scraped grocery data became usable planning inputs
Core customer journey built across frontend and backend

W.03 Mobile app · Dating

London dating app for iOS and Android

The problem

A London-based dating product needed a mobile app from scratch, covering product shape, interface design, cloud setup and release-ready implementation.

What we built

Designed and built the iOS and Android app with Expo, AWS backend services, authentication, matching flows, profile UX and production-minded app architecture.

What changed

Cross-platform app delivered from a blank slate
Cloud backend and mobile frontend built together
UI and UX shaped around the product's local market

W.04 Financial services · Fraud screening

Fraudulent call detection API and frontend

The problem

A banking screening workflow needed to identify suspicious inbound calls earlier, giving teams a clearer way to review risk signals before calls reached sensitive processes.

What we built

An API and frontend for fraud-call detection, combining screening logic, review views and operational controls that could be tested against bank-facing workflows.

What changed

Risk signals exposed through a usable review interface
API designed for integration with screening workflows
Frontend gave teams a practical way to assess flagged calls

Next step / Project fit

Reporting problem, data gap, internal tool, platform idea or AI workflow worth testing?

Send the rough shape of the problem. You will get a grounded view of what could be built, fixed, connected or tested first, without turning it into a bigger project than it needs to be.

Talk through the work