A business website is a set of pages with jobs: explain the work, and help a stranger start a conversation. If you have been asking what is a business website for, that is the answer worth keeping. The design is there so each job is obvious. You should know what to ask of the homepage and the service pages before anyone discusses colors.
Takeaways
- Write one sentence for the homepage and one sentence for each service page before you talk about color.
- A page that cannot explain the work, or cannot start a conversation, does not have a job yet.
- Choose a stack an editor can still update after launch, or the true sentences will go stale.
- Do not expect a redesign alone to produce traffic or enquiries. The pages still have to say something a buyer can use.
Give Every Important Page a Job
The useful way to look at a site is page by page. Each important URL has a job, and the job is a sentence you could say out loud to someone who has never heard of the firm. The homepage helps a stranger see what you do and how a conversation starts. A service page explains one kind of work. A contact page makes the next step obvious. If you cannot say the sentence, the page is not ready to design.
Website Design starts from that idea. A site is a set of pages with a job: explain the work and start a conversation. A handsome layout wrapped around a vague sentence is still a vague sentence. Visitors do not reward effort they cannot see. They reward a page that tells them, quickly, whether they are in the right place.
When two pages want the same job, you do not have two pages yet. Merge them, or give one of them a narrower job. Overlap is how visitors get lost, and it is how editors later update the wrong URL and leave the right one stale. A short list of sentences is a better brief than a folder of references.
| Page | Its job | It is failing when |
|---|---|---|
| Homepage | Show what the firm does and how a conversation starts | A stranger cannot tell what you sell, or finds several competing offers |
| Service page | Explain one kind of work in the buyer's words | The page names every service and explains none of them |
| Proof page | Show how the work proceeds without invented results | The page hints at outcomes you cannot stand behind |
| Contact page | Make the next step obvious and specific | The form gives no clue what happens after someone sends it |
Ask Something Specific of the Homepage
The homepage is not a storage room for every sentence the firm has ever liked. Its job is narrower. A stranger should be able to say what you do, who it is for, and what to do next, without opening a menu. If those three things are missing, no amount of polish on the hero will repair the visit.
Ask the homepage to introduce the firm, not to close every sale. People who arrived without a specific offer in mind need a map. People who arrived for one offer often need a different URL, and stuffing that offer into the homepage makes both visitors work harder. Give the homepage the orientation job, and let deeper pages carry the detail.
A homepage can mention several services. It should not explain all of them at equal length. Pick the work you actually want enquiries about, say it in plain language, and link to the page that explains it. The link is a promise that the next page will go deeper, not a second copy of the same paragraph.
Write the homepage sentence on paper before anyone opens a design file. If the sentence is "we help businesses grow," it is not finished. Name the work. Name the kind of buyer. Name the next step. Then the layout has something to make obvious.
Let Service Pages Explain the Work
A service page earns its place when it can explain one kind of work well enough that a qualified buyer knows whether to talk to you. That means the scope, the boundaries, and the way an engagement starts. It does not mean a list of adjectives. "Strategic, trusted, full-service" can sit on any firm's page. A buyer cannot tell two firms apart with those words.
Start from the questions people already ask on the phone. What do you take on? What do you refuse? What should the buyer have ready? What happens after the first conversation? Answer those on the page, in the same order a careful person would ask them. The page becomes a rehearsal of the real conversation, which is what a stranger needed.
Give each real service its own page only when the explanation would be false if you merged it with another service. If two offers share the same buyer, the same process, and the same next step, one page is kinder. If they diverge, separate them so the right person finds the right explanation. A long menu of near-duplicates helps no one.
Internal links should use the name of the service, and they should point at the URL that actually explains it. A button that says the name and lands on the homepage breaks the job you just assigned. The service page is the explanation. The homepage is the introduction. Do not swap them.
Start the Conversation on Purpose
Explaining the work is only half the job. The other half is starting a conversation with the right person. A conversation starts when the visitor knows what they are asking for, what you need from them, and what will happen next. A form with five fields and no context is not a conversation. It is a box.
Decide, for each important page, what the conversation is. A service page might ask for a short description of the work and a way to reply. A general contact page might be for everyone who does not fit a service yet. Those are different conversations. Mixing them produces messages your team cannot route, and it teaches visitors that sending a note is a gamble.
Put the path where the explanation ends, not in a corner that fights the page. If the page has done its job, the reader is ready. If the page has not, a louder button will not fix the confusion. Design serves the job. It does not replace it.
Landing Pages are the version of this idea for a single offer. The homepage introduces the firm. A dedicated page repeats one promise and asks for one action. Use that distinction when a campaign, an email, or a partner link is about one thing, and keep the homepage for people who are still orienting.
Keep a Stack Someone Can Update
A site that no one can edit is a brochure you already regret. The sentences that were true at launch will drift. A service will change name. A person will leave. A form will start asking for something you no longer need. If changing a sentence requires a project, the sentence will stay wrong.
Build on a stack someone can keep updating after launch. "Someone" should be a named person on your side, or a maintainer you trust, and they should be able to change words without breaking the layout. If the only way to edit is to open a code file, be honest about that, and staff it. Pretending the team will "just update it" is how pages rot.
This is where the editor matters more than the theme gallery. WordPress Development is one way to give editors a safe way to change pages. A different stack can do the same job if the people who own the words can use it. The test is not the brand of the tool. The test is whether a careful editor can publish a true sentence on a Tuesday without calling in a rescue.
Keep the stack small enough that updates are boring. Every extra plugin, script, or one-off template is a thing that can break the edit. Boring is a compliment. A site your team can keep true will outperform a fragile site that looked perfect on the day it launched.
Leave Traffic Promises Off the Table
A clearer site can make a visit more useful. It cannot, by itself, manufacture visits. People still have to arrive, and arrival depends on search, referrals, ads, and the reputation you already have. Treat those as separate work. Do not let a design conversation quietly become a promise about traffic or enquiries.
Do not promise traffic or enquiries from a redesign alone. Website Redesign can keep the URLs that still apply and replace the pages that no longer say what you do. That is a real improvement. It is not a forecast. If someone offers you a number of leads in exchange for a new look, ask them what else has to be true. If the answer is only the visual, the promise is larger than the work.
Use this order when you brief the work:
- Write the job of the homepage in one sentence a stranger could repeat.
- List the services you want conversations about, and keep a page only if you can explain that service on its own.
- Mark any page that no longer matches the work, and decide whether it is replaced or removed.
- Name the person who will edit sentences after launch, and confirm the stack lets them do it.
- Only then talk about color, type, and pictures.
If a proposal skips to the last item, send it back. You will know what to ask of the homepage and the service pages, which is the decision that makes every later choice easier to judge.
Questions
What Should the Homepage Actually Do?
The homepage should show what the firm does, who it is for, and how a conversation starts. It introduces the whole firm. It should not try to finish every sale or carry every detail that belongs on a service page. If a stranger cannot repeat the point of the page, the homepage has not done its job yet.
How Do You Know a Service Page Is Ready?
A service page is ready when it explains one kind of work, including what you refuse and how a conversation starts. A buyer should be able to tell whether they fit. A list of flattering adjectives is not an explanation. If the page could be copied onto a competitor's site and still sound right, it is not finished.
Who Should Be Able to Change the Words?
Someone who knows which sentences are true should be able to change them without breaking the layout. That person might be on your team or might be a maintainer you keep. If every edit waits on a developer who is hard to reach, the site will go stale. Name the editor before you choose the stack.
Will a Redesign Bring Enquiries on Its Own?
A redesign can make the pages clearer and can replace URLs that no longer say what you do. It does not, by itself, create traffic or enquiries. People still have to arrive, and the pages still have to explain the work. A lead forecast that rests only on a new look is a claim the work cannot support.
What Belongs in the Brief Before Colors?
The brief should name the job of the homepage, the job of each service page, and the person who will edit the site after launch. It should also say which pages no longer match the work. Colors, type, and pictures come after those sentences exist. A mood board is not a substitute for the jobs.
Conclusion
A website is a set of pages with jobs, not a brochure that happens to be online, and the design is there so the job is obvious. Ask what the homepage and the service pages must do before anyone discusses colors. When those sentences are true, and someone can still edit them after launch, the site can start a real conversation.
If you want help deciding what each important page is supposed to do, Speak With Us.
