Why services get packaged
The product marketing hub notes that while a software company's product marketing leans towards enablement, a services firm's leans towards packaging what it does into something that can be described and priced. The reasons are practical. A buyer who cannot see a price has to ask for one, and many small business buyers would rather compare firms whose offers they can read than book a call with each. A firm that quotes every job spends time on proposals that do not convert, and prices the same work differently for different clients. And a service described only as expertise is hard to market: there is nothing to put on a landing pageThe page a visitor arrives on from a campaign, built to turn that visit into one action. except the firm's credentials.
The professional services industry guide describes the core difficulty: a professional firm has nothing to show before the engagement starts, and the client often cannot judge the quality of the work even after delivery. A package does not remove that difficulty, but it gives the buyer something concrete to evaluate before committing: what will be done, what will not, by when and for how much.
Packaging also changes the firm. Work sold as a package has to be delivered as a package, which means a defined recipe, predictable effort and a known cost. The marketing mix framework extends the original four levers with people, process and physical evidence for offers where the customer experiences the service as part of what they buy. A package is a decision about all three: who delivers it, the process they follow and what the client sees that signals quality, from the scope document to the handover.
Choosing the outcome to package
Start from what clients are trying to get done, not from the firm's list of services. The value proposition canvas, as its framework page sets out from Strategyzer's description, maps a segment's jobs, pains and gains against what an offer provides, and fit exists on paper when the offer addresses the most severe pains and most essential gains. For a service, the job is often a moment in the client's business: opening an office, filing a return, launching a website, passing an audit. The package is built around reaching that outcome.
Good candidates for packaging share a few traits:
- The outcome is easy to describe before the work starts. A buyer can tell whether they need it.
- The work recurs. The firm does it often enough to have learned what it usually involves.
- Variation between clients is small, or falls into a few groups. Most jobs look alike, or fall into a handful of recognisable sizes.
- The buyer is a recognisable segment. The buyer persona who needs it can be described, which is what lets the package be marketed to them.
Look at the firm's records for past jobs of this kind. The quotes, the time actually spent and the questions clients asked show what the work involves, where it varies and which extras keep coming up. A package built from memory usually underestimates the effort, because the memorable jobs are the smooth ones.
Where clients fall into genuinely different groups, such as small, medium and complex versions of the same job, the good-better-best framework offers three versions at rising prices, each for a different kind of buyer, with fences that follow what each buyer values. Where they do not differ, one package is better than three that split the same buyers arbitrarily.
Scope, exclusions and the delivery recipe
The scope is what the client gets; the exclusions are what they do not; the recipe is how the firm delivers it. All three are written down before the package is sold.
| Part | What it states | Why it matters |
|---|---|---|
| Outcome | What the client will have at the end, in their words | Lets the buyer decide whether this is what they need |
| Included | Each deliverable, the number of revisions or visits, and what the client receives | Sets expectations and makes the price comparable |
| Excluded | The work that is not included, and what happens if it is needed | Prevents disputes and protects the margin |
| Client inputs | What the client must provide, and by when | Stops delays the firm cannot control from eating the effort |
| Timing | How long delivery takes once inputs are in, as the firm can actually deliver it | A stated time has to be one the firm meets |
| Extras | The common additions, each with its own price or a clear quoting route | Gives larger jobs a path that does not break the package |
| Delivery recipe (internal) | The steps, checklists, templates and roles used to deliver it | Makes the effort predictable and the quality consistent |
The exclusions deserve as much care as the inclusions. A short, plain list of what is not included, written where the buyer will see it before buying, is fairer to the buyer and safer for the firm than an implied scope argued about later. Each exclusion should have an answer: a priced extra, a separate package, or a quote.
The delivery recipe is the internal half of the package and the part buyers never see. It turns the scope into steps someone else in the firm could follow: what happens first, which templates are used, what is checked before handover. Without a recipe, every job is designed afresh and the package's effort, and therefore its margin, varies with whoever happens to deliver it.
Naming and describing the package
The name should say what the package is. The tutorial on naming a product or brand makes a descriptor, the master brand plus a plain description of what the product does, the default, and the same reasoning applies to a service: a descriptive name builds the firm's brand and asks nothing new of the buyer's memory. "Office set-up for small teams" tells a buyer more than an invented package name, and it is what they would search for.
The description follows the same order as the buyer's questions: the outcome, who it is for, what is included, what is not, how long it takes and what it costs. The messaging hierarchy and proof points guide applies here in miniature: the package's main message connects to one of the firm's value pillars, and every claim in the description is one the firm can back up. A statement about how quickly the work is delivered, how many clients the firm has served or what results clients get is an objective claim and needs evidence on file before it is made, as that guide summarises from the Advertising Standards Authority's codes.
Proof matters more for services than for most products, because buyers cannot try the work in advance. Client stories, reviews and examples of finished work all help, used with permission, as the trust and proof guide sets out.
Pricing the package
The pricing guide's concepts carry over to a service with little change. The model is usually a fixed price for the package, sometimes a recurring fee for a service delivered every month. The metric is what the price scales with, if anything: the number of people, sites, documents or visits the package covers. Choose a metric the buyer can predict and the firm can count, and that tracks the effort genuinely involved.
Tiers are built from segments, not from the list of tasks, as the pricing guide says of products. A small, standard and complex version of a package is useful only if those groups of buyers really exist and need different things. Fences between tiers should follow value: the larger tier includes what larger clients need, such as more sites, more people or more complex systems, rather than withholding something every client needs. Add-ons suit the extras a minority of clients need, which the scope table has already listed.
Check the price against the firm's own costs before publishing it. The cost of a package is mostly the time it takes to deliver, at the firm's own cost of that time, plus anything bought in. Compare the package price with that cost from the firm's records to find the package's gross marginShare of revenue left after the direct cost of the goods sold., and look at the spread of past jobs, not only the average, because a fixed price takes on the risk of the slow ones. Once the price and margin are known, the break-even calculator shows the most the firm can spend to win each sale and how many sales a marketing spend needs to pay back. For a package that leads to an ongoing relationship, the LTV and CAC guide covers how lifetime value and acquisition cost fit together, and the unit economicsThe revenue and costs of one unit, an order or a customer, used to test if growth pays. definition sets out why one sale that loses money only grows the loss with volume.
Presenting packages honestly
A published package is a price claim, and the rules on prices apply to it. The pricing guide records that the Competition and Markets Authority enforces UK consumer protection law covering misleading pricing practices, including reference prices that were never genuinely charged, urgency claims that are not true and fees revealed late in the purchase, and that the Advertising Standards Authority's codes cover price statements in advertising. Its practical summary applies directly to a service package:
- Be complete about cost. Show what is included, what is extra and how the bill grows, before the buyer commits. A package whose real price appears only once the extras are added is not the price it advertises.
- State the extras. List the common additions with their prices or how they are quoted, beside the package.
- Keep time limits real. An offer price with a deadline must end when it says it will.
- Make "from" prices honest. A starting price should be one that a real client in the stated segment could pay for the stated scope.
The guide to designing a pricing page covers how packages appear to buyers, with each option led by who it is for and costs shown in full. None of this is legal advice; packages with comparative pricing, reference prices or promotional deadlines should be checked by whoever handles compliance. Firms in professions with their own regulators, such as law, medicine or regulated financial advice, have further rules that this guide, like the professional services guide, does not cover.
What stays bespoke
Not every job fits a package, and forcing one into it damages both the job and the package. Keep work quoted when the scope cannot be known until the problem is understood, when each client's situation differs in ways that change the effort a great deal, or when the work is rare enough that the firm has no recipe for it.
Make the boundary visible. The package description says which situations fall outside it and how those are handled, so that a buyer with a complex need is routed to a conversation rather than sold a package that will fail them. Many firms use a package as the first step: a fixed-price assessment that ends with a quote for the bespoke work, so the buyer gets a defined first purchase and the firm learns enough to price the rest.
Review the boundary as the firm learns. Quoted jobs that keep looking alike are candidates for a new package; package jobs that keep needing extras suggest the scope or the tiers need redrawing.
An IT support firm packages its office set-ups (illustrative)
Brannixa IT Support turns a quoted job into a package
Brannixa IT Support, an invented IT support firm serving small offices, quoted every office set-up separately. Its records for the last 40 set-ups showed most were for offices of 5 to 15 people with a broadband line, a shared printer and cloud email, and took between 9 and 14 hours of engineer time; 6 involved older on-site servers or several floors and took far longer. The firm wrote a package, "Office set-up for small teams", for up to 15 people: laptops and phones configured, cloud email and shared drives set up, one printer, a Wi-Fi network and a handover session, delivered within 10 working days of receiving the client's account details. Exclusions were listed on the page: on-site servers, cabling, networks across more than one floor and data migration from old systems, each with a priced extra or a route to a quote. At an engineer cost of £45 an hour, the 14-hour jobs cost £630 in time, so the package was priced at £1,150 plus £60 per person above 10, giving a gross margin above 40% even on the slowest standard jobs. The break-even calculator showed the most the firm could spend on advertising per package sold. Complex networks stayed as quoted work, reached through a fixed-price network assessment. In the first 2 quarters, the firm sold 22 packages, 9 of them through the page without a call.
Common mistakes
- Packaging the service list, not the outcome. A package is bought for what the client will have at the end, not for the tasks the firm performs.
- Building the scope from memory. The firm's records of past jobs show the real effort; memory shows the smooth ones.
- Implied exclusions. Anything not included is written down where the buyer sees it before buying.
- Pricing from the average job. A fixed price carries the risk of the slow jobs; check the spread, not only the middle.
- Tiers that split the same buyers. Three versions help only where three groups of clients really differ.
- A clever name. A plain descriptor tells buyers what the package is and is what they search for.
- Extras that appear after the sale. The common additions and their prices belong beside the package.
- Forcing complex work into a package. Keep it quoted, and make the route to a quote visible.
