![\"The](\"https:\/\/kryloweb.com\/blog\/wp-content\/uploads\/2026\/10\/website-design-process-steps-1.jpg\")
<\/figure>\n\n\n\n1. Brief<\/h2>\n\n\n\n
What happens:<\/strong> we agree what the site is for, who it is for, the pages and features it needs, the budget and the timeline.<\/p>\n\n\n\n What you provide:<\/strong> answers to our questions, examples of sites you like, access to your current site and analytics if you have them.<\/p>\n\n\n\n What you approve:<\/strong> a written scope and price.<\/p>\n\n\n\n A website RFP<\/a> makes this step faster.<\/p>\n\n\n\n What happens:<\/strong> the sitemap (every page and how they connect), the main user journeys, and the structure of key pages. For redesigns, an inventory of current pages and a redirect plan.<\/p>\n\n\n\n What you provide:<\/strong> feedback on the sitemap and priorities.<\/p>\n\n\n\n What you approve:<\/strong> the sitemap and page outlines.<\/p>\n\n\n\n What happens:<\/strong> text and images are written, gathered or edited. Ideally this starts during planning and runs alongside design.<\/p>\n\n\n\n What you provide:<\/strong> text, or input for us to write from; photos; logos; any documents to link.<\/p>\n\n\n\n What you approve:<\/strong> final text for each page.<\/p>\n\n\n\n This is the step that stalls most projects. Design can start with draft text, but the build can’t finish without final content.<\/p>\n\n\n\n What happens:<\/strong> the look of the site, starting with key pages such as the homepage and a service page, on desktop and phone. Once those are approved, the remaining templates follow the same system.<\/p>\n\n\n\n What you provide:<\/strong> feedback, in writing, consolidated from everyone who needs a say.<\/p>\n\n\n\n What you approve:<\/strong> designs for each template.<\/p>\n\n\n\n Tip: collect feedback from your whole team before sending it. Conflicting rounds from different people are the second most common cause of delay.<\/p>\n\n\n\n What happens:<\/strong> the design becomes a working site on the chosen platform, on a private staging address. Content goes in, features are connected, SEO settings and structured data are set.<\/p>\n\n\n\n What you provide:<\/strong> access to accounts the site connects to, such as booking, payments or email tools.<\/p>\n\n\n\n What you see:<\/strong> a staging link you can click through as the build progresses.<\/p>\n\n\n\n What happens:<\/strong> every page on phones and desktops, in Chrome, Safari and Firefox; every form and payment tested end to end; speed, accessibility and SEO checks; redirects tested for redesigns.<\/p>\n\n\n\n What you provide:<\/strong> your own test run, especially of forms and anything customers pay through.<\/p>\n\n\n\n What you approve:<\/strong> the site, ready to launch.<\/p>\n\n\n\n What happens:<\/strong> the site goes live, redirects switch on, the sitemap goes to Search Console, analytics are checked, and we run the live site through the tests again.<\/p>\n\n\n\n What you provide:<\/strong> a launch time that suits you; avoid Friday evenings.<\/p>\n\n\n\n Real visitors find things testing doesn’t. The first weeks are for fixing issues, watching search data and making small improvements. After that, a site needs updates and occasional changes; our website management<\/a> plans cover that.<\/p>\n\n\n\n It depends on size and how quickly content and feedback arrive. As a rough guide, a small business site often takes a few weeks from approved scope to launch, and larger sites take longer. The fastest projects have content ready before design starts and one person collecting feedback.<\/p>\n\n\n\n2. Plan<\/h2>\n\n\n\n
3. Content<\/h2>\n\n\n\n
4. Design<\/h2>\n\n\n\n
5. Build<\/h2>\n\n\n\n
6. Test<\/h2>\n\n\n\n
7. Launch<\/h2>\n\n\n\n
After launch<\/h2>\n\n\n\n
How long does the website design process take?<\/h2>\n\n\n\n
Where projects stall, and how to avoid it<\/h2>\n\n\n\n