Selected work

Real problems, working results.

Most of what I build is internal and confidential — the kind of system a business runs on, not something with a public front door. So rather than screenshots, here's the shape of the work: the problem, what I built, and what changed.

Logistics
.NETSQL ServerAzureBlazor

Three spreadsheets and a legacy database, replaced with one system.

The problem

Operations ran across several shared spreadsheets and an ageing database. Numbers never quite matched, stock visibility was guesswork, and reporting meant one person stitching files together by hand each week.

What I built

A single .NET system that became the source of truth for orders, stock and customers — with live dashboards and reporting that runs itself, hosted on Azure with proper backups.

~12hsaved every week
1source of truth
livestock visibility

Recognise this? → Business & CRM systems

Rescue · SaaS
.NETC#SQL ServerAuth

An AI-generated build that broke the moment real users arrived.

The problem

A founder had a product generated quickly with AI tooling. It demoed well, but the data layer was inconsistent, logins failed unpredictably, and nobody could safely change anything without something else breaking.

What I built

I took over the codebase, fixed the data and authentication layers, removed the parts that couldn't be trusted, and got the core flows stable and shippable — with a clean structure the founder could actually build on.

6 wksfrom broken to live
100%core flows fixed
0mystery failures

Recognise this? → Project rescue & recovery

Professional services
.NETSQL ServerBespoke CRM

A CRM built around the firm — not an off-the-shelf tool nobody used.

The problem

The firm had paid for an off-the-shelf CRM that didn't match how they actually worked, so staff quietly went back to spreadsheets and email. Reporting to partners was slow and unreliable.

What I built

A bespoke CRM shaped around their real workflow and the reports the partners needed — so it became the tool people reached for first, and one fewer subscription to pay for.

staff adoption
−1tool to pay for
fastpartner reporting

Recognise this? → Business & CRM systems

Manufacturing
Legacy .NETAzureMigration

A decade-old system, modernised without stopping the line.

The problem

A business-critical application built years ago still worked, but ran on end-of-life technology. It was slow, fragile, and the original developer was long gone — so nobody dared touch it.

What I built

I modernised it onto current .NET and Azure in stages, preserving every bit of data and keeping it running throughout — then documented it so it's maintainable again.

0downtime
EOL→supported stack
alldata preserved

Recognise this? → Legacy modernisation

How engagements work

A straight line from problem to working software.

Most projects start with a fixed-scope first phase, so you can see how I work before committing to the whole thing. You'll always know what's happening, what it costs, and what you're getting.

01

Understand

I learn how your business runs and where it hurts — in plain language, not jargon.

02

Scope & quote

A clear, fixed picture of what gets built, what it costs and when.

03

Build

Working software in steady increments, so you see real progress.

04

Support

It doesn't end at launch. I keep it running and grow it as you do.

Not sure which one you need?

That's fine — most people aren't. Tell me the problem and I'll tell you straight whether and how I can help.