Website development stages: from brief to launch

The first time you order a website, the price is rarely what keeps you up at night. The silence does. You pay, and then nothing. A week goes by. Then a message lands: “here’s the design.” Then quiet again. You start to wonder whether the project has stalled or quietly drifted somewhere you never asked it to go, and you have no handle to grab.

It doesn’t have to feel that way. Building a site is a sequence of stages, and each one has a clear shape: something goes in, something comes out, and somewhere in the middle there’s a moment where your decision sets the direction. Below is the whole route, from the first conversation to a live site, the way it runs for us. You should always know what is happening now, what comes next, and where we are waiting on you.

Stage 1. Discovery and brief

We open with questions, not Photoshop. Who do you sell to? What makes a buyer pick you over the firm next door? And once someone lands on the site, what do you want them to do: send an enquiry, place an order, pick up the phone? Skip those answers and even a gorgeous mockup is just wallpaper.

What comes out of this stage is an agreed brief, and on bigger projects a spec on top of it: the page structure, the list of features, the integrations, the languages. That document is not paperwork for its own sake. It is what stops you paying twice. We unpacked why cutting this corner ends up the expensive option in a separate piece on what a brief and a spec are.

An hour on the brief saves a day on the build. Budgets rarely blow up over code. They blow up over the sentence “but we assumed you knew we meant it differently.”

Stage 2. Prototype and structure

Colours and fonts come later. First we lay out a prototype: a plain black-and-white skeleton of every page. It shows which blocks follow which, the order your argument unfolds in, and where the buttons that ask for action sit.

Right now changes are cheap. Nudging a block in a wireframe takes a minute. Pulling that same block out of a finished design, or a half-built site, takes the afternoon. That gap is the whole reason we ask you to read the prototype slowly and tell us whether the order of blocks makes sense to your customer, whether every service and selling point is actually there, and whether it’s obvious where a visitor is supposed to click. Three questions, and they save a lot of grief downstream.

Stage 3. Design

Once the structure is signed off, the visual work begins. We lay your brand over the skeleton: colour, type, photography, icons, a little motion. None of it is decoration for the sake of it. Every screen is being pushed toward the one action the prototype set for it.

We hand over design in stages, not in one drop. You see the homepage or another anchor screen first, we settle the style together, and only then does it roll out across the rest. So you never open a folder of fifteen finished screens and realise on the fifteenth that the whole look is wrong for you. Mobile is in the picture from the opening sketch, and we go into why that matters so much in responsive and mobile.

Stage 4. Build and development

Now the approved design turns into something you can click. We write the code, hook up the forms and the integrations (your CRM, payments, analytics), and add an admin panel or CMS if you plan to edit content yourselves.

This is where we need the real materials from you: the copy, the photos, the logo files, the logins for your domain and services. It’s also where most delays are born. The design is finished, the text never arrives, and the site sits dressed in placeholder gibberish for a month while everyone waits on a paragraph. Other things move the timeline too, and we walk through them in how long it takes to build a website.

Stage 5. Testing (QA)

Nothing goes live unchecked. We run the site across phones, tablets and laptops, in different browsers, and we push on every part of it: does each form send, do the links land where they should, does an enquiry actually reach you, how quickly does a page appear.

What we check	What we look for
Responsive	Phone, tablet, desktop, no broken blocks
Forms	The enquiry really reaches your messenger or CRM
Speed	Load time, Core Web Vitals
SEO base	Headings, meta tags, schema markup, sitemap
Content	No “Lorem ipsum”, no dead links

QA is the first thing people try to trim when the budget gets tight. It also separates a site that does its job from one that’s merely “basically ready.” Picture a customer on the train, thumb on the screen, tapping your product page while it spins. They give it a beat, then back out and tap whoever loaded first. That gap is what this stage closes.

Stage 6. Launch and support

Launch is the publishing day: the site goes onto your domain, SSL is switched on, analytics connected, access handed over. We don’t disappear once the button is pressed. For the first few days we keep an eye on it and patch the small things fast.

Then the ordinary life of a site starts. New promotions, a tweak here, a security check there, the odd edit: that’s support. We bill it plainly, €60/h for routine work and €90/h when you need something fixed in a hurry, and that’s the whole price. You pay for the hours we spend, not a retainer that sits there in case.

Pulled together, the route looks like this:

1. Discovery: pin down the task, lock the brief and spec.
2. Prototype: agree the structure before anyone draws a thing.
3. Design: layer the brand on, screen by screen.
4. Build: write the code, wire up the integrations.
5. QA: test the devices, the forms, the speed.
6. Launch and support: publish, then look after it.

One thread runs through all six. At every stage there’s a moment when your decision costs almost nothing, and a moment soon after when the same decision gets expensive. A good process doesn’t save the finished result for a big reveal at the end. It brings you in while your choices are still cheap.

If you have a site in mind and want to see the order of the steps for your particular case, not just a number, send us a few sentences about it. We’ll tell you which stage you’d start from and how long each one is likely to take.