What I build, and what it costs.
Six things, explained properly. Prices are honest starting points — the real number depends on scope, and I will give you that in writing before you commit to anything.
Business website
Best for: Trades, professional services, anyone whose site is a shop window
Written in HTML, CSS and PHP by hand — no page builder, no theme, no plugin stack to maintain. That means there is nothing installed that you are not using, nothing to update at 3am, and nothing that breaks because a third-party extension changed.
Every page is built to pass Core Web Vitals on a mid-range phone over 4G, not just on a desktop with fibre. Semantic markup, proper heading structure and schema.org data are in from the start, because retrofitting them later is how sites end up invisible to search.
CMS website Most asked for
Best for: Businesses that publish regularly — news, listings, case studies, events
Everything from the business website, plus a bespoke admin area so you can add and edit content without touching code or paying me to change a phone number.
I build the CMS around your actual content types. A letting agent gets properties with photos, prices and availability. A restaurant gets menus and opening times. You are not fighting a generic page builder to describe something it was never designed for.
Role-based logins mean staff can update what they are responsible for and nothing else. Every change is logged, so you can see who edited what.
Online shop
Best for: Selling products or taking bookings and deposits online
Stripe for card payments, so money reaches your account directly and card details never touch my server. Stock levels, variants, delivery rules and VAT handled properly.
The checkout is the part most shops get wrong. Every extra step and every slow page loses sales, so it is built as few steps as the transaction allows and tested on a phone on a bad connection — which is where most people will actually buy from you.
SaaS & web applications Most asked for
Best for: Turning a process, a spreadsheet or an idea into software people log in to
If you run something on a spreadsheet that three people email back and forth, that is usually an application waiting to happen.
I build multi-user systems with proper authentication, role-based permissions, subscription billing and an audit trail — the parts that are unglamorous but decide whether software survives contact with real users. Security is designed in: hashed credentials, CSRF protection on every form, parameterised queries throughout, rate limiting, session hardening.
The client portal on this website is an example. Messaging with file and voice attachments, invoicing, project tracking, an approvals workflow and a full audit log — all built from scratch.
App development
Best for: Something that needs to live on a phone — offline use, camera, push notifications
Most businesses that ask for an app need a progressive web app: it installs to the home screen, works offline, sends push notifications, and needs no App Store approval to ship a fix. It costs a fraction of native and updates the moment you want it to.
Where you genuinely need native — deep hardware access, App Store presence — I will tell you that plainly rather than sell you the thing I would rather build.
Either way the app and the website share one backend and one database, so there is a single source of truth instead of two systems drifting apart.
Hosting & care
Best for: Anyone who would rather not think about their website until they need something changed
Your site hosted on UK infrastructure, backed up daily, with SSL kept current and uptime monitored. If something goes down I generally know before you do.
Plans include support hours each month for content changes, new pages and small features. You can see exactly how much you have used in your client area, so there are no surprise invoices and no argument about what was included.
No contract beyond the month you are in. If you want to leave, you take the code and a full backup with you — I have no interest in holding anyone's website hostage.
No surprises, either direction.
The same five steps whether it is a five-page site or a platform.
-
01
We talk
Twenty minutes on the phone about what the business actually needs. Not a sales call — if I am the wrong fit I will say so and point you somewhere better.
-
02
Fixed quote, in writing
Scope, price and timescale on paper before anything starts. The price does not move unless you ask for something outside that scope, and then you approve the change first.
-
03
Build, in the open
You get a client area login from day one. Progress, milestones, files and a direct line to me — no wondering what is happening.
-
04
Review and launch
You sign off before anything goes live. Tested on real phones, not just a desktop browser window made narrow.
-
05
After
Your code and data are yours. Take a care plan or take a backup and go elsewhere — both are fine, and I will not make the second one difficult.
Not sure which one you need?
Most people aren't. Tell me what the business does and what is not working — I will tell you what it actually needs, even if that is less than you came for.
Start a project