Skip to content

Website design & rebuild

A clear site designed for speed and a lower-friction path to action.

A website is not a digital brochure: it is where interest becomes a qualified request. We treat it as a commercial asset, with the message decided before the design and measurement planned before launch.

Direct answer

What does a website project actually involve?

It starts with message and architecture, then copywriting, design, development, SEO and measurement — in that order, to reduce avoidable rework once design and development begin.

Important considerationWe do not promise a fixed timeline, ranking gains or zero traffic loss. A rebuild plan inventories URLs, redirects and measurement to reduce and detect migration risk.

Design blueprint

The blueprint of a page that has to convert.

Before any art direction, each page is described through four zones and the exact role of each. A zone that serves none of these roles is removed, regardless of how good it looks.

Message: what you do, for whom, and why it is credible — readable without scrolling and without jargon. Journey: the sequence of questions in the order the visitor asks them, not the order of your org chart. Proof: what makes the promise verifiable. Action: one main action per page, stated with what the visitor actually gets from it.

Process

Seven steps, in an order that protects the outcome.

Art direction comes after message and architecture, to reduce avoidable rework once design and development begin.

  1. 01

    Strategy & message

    Audiences, promise, objections, available proof, expected action on each page.

  2. 02

    Architecture

    Sitemap, journeys by intent, hierarchy of conversion pages.

  3. 03

    Copywriting

    Decision-oriented writing: what the visitor needs to understand, believe, then do.

  4. 04

    Art direction

    A visual system consistent with your positioning, built into reusable components.

  5. 05

    Development

    Careful build, accessibility, mobile compatibility, editable content depending on the technical choice.

  6. 06

    SEO & performance

    Indexable structure, metadata, load time, redirects in case of a rebuild.

  7. 07

    Measurement

    Conversion events defined and verified before launch.

Example framework used during the engagement. It is adapted to your context, data and decisions.

Rebuild

A rebuild is prepared with an inventory, not a mockup.

A rebuild's risk is not visual: it lies in URLs that disappear, content that performed and gets abandoned, and measurement reset without anyone noticing.

We start from what exists: traffic-bearing URLs, conversion paths and redirect needs. A temporary or lasting drop remains possible; the plan is designed to detect it quickly and define remediation.

Before launch
URL inventory, redirect plan, content kept, conversion events verified.
After launch
Monitoring of errors, redirects and measurement, over a period agreed at framing.

Formats

Three scopes, one standard.

  • New build

    A first structured site, when positioning has just been clarified or the business is scaling.

  • Rebuild

    Taking over an existing site: preserving SEO equity, redirect plan, fixing friction points.

  • Landing page

    A dedicated page for a campaign or offer, designed to be tested and measured on its own.

Deliverables

What is handed to you.

  • Framing note: audiences, message, conversion objectives.
  • Sitemap and journeys by intent.
  • Mockups of key templates.
  • Content written or integrated from your material.
  • Site built, tested and reviewed.
  • Handover: access, short documentation, walkthrough.

Read next

Related pages in English.

  • Website by subscription

    The same standard, with the investment spread over time.

  • SEO & GEO

    A new site is a good moment to fix technical foundations before content.

  • Google Ads

    A conversion-focused site changes how paid traffic performs.

FAQ

Frequently asked questions

Which technology or CMS do you use?

It depends on the need: expected editorial autonomy, page volume, performance constraints, existing integrations. We do not favour a single technology and we explain the trade-off before locking it in.

Will we be autonomous to edit the site afterwards?

That is a framing goal. If editorial autonomy is a priority, we choose a solution that allows it and plan the handover training. Some structural changes will remain technical.

How long does a project take?

It depends on the number of templates, content production and how fast approvals move. The schedule is set in the proposal, with the dependencies that can shift it.

Does a rebuild hurt SEO?

The risk exists if ignored. We inventory URLs and existing traffic, plan redirects and keep the content that performs. A temporary variation remains possible after launch.

Do you provide maintenance afterwards?

Yes, depending on the contract: updates, fixes, evolutions. That is also the purpose of the subscription formula if you prefer to spread the investment.

Next step

Let's look at what your site needs to produce.

Before discussing mockups, we clarify the expected action and the volume of demand the site needs to support.