Published
9 MIN READ
Company Website Design: What Goes Into the Scope
Company website design is the project for a business's official website: the pages that explain who it is, what it does and how to hire it. The scope comes down to three things: the number of unique pages, who writes the copy and the level of animation. Deciding this before the proposal avoids rework.
This article settles the decision that almost no page in search results tackles: the scope of the first version. It's based on eight pages on the topic read in September 2026 and on Wama's experience across more than 200 projects, 50 of them published in Framer.
What is a company website?
A company website is a business's official address on the internet: who it is, what it offers and how to get in touch. It exists to hold up under scrutiny, not to capture a campaign lead. People who land on it have usually already heard the company's name and are checking whether it holds up.
This distinction shows up in an analysis published on August 10, 2026 by a B2B marketing agency in the interior of São Paulo state: visitors arrive carrying questions, and those questions should define the page structure. A B2B design studio, in a guide from July 5, 2026, adds what explains why this matters: most of the corporate buying journey happens before the first contact with a salesperson.
What a company website is not: a store with a shopping cart, a campaign microsite or the product itself. Confusing these formats is the start of a wrong scope.
Which pages go into the first version of a company website?
Five pages cover the first version of most company websites: home, one page per service or product line, about, proof (case studies or clients) and contact. Blog, careers, policies and industry-specific pages come later, once there's someone to keep each of them updated.
The Brazilian market sells the opposite. One technology agency, on a page updated on January 11, 2026, describes the company website as the format for businesses that need lots of pages. Another, on a page updated on January 22, 2026, bundles "up to 12 pages" into its plan. The number comes from the package, not from the business. At Wama, the order is reversed: the scope comes from the answer to one briefing question, which is what needs to happen after someone visits the website. Each page exists to lead to that, or it doesn't exist.
An extra page is a page someone will have to write, approve and maintain. Among the three things that move a project budget the most at Wama, the number of unique pages comes first, followed by who writes the copy and the level of custom animation. Check how much the number of pages weighs on the budget before asking for a proposal with fifteen of them.
What each page needs to prove
A page is only justified if it answers a question the visitor brings. Defining scope means writing, next to each page, which question it closes. If two pages close the same one, one is a section of the other.
Home: what this company does and why I'd keep reading. The logic of what the homepage has to solve in the first few seconds applies.
Services or products: do you do exactly what I need, and how does it work in practice. One page per offering line, never a single page with everything in it.
About: who's behind it and with what team. It's not the history in chronological order; it's the reason to trust the company.
Proof: you've already done this for someone my size. Case studies, clients, testimonials with name and title.
Contact: how do I talk to a person. Phone, a short form and who replies.
Technical requirements aren't pages; they're a delivery condition for all of them. A digital consultancy, in an article updated on May 12, 2026, lists the essentials: responsiveness, speed, social proof, security and accessibility. Accessibility, by the way, has its own Brazilian standard: the digital accessibility page of Governo Digital, the Brazilian federal government's digital office, read in September 2026, points to ABNT NBR 17225 for web content and applications. None of this becomes a separate line in the scope. It all goes into every page, or the website isn't ready.
What can wait for the second version
Blog, careers, industry-specific pages, a resources area and a version in another language. All good ideas. None of them need to be live at launch, and several get worse if they go live empty.
The criterion is simple and uncomfortable: is there someone responsible for keeping this page updated over the next six months? A blog without a writer becomes proof of neglect, with the last post from two years ago visible to anyone evaluating the company. A careers page with no open roles says the same.
Cutting these pages has two practical effects. The project gets shorter, and it's worth looking at how many weeks each block of pages adds before locking the schedule. And the cost of maintaining pages nobody updates is paid every month, in attention and in money.
At Wama, the number one cause of delay isn't design or development: it's client content that never arrives. A lean scope is a timeline decision.
Company website, landing page or one-page site: how do you decide?
Decide based on what needs to happen after the visit. A company website serves a business that needs to be vetted and has more than one offering. A landing page serves a campaign with a single offer. A one-page site serves someone with a single offering and too little content to support separate pages.
Format | What it's for | When to choose it | Where it fails |
|---|---|---|---|
Company website | Official presence, vetting, multiple offerings | A company with more than one service line and content to support it | Becomes an expense when the business still has a single offering |
Landing page | One campaign, one offer, one conversion | Launches, paid traffic, offer testing | Doesn't hold up for someone checking whether the company really exists |
One-page site | A short presentation in a single scroll | Single offering, little content, early-stage operation | Gets cramped as soon as a second service line appears |
A page-building platform, in an article from August 21, 2026, reaches the same criterion: the choice depends on the goal, the number of offerings and what the company can maintain. If the question is about budget, the cost of a separate campaign page settles the comparison faster than any design argument.
Who edits the company website after it goes live?
Ideally the client's team, on their own, without depending on whoever built the website. That isn't a side effect of hiring well; it's a scope decision: what becomes editable content in the CMS and what stays locked in the design needs to be defined before the project starts.
At Wama, the website is delivered with training for the team on how to use the CMS, and people who only publish content use an editor profile, with no risk of touching the layout. The domain and subscription stay in the client's name. Company websites built this way, like those for Vibra, Medellin Games and Biz, launch ready for the client to publish without opening a ticket.
That capability depends on the platform, and that's where the platform that decides who can publish a new page deserves attention before the proposal is signed. The same digital consultancy frames the choice of CMS as a team decision, not a technology one. We agree, with one caveat: the Framer CMS page, published on September 8, 2026, describes editing and publishing content right on the canvas, and that's what lets the marketing team publish without calling anyone.
Common mistakes when defining scope
Accepting the package's page count. When the proposal arrives with "up to 12 pages," the vendor defined the scope. Write your own list first, with the document that locks the scope before the proposal.
Confusing a requirement with a page. SEO, accessibility and speed are a condition on every page. A proposal that sells them as extras charges twice.
Launching the blog with the website. Without someone writing every week, the blog becomes the most visible proof that the company has been neglected.
Leaving the copy for last. Who writes the copy is a scope item and moves the price. Defining it in the proposal separates the project that delivers on time from the one that stalls waiting for content.
Changing scope after the design is approved. It's the third biggest cause of delay in Wama projects, behind content that doesn't arrive and approvals that take too long.
With the list written, you can check whether the proposal covers the scope you wrote, instead of comparing vendors by the total at the bottom. And if who does the work is still undecided, choose which production path fits that scope.
Frequently asked questions
How many pages does a company website need?
Five cover the first version for most companies: home, services, about, proof and contact. The right number is the smallest set that answers the questions visitors bring. Additional pages only go in when there's someone responsible for writing and maintaining each one.
What's the difference between a company website and a landing page?
A company website is the business's official presence and serves people checking whether it holds up. A landing page exists for one campaign and a single offer, with a single conversion. They're formats with different goals, and one doesn't replace the other.
Does a company website need a blog?
Not in the first version. A blog helps attract organic search traffic and build authority, but it only works with steady output. Without someone responsible for publishing, it becomes the most visible proof that the company has stalled. Better to launch it later, with a content plan in place.
What makes a company website budget go up?
Three things, in this order of weight in Wama's experience: the number of unique pages, who writes the copy and the level of custom animation and interaction. Integrations and a logged-in area don't make a company website more expensive; they change the type of project.
Can I edit the company website on my own afterward?
Yes, when the scope defines what stays editable in the CMS. At Wama, the client's team gets training and uses an editor profile, which publishes content without touching the design. The domain and account are in the client's name from delivery onward.
The next step
Before asking for a quote, write the list of pages for the first version and the question each one closes. With that document in hand, the conversation shifts from "how much does a website cost" to "how much does this website cost." Wama designs and builds company websites end to end, with a single person from briefing to launch. To discuss your scope before it becomes a proposal, talk to Wama about your website's scope.
