From Brief to Launch: How Website Development Actually Works From the Inside
For a client, building a website usually looks like a black box. A brief and a deposit go in; a link comes out a few months later. What happened inside, why it cost exactly that much, and why some stages flew past in a week while others dragged on for a month, all remains a mystery.
Here is the process from the inside: what actually happens at each stage, how long it takes and, most importantly, at which moments the project depends not on the agency but on the client.
Stage 1. The brief and what really surfaces
A brief is rarely about the website. It is about the business: who pays, for what, how much it costs to acquire a customer, what is blocking sales right now. The site is only an instrument, and until it is clear which problem it solves, discussing colours is pointless.
Three uncomfortable questions are worth asking at this stage:
- What has to happen for you to call this project a success a year from now? “A beautiful website” does not count; a number is needed.
- Who makes the final call on design? If more than two people do, approvals will take twice as long.
- Where will the content come from? This is the single most common reason deadlines slip, and almost nobody thinks about it at the start.
Stage 2. Structure and wireframes
A wireframe is a page layout without colours, fonts or images. Deliberately grey and deliberately unattractive. The reason is simple: the moment design appears, the conversation slides towards shades of blue and the underlying logic goes unchecked.
Wireframes settle which blocks appear on a page, in what order, what a visitor sees first and where every button leads. This is the cheapest stage for changes. Moving a block in a wireframe takes fifteen minutes. Moving the same block after front-end work is a day of three people’s time.
Stage 3. Design
Design does not start with the homepage. It starts with a system: grid, typography, colour, states for buttons and fields. Screens are then assembled from that system. This order produces predictable results and saves time during build.
This is also where mobile behaviour is decided. Not “we will shrink it later”, but separate layouts: a different block order, different navigation, different sizes. More than half your traffic usually arrives from there.
Stage 4. Build and development
The build turns layouts into working pages. Development adds what layouts do not show: the admin area, forms, integrations, multiple languages, performance.
This is where questions surface that looked trivial during design. What do we show if a block has one card instead of three? What happens when a heading is longer than the mock-up? What does an empty state or an error look like? A good agency raises these in advance; a poor one decides alone, and it gets rebuilt later.
Stage 5. Content and testing
The most underestimated stage. A site assembled on Lorem ipsum and a site with real copy are two different sites. Real headlines are longer, real photos are the wrong aspect ratio, real descriptions do not fit the space allowed.
Testing covers what a demo never shows: behaviour across browsers and screen sizes, form handling, email delivery, load speed, keyboard accessibility.
Stage 6. Launch and the first weeks
Launch is not the end. It is the point at which data starts arriving. Over the first two weeks you collect real numbers: where people come from, where they close the page, which forms they abandon halfway. That is when you see which assumptions held.
How long it takes
| Stage | Duration | What is needed from the client |
|---|---|---|
| Brief and research | 1-2 weeks | Access to data, time for meetings |
| Structure and wireframes | 1-2 weeks | Careful approval, not “looks fine” |
| Design | 3-5 weeks | Photos, logo, brand guide, one decision maker |
| Build and development | 4-8 weeks | Access to hosting, domain, email |
| Content and testing | 1-3 weeks | Finished copy and images |
| Launch | 2-5 days | A decision on the date |
Ten to twenty weeks in total for a typical corporate website. The spread is wide because of the right-hand column: deadlines are rarely missed by developers, they are missed waiting for content and approvals.
Where projects get stuck most often
- Content. Copy is promised “next week” and arrives two months later. The fix: write in parallel with design, not after it.
- Vague approval. “Broadly good, but something feels off” cannot be actioned. Specific points are required.
- New stakeholders mid-project. Someone seeing the designs for the first time during build almost always reopens the discussion from scratch.
- Out-of-sequence changes. Restructuring after design sign-off does not cost “a bit more”, it costs several times more.
- Access credentials. Hosting, domain, email, analytics. Finding the person who registered them five years ago can take weeks.
What genuinely speeds a project up
Not adding people to the team. What helps is different:
- One person on the client side with authority to decide.
- Content at least 70% ready before design begins.
- Feedback as a single consolidated list, not one message at a time across a week.
- An honest “I do not know” instead of guesses about your own business.
- An agreement that minor notes are collected and shipped as a batch after launch.
Questions worth asking your agency
Asked before signing, these save more than negotiating the price:
- What is included in the quote and what is billed separately?
- How many rounds of revisions are budgeted at each stage?
- Who writes the copy, and is it in the budget?
- What happens after launch: is there support, what does it cost, what are the response times?
- Who owns the design source files and the code?
Website development stops being a black box the moment both sides understand which decisions are made at which stage and what they cost. Everything after that is just work, and work gets done predictably.
