Planning a new business website is about much more than choosing colours and a homepage layout. Before a designer writes code or a developer sets up WordPress, you need to understand what the website should achieve, who it needs to serve, what content it requires and how success will be measured.
This practical guide walks through the decisions that make website projects more predictable. It includes an interactive Website Project Brief Builder that turns your answers into a structured brief you can copy or download and send to a web designer.
- Set business goals
- Understand your audience
- Research the competition
- Plan your sitemap
- Prepare content
- Design and branding
- Choose the platform
- List required functionality
- Plan SEO from the start
- Accessibility and privacy
- Budget and timeline
- Interactive brief builder
- Testing and launch
- After launch
- Common mistakes
- FAQs
1. Start With Business Goals, Not a Design Template
Before discussing platforms or visual style, decide what the website is supposed to do. A local service company might want more qualified enquiries. A consultancy might need to establish credibility and explain complex services. A retailer may need to increase online sales, while a new organisation might simply need a professional, trustworthy online presence.
Choose one primary goal and a few supporting goals. Trying to make every visitor do ten different things usually creates a confusing experience. A homepage can offer several routes, but the hierarchy should reflect what matters most to customers and the business.
Track relevant form submissions, phone calls and consultation bookings.
Track completed orders, revenue and checkout friction.
Help people find services, answers and contact details without unnecessary effort.
Define success before launch. For example, “generate more enquiries” is less useful than “increase the number of relevant enquiries from our core services while reducing spam and unqualified submissions”. That gives you a clearer way to evaluate the finished website.
2. Understand Who Will Use the Website
Many business websites are organised around the company’s internal departments rather than the questions customers actually ask. A more effective starting point is to list the people you want to reach, what they already know, the problems they are trying to solve and what might stop them taking action.
For a business offering local services, visitors may want to know where you operate, whether you have experience with similar projects, what the process involves and how to request a quotation. This is why a focused web design service page for Leamington Spa should do more than repeat a location name: it needs to answer useful local questions.
Consider different levels of readiness. Some visitors want to buy or enquire immediately. Others are comparing options and need educational content first. A strong sitemap accommodates both without forcing everybody down the same journey.
3. Research Competitors Without Copying Them
Competitor research can show which information customers expect to find, which questions are poorly answered and how different businesses position their services. Review a handful of direct competitors and relevant businesses outside your immediate area. Look at navigation, messaging, proof, pricing transparency, content quality and the ease of making contact.
Do not assume the most visually elaborate website is the most successful. A polished animation-heavy homepage may be impressive but still leave visitors unsure what the company does. Research should inform your strategy rather than turn the project into a collection of borrowed features.
Record gaps and opportunities. Perhaps competitors explain their services but offer no case studies. Perhaps they hide contact information or make pricing impossible to understand. Those observations can help your own website stand out through clarity and usefulness.
4. Create a Sitemap Before Designing Pages
A sitemap is a plan of the pages your website needs and how they relate to each other. It is not necessarily the same as the XML sitemap submitted to search engines; here, we mean the human-readable structure of your site. The sitemap should reflect business priorities, customer questions and the content you can realistically maintain.
| Page | Purpose | Typical next step |
|---|---|---|
| Homepage | Introduce the business and guide visitors to key areas | Explore services or enquire |
| About | Explain experience, people and approach | Build trust or make contact |
| Service pages | Answer questions about each main service | Request a quotation |
| Case studies | Show real work and relevant results | View related service |
| Blog or resources | Provide useful explanations and support discoverability | Read related content |
| Contact | Make it easy to get in touch | Submit enquiry or call |
A small site does not need dozens of thin pages. Create dedicated pages where a subject deserves its own explanation and search intent. Group closely related information when separate pages would be repetitive. Make sure every important page has a logical route from the main navigation or relevant internal links.
5. Gather Your Content Before Development
Content is one of the most common causes of delays. A project may have approved designs and finished templates but still be waiting for service descriptions, team biographies, testimonials or photographs. Starting early reduces the need to redesign sections when the real text arrives.
For each planned page, note its audience, primary message, supporting evidence, likely questions, images and next action. Collect logos in usable formats, original photography, case studies, testimonials with appropriate permission and any existing copy worth retaining. Decide who has authority to approve the content.
When preparing a blog or resources section, plan topics around genuine questions rather than publishing articles purely to fill space. My web design blog demonstrates how related guides can create useful paths between educational content and services.
Draft the homepage headline, core service descriptions and main calls to action before finalising visual designs. These elements shape the page hierarchy more than placeholder text ever can.
6. Establish Your Brand and Design Direction
Good website design is not simply about personal taste. It should communicate the character of the business while helping people read, navigate and act. Agree on typography, colour, imagery, spacing, component styles and the level of visual complexity appropriate for the audience.
Prepare a small set of reference websites, but explain what you like about each one. “I like the way the services are organised” is more actionable than “make it look like this site”. Include examples of things you do not want as well, especially if several stakeholders are involved.
Responsive behaviour should be designed intentionally. A three-column desktop section might become stacked cards on a phone, and a complex menu may need a different interaction model on touch devices. The goal is not to shrink the desktop layout but to preserve its usefulness.
7. Choose the Right Website Platform
Platform choice affects content management, functionality, hosting, ongoing costs and the ease of future development. A brochure website with a blog may suit WordPress, while an online store may need a platform chosen around products, stock, checkout, shipping and integrations. Custom applications can require an entirely different approach.
For many service businesses, WordPress website design provides flexible content editing and a broad ecosystem. That flexibility still needs sensible technical decisions: too many plugins, inconsistent page-builder components or fragile custom code can make a site difficult to maintain.
If selling products is central to the business, review the requirements of your ecommerce website before selecting the platform. Product variants, tax, fulfilment, subscriptions, wholesale accounts and payment providers can influence the decision more than homepage aesthetics.
If unfamiliar terminology is slowing down discussions, the website design glossary explains common CMS, hosting, SEO and development terms.
8. List Essential Features and Integrations
A project brief should distinguish essential functionality from features that would be nice to add later. Common requirements include enquiry forms, booking systems, ecommerce, account areas, searchable directories, multilingual content, calculators, customer portals and CRM connections.
Think about what happens after a visitor submits information. Should an enquiry enter a CRM, notify a particular team member or trigger a follow-up? My website automation work focuses on connecting these actions to useful business processes. Planning integrations early helps avoid discovering API limitations when the site is nearly finished.
Include any third-party services already in use, the account owner and the person who can provide access. Also decide how the site should behave if an external service fails: important enquiries should not silently disappear because a connection temporarily stops working.
9. Plan SEO Before the Website Goes Live
Search engine optimisation is easier to incorporate during planning than retrofit after every page has been built. Start by understanding what potential customers search for, how those questions relate to your services and which pages deserve a distinct focus. Titles, headings, content, internal links and URL structure should follow from that research.
Google’s SEO Starter Guide explains that SEO helps search engines understand content and helps people find relevant pages. It does not promise rankings, and neither should your project plan. Think of SEO as ongoing work supported by a sound technical foundation and useful content.
For an existing site, migration planning matters. Record important current URLs, assess which content to keep and map old pages to appropriate new destinations if addresses change. Preserve useful search visibility where possible instead of simply replacing everything and hoping for the best.
Set up a plan for analytics and Google Search Console, but remember that measurement configuration and cookie requirements may affect which scripts run before visitors have made a choice.
10. Plan Accessibility, Privacy and Compliance
Accessibility should be part of the original brief, not a plugin installed the day before launch. Consider keyboard navigation, focus visibility, readable text, meaningful heading structure, form labels, image alternatives and the behaviour of menus, pop-ups and interactive features.
The W3C guidance on planning and managing accessibility recommends integrating accessibility across the production process, assigning responsibilities and evaluating early and regularly. That is more practical than trying to correct every issue after the design and development decisions have already been made.
Privacy needs similar attention. Decide what personal information forms will collect, where it will be sent, how long it will be retained and who can access it. The UK ICO guidance on cookies and similar technologies explains the rules around informing visitors and obtaining consent where required. The specific legal requirements depend on the website and technologies used.
Performance and efficiency can be considered at the same time. Lightweight pages and thoughtful asset choices are explored further in my guide to sustainable web design.
11. Set a Realistic Budget and Launch Window
Budget conversations should cover more than the initial build. Allow for strategy, design, content creation, photography, development, integrations, testing, hosting, domain registration, maintenance and future improvements. Some of these may be included in a proposal, while others will be separate.
Decide what budget range the business is comfortable investing rather than asking a designer to guess what is affordable. A range helps suppliers recommend an appropriate scope and explain trade-offs. It is also useful to separate essential launch features from later phases.
A launch date should be based on dependencies: when content can be supplied, how many approval rounds are needed, which integrations must be tested and whether existing URLs or data must be migrated. Build in contingency, especially if the website supports an event, opening or marketing campaign.
| Budget item | Questions to ask |
|---|---|
| Strategy and design | How much discovery, content planning and bespoke design is included? |
| Development | Which templates and features are in scope? |
| Content | Who writes copy, supplies images and uploads products? |
| Integrations | Are there third-party subscriptions or API costs? |
| Ongoing | Who manages hosting, security, backups and updates? |
Interactive Website Project Brief Builder
Fill in as much or as little as you know. The tool generates a structured brief you can copy or download as a plain-text file and send to a designer. Everything runs in your browser: the form does not submit your details to a server.
Complete the fields to build your brief.
Review and edit your requirements before sending them to a designer. The brief is a starting point for discovery, not a final technical specification or quotation.
12. Plan Testing, Approvals and Launch
Before the website goes live, agree what will be tested and who will sign it off. That should include navigation, forms, mobile layouts, accessibility, key browser combinations, analytics, integrations and—where relevant—complete purchase or booking journeys. Testing needs realistic content and realistic scenarios.
If the project replaces an existing site, review redirects, important metadata, tracking and any content or data migration. Decide who is responsible for the domain, DNS, hosting, SSL certificates and backup before launch day. My website hosting page covers the infrastructure side of supporting a business website.
A launch checklist should distinguish blocking issues from small refinements that can be handled afterwards. It is sensible to reserve time for fixes rather than scheduling the final test on the same afternoon the website is meant to become public.
13. Decide What Happens After Launch
A website should not become static the moment it goes live. Decide who will update service pages, publish news, check forms, review analytics and maintain plugins or other dependencies. The right level of ongoing support depends on the platform and how critical the website is to daily operations.
Measure the outcomes chosen at the start of the project. If the goal is qualified enquiries, monitor enquiry quality rather than counting every form submission as success. If the goal is sales, examine product discovery, checkout completion and customer questions. Use those observations to prioritise improvements.
Set a practical review schedule. A short review after launch can catch operational problems; subsequent reviews can focus on content, performance and business results. Improvements are more useful when driven by evidence than by a constant desire to redesign whatever is newest.
Common Website Planning Mistakes to Avoid
Choosing a template before understanding goals and content can force the business into the wrong structure.
If nobody is responsible for copy and approvals, even a technically straightforward project can stall.
Late CRM, payment or booking requirements can change both scope and testing needs.
Without a clear goal, it is difficult to know whether the finished website is doing its job.
Existing URLs, content and search visibility need a plan when replacing a live site.
Hosting, maintenance, updates and content ownership should not be left until after launch.
The interactive brief builder above is designed to expose these gaps before they become expensive changes. It does not need to be completed perfectly; unanswered questions are useful prompts for the initial discovery conversation.
Frequently Asked Questions
What should a website project brief include?
Include your business background, goals, audience, proposed pages, content readiness, branding, required functionality, integrations, preferred platform if known, budget, timeline and any existing website or migration requirements.
Do I need to know which website platform I want?
No. A good project brief explains what the website must do. The platform can then be recommended based on content, functionality, ecommerce requirements, editing needs and ongoing support.
How many pages should a new business website have?
There is no universal ideal number. Start with the pages required to answer important customer questions and support key journeys. A smaller set of strong pages is often better than a large collection of repetitive pages.
Should I prepare all content before contacting a designer?
Not necessarily. You should understand the core services, audience and goals, but copywriting and content planning can be part of the project. Be clear about what is ready and what support you need.
When should SEO be considered?
From the planning stage. Search intent, sitemap structure, URLs, page topics and internal links can influence both content and design. Retrofitting these decisions later can create avoidable rework.
Can I download the project brief?
Yes. Complete the interactive builder, choose “Generate my project brief” and then use “Download .txt”. You can also copy the text into an email or document.
Does the brief builder send my details anywhere?
No. The interactive form processes your entries locally in the browser and creates text for you to copy or download. It does not submit your answers to a server.
Is the generated brief enough for a fixed quotation?
It is a useful starting point, but detailed technical discovery may still be required to confirm scope, integrations, content responsibilities and pricing.
Final Thoughts: Plan the Website Before You Build It
A successful business website starts with clear decisions. Understand who it serves, what it needs to achieve, what content and functionality it requires, and who will be responsible for keeping it useful after launch. The design and technology should follow from those decisions rather than dictate them.
Use the project brief builder to capture your initial requirements, even if some answers are not yet decided. The result will make early conversations more productive and help identify where specialist advice is needed.
Ready to Plan Your New Website?
I can help turn your initial ideas into a clear project scope, then design and develop a website around your business goals, content and customers.
Web Design Leamington Spa →WordPress Website Design →
