Freelance services page: make your offer easy to understand

Start with a working situation you know how to handle. “I build websites for all businesses” describes a very broad activity. “I design brochure websites for independent professionals who have a defined offer and want to present it clearly” already identifies an audience, a need and a starting condition. This choice does not prevent you from accepting other work. It gives this page a clear centre.

Write three sentences in a document: the client's situation before your involvement, the work you do and what the client receives. Prefer an outcome under your control, such as pages that have been built and checked, to a commercial promise your service alone cannot guarantee. You can contribute to a better presentation without controlling the quality of the client's offer, their competition or their sales activity.

Then add a concrete suitability criterion. Does the client need to have chosen their activity, gathered their text or identified the person who approves the work? Also identify projects that require another solution: a complex shop, a members' area or a business application, for example, if you do not handle them.

If you are still unsure about the need, do not compensate with very general wording. Return to the conversations that help you test an offer before building. A page cannot, on its own, resolve uncertainty about what customers are actually looking for.

A first version can follow six sections: the offer in one sentence, the situations it suits, the deliverables, an explained example, the working conditions and contact. This sequence is a proposal to adapt, not a universal rule. Its main purpose is to check that each section answers a specific question rather than repeating “bespoke” in several different ways.

In the first screen, state the service, the audience and the next step. A visitor arriving through a recommendation may already want to contact you. Another will need to read the details. Provide a way to reach the contact section without making everyone follow the same path, then explain the offer further down the page.

Make your headings informative: “What you receive” is more precise than “Our added value”. Use a list for comparable items and short paragraphs to explain a condition. If one sentence answers three different questions, split it up. On mobile, check that decisive information is not available only inside an image or a tooltip.

To keep costs down, avoid creating several nearly identical pages before you understand your needs. One main page is enough for a coherent offer. A second becomes useful when a service genuinely involves a different audience, different deliverables or a different process. The structure should follow those differences rather than an arbitrary number of sections.

A deliverable should be specific enough for two people to recognise the same thing. “A professional website” is not sufficient. You might write: “A home page, a service description page and a contact page, built using content we have approved together.” Adapt the list to your actual offer and identify anything that still depends on scoping the project.

Separate what is included, what the client supplies and which requests will be considered separately. For example, adding approved text to a website does not necessarily mean that writing all of that text is included. Setting up a form does not mean that you will then organise the sales follow-up for incoming enquiries. These distinctions are useful even before discussing price.

Also describe revisions. A consolidated round of corrections to one version is not the same as a complete redesign after approval. Your page can explain the approval principle and leave the details for the project-scoping conversation. Do not publish a numerical limit you do not intend to apply or that systematically varies from project to project.

Finally, translate necessary technical terms into their practical consequences. If you offer a website the client can edit, explain which areas they can change and which changes they will still need to request from you. If some expenses are separate, such as the domain or hosting, identify them and explain how they will be specified. The aim is to prevent the same expression from carrying two different expectations.

You can show your work without inventing a client or a result. A personal demonstration is suitable if its status is visible next to the visual: “Demonstration project, fictional business, not commissioned by a client.” This clarification should accompany the evidence rather than being hidden in a distant note.

Present the problem you chose to address, the constraint you worked with and the decisions someone can observe. For a services page, you can explain why you separated two offers, reduced the number of questions or made a condition visible before contact. Show the part of the interface that allows the reader to verify your explanation. A decorative screenshot alone says little about how you work.

Distinguish what you built from what you did not measure. You can say that you produced a mock-up or tested a button's behaviour if that is true. You cannot turn that demonstration into a case study about sales at a business that does not exist. Also avoid improvement percentages without a source and reconstructed testimonials.

On a small budget, one well-explained example is often easier to produce and maintain than several superficial projects. For real work, obtain the necessary permissions before publishing project material. Otherwise, create an independent demonstration instead of allowing names, messages or confidential information to appear in a screenshot.

The time a project needs also depends on what is available at the start. List the things that genuinely block your work: required access, content, usable images, a decision about the service to present and the person responsible for approvals. Do not ask for everything that might someday be useful. Distinguish what you need to assess the enquiry from what you will request after agreement.

Then explain the stages and their completion conditions. For example: scoping when the objective and boundaries are understood; preparation when the necessary content is available; production when the main choices are approved; handover after the planned checks. A stage is more useful when the client understands what allows the project to move to the next one.

If you provide an estimated duration, explain the assumptions behind it and when it can be confirmed. Avoid presenting a duration as fixed when it assumes immediate replies or text that is already ready. Do not announce an availability date you have not checked.

For the budget, choose a presentation you can honour: a genuinely defined fixed scope, an explained reference point or a quote after a few questions. Do not use an entry price if almost every request requires substantial additions. Before publishing an amount, work through your price floor and the actual cost of a project. The page should remain consistent with your ability to deliver the service properly.

The first enquiry helps you decide what conversation should happen next. It does not need to contain the entire production brief. For a simple offer, you can begin with a reply address, a short description of the need and, if it genuinely changes your response, a question about the current situation. You can ask for a name to personalise the exchange without automatically adding a phone number, postal address or several ways to contact the person.

The W3C guidance on forms highlights necessary fields, clear labels and understandable feedback. Check that labels remain visible and errors explain the required correction.

The GOV.UK design system encourages justified questions and uncertainty where appropriate. For a schedule or budget, “Not decided yet” can be a useful answer.

Choose a button that describes the action, such as “Send my enquiry”. Nearby, explain the next step plainly: you will read the request and indicate whether another conversation is needed. Announce a response time only if you can meet it. Finally, test actual receipt using fictional data and check that the message reaches the person who should handle it.

The page title should describe the service on offer. If you work with a particular audience or sector, mention it when doing so genuinely helps the reader. Do not add a list of towns where you have no reason to provide a distinct offer. Clear wording will be useful both in a shared link and in a search result.

Google's guidance on titles favours descriptive, concise wording. Choose a title that names your service and matches the visible content.

Place the words of your trade where they make a sentence more precise. You do not need to repeat “freelance website design” mechanically in every subheading. Instead, explain the real questions: types of pages, content to prepare, possible changes and requests outside the scope.

Google recommends useful content created for its audience, without a preferred word count. Keep information that helps readers decide. No structure guarantees search rankings or incoming enquiries.

Copy this worksheet into your working document. Answer in everyday sentences, then use your answers to build the page. Replace the text in square brackets; the examples are not commitments to copy unchanged.

Main offer

• I help [type of client] who is in [concrete situation].
• I take responsibility for [work performed].
• At the end, the client receives [observable deliverables].
• This offer is suitable if [suitability conditions].
• It does not cover [requests outside the scope].

Scope and responsibilities

• The included elements are [short, precise list].
• The client supplies [necessary content or decisions].
• Requests considered separately are [list].
• Approvals work like this: [who approves, and when].
• Changes after approval are reviewed through [process you actually use].

Available evidence

• I can show [permitted real project or demonstration].
• Its exact status is [explicit description].
• The reader will be able to observe [visible decision or work].
• I do not have data about [unmeasured outcome].

Process and estimate

• To assess the request, I need [minimum information].
• To begin production, I need [dependencies].
• The schedule will be clarified when [conditions].
• The budget will be presented as [format actually used].
• Possible separate expenses are [relevant categories].

First enquiry

• The button offers to [actual action].
• The questions asked are [minimal list].
• Optional fields are clearly identified: [which ones].
• After sending, the visitor sees [confirmation].
• I receive the enquiry in [verified destination] and decide [next step].

Then reread each line, looking for words that are difficult to verify: “complete”, “fast”, “unlimited”, “optimised”. Replace them with a description or remove them. If an answer remains unknown, record the decision you need to make. Do not turn it into a promise just to fill a box. This worksheet can also support your scoping conversation, keeping the page consistent with the way you work.

The following example is entirely fictional. It illustrates possible wording for an imaginary freelancer and describes neither a client nor a SprintLead commercial offer.

Title: A brochure website to present your consulting business

“You have defined your activity and want a simple website to share with your contacts. I design the pages that explain your offer, your background and how to get in touch.”

Which projects is it for?

“This service is for independent consultants who have one main offer and can provide an initial version of their text. If you are looking for a training platform or a client area, we will first check whether a different solution is needed.”

What is planned

“The scope is defined before production: pages to create, content to add and how contact will work. You first approve the organisation of the information, then the completed version. Full content writing, visual identity creation and recurring maintenance are considered separately.”

Work example

A relevant demonstration for this offer would show how to distinguish two services and clarify what a visitor can request. Its caption would explain that it concerns a fictional business, without attributing any commercial results to it.

Getting started

“Tell me about your activity, what you want to present and what already exists. If your schedule is not yet decided, you can say so. I will check whether the request fits this service before proposing the next step.”

This draft does not replace project scoping. It does, however, give the reader several useful pieces of information before writing. In your version, replace every sentence with what you can actually deliver and show evidence that corresponds exactly to the advertised service.

Ask someone close to your intended audience to read the page without an oral explanation from you. Then ask three questions: “What service is offered?”, “What would be included in a project?” and “What would you do to discuss it?” Ask them to point to the passages supporting their answers. You are looking for a concrete misunderstanding, not a general design rating.

If they assume your offer includes an absent service, find the sentence that created the expectation. If they do not know whether their project fits, make the suitability criterion more visible. If they hesitate about contact, first check the button's wording and position before adding a second route.

Also perform functional checks with fictional data: navigation on a small screen, text readability, links, required fields, error message, confirmation and receipt. Move through the form with a keyboard. Check that an image does not hide essential information and that a demonstration link leads to the correct project.

Keep a short list of observed problems, their consequences and the chosen correction. Fix what prevents someone from understanding the offer or sending an enquiry first. A colour preference can wait if the form does not work. After every important correction, repeat the relevant journey all the way through. You can test what exists without claiming to have measured its commercial effect.

Once the page is in use, record recurring questions and observed misunderstandings. You can keep a very simple private table: type of request, missing information, next action and possible page change. Avoid copying personal information you do not need for this analysis.

Group observations by problem. Several maintenance requests might suggest that your scope is unclear, but they could also come from another channel where you present a different offer. Check the source before drawing a conclusion. One unusual enquiry does not necessarily justify changing the entire page.

Choose one correction at a time where possible: clarify a deliverable, explain a dependency or make an example more visible. Record the date and the reason for the change. With few visits or enquiries, remain cautious about conclusions. A variation may come from the audience, the time of year or your prospecting activity, rather than the text alone.

Finally, keep the page aligned with your actual practice. Remove an example you can no longer present, correct availability that has become inaccurate and revise conditions you no longer apply. Your page will be easier to maintain if every section has an identifiable function. The right next addition answers an observed question rather than simply making the presentation longer.