Public tenant form
One clean, public form for tenants to log a maintenance request. No account, no friction, no lost message.
The proof
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
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.
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.
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
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???
Oakwood Ops
Maintenance · one queue
7
Open
2
Urgent
12
Resolved this week
02 · What was built
The whole system a small property team actually runs on. No more, no less.
One clean, public form for tenants to log a maintenance request. No account, no friction, no lost message.
One place for the team to see every request, its status, and its history. The spreadsheet that broke, replaced.
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 document that scoped the system before a line was written. Proof the judgment happens up front, not mid-build.
A standalone, plain-English guide handed to the team. Proof of polish and communication, not just working software.
03 · Under the hood
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.
04 · Try 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 →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
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.
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
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.