Website for sole traders: what should the first version include?

Do you need your own website yet?

A network or platform profile can sometimes support an early business. Your own website becomes more useful when you need independence from a platform, space to explain services, a home for project evidence, a way to qualify enquiries or an address on your own domain.

It does not need to automate the entire business. Answering common questions and improving the quality of the first conversation can be a worthwhile first scope.

Six things a visitor should understand at launch

1. What you provide. Name the service or result in concrete language. A broad promise to help people move forward is difficult to assess.
2. Who it suits. Describe the situations where your work fits so a relevant customer can recognise their need.
3. Which problem it addresses. Explain the uncertainty, delay, error or missed opportunity from the customer's perspective.
4. How you work. Describe what follows an enquiry, the information you need and the decisions the customer makes.
5. Why you are credible. Use relevant experience, projects, qualifications, demonstrations or a transparent process that you can substantiate.
6. What to do next. Choose a main action and explain what the visitor can expect after clicking.

One page or several?

A one-page site often fits one clear service, one main customer group and one primary action. The essential information can follow a continuous decision path.

Separate pages become useful when services answer different questions, need different evidence or have distinct entry points. Projects and knowledge articles can also deserve their own pages when they contain enough useful material. Splitting near-identical copy into thin service pages does not improve the customer's decision.

A practical structure is a home or landing page, service pages where justified, an introduction to the business, relevant examples, contact and necessary legal information. Let the tasks determine page count rather than choosing a larger package for appearance alone.

Use the proof you actually have

A new business may have few customer cases. Be clear about that. A carefully explained own project or working demonstration can show how you think without suggesting a customer result you have not achieved.

Match proof to the buyer's doubt. Technical work may need a working example and explanation of constraints; a personal service may need relevant experience and a clear process. A vague compliment or unexplained logo provides little evidence of the specific work.

Account for costs and ownership after launch

List recurring domain and hosting charges, software licences, maintenance, email and form services, backups, content changes and support. Confirm who controls the domain, hosting, incoming enquiries, content and relevant accounts.

Keep the site representative as the business changes

Recurring charges should be visible and understandable. Plan time to review services, prices and project evidence as the business changes. A website that is never updated gradually describes a business that no longer exists in the same form.

Launch with a question you can evaluate

The first version tests whether relevant visitors understand the offer and take an appropriate next step. Review entry pages, repeated questions in conversations, incomplete forms, confusing service descriptions and the suitability of enquiries. Visitor totals alone will not explain these issues.

Expand when real questions justify another page or a recurring task justifies a feature. Before requesting a quote, write one example: what does your ideal customer ask, what evidence helps them choose and what should happen after contact?

Compare website development, a one-page website and the current pricing options. If different services need different explanations, record them in a website brief.