How to plan a business website before development starts
A business website is rarely “just pages.” It carries positioning, lead capture, support content and often integrations with CRM or booking tools.
Planning before development means aligning stakeholders on what the site must do — not only how it should look.
Start with outcomes, not page count
List the jobs the site must perform: explain the offer, build trust, capture enquiries, support SEO, or host product documentation.
Those jobs drive information architecture more reliably than copying a competitor sitemap.
Map content early
Draft real headings and key messages for core pages, even if copy is rough. Design and development both depend on content hierarchy.
Identify gaps — case studies, FAQs, policies — before build so launch is not blocked by missing assets.
Choose the right technical foundation
Marketing sites may suit a CMS; authenticated portals need application architecture. Match the stack to editability, performance and future features.
Document non-functional needs: accessibility, analytics, forms, localisation and hosting constraints.
Define success before launch
Agree on baseline metrics: form submissions, key page engagement, search impressions or support deflection.
A short post-launch review plan keeps the site evolving instead of freezing on day one.
Takeaway
A week spent on outcomes, content and technical constraints before design saves multiple weeks of rework during development.
Bring a sitemap sketch and real copy outlines to your first studio conversation — not a blank brief.