Skip to content
Sprint10

The proof

The work.

Two builds you can use right now. One is a working preview of what I’d build for you. The other proves the engineering underneath holds up when it genuinely matters.

01 · Oakwood

A complete property-maintenance system, built as a demonstration.

Not a real client, and that’s the advantage. I built the whole system a property manager would actually need, end to end, so you can log in, poke it, and read every line of its code. It’s a preview of your build, not a portfolio slide. No NDA, nothing hidden.

The chaos before

Meet Oakwood: 3 staff, around 80 rental properties. Maintenance requests arrive by email, text and WhatsApp, tracked in a shared spreadsheet that broke the moment two people edited it at once. Requests vanish into a thread. Nobody’s sure what’s been actioned. The job only one person understands, and they’re on holiday.

Why it’s a demo, out loud

There is no paying client behind Oakwood, and I’ll never pretend otherwise. That’s the point: because it’s a demonstration, it’s completely open. Use the real software, read the real code, and judge the quality yourself. Almost no portfolio lets you do that.

Oakwood · before → after

Watch the chaos become the system

Before: spreadsheets, WhatsApp, sticky notes, a stray email
R11414 Birch Ln boiler??URGENT
R0973 Harbour St gutterwho??
R10122 Mill Rd latch#N/A

The boiler's gone again at Birch Lane, can someone come today?

WhatsApp · 07:42

Did anyone pick up the gutter job?

WhatsApp · 21:17

Call Mrs Patel back!! boiler

Chase the gutter quote

From tenant

Re: Re: Fwd: leak in bathroom???

After: one dashboard for the team

Oakwood Ops

Maintenance · one queue

7

Open

2

Urgent

12

Resolved this week

  • 14 Birch Lane · boiler not firingFormUrgent
  • 3 Harbour St · leaking gutterFormScheduled
  • 22 Mill Road · broken latchFormNew
  • 8 Vicarage Close · damp patchFormTriaged

02 · What was built

One form. One dashboard. Three emails. Nothing lost.

The whole system a small property team actually runs on. No more, no less.

Public tenant form

One clean, public form for tenants to log a maintenance request. No account, no friction, no lost message.

Staff triage dashboard

One place for the team to see every request, its status, and its history. The spreadsheet that broke, replaced.

Three automated emails

Confirmation to the tenant, alert to staff, and an update when the job moves. The follow-through that used to fall through.

I don’t just hand over code

The build spec

The document that scoped the system before a line was written. Proof the judgment happens up front, not mid-build.

The user guide

A standalone, plain-English guide handed to the team. Proof of polish and communication, not just working software.

03 · Under the hood

The decisions that don't show up in a screenshot.

Anyone can draw a form. This is the senior judgment you're actually paying for: the choices that decide whether software survives contact with the real world.

  • The data model. The invisible structure that decides whether the system still works in two years, not two weeks.
  • A deliberate v1 boundary. What was left out, and why leaving it out on purpose is the senior move, not the lazy one.
  • Quiet anti-abuse. A honeypot and rate limiting on the public form. Spam stopped without a clunky CAPTCHA in a tenant’s way.
  • Address snapshots. Each request keeps its own copy of the property address, so correcting or removing a property later never quietly breaks old jobs.
  • Defence-in-depth auth. The staff area is protected at more than one layer, not a single check standing between the data and the internet.

04 · Try it

Don't take my word for it. Use it.

The live form is embedded right here. Submit a real request and watch the system respond.

Submit a test request. Made-up details welcome.

Open the form in a new tab →
Read-only walkthrough of the staff triage dashboard

The build itself took about 3 days. The 10-Day Build wraps that speed in discovery, your revisions, your accounts, and a proper launch.

Inspect the code on GitHub →

05 · Poker

And when the problem is genuinely hard.

A real-time, multiplayer platform with a custom rules engine and AI opponents, built for a university society. Proof the engineering under your build holds up under real pressure.

Play-money · student society

This is a play-money platform built for a university poker society. There is no gambling anywhere on it. No real money in, no real money out. It’s here purely as an engineering exhibit.

Under the hood

  • A correct, deterministic No-Limit Hold’em engine, with hand evaluation and side pots.
  • Tiered AI bots: opponents at different strengths.
  • A live Elo ranking ladder across players.
  • Real-time sync over WebSockets. Every seat sees the same table, instantly.
  • Secure accounts, and a production guard that refuses to boot insecurely.

Why it’s here

You don’t need a poker engine. But the same engineering that makes this correct, fast, and reliable under real-time pressure is exactly what goes into your build.

Guest mode. One click, no signup.

Booking

Seen enough? Tell me what's slowing your business down.

20 minutes. No pitch, no obligation. You'll leave knowing whether a 10-day build is right for you, and roughly what it would cost.

Book the free call. Leave with a fixed price.
  • Fixed price
  • You own everything
  • No balance until it works
Get your fixed quote →