Most service pages are inventories. They list what the team can do, grouped by internal department, written in the language of the trade. The reader, who has a problem and a budget, has to translate all of it into an answer about their own situation.
A decision page does that translation for them. It states the outcome, sets the boundary, explains the process, and gives a price signal. Here is how to rebuild a feature list into one.
Name the decision the reader is making
Before writing, finish this sentence: this page exists so the reader can decide whether to ___. The blank is usually a version of whether this service fits my problem and whether I can afford it.
Everything that does not help that decision belongs on another page, in a proposal, or nowhere. This single test removes half the usual content, including the history of the methodology and the biography of the department head.
Lead with the situation, not the service
Open by describing the reader's week. Late filings piling up, a spreadsheet that three people maintain badly, a warehouse that keeps sending the wrong item. Then state what you do about it in one sentence.
This works because readers recognise their own situation faster than they recognise a service category. It also gives the page a natural place for the words customers actually search for.
Turn each feature into a consequence
A feature list says what you provide. A consequence says what changes for the reader. Rewrite in pairs until every bullet has one.
- Monthly management accounts becomes you know your cash position before the tenth of the month.
- Dedicated account manager becomes one person who knows your file, reachable by phone.
- Cloud-based system becomes your team can log in from site without a VPN.
Keep the feature, because some readers scan for it. Put the consequence first, then the feature in plain words. A bullet that runs to three lines is usually two bullets.
Say who it is not for
Every service has a bad-fit customer, and naming them is a service to both sides. Not designed for businesses under five staff. Not suitable if you need same-day turnaround. We do not handle litigation.
This paragraph increases enquiries from the right people and reduces the ones you would decline. It also makes the rest of the page more credible, because a page that claims to suit everyone reads as a page written for nobody.
The fastest way to look trustworthy is to describe, accurately, the work you turn down.
Explain scope, process, and price together
Readers want to know what is included, what costs extra, and what they have to do. Put those three in one section, because they answer the same anxiety about control.
Then give the sequence: a call, a site visit, a written scope, a start date, a review point. Add realistic durations, including the waits that depend on the customer. If you need access to a system, say how long that usually takes to arrange.
On price: hiding all of it is a choice, but it costs enquiries. You do not need a full rate card. A range, a starting point, or the shape of the pricing model is enough: fixed fee per site, from four thousand, billed monthly over twelve months.
State what changes the number: number of locations, volume, turnaround, whether travel is involved. A reader who understands the variables can self-qualify before writing to you, and the first call starts further along.
One line belongs in every price section: whether tax is included. A UK reader expects VAT stated, a US reader expects state sales tax added at the end, and the UK vs US proposal guide explains how to say it without ambiguity.
Answer the risk questions
Four questions come up in almost every service purchase. What if it goes wrong? Who else do you work with? Can you prove this worked before? What happens when I want to stop?
Answer each in two or three sentences. Name the guarantee, the insurance, the notice period, or the exit process. If there is no guarantee, say what you do instead when a job misses the mark.
Close with a small next step
Book a call is a big ask for a reader who has just met you. Offer something proportionate: send the brief, get a scoping call, check availability for a date. Say what the reader will receive and when.
- Decision statement written at the top of the draft
- Opening paragraph describes the reader's situation
- Every feature paired with a consequence
- Bad-fit paragraph included
- Scope, exclusions, and customer duties listed
- Timeline with realistic waits
- Price signal plus the variables that change it
- Risks answered, small next step offered
Read the finished page as a buyer with a budget and a deadline. If you would still need a call to understand what you are buying, the page is not finished.
