When to use this template
Use the one-page service offer when you're ready to show a specific buyer what you deliver, for how much and what to do next — before you have a website. It's the document you attach to a first message, share after a discovery call or send when someone asks "what exactly do you do?".
It works best for a productized service: one deliverable, one price, the same scope for every client. If you're not there yet, read productized service: define scope and acceptance first.
How to fill it in
Who and why. Name the buyer by type, size and market. Describe the problem in their words — phrases you heard in conversations are best. Mark it as a hypothesis until buyers confirm it. Add a trigger if you know one: the moment the problem becomes urgent, like a promotion or a reporting deadline.
What you deliver. Describe the deliverable so concretely that a buyer could picture opening it. List the inputs you need from the client, the limits (size, rounds of changes, response time) and what's excluded. Write the timeline as an assumption until it's confirmed with the client.
Price and acceptance. State a price and currency. "Contact us" hides the most useful signal you'll get from a test. Then write the acceptance check — how both of you will know the work is done — and link a labelled sample.
Next step. Offer one small action, like a free check of part of their data, or a 15-minute call. Add your name and business contact.
A filled-in example
| Field | Example |
|---|---|
| For | Independent UK online shops with 100–2,000 products |
| Problem | Duplicates and mixed units cause rejected listings before promotions (hypothesis) |
| Deliverable | Defect report by row, field and rule; corrected copy with safe fixes; open questions |
| Client provides | Authorised CSV export, ≤ 2 MB, ≤ 200 rows, ≤ 10 fields |
| Limits | One round of questions; IDs and prices never changed; no write-back |
| Timeline | 3 working days after inputs (to confirm) |
| Price | €150 per audit (hypothesis) |
| Acceptance | Every flag references a row, field and rule; protected fields unchanged |
| Next step | Share an export for a free 20-row check |
Checklist before you send it
- Every field is filled, or marked "To confirm".
- Nothing claims experience, clients or results you can't show.
- The sample is labelled as synthetic or authorised.
- The price includes currency and says whether tax is added.
- It fits on one page.
Variations for other services
| Service | "For" | "Deliverable" | "Next step" |
|---|---|---|---|
| CRM cleanup | Agencies with 1,000–10,000 contacts | Deduplicated export + merge log | Share a sample export for a free 100-record check |
| Help-centre rewriting | SaaS teams with 20+ support articles | Three rewritten articles to your style guide | Send links to your three most-read articles |
| Supplier research | Small manufacturers sourcing one component | Five-supplier comparison with sources | Book a 15-minute call to agree criteria |
The structure stays the same; only the content changes. That consistency is what makes the offer easy to read and easy to compare.
After you send it
Watch which parts cause questions — those are the parts to rewrite. Record every response in an evidence log, and judge the result against the decision rule in your validation plan, not against how the conversations felt.