Services
Three kinds of work: business websites, custom web apps, and automation. Every project gets a fixed written quote before any work starts, and everything I build is yours outright when it ships.
Business sites and landing pages
What it is
A website that loads fast, reads properly on a phone, and does the job you need it to do: say what you sell, and make it easy to get in touch. That covers a new site from nothing, a single landing page behind one product or one campaign, and rebuilding a site you already have.
If your current site is on a page builder, an old theme, or a platform you pay for every month, I can rebuild it as a static site. Static means every page is prepared in advance, so when a visitor arrives there is nothing left to compute. That is why these sites are fast. Your content moves over, your address stays the same, and the old site stays up until the new one is ready, so visitors never see a gap.
Who it suits
A business whose customers need to find it, read it on a phone, and act on it. It suits you if:
- Your site is slow on a phone
- The bill for it grows every year
- Changing one line means finding a developer and waiting
- You have no site at all and would rather start with something small and fast than something large and fragile
If what you have is working and the real problem is speed or a short list of fixes, I would rather work on the site you already have, on the platform you are already on, than talk you into a rebuild you do not need.
What you receive at the end
This is what a new build or a rebuild delivers.
- Every page built and checked on a phone screen first
- Your existing text and images moved over, cleaned up where they need it
- A contact form that lands in your inbox
- Working search engine basics: titles, descriptions, a sitemap
- Free hosting, set up in your accounts and in your name, not mine
- Automatic publishing: a saved change is live in minutes, and every earlier version is kept
- Your pages as plain text files, and a written guide to editing them yourself
If instead I am working on the site you already have, on the platform it already runs on, what you get is the specific fixes in the quote and a written note of what I changed and why.
The part I care most about
On a site I build or rebuild, your pages are stored as plain text in a simple format called Markdown, which means the words on your website are just words in a file. If you can write an email, you can read and edit them.
AI coding assistants changed what a non-technical owner can do with files like that. With the guide I write for your specific pages, you can ask an assistant to update your opening hours, add a news post, or create a new page, and see it live minutes later. No developer, no invoice, no waiting. In the ordinary course of editing, each change you save leaves the version before it in the history, so a change you regret can be reversed; the worst realistic outcome is undoing it, which the guide also covers.
This part applies to websites, and specifically to a site I build or rebuild. Fixes to the site you already have, on the platform it already runs on, leave your pages where they are, so plain text files and an editing guide are not part of that work. Web apps and automation are yours in every other sense, and I set out below exactly what you get with those.
Custom web apps
What it is
Software that runs in a browser and does part of the job of running your business. That might be a dashboard, an internal tool that finally retires a shared spreadsheet, or a client portal where your customers sign in and see their own orders, files, or invoices without emailing you to ask.
I start from the daily reality: who types what, who needs to see what, and what nobody should be able to change by accident.
Who it suits
A business that has outgrown a spreadsheet, or that pays every month for a tool that almost does the job and cannot be made to do the rest. It suits you if:
- The same information gets retyped in more than one place
- A routine customer question means digging through folders
- How the business is doing lives in four different systems
This is not a rewrite of software that already works for you. If a tool you own does most of what you need, connecting it to the rest of your business is usually cheaper than replacing it, and that is the automation section below.
What you receive at the end
- A working application at your own address, built for the way your business runs
- Every account in your name: the code, the hosting, and anything it depends on
- The full source code, kept in the same kind of repository described above, so any competent developer can take it over
- A written guide to using it, in plain language, for the people who will use it daily
- A written record of what it does and how it is put together, so a later change starts from facts instead of guesswork
- Changes after delivery quoted by the task, with no retainer and no ongoing fee to me. If it breaks in the first 30 days after delivery, fixing it is on me, not a new quote.
One difference from the website side: changing how an app behaves is developer work, not something you do yourself.
Automation
What it is
Work a computer should be doing instead of a person. Connecting two systems you already pay for so information moves between them by itself. Collecting information from websites on a schedule and dropping it into a spreadsheet you can actually read. Scripts that run a repetitive job from start to finish while nobody watches.
Connecting systems, usually called API integration, means using the official access points that software provides for exactly this purpose, so your order system can tell your accounting system what happened without a person copying it across. Collecting information from a website, often called scraping, means reading the public page the way a visitor would, automatically, at whatever hour suits you.
Who it suits
A business where somebody loses hours every week to the same mechanical task:
- Copying orders into a spreadsheet
- Checking competitor prices by hand
- Renaming and filing documents
- Pulling the same report every Monday morning
The test is simple. If you can write the task down as a list of steps that do not need judgement, it can usually be automated. If every case needs a decision from someone who knows the business, it usually cannot, and I will tell you which one yours is before you spend anything.
What you receive at the end
- The automation running where you can see it, on a schedule or on demand
- Everything in your own accounts, so it keeps running whether or not I am involved
- Written instructions in plain language for starting it, stopping it, and changing what goes into it
- A written note of how it tells you when it fails, so you hear it from the tool and not from a customer
- The scripts themselves, written to be read, with plain notes through them explaining what each part does, so another developer can take them on
- A written note of what it does not cover, so nobody assumes a case it was never built for
Anything that reads from a website I do not control carries one risk: those websites change, and when one changes the automation can stop working. I build these to stop loudly and tell you rather than fail quietly and leave you with bad numbers. If something breaks in the first 30 days after delivery I fix it. Changing what the automation itself does, so that it collects something different or sends it somewhere new, is new work, and I quote that before I start it.
How a project runs
- You describe the situation and what a good outcome looks like.
- I ask questions until the job is clear, then reply with what I would build, what I would leave alone, and a fixed quote.
- If the quote works for you, I build it where you can watch it take shape, at a preview address when there is a site to look at, while whatever you are running now stays untouched.
- You review it and I make adjustments, as many rounds as it takes to get the agreed thing right. Something genuinely new is a separate quote, and I say so at the time.
- It goes live in your own accounts, and you get the written handover for what I built.
There is no retainer and no ongoing fee to me. If you want changes later, you can hire me by the task.
What it costs to run
A website built this way runs on free hosting tiers that exist for exactly this kind of site. After the build, your recurring cost is the domain name registration you already pay for. There is no platform subscription and no hosting bill. The work page shows this site’s own running costs as proof.
Web apps and automation are different, because they keep doing work after they ship. Some of them fit on the same free tiers. Some need a small paid service behind them, for storing data, sending mail, or running on a schedule. I price that out in writing before you commit, so the running cost is a number you agreed to and never a surprise on a card statement.
Start with what you have now.
Tell me which of the three you think you need, or just describe the problem and let me work out which it is. I will come back with what I would do about it and what it would take. If what you have is fine as it is, I will say so.