Search "what website does my business need" and you'll get a list of website types: ecommerce, portfolio, blog, directory, sorted by industry. That's the wrong axis.

A five person landscaping company and a 200 person logistics firm aren't different because one sells online and the other doesn't. They're different because of what breaks first as they scale.

Here's the framework we actually use with clients, organized by business size instead of industry, because that's the variable that actually determines what you need.

Small Business (Roughly 1 to 15 People): The Question Isn't "What Type," It's "Do You Even Need One Yet"

If you're a solo operator or small team, the honest first question is whether a full website beats a well run set of social profiles plus a single landing page.

It usually does. A website is the one piece of your online presence you actually own, not rented space subject to an algorithm change. But "usually" isn't "always."

What actually matters at this size:

• A domain you control, even if what sits on it is minimal.

• One clear conversion path. Call, book, or get a quote, not five competing calls to action.

• Real trust signals. Actual client names or photos, not stock testimonials. At this size, a visitor can usually tell the difference between a real case study and filler. It's worth seeing what this looks like done well: we recently took an industrial client whose site we manage and surfaced a set of real, previously unlinked project pages, including a roofing project completed in 7 days without stopping production, onto a proper projects page. That's the difference between a real case study and a placeholder testimonial.

• Mobile performance over visual complexity. A fast, simple site outperforms a slow, animated one. More than half of mobile visitors leave a page that takes over three seconds to load, and small business sites rarely have the traffic volume to absorb that loss and recover.

What you don't need yet: a custom CMS, a headless architecture, or a blog posting three times a week. Most small businesses are better served by one excellent page than five mediocre ones.

Growing Or Midsize Business (Roughly 15 to 100 People): The Constraint Shifts From "Do We Have A Site" To "Can Our Team Actually Run It"

This is where we see the most expensive mistakes. Not from choosing the wrong platform, but from choosing a platform built for a company one size smaller or one size larger.

The real question at this stage is operational: can your marketing team publish, update, and manage content without filing a developer ticket every time?

What actually matters here:

• A CMS your team can use without needing a developer for every change. This is worth more than almost any feature list, because the alternative is a content bottleneck that compounds every month.

• Integration with the tools you already run. CRM, booking, email. Retyping leads by hand between systems is where growing teams quietly lose the most time.

• A site structure that can add pages and sections without a rebuild. If launching a new service line means calling your developer, the site was built for a smaller company than the one you're becoming.

• Real analytics, not vanity metrics. At this size you have enough traffic for the data to be meaningful, so use it.

What you don't need yet: full enterprise infrastructure (single sign on, governance based on user roles, compliance across multiple regions). That's solving a problem you don't have yet, at a cost that doesn't make sense until you do.

Enterprise (100+ People, Or Any Regulated Operation Run By Multiple Teams): The Website Stops Being A Marketing Asset And Becomes Infrastructure

At this size, the conversation changes entirely. Nobody at an enterprise is asking "what type of website." They're managing a system that has to survive multiple teams, multiple regions, and real security and compliance exposure.

What actually matters:

• Governance, not just a CMS. Permissions based on role, approval workflows, and audit trails matter more than any single feature, because the risk isn't "the site looks bad," it's "the wrong person published something that shouldn't have gone live."

• Security built in, not bolted on. Single sign on, two factor authentication, and a real incident response plan, because a breach at this scale costs far more than it would for a smaller business, in both money and trust.

• Performance under real load. Meeting the same Core Web Vitals thresholds Google publishes (LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1), tested under enterprise traffic, not a quiet afternoon.

• Integration depth. CRM, ERP, marketing automation, and often custom APIs connecting systems that predate the website entirely.

The One Question That Actually Sorts This, If You Only Ask Yourself One Thing

Don't ask which type of website is popular. Ask yourself this instead:

Whichever one breaks first tells you which size bracket you're actually building for, regardless of your current headcount.

A fast growing eight person team can already have problems that belong to a much bigger company. A stable 150 person company that's never scaled its site can still be running on small business infrastructure. Headcount is a proxy, not the actual answer.

Not sure which bracket you're actually in? Take our 2 minute quiz to get a straight answer, or schedule a free consultation and we'll walk through it with you directly.