Process
Hiring someone to build your website is a leap of faith. This page exists so it doesn't feel like one — here's exactly what happens from your first message to long after launch, so you know what to expect at every step.
It starts with a message. You tell me what your business does and what's getting in the way — a website that's embarrassing to share, bookings lost to phone tag, or simply nothing online at all.
There's no pressure and no cost here. This is where I listen and figure out whether I'm genuinely the right person for what you need. If I'm not, I'll say so and point you somewhere better.
If it feels like a fit, we talk properly — a relaxed call where I learn how your business actually works, who your customers are, and what success would look like for this project.
This is the most important half-hour of the whole process. You don't need to prepare anything technical — just come as you are.
Now I put it in writing. You receive a clear proposal: what I'll build, what's included, what it costs, and roughly how long it'll take. The agreed price is fixed for the agreed scope — if you request additional work, it's discussed and quoted before that work begins.
Once you're happy, we agree it in writing. This protects us both and means nobody's working on assumptions.
Before any design, we map the site. Which pages, what goes on them, how someone moves from landing to booking or enquiry. It's the blueprint — cheap to change now, expensive to change later.
This is where it becomes real. I design the look of your site in Figma — first the layout, then the full visual design — and we refine it together here. Design adjustments are easiest to handle at this review stage and are covered within the agreed revision rounds, long before any code exists.
You'll never see your finished site for the first time at launch. You watch it take shape and shape it with me.
Once you approve the design, I build it — properly, on a private staging link you can visit any time. No black box, no waiting months for a big reveal. You watch it come together.
A site needs words and images. Some clients have these ready; most don't, and that's completely normal. I'll tell you exactly what I need and when, and I can guide you on writing it or work with what you have.
Content is the single most common reason projects slow down — so I make this part as painless as possible.
You review the site properly and we polish it together. This is a dedicated, structured round of feedback — not endless tweaking, but a clear, generous window to get everything right.
Before anything goes live, I test everything. Every page on phones, tablets and desktops. Every form. Speed. Security. Different browsers. The unglamorous, essential part that separates a professional site from a risky one.
The exciting part. I take your site live — domain, secure connection, the works — and make sure everything works in the real world exactly as it did in testing.
After launch, I don't vanish. You get a straightforward handover so you understand what you have, plus a warranty period where I fix anything that isn't working — free. When you're ready to grow, I'm here for that too.
You'll always know where your project stands. Throughout, you talk directly to me — the person actually building your site, never a queue or an account manager.
One point of contact — me, start to finish.
Regular updates — and the staging link means you can check in any time.
Replies within about a day — usually much sooner. If I need longer, I'll tell you why.
Calls when they help — when a decision needs it, not for the sake of meetings.
Feedback is a built-in, expected part of the process — not an interruption. Here's how it stays smooth for both of us.
Each project includes a set number of revision rounds, agreed in your proposal from the start. That structure isn't about limiting you — it's what keeps the project moving, the price predictable, and "just one more small change" from quietly turning into a different project.
The best feedback comes consolidated: rather than lots of separate messages, a single clear list per round lets me work through everything efficiently. When you approve a stage, we move forward together — and if something genuinely needs rethinking later, we'll talk about it honestly rather than pretending it was always in scope.
I'll always give you a realistic timeline with your proposal. What I won't do is promise a date I can't be sure of. A few things genuinely shape how long a project takes:
The honest summary: most small sites take a few weeks; larger ones a couple of months. You'll always have a realistic estimate, and you'll always know if something changes it.
"Launch" isn't just flipping a switch. Before your site goes live, I work through a full pre-flight check:
Launch day is a beginning, not an ending.
If something I built isn't working, I put it right — free.
For updates, backups and peace of mind — entirely your choice.
Getting started
It depends on size and how quickly things like feedback and content come together, but most small sites take a few weeks and larger ones a couple of months. You'll get a realistic estimate with your proposal.
Website projects can start from one of my published packages — see the pricing page. Custom applications, integrations and more advanced digital solutions are scoped and quoted individually. Either way, you get a clear price for the agreed scope before any work begins.
That's completely normal, and it's my job to help. Bring the problem; we'll shape the solution together.
New ideas are welcome. If a change affects the scope or timeline, I'll tell you honestly before we proceed — no silent surprises on the invoice.
Yes. Most of the process works beautifully remotely, wherever you are.
Building it
Yes — if you have a brand or designs already, I'll work with them. If you don't, design is part of what I do.
You can, though content is the most common reason projects slow down, so earlier is smoother. I'll tell you exactly what I need.
A set number of structured rounds, agreed in your proposal from the start, so you always know what's included.
Always. Every site is built and tested to work beautifully on phones, tablets and desktops — most of your customers are on their phones.
Yes — booking and online payments are among the most useful things I build.
Yes. Custom web applications, dashboards, internal tools and integrations with other services are part of what I do.
Yes — you approve the design before development, and you can visit a private staging link throughout the build. No surprise reveal at the end.
Owning it
For purchased projects, the agreed website deliverables and rights are transferred according to the project agreement after full payment, and your domain, content and accounts stay yours. Managed Websites use a different service model, with a defined buyout option agreed before the project starts.
For purchased projects, yes — the custom code written for your project is handed over according to the project agreement. There's no proprietary platform you're stuck paying for. On a Managed Website, the implementation is part of the active service, with a defined buyout option.
For purchased projects, I can set up the domain, hosting and relevant accounts in your name from the beginning where appropriate. Managed Websites follow the service model defined in the agreement.
Absolutely. Whether it needs a refresh, a performance fix or a full rebuild, I'll give you honest advice on what's actually worth doing.
If you’d like. For purchased websites, ongoing Care is always optional. Managed Websites include maintenance and have a 12-month initial term.
Not at all — that's my job. I'll explain anything you want to know in plain language.
That's the whole journey — no mystery, no jargon, no pressure. If it sounds like the kind of process you'd want to be part of, I'd love to hear what you're working on.
Start a project →
