Most website projects that disappoint do not fail because of poor code or weak design. They fail because the business built the wrong kind of website for what it needed. A beautiful brochure site will not fix an operations problem, and a complex web application is wasted effort when prospects simply need to understand what you do.
This guide offers a practical way to decide what your business actually needs before you speak to designers or developers.
Start with the job the website must do
Ask one question first: what should happen because this website exists? Write the answer as outcomes, not features.
- "Prospects understand our three services and book a consultation."
- "Customers can order replacement parts without calling us."
- "Our team can publish two practical articles a month without a developer."
- "Clients can check the status of their project themselves."
Each outcome points to a different kind of website. Most businesses have one primary outcome and two or three secondary ones. Be honest about which is primary — it should drive the budget.
The four common types of business website
1. Business or corporate website
This is the right choice when your main goal is credibility and enquiries. It explains who you are, what you offer, who it is for and how to get in touch. Typical pages include services, about, case studies or examples, and contact.
Choose this if: sales happen through conversations, and the website's job is to start them.
Plan for: clear service pages, strong calls to action, enquiry forms that reach a monitored inbox or CRM, and basic search engine optimisation.
2. Content platform
If you win customers by teaching — publishing guides, articles, resources or news — your website becomes a publishing platform. The content management system matters more here, as does the structure of categories, tags and internal links.
Choose this if: your audience researches extensively before contacting anyone, or your expertise is your differentiator.
Plan for: an editor-friendly CMS, an editorial workflow, a search function and a content plan you can realistically sustain.
3. E-commerce store
When customers can buy without speaking to you, an online store reduces friction and staff time. The complexity is often hidden: product data, payments, shipping, tax, returns and stock synchronisation.
Choose this if: your products have clear prices and specifications, and customers expect to buy online.
Plan for: catalogue management, payment and shipping integrations, order notifications, and how the store connects to inventory or accounting.
4. Web application
If users need to do things — log in, manage records, submit and track requests, collaborate — you are building software rather than a website. That brings different considerations: user roles, permissions, data security, testing and ongoing maintenance.
Choose this if: the core value is a workflow or service delivered through the browser.
Plan for: discovery work, a focused first release, and a long-term maintenance arrangement.
Many businesses need a combination — for example, a corporate website with a separate client portal. That is usually better than forcing one platform to do everything.
Questions to answer before you build
Use these to shape a brief, regardless of type:
- Who are the two or three main audiences? What do they need to know or do first?
- What is the single most important action you want visitors to take?
- Who will maintain the content, and how often will it change?
- What other systems must the website connect with — CRM, booking, payments, email marketing?
- How will you measure success? Enquiries, sales, sign-ups, reduced support calls?
- What content already exists, and who will write what is missing?
- What are the constraints? Budget range, launch date, internal approvals, accessibility or regulatory requirements.
Content is the most underestimated part of most projects. Agree early who is responsible for writing and approving it.
Build versus platform
For many business websites, a well-chosen platform or CMS with a thoughtful design is more cost-effective than a fully custom build. Custom development earns its place when you need specific performance, integrations, unusual workflows or a distinctive experience that templates cannot provide.
A good partner should explain the trade-offs plainly, including the ongoing cost of hosting, updates and maintenance — not just the initial build.
Avoid these common mistakes
- Designing before structuring. Agree the sitemap and page purposes first; visual design follows.
- Treating launch as the finish line. Websites need updates, security patches and content improvements.
- Ignoring mobile. For many businesses, most first visits happen on a phone.
- Forgetting measurement. Without analytics and conversion tracking, you cannot tell what is working.
- Collecting enquiries nobody owns. Every form should have a named owner and a response target.
A simple decision checklist
| If your primary goal is… | Start with… |
|---|---|
| Generating enquiries | A business website with strong service pages |
| Demonstrating expertise | A content platform with a sustainable editorial plan |
| Selling products directly | An e-commerce store with reliable integrations |
| Delivering a service or workflow | A web application with a focused first release |
Next steps
Write down your primary outcome, your audiences and the constraints above. That one page will make every conversation with designers and developers faster and more productive — and it will help you recognise proposals that solve the wrong problem.
If you would like a second opinion on what your business needs, tell us about your project. We are happy to recommend the simplest option that meets your goals.
