Approach

No black box. This is exactly how I work.

Most people aren't afraid of a website — they're afraid of the process: vague quotes, missed deadlines, a developer who vanishes. Below each phase, what you do, and honestly: what can go wrong and how I handle it.

The six phases

First meeting

~45 min

What happens: A no-obligation chat (online or at your place). I listen more than I talk: what you have, what you want to achieve, the budget and timeline.
What you do: Speak honestly about your business and expectations. No preparation needed.
What you get: A clear picture of whether we're a match — and if not, honest advice on where to go.
If it goes wrong: No risk: it's free and binds you to nothing.

Scope + quote

2–4 days

What happens: I put in writing what I build, what I don't, what it costs and when it's ready. One document, no asterisks.
What you do: Read critically. Question anything unclear — that's exactly the moment.
What you get: A fixed quote with scope, price and schedule. Valid 30 days.
If it goes wrong: Scope too expensive? We trim together until it fits. Better a small project that's right than a big one that derails.

Design

~2 weeks

What happens: No static mockups that never look like that. A first clickable version on a staging environment, iteratively refined with your input.
What you do: Click through, give feedback. You don't need to be a designer — 'this feels off' is usable input.
What you get: A working, clickable version on your own staging URL.
If it goes wrong: Taste differences are normal. We work in rounds; the package defines how many are included.

Development

2–6 weeks depending on scope

What happens: The real build: site + admin + integrations. Interim demos so you're not in the dark for four weeks.
What you do: Provide content (text, photos) and test on staging. The faster your input, the faster delivery.
What you get: A complete, tested site on staging — for you to test yourself.
If it goes wrong: Delay due to missing content shifts the deadline proportionally — which is why we plan content delivery explicitly.

Launch

1 day

What happens: No leap in the dark. Soft launch: redirects live, sitemap submitted, ranking monitored. For migrations: zero downtime.
What you do: One final approval. Then it goes live on your domain.
What you get: Live site, old URLs permanently redirected, monitoring active.
If it goes wrong: Something wrong after launch? The first 30 days I fix bugs for free.

Aftercare

ongoing or stopped — your choice

What happens: A site isn't 'done' at launch. 30 days free bug fixing, then an optional Care/Plus/Scale subscription or by the hour.
What you do: Decide whether you do maintenance yourself, take a subscription, or work by the hour. No obligation.
What you get: A working site, the code in your GitHub repo, and a clear maintenance agreement.
If it goes wrong: No lock-in: the code is yours. If we ever stop, everything keeps working.

Underlying principles

Written over spoken

What we agree is on paper. Not out of distrust — out of respect for everyone's memory.

Demos over promises

You see working software at every step, not just an invoice and a promise.

Honest about risks

I name up front what can go wrong. A surprise afterwards always costs more than a conversation before.

Sound like a process you can be confident in?

It starts with a no-obligation chat. No quote pressure, no sales pitch.

Schedule a chat