Selected work
01A paper booking process, gone
Hundreds of pieces of equipment lent across three sites on a paper diary and a shared inbox. Replaced with one system the technicians maintain themselves.
Everything was in a different file
A department planning courses across dozens of scattered documents. Now one tool, used daily by twenty-plus staff.
Word of mouth, and nowhere to send it
An independent travel agent whose referrals had nowhere to land. A site built from the brand she already had, and an enquiry form that does the first twenty minutes of the conversation.
How I work
Fixed price
Quoted before I start, based on the problem rather than an hourly rate. If it turns out to be bigger than we thought, we talk about it before anything changes.
Yours at the end
Your hosting, your accounts, your code. I build things that keep working without me, and I'd rather you could leave than feel you couldn't.
Plain English
You don't need to know what you want built. Describe what isn't working and I'll tell you what I think would fix it, in language you can repeat to someone else.
Who you'd be working with
I build for people who aren't technical
I teach interactive media and games at a further education college, and I've spent years building the tools my own department runs on — booking systems, planning software, trackers. All of it used daily by people who never asked for software and just want their afternoon back.
That's shaped how I work. I'm less interested in the newest way to build something than in whether it'll still be running in three years, and whether the person using it can work it out without a manual.
Freelance work happens evenings and weekends, which I'm upfront about. It means I take fewer projects and finish the ones I take.
Got something in mind?
Tell me the problem, not the solution. I'll tell you honestly whether I'm the right person.