The short answer: productising a service means turning “it depends, let’s talk” into a defined offer with a name, a fixed scope, a clear outcome and a price or price range. It works because buyers compare options, and an offer they can compare is an offer they can choose. A custom service that nobody can explain in a sentence tends to lose to a mediocre one that they can.
This guide covers how to decide what goes into the package, how to name it, how to set the price, and where productising goes wrong. It is aimed at consultants, agencies, trades and professional services businesses that currently sell by the hour or by quote.
What does “productising a service” actually mean?
It does not mean removing all flexibility. It means choosing which parts of your service are the same every time and packaging those parts, then handling the rest as defined add-ons. A productised service has five properties:
- A name that describes what the buyer gets.
- A defined scope: what is included and what is not.
- A fixed timeframe or cadence.
- A price or price band shown or explained up front.
- A repeatable delivery process that your team can follow without reinventing it.
Think of a plumber who sells “Boiler service, fixed price, 60 minutes, includes safety certificate” instead of “plumbing services”. The work did not change; the buying experience did.
Step 1: Find the job that already repeats
Look at your last 20 to 30 projects. Group them by outcome rather than by activity. Most businesses find that two or three outcomes account for the majority of their revenue. Those are your candidates.
For each candidate, ask:
- Do clients ask for roughly the same thing?
- Do we deliver it in roughly the same steps?
- Does it usually take a similar amount of time?
- Do clients come back to us with the same kind of question afterwards?
If the answer to most of these is yes, you have a productisable service. If every project is genuinely different, start by productising only the first phase, such as a diagnostic or a workshop, which is often the easiest entry point.
Step 2: Define the scope with edges
A package is mostly defined by what it leaves out. Write three lists:
- Included: deliverables, number of revisions, meetings, reports.
- Not included: the things clients commonly assume are included.
- Needed from the client: access, assets, approvals, and the deadline for each.
The “not included” list prevents most scope arguments. Typical items are extra revision rounds, work in additional languages, third-party costs such as stock or licensing, and emergency turnaround. Each can become a priced add-on.
Step 3: Name it so the buyer instantly understands
Creative names feel tempting and cost you clarity. A buyer scanning a page should understand, from the name alone, what the offer is and roughly who it is for. We use a simple pattern: [outcome or object] + [format or timeframe].
| Vague name | Clear name |
|---|---|
| Brand Spark | Brand Messaging Workshop: Half-Day, With Written Summary |
| Growth Pack | Website Conversion Review: 10 Fixes in 5 Working Days |
| Essentials | Monthly Bookkeeping for Sole Traders, Up to 50 Transactions |
If you want a more distinctive name, use it as a brand label in addition to the plain description, never instead of it. The principles in our post on naming a B2B brand apply at the offer level too: clarity first, memorability second.
Step 4: Set the price, and decide how much to show
There are three common ways to price a package.
- Fixed price per package. Best for repeatable work with predictable effort.
- Tiered packages. Three levels (for example Starter, Standard and Extended) let the buyer pick their depth. Keep the differences in scope obvious and avoid more than three or four options.
- Subscription or retainer. Best where the value comes from continuity. We explain the logic in the retainer pricing model we use.
To arrive at the number, calculate your true cost to deliver (including unbilled time spent on sales, onboarding and revisions), add the margin you need, then check it against what the outcome is worth to the buyer. A package that saves a client €5,000 can reasonably cost more than one that saves them €500, even if both take you two days.
On visibility: showing at least a “from” price filters out poor-fit enquiries and builds trust. If you cannot publish a price, publish the factors that move it. We cover this decision in detail in whether to show prices on a service page, and how assistants quote prices in how AI answer engines read your pricing page.
Step 5: Build the delivery system behind it
A package only saves time if the delivery is standardised. Prepare these five things once:
- An intake form that collects what you need in one go.
- A checklist covering every step from kick-off to handover.
- Templates for the outputs that repeat: reports, documents, emails.
- A fixed schedule with clear client deadlines.
- A closing routine: handover, feedback request and a suggested next step.
The first few deliveries will feel slower than custom work because you are still tuning the process. Track the hours spent on each, and revise the scope or price after three to five projects, not after one.
Where productising goes wrong
Too many packages. If you launch eight offers, buyers freeze and your team cannot specialise. Start with one flagship and, at most, one entry offer and one premium offer.
Scope that is secretly custom. If every client needs exceptions, the package is just a rebranded quote. Say no to the exceptions, or price them as add-ons.
Underpricing to attract buyers. A fixed price that is too low is worse than an hourly rate that is too low, because every sale locks in the loss. Test the numbers on paper first.
Packaging what clients do not want. Productising only helps if the offer matches demand. Before building anything big, ask five past or prospective clients to describe the problem in their own words, and use their phrases in the name and the page copy.
What if your clients insist on custom work?
Some do, and that is fine. Keep a custom option for larger or unusual projects and use your productised offers as the starting point. A client who enters through a defined entry offer is also easier to move into a longer engagement later, because trust has already been built with a low-risk first step.
How do you test an offer before building everything?
You do not need a finished website to find out whether a package sells. Describe the offer in a one-page document, send it to five people who match your ideal client, and ask three questions: what would you expect to receive, what would you expect it to cost, and what would stop you from buying? If their expectations match your scope and price band, you are close. If they expect something different, you have just saved yourself a month of building the wrong thing.
Then sell it once or twice manually, with the delivery steps written on paper. Treat those first sales as research. Note which questions came up on the call, which objections appeared, and which parts of the scope people tried to stretch. Each of those becomes a line on the final page, which is why productised pages written after a few real sales tend to convert better than those written in advance.
A one-page template to start with
Fill in these lines for the first service you want to package:
- Offer name (outcome + format):
- Who it is for and who it is not for:
- Outcome the buyer gets, in one sentence:
- Included / not included / needed from the client:
- Timeline and delivery steps:
- Price or price band, and add-ons:
- Proof you can show (examples, results you can verify):
If you can fill all seven lines in under an hour, you have the draft of a page. If you cannot, the gaps tell you exactly which decisions are still open, and that is the real value of the exercise.