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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
Three uncomfortable questions are worth asking at this stage:<\/p>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n