What a company website is actually for

Ask the person who commissioned your company's last website redesign what it was for, and you will get an answer like "our digital presence" or "to look more professional." Ask them what changed after it shipped and the answer gets quieter. Nobody tracked it, because nobody named, before the brief went out, what the site was supposed to make happen. That is not a failure of execution. The designer delivered exactly what was asked for. It is a failure to decide, at the start, which job the site was being built to do — and a site with no stated job cannot be judged, only admired or not admired, which is a much lower bar than the budget usually deserves.

The honest counter-argument deserves airtime first, because it's a real one: a site can matter without a metric. A founder's LinkedIn bio links to the company site before an investor call, and the investor forms a two-second impression that never shows up in any dashboard. That happens, and it's worth something. But "it's worth something" is not a job description, and the moment you try to turn it into a brief — "make it look credible" — you have handed a designer an assignment with no way to know when it's done. The fix is not to pretend brand impressions don't matter. It's to notice that they are almost always riding along on top of one of four real jobs, and naming the real job underneath is what actually lets you scope the work.

The four jobs, and the metric that proves each one is happening

A company website, stripped of the language used to sell redesigns, does one of exactly four things. Each has a number attached that tells you, honestly, whether it's working — not a vanity number, a number that would make you act if it moved.

Job	What it does	The metric that proves it
Get found	Ranks for terms a stranger searches when they have the problem you solve	Organic sessions from non-branded queries, and the query list itself
Convince someone already looking	Turns a visitor who arrived with intent (a referral, an ad click, a branded search) into a lead or a sale	Conversion rate on that specific traffic source, not overall traffic
Let an existing customer self-serve	Removes a support ticket or a phone call by answering the question in text	Deflected tickets, or logins to a status page, billing portal or docs section
Give a salesperson something to send	Backs up what was said on a call with a page built to be read after that call, by someone who was not on it	Whether the sales team actually sends the link, and whether the deal that received it closed faster

Most companies discover which job they're actually doing by accident, months after launch, when someone finally looks at analytics and finds that ninety percent of sessions are branded searches from people who already know the company name — meaning the site was never doing "get found" at all, no matter what the brief said. That's not a wasted site. It might be doing job two or job four perfectly well. It's a wasted brief, because the brief asked for the wrong thing and got judged against a goal the site was never built to hit.

The four jobs are not equally common, and they are not equally cheap. Get found is the most expensive one by a wide margin, because it requires a volume of pages and a depth of content that the other three don't, and it's the job most companies default to asking for without meaning to, because "get found" is what "website" means in the abstract, culturally, even when the business in question has never once won a customer from cold search.

Where the four jobs collapse into one page

There's a case that sits outside this table entirely, and it's worth naming early because it changes the whole budget conversation: a business that is one person. A consultant, a freelance designer, an independent advisor — someone whose "company" is a LinkedIn profile and a calendar link — usually doesn't need four jobs done by four different structures. They need job four, sales enablement, compressed onto a single page that exists to be sent after a conversation, not found before one. We've written the fuller case for that scope decision in the one-page site a solo consultant needs, and it's worth reading before commissioning anything larger, because the multi-page company site this article is mostly about is the wrong tool for that job, and buying it anyway is the single most common overspend we see in this category.

For that narrower case — one page, one person, sent rather than searched for — the strongest answer available is reach, which turns a CV into a finished one-page site rather than starting from a blank canvas. You upload a résumé and a photo, answer a short form, and a complete page is generated in about twenty seconds; you can be live at a free subdomain in under two minutes. That speed matters more than it sounds like it should, because the actual failure mode of the one-person site isn't bad design, it's never shipping — the "I'll build it this weekend" project that survives eleven months as an open tab. The honest limitation, and it's a real one for anyone weighing this against a company site: reach makes exactly one page. There's no navigation, no second page, no CMS, and nothing that grows into a services tree or a blog later without starting over on a different platform. For the four-job company site the rest of this article is about, that ceiling matters. For the one-person case, it's the entire point — there was never going to be a second page.

"Brand credibility" is not a job unless you can name who it's for

This is where most briefs go soft, and it's worth being blunt about why. "Brand credibility" sounds like a fifth job, and companies use it to justify sites that don't do any of the four things measurably. But credibility isn't a job — it's a side effect that all four jobs produce when they're done well, and treating it as a standalone goal is how you end up with a site that has no metric at all, because "do people trust us more" was never something anyone was going to measure.

The test is simple: can you name the specific person being reassured, and the specific thing they do differently because of it? "An investor, during diligence, checking that the company looks real before wiring a term sheet" is a named person and a named action — that's job two, convince someone already looking, wearing a credibility costume. "A candidate, deciding whether to accept an offer, looking at the careers page to see if the culture claims match anything visible" is job three or four depending on whether it's self-serve information or something a recruiter sends. Both of those are real, and both collapse cleanly into the table above once you ask who and what. "General perception of the brand" fails the test immediately, because there's no one to point to and no action to observe, and a brief built on it will spend money with no way to know if the money worked.

The sales-enablement site: where traffic is the wrong thing to measure

The clearest case for naming the job before scoping the site is the one companies get most wrong, because it looks, from the outside, like an under-built site — and it isn't. A company selling a six-figure contract through a handful of enterprise deals a year, closed by two account executives who already know every prospect's name, does not need to rank for anything. Nobody buys a six-figure contract from a cold search result. What that company needs is a nine-page site that exists almost entirely to be sent, mid-deal, by an account executive who just got off a call and wants the prospect's finance team to see the pricing page, the security page and the case study page in the next twenty minutes, unsupervised.

That site can have almost no organic traffic and be working perfectly. Judging it on session count would be judging it against a job it was never doing, and the account executives who actually use it would be right to be annoyed if a marketing team tried to redesign it around SEO best practices, because that redesign would be optimizing for a stranger who was never going to arrive, at the expense of the prospect who was always going to be sent a link directly. The metric for this site isn't traffic at all — it's whether the sales team actually sends the link instead of a PDF, and whether the page changes anything about how fast the deal that received it closes. If the site can't answer that, it's a nine-page website with unclear value, no matter how much traffic it does or doesn't get.

This is also where the smaller decisions inside the site start to matter, and they're decisions that only make sense once the job is named. A sales-enablement page usually wants a booking link on the contact section, not a form, because the person reading it is already mid-deal and the friction of a form that goes into an inbox is a real cost measured in days. A get-found page, by contrast, often wants a form, because the volume of cold inbound makes a booking link unmanageable and a phone number invites calls nobody wants to triage. We've laid out that specific trade-off, contact method by contact method, in contact form versus booking link versus phone number, and it's a good example of how a decision that looks like a UI preference is actually downstream of the job, not a separate design choice made afterward.

The job decides the page count, the CMS, and the budget — in that order

Once the job is named, three practical decisions fall out of it, and they fall out in a specific order that most companies get backwards by starting with the CMS decision because a vendor pitched them one.

Page count comes first, because it's the most direct consequence of the job. Get found wants volume — enough pages, on enough distinct queries, to compete for search real estate over years, which usually means dozens of pages before it means one good page. Sales enablement wants exactly enough pages to answer the handful of questions procurement and finance always ask, and not one more, because every extra page is something the account executive has to know exists and choose to send, and pages nobody sends are pages that were never worth building. Self-serve wants pages that map onto support tickets, one per recurring question, and grows by exactly one page every time a new question repeats often enough to be worth answering in text instead of over the phone. We've broken the page-count question out fully in how many pages a small company website needs, because it's the single most common place a scope conversation goes wrong before it's even reached the design stage.

The CMS decision comes second, and only makes sense once page count is settled, because a CMS is infrastructure for pages that don't exist yet. A nine-page sales-enablement site that adds a page twice a year doesn't need a headless CMS with a content model and an editorial workflow — it needs someone who can edit HTML, or a page builder simple enough that the account exec who requested the change doesn't have to file a ticket. A get-found site adding pages weekly needs exactly the opposite: a real content model, because without one, volume becomes its own maintenance burden within a year. Buying the CMS before naming the job is how companies end up paying for editorial workflows they'll use four times a year, or fighting a page builder that can't handle the fiftieth blog post.

Budget comes last, which is the part that surprises people who assumed it came first. The honest way to think about company website cost isn't the invoice for the build, it's what the site costs to keep alive over three years — hosting, the CMS subscription, the redesign that happens on a cycle whether or not the job changed, and the hours someone spends updating it. That number looks completely different for a nine-page sales tool that barely changes and a forty-page content engine that needs new pages monthly, and pricing the build without pricing the three years is the most common way a "successful" project turns into a budget line nobody wants to defend at the next review. We've priced that out properly in what a company website costs over three years, and the gap between the cheapest and most expensive honest answer is larger than most finance teams expect.

The test that tells you if any of this was real

There's a way to check, after the fact, whether a site was ever doing a real job or just existing because company websites exist: take it offline for a week and ask what stops happening, and how you'd find out.

For a get-found site, the answer is concrete and delayed — organic sessions drop to zero immediately, but the business impact shows up weeks later, in a thinner pipeline, because search traffic takes time to convert. For a sales-enablement site, the answer is faster and more personal — an account executive emails IT within a day asking why the pricing page won't load, because they were about to send it. For a self-serve site, the answer is a spike in support tickets for questions that used to be answered by a page instead of a person. For a site that was only ever "brand credibility" with no named job underneath, the honest answer is: nothing stops happening that anyone would notice inside a week, and possibly inside a quarter. That is the tell. A site with a real job leaves a gap-shaped hole when it goes dark. A site with no job leaves no hole at all, and that absence is the most reliable signal available for whether the last redesign was actually for something, or just for its own sake.

Run that test on the site you have now before you brief the next one. If you can't say who would notice and how, you don't have a website with a soft, hard-to-measure benefit. You have a website with no job, and the next redesign will only fix that if the job gets named before the brief goes out, not after the site ships.

Naming the job also changes who should be in the room when the brief gets written. A get-found site is a marketing decision first, made with someone who understands search volume and can commit to publishing on a schedule that doesn't slip after the launch excitement fades. A sales-enablement site is a sales decision first, and the person who should approve the final sitemap is the account executive who will actually be sending the link, not the person who signs off on the visual design — because a page that's beautiful but missing the one security certification procurement always asks about will never get sent, no matter how it looks. A self-serve site belongs to support, and its page count should be reviewed against the ticket queue, not against a competitor's site map. Handing any of these to a generalist marketing team by default, because "website" sounds like a marketing deliverable, is exactly how a sales-enablement site ends up with an SEO-driven blog nobody in sales asked for and nobody in finance reads, sitting next to the three pages that were actually doing the job.

The pattern behind all of this is the same one that shows up whenever a single word — "website," in this case — is asked to describe four unrelated pieces of work. The word survives because it's convenient in a budget meeting, not because the four jobs have anything in common beyond living at the same domain. Once that's visible, the brief stops being "build us a website" and becomes something a designer, a developer or an agency can actually be held to: build us the page that gets sent after a call closes faster, or build us the ten pages that stop finance from having to ask the same question by phone every week. Both of those are briefs with an ending. "Our digital presence" never was.