What I Can Build For You
I build websites and web apps for businesses that need them to genuinely work — quick, dependable, and easy to change later. You bring the problem; I handle the technical side and explain it in language you can actually use. Here is what I can take off your plate.
Websites & app interfaces
The part your customers actually touch.
- Your design, built properly: Send a Figma file, a screenshot, or a sketch on paper. You get it working on desktop, tablet, and phone — not "close enough on mobile".
- Pages that load fast: Most people leave a site that takes more than three seconds. Speed is something I build in from the start, not patch on at the end.
- Room to grow: Built so that adding your tenth feature is as straightforward as your second, instead of triggering a rewrite.
- Found and usable by everyone: Works with keyboards and screen readers, ranks properly on Google, and looks right when someone shares the link.
The engine behind it
Accounts, data, and the rules that keep everything correct.
- APIs your other systems can talk to: Typed GraphQL, or REST where that suits you better. If you outgrow one service, I can federate several behind a single endpoint so the apps calling them never notice.
- Sign-in that you can trust: Google, email, or company logins, with the right people seeing the right things. I use proven providers rather than inventing security myself.
- Your data, organised: A database shaped so your reports stay quick whether you have five hundred records or five million.
- Connected to your other tools: Payments, email, file storage, spreadsheets. Wired together so nobody on your team is retyping the same information twice.
- Work that runs in the background: Imports, exports, reports and scheduled jobs run on a proper queue, so a slow task never leaves someone staring at a spinner.
- Quick to fix when it matters: Clear logging and sensible error messages, so a problem at 2am takes minutes to find, not days.
Launching & keeping it online
Live, backed up, and quietly watched.
- Live without the drama: Hosted on infrastructure that copes when you get busy and costs very little when you are quiet.
- Updates without downtime: New features go out in the middle of the working day without taking your product offline.
- Someone watching: Automatic alerts when something fails, so I usually know before your customers do.
- A smaller monthly bill: Trimming cloud costs is genuinely a hobby of mine. I will happily spend an evening saving you money every month.
Planning & second opinions
Before you spend the budget, or after you inherited something worrying.
- A plan before the spending: A written outline of what to build, in what order, and where the first portion of the budget should go.
- An honest review: If what you already have is fine, I will say so. If it is not, you get a prioritised list of fixes rather than a sales pitch.
- The right size of solution: I will talk you out of complexity you do not need. Most products are not big enough to justify the architecture people try to sell them.
- I already know your world: Three years building logistics and operations software — jobs, fleets, drivers, rates, warehousing and the documents that follow them. If you move things for a living, I will not need the vocabulary explained.
- Nothing locked to me: I choose tools your team can hire for and maintain long after the project ends.
AI that does a real job
Useful automation, not a chatbot bolted on for the announcement.
- Stop typing in paperwork: Photograph or upload a document and have it read into proper fields — Optical Character Recognition with a checking step, so nobody rekeys a delivery note. I do this in production today.
- Answers from your own documents: Your staff or customers ask a question in plain English and get an answer pulled from your files, with a link to where it came from.
- Assistants that can actually do things: Look up an order, check stock, book a slot. Not just talk about it.
- Tested, not guessed: Checked against real examples so the answers stay consistent, instead of being impressive in the demo and wrong in practice.
Apps for staff in the field
For the people who are not sitting at a desk.
- One app, both phones: A single React Native codebase on the App Store and Google Play, rather than paying to build the same thing twice.
- Keeps working without signal: Your team can carry on in a basement or a dead spot, and everything they did syncs once the phone finds a network again.
- Built for a working day: Big targets for gloved hands, staying signed in across a shift, and camera capture where paperwork used to be.
- You find out before they complain: Crash and error reporting wired in from day one, so a failure reaches me instead of quietly stopping someone working.
Working with your team
The parts of a project that are not code.
- See it before it is built: A clickable prototype, so we agree on how it should work while changes are still cheap.
- Progress you can see: A link you can open any time to watch it come together, plus a short update every week. No month-long silences.
- Handover your team can use: Documentation written in plain terms, so bringing in the next developer takes days rather than weeks.
How I work
- 01
We talk it through
A conversation about the problem, not the technology. You get a written proposal: what gets built, what deliberately does not, how long it takes, and what it costs. Free, and yours to keep even if you decide to go elsewhere.
- 02
You watch it happen
A link that updates as I work, and a short summary every week. If something is heading the wrong way, you can say so on day three instead of discovering it on day thirty.
- 03
It becomes yours
The code, the accounts, and the documentation all transfer to you. Two weeks of support after launch while your team settles in, and I stay reachable after that.
Engagement
Project build
One agreed price for one agreed outcome, start to finish.
Best if you know what you want built.
Retainer
A set number of days each month, reserved for you.
Best for steady improvements and someone on call.
Health check
A written review of what you already have, delivered in about a week.
Best if something is slow, fragile, or inherited.
Questions I usually get
I am not technical. Is that a problem?
Not at all — most of the people I work with are not developers. I will explain things in plain language and I will never ask you to approve something you do not understand.
What is this going to cost?
It depends on what you need, which is exactly why the scoping conversation is free. You will have a fixed figure before any work begins, so there are no hourly surprises.
How long will it take?
A small project runs a few weeks; a full product is usually a few months. The proposal gives you a realistic date rather than an optimistic one.
I already have a developer or a team.
That is fine — I will fit around them. I have spent three years in cross-functional teams and I am comfortable being the extra pair of hands rather than the one in charge.
Do I own what you build?
Completely. The code, the repository, the hosting accounts, and the documentation are all yours. Nothing is tied to me.
What if something breaks after launch?
Two weeks of support are included as standard, and I do not disappear afterwards. Plenty of my work is helping with things I did not originally build.
Tell me what you're building
A rough idea is enough. Tell me what you are trying to fix and roughly when you need it, and I'll tell you honestly whether I'm the right person — including when the answer is no. If you'd rather look around first, the projects page has the work itself.