What does a services page need that a homepage does not?

What does a services page need that a homepage does not?

Scope, sequence, and price shape. A homepage introduces you to everyone. A services page is read by one person deciding whether to start a specific engagement with you, so it has to answer what is included, what happens in what order, and roughly what this costs.

I redesign these pages often, and the pattern is consistent. The homepage is usually fine. The services page is a homepage with a different heading, which means the person closest to buying gets the least useful page on the site.

This post is about what belongs on that page, in what order, and why each section earns its place.

Why do most services pages read like a second homepage?

Because they get written by the same person on the same afternoon with the same instincts. The homepage voice is broad and aspirational, and that voice carries over into a page whose only job is to remove uncertainty from one decision.

There is also a quieter reason. Writing a services page forces you to commit. What is in, what is out, how long it takes, what it costs. Those commitments are uncomfortable, so pages drift toward language that sounds substantial while promising nothing.

The test I use is the same one I use everywhere. Could a competitor publish this page with their logo on it? If yes, you have written a brochure. A real services page should be slightly awkward to copy, because it contains your actual choices.

What is the first section actually for?

Confirming the reader is in the right place and naming the outcome. One sentence on what the service is, one on who it is for, one on what changes when it is done. The hero on a services page is a filter, not a pitch.

The reader on this page usually arrived from somewhere specific. A search, your nav after reading the homepage, a referral link, or a sales conversation. They already believe you might be able to help. What they need is confirmation that this particular page is about their situation.

That is why an aspirational hero wastes the most valuable space on the page. Say the plain thing. Naming the audience out loud also lets the wrong readers leave quickly, which is the same logic as a who this is not for section, and it protects both your time and theirs.

How much process detail belongs on the page?

Enough to make the engagement feel real and bounded. Three to five stages, in order, each with what you do and what you need from them. The point is not to impress anyone with methodology, it is to let a buyer imagine their next four weeks.

Process sections fail in two directions. Too vague and they read as filler, since discover, design, deliver describes every service business on earth. Too detailed and they read as internal documentation, and nobody hires a process, they hire a person who has run it before.

The detail that earns the most trust is the part where you say what you need from the client. A sentence admitting that stage two needs their feedback within a week does more for credibility than three paragraphs of philosophy, because it shows you have done this with real people who were busy.

Where should price, or the shape of price, appear?

On the page, above the last section, in whatever form you can honestly commit to. A range, a starting point, a typical project size, or the variables that move it. Silence about price does not create intrigue, it creates a filtering problem you now have to solve in calls.

I price on a fixed fee, and most of my projects fall between one thousand and ten thousand dollars depending on scope. Saying that publicly costs me the enquiries from people whose budget is far away from it, and that is precisely the point. The conversations that remain start from a shared reality.

If you genuinely cannot publish numbers, publish the shape. What the price depends on, what a small engagement includes versus a large one, and what would make a project expensive. A buyer who can place themselves in a range will fill in your form. A buyer who cannot will ask three competitors who did publish something.

What kind of proof works on a services page?

Proof that matches the service being sold on that page. A testimonial about your responsiveness belongs next to the process section. A named outcome belongs next to the promise it supports. Generic logos at the bottom of every page have stopped carrying weight.

The strongest proof on a services page is specific and modest. One short client quote that mentions the actual problem beats five that call you a pleasure to work with. If you have relevant numbers you can stand behind, place them next to the claim they support rather than in a separate band of statistics.

Where you have no proof yet, say what you would do instead of implying experience you do not have. Describing your approach honestly reads better than an empty logo wall, and it avoids the trap of building a page you would have to defend.

What should the page do about objections?

Answer the three or four real ones in the reader's words, on the page, before the form. Timeline, ownership, what happens if it does not work, and who does the work. These come up in every call you have, which is exactly why they belong on the page.

I build this section from sales conversations rather than imagination. The questions people actually ask before hiring me are narrow and repeatable, and every one I answer in advance is a shorter call and a warmer start. A frequently asked section written from real questions is a conversion feature, not filler.

Handle the uncomfortable ones directly. What if we already tried this and it failed. What if we cannot give you access to the data. What if the project has to pause. A page that addresses those reads as experienced, which is the whole impression a services page is trying to create.

How should the page end?

With one ask, sized to the reader's readiness, and no competing options. A services page that ends with three equally weighted buttons has moved your decision problem onto the buyer. Pick the next step you actually want and make everything else quieter.

For most service businesses that next step is a conversation, and the fastest version of it wins. A short form or a booking link through Calendly or Cal.com both work. What matters more is what you ask for. Fields that let you prepare are worth including, fields that only feed a CRM report are worth cutting.

Keep one secondary path for people who are not ready, and make it visibly lighter. A relevant article, a worked example, or a short recorded walkthrough in Loom gives them somewhere to go that is not the back button.

What does this mean for how the page is built?

Build it as its own page type rather than a variation of the homepage template. Different sections, different order, different components, reusable across services. On Webflow that usually means a small set of section components you can rearrange per service rather than one long custom page each time.

The practical benefit shows up on the second and third service page. If the process, pricing, objections, and proof sections exist as components, a new service page becomes an afternoon of writing rather than a design project. Consistency also helps readers who compare two of your services.

Design them from the content out. I sketch the section order in plain text first, in Figma or a Notion doc, and only then decide what it looks like. Doing it the other way round produces beautiful sections that the copy has to be trimmed to fit, and a homepage that got too long is usually the result of that habit, which is why deciding what to cut from a homepage is a related exercise worth running first.

What should you do next?

Open your main services page and check for four things. A scope sentence in the first screen, an ordered process, something about price, and answers to the objections you hear on calls. Add whichever is missing before you touch the visual design.

If you want a second opinion on a services page before you rebuild it, that is the kind of review I do regularly, and it is usually clearer when the person reading it has never seen your internal slides. The same instinct applies to writing service pages around outcomes rather than features. Reach out if you want me to read yours.