Fri Aug 07 2026
Most projects start with a discovery phase, where the agency asks questions about the business, its goals, its audience, and what success looks like for the site. This stage often produces a scope document or proposal outlining pages, features, timeline, and cost. It's worth treating this phase seriously rather than rushing through it — decisions made here shape everything that follows, and changes later tend to be more expensive than getting it right upfront.
Once scope is agreed, design typically comes next — often starting with wireframes (rough layouts showing structure and content placement) before moving to full visual design. This is the stage where client feedback matters most; it's much cheaper to change a layout in a design mockup than after it's been built. Most agencies build in a set number of revision rounds, so it helps to consolidate feedback rather than sending small changes one at a time.
Development is where the design gets built into a functioning site. In parallel, content — copy, images, any necessary legal pages — needs to be finalized, since delays here are one of the most common causes of project slowdowns. Some agencies handle content as part of the project; others expect the client to provide it. It's worth clarifying this upfront rather than discovering the gap mid-project.
Before launch, the site goes through testing — checking it across browsers and devices, verifying forms and links work, and confirming performance. After launch, most agencies offer some form of ongoing support or maintenance, whether that's fixing bugs, applying updates, or making small content changes. It's worth asking upfront what happens after launch: is there a support window included, and what does ongoing help cost once that window ends?
