A professional web design process runs in stages, from discovery and a content plan through wireframes, visual design, build, SEO setup and testing, to launch and training. Most of our business websites take 8 to 12 weeks, and the biggest delays come from content and approvals, not design or code.
On our projects, the weeks that slip are rarely lost in design or code. They go to page copy that isn't written yet, a domain login nobody can find, or a late round of opinions on the homepage. Each of those delays is predictable, and each one is easier to prevent when you know what a stage will ask of you before it starts.
I'm Meet Chaudhari, Partner and Visual Designer at DigiBenders. I lead layout and visuals; Nikhil leads copy and structure. Below is the web design process we run on client projects, stage by stage: what happens, roughly how long it takes, and what we need from your side.
It also covers the parts that shape a project from the first call, including advertising rules for law and health clients, bilingual English and French builds, and the redirect step that protects your search rankings during a redesign. For everything the service itself includes, see our web design service.
A professional website moves through nine stages, from a discovery call to training your team on the editor. Each stage ends with something you approve, so the next one starts from a settled decision instead of a guess.
These website design process steps overlap a little in practice. SEO setup and tracking run alongside the build, for example. The order of approvals does not change, though, and that order is what keeps rework down.
Most of our business websites take 8 to 12 weeks from first call to launch. Where a project lands in that range depends mostly on how quickly content, logins and approvals arrive.
How long does it take to build a website, then? The honest answer is that our side of the work is planned and scheduled once the project starts, and your side is the variable. The table below breaks the web design timeline into stages and shows what each one needs from you.
| Stage | What happens | Typical time | What we need from you |
|---|---|---|---|
| Discovery | Goals, audience, what counts as a lead, competitors, advertising rules | A few days | Your goals, competitor names, any advertising rules your regulator sets |
| Sitemap and content plan | Every page decided, a writer named for each | Set by how quickly copy is written | Sitemap approval, page copy or the facts to write it, photos and bios |
| Wireframes | Layout and page order in greyscale | Short, once the sitemap is approved | Structure sign-off from your decision-maker |
| Visual design in Figma | Brand applied to key pages | Set by revision rounds and feedback turnaround | Logo and brand files, one consolidated set of notes per round |
| Build on Webflow or WordPress | CMS, mobile layouts, accessibility, page speed | Scheduled by us once designs are approved | Domain and hosting access |
| SEO setup | Titles, meta descriptions, structured data, redirect map | Runs alongside the build | Your list of services and locations, access to the current site and Search Console |
| Lead capture and tracking | Click-to-call, forms, booking, call and form tracking | Runs alongside the build | Who receives leads, booking tool details, Google Analytics access |
| Testing and launch | Devices, forms, links, speed, redirects, then go-live | A few days before launch | Test submissions on your own devices, final sign-off |
| Training and handover | Editor training, optional ongoing care | A walkthrough after launch | The people who will edit the site |
Read the last column as your share of the schedule. If a stage is waiting on something from you, every stage after it waits too. A homepage design can't be approved before the homepage copy exists, and a site can't launch before someone can sign in to the domain registrar.
Because the design has to fit the words, not the other way round. When layouts are built around placeholder text, the real copy arrives later and breaks them, and pages that were already approved go back to design.
Placeholder text is uniform and tidy. Real copy isn't. A practice-area page sketched with one short paragraph turns out to need an FAQ block, a process explanation and links to related services. A heading the layout assumed would be short becomes a full sentence. A bilingual site needs every layout to hold an English and a French version of each page. Each surprise sends a page back to the designer, and that rework costs you time.
So the content plan comes first. It lists every page on the sitemap and assigns a writer to each one:
This also answers a common question about order: wireframes come after the content plan. Final wording can still be polished while wireframes are reviewed, but by then we know which pages exist, what each one must say and roughly how much room it needs.
They run in sequence, and each one locks a different decision: wireframes lock structure, Figma designs lock the look, and the build turns both into a working site. Keeping those decisions separate stops a colour discussion from reopening the page order.
Wireframes show the layout and page order in greys. With no colour or photography to react to, feedback stays on the questions that matter at this point. Is the phone number where people look for it? Does the services page lead to a clear next step? Is a page missing?
I design the brand onto the key pages in Figma, usually the homepage, a service page, a location or team page, and the contact page. Visual design includes two rounds of client revisions. Each round works best with one decision-maker on your side who gathers everyone's comments into a single, consistent set of notes. Conflicting feedback from several people can use up a round without moving the design forward.
Once the designs are approved, we build on Webflow or WordPress, depending on who will edit the site and what it needs to do. Every build includes:
Map every old URL to its new home and set a permanent redirect for each one before launch. Then test those redirects, the forms and the tracking on the live site, and ask Google to index the new pages.
In any website redesign process, URLs change. Pages get renamed, merged or moved into new folders, and without redirects every old link in search results and on other websites leads to an error page. Google Search Central explains that a redirect tells visitors and Google Search that a page has a new location, and that permanent redirects show the new target in search results while temporary ones keep showing the source page. The same guidance notes that a server-side redirect has the highest chance of being interpreted correctly, so that is the type we set up.
Click-to-call buttons on mobile, short contact forms, and online booking where your practice uses it. Calls and form submissions are tracked so you can see which pages produce leads after launch.
Before go-live we test on phones, tablets and desktops, submit every form, check links, measure page speed and run the old URLs through the redirect map to confirm each one lands where it should. After launch, we submit the sitemap in Search Console and request indexing for key pages with the URL Inspection tool. For the wider planning side of a rebuild, read our guide on how to redesign a website.
In our experience, delays come from three places: late content, missing logins and too many approvers. None of them is technical, and each has a simple fix you can put in place at the start.
Design and build wait for real copy, so a page without words is a page that can't be finished.
Tip: give every page in the content plan a writer and a due date, and send copy in batches, starting with the homepage and your main service pages, rather than holding it until everything is done. If writing internally isn't realistic, hand the copy to us at the start, not halfway through.
Launch needs access to your domain registrar, hosting, Google Analytics, Search Console and Google Business Profile. Accounts registered to a former employee or a past provider can take time to recover.
Tip: during discovery, make one list of every account, who owns it and who can sign in. Start recovering any lost accounts that week, not the week of launch.
When several partners or managers each send their own notes, the feedback conflicts and a revision round produces no clear direction.
Tip: name one decision-maker before wireframes. Others can comment, but their feedback goes through that person, who sends us one consolidated set of notes per round. In a partnership, agree internally who has the final say on design before the first review.
Two law firm projects show the same process at different scales: a multi-province rebrand and a firm's first bilingual website. Both ran through the stages above, with the content plan carrying much of the weight.
CLG Injury Law is a personal injury firm with six offices across New Brunswick, Nova Scotia and PEI. We delivered a full rebrand and a Webflow site with a page for every location and service. At that scale, the sitemap and content plan hold the project together: every office and every service needs its own page, and each of those pages has to be planned before a layout is drawn. The CLG Injury Law rebrand and Webflow build case study shows the finished work.
For Gandy and Associates in Saint John, we built the firm's first website, in English and French, and wrote all of its practice-area copy. Because we were writing the copy, the content plan and the writing schedule were our responsibility, and every layout had to hold both languages. See the Gandy and Associates bilingual website case study for the result.
Our business website projects typically begin around $5,000, quoted as one fixed price after a free consultation. For the factors that move a budget up or down, see our guide on how much a website costs in Canada.
A website project is a series of decisions made in the right order: goals, then pages and words, then structure, then look, then build. Get that order right and rework stays small. The real schedule risk sits with content, logins and approvals, which is why we ask for them early and name who owns each one. For a redesign, the redirect map deserves the same care as the homepage, because it tells Google where every old page now lives. When you know what each stage needs from you, you can plan your own workload around the project instead of reacting to it.
If you want a clear plan and a fixed quote for your own site, book a free consultation with our team in Saint John.
