How I build a website
A clear method, in 4 stages, with the duration and deliverable of each. It exists for a simple reason: once the project starts, you must be able to check that what happens matches what was announced.
- 01 First call 20 minutes
- 02 Proposal 5 business days
- 03 Design and build 14 to 30 days depending on the plan
- 04 Go-live and measurement 1 day
A verifiable method, no vague promises.
At a glanceFirst call (20 minutes, deliverable: written summary); Proposal (5 business days, deliverable: detailed quote with schedule); Design and build (14 to 30 days depending on the plan, deliverable: complete site on staging); Go-live and measurement (1 day, deliverable: dated control protocol).
My method
Four stages, one clear result.
From understanding your situation to a live, measured site: each stage produces a concrete deliverable you can validate.
-
First call 20 minutes
I look at your current site, your Google position, your direct competitors and what answer engines already say about you. Free and without commitment: if your need falls outside my scope, I say so then, not after you sign.
DeliverableWritten summary
-
Proposal 5 business days
Written scope, named deliverables, fixed price and calendar. No ranges: the entry plan is €39/month with a €490 setup fee, and it does not move mid-project.
DeliverableDetailed quote with schedule
-
Design and build 14 to 30 days depending on the plan
I write your copy from a 45-60 minute guided interview. The site is built in HTML and CSS, without a CMS and without third-party plugins. You see it on a staging address before any go-live, and you request adjustments at that point.
DeliverableComplete site on staging
-
Go-live and measurement 1 day
Before go-live, the site goes through a control protocol: speed, mobile, forms, basic accessibility, indexability. You receive the dated summary and the PageSpeed Insights link so you can repeat the measurement yourself.
DeliverableDated control protocol
Verification
What you can check at every stage.
Concrete deliverables, named and dated. At any time you know where the project stands and what has been delivered.
-
Written summary
A clear view of your current situation.
-
Detailed quote with schedule
A precise scope, a fixed price and a calendar.
-
Complete site on staging
A complete version online, to test before go-live.
-
Dated control protocol
A dated summary and the PageSpeed Insights link.
Technical
Technical choices, and why
A simple, controlled approach. Fewer dependencies, fewer parts to watch.
-
Static HTML, no CMS
No CMS or plugin to update. Static reduces some risks, provided forms and connected services are secured: that is what maintenance covers. The accepted downside: you do not change the structure yourself, you ask me.
-
Zero JavaScript by default
The content is readable without running a single script. That is what makes it readable by answer engines, many of which do not execute JavaScript at retrieval time.
-
Self-hosted fonts
No call to a font CDN. Less latency, and no visitor data sent to a third party.
-
A single structured-data graph
Site entities (company, founder, pages, services) are linked to each other by stable identifiers rather than declared in separate blocks.
My position
What I do not do
I stay focused on what I know how to do, and I say so from the first call.
-
No WordPress, no Wix
No visual builder either. If that is what you want, I am not the right supplier and I will say so on the first call.
-
No real-time stock shop
E-commerce with real-time stock is not my trade.
-
No guaranteed position
Not on Google, and no guaranteed citation in ChatGPT. Nobody can keep that promise; two identical queries already return different sources.
-
No automated 40-page report
A summary nobody reads is worth nothing.
Project
Take stock of your online presence.
A first conversation to understand your goals, identify the levers and define the next steps.
Request a free first call Free first call, no commitment. Response within 48h (business days).
Measurements taken on . Measurements taken with Lighthouse 13.4.1, commands published on the Sources page.