Back to the blog

Websites for service businesses

Plan or improve your service business website: review enquiries, define its scope, compare quotes and agree on maintenance, with real project examples.

By Updated:

What to decide before building or improving your website

A service business website needs to explain your offer, provide evidence of your work and make contacting you straightforward. Before commissioning a new site or a redesign, define who it serves, which pages it needs and who will maintain it.

This guide connects four decisions: why enquiries are scarce, which content needs a page of its own, what affects the budget and who will own the website after launch. Start with the question that matches your situation, then compare the approach with two published client projects.

Start with the decision you need to make

If you already have a website, establish what is failing first. For a new website, define the scope before comparing proposals on the same basis.

  1. Your website receives few enquiries

    Check whether the issue is relevant traffic, a clear offer, reasons to trust you or a working contact route. Each one calls for a different improvement.

  2. You are choosing between a landing page and a full website

    One specific offer may work on a single page. Several services, audiences or journeys may need separate routes. Let the information your client needs determine the structure.

  3. You want to request or compare quotes

    Pages, content, languages, integrations and maintenance change the work involved. Define what a proposal needs to cover so you can compare equivalent deliverables.

  4. You need to define what happens after launch

    Domains, hosting, content, dependencies and integrations all need owners. Separate maintenance, support, bug fixes and improvements before agreeing to a retainer or one-off work.

What to prepare for the first conversation

  • Your business, who you help and which service you want to lead with.
  • Your current website, if any, and a specific problem you want to solve.
  • Services, work examples and testimonials you have permission to publish.
  • Available copy, images and branding, and who will supply anything missing.
  • Required features, an indicative budget and any target launch date.
  • Who will update content and whether they need an editing dashboard.

Two projects showing these decisions in practice

  • Patricia Pólvora

    A 17-page website organising consultancy services, reports, publications and career information, with contact and booking options. The case documents its scope and implementation.

    Read the Patricia Pólvora case study
  • Paula Márquez Brandon

    A 12-page website explaining her method, separating three programmes and bringing client stories together, with WhatsApp and email contact. The case covers content, design and publication decisions.

    Read the Paula Márquez Brandon case study

Apply these decisions to your project

I design and build Astro and TypeScript websites for professionals and service businesses. See the scope, process and how updates are handled after launch.

See the web design and development service