Tjänster skalas inte; produkter personaliseras inte. Produkt-tjänstesystem gör båda. Så här paketerar du expertis till något repeterbart utan att förlora expertisen.
Pure services don't scale because they're bottlenecked by your time. Pure products don't personalise because they have to fit everyone. Most successful small businesses end up somewhere in between — a *product-service system*, in the language of the PSS literature.
A barber sells hours, but with a recognisable haircut you can ask for. A bakery sells loaves, but the artisan version is a known recipe with a name. A consultancy sells thinking, but with a defined deliverable.
The Long Way is itself a PSS. Read on.
The two failure modes
**Pure services.** A freelance developer billing hourly is selling pure service. Revenue is capped at hours-in-the-week × rate. Days off are days unpaid. Expertise grows but the business doesn't.
**Pure products.** A SaaS template generator selling templates is selling a pure product. It scales but it doesn't differentiate, and it leaves the customer to figure out the hard problem (what do I want the template to *say*?) on their own.
The PSS sweet spot: a productised service. Defined scope, defined price, repeatable delivery, *but* with a human in the loop where it matters.
How to productise without losing the soul
The trick is figuring out which parts of the work genuinely require expert judgement and which parts only feel that way because nobody's bothered to write down the procedure.
Three steps:
1. **Inventory the work.** Pick three projects you've delivered in the last year. List every step. Be ruthless about granularity — "kickoff call", "competitor research", "wireframes", "build the contact form".
2. **Tag each step.** Either *recipe* (the same every time) or *judgement* (genuinely depends on the project).
3. **Productise the recipe steps; keep the judgement steps human.** The recipe parts can become a checklist, a template, a tier with a fixed price. The judgement parts are why anyone should hire you over a $5 template.
After that exercise we found that 60 % of a typical "Standard" website project is recipe — semantic HTML scaffolding, GDPR compliance, accessibility checks, sitemap generation. That's the part that lets us quote a fixed price. The other 40 % — what the homepage actually says, how the product photography is lit, which case studies make the cut — is where our judgement earns its fee.
The Long Way as a PSS
Our own tier structure is exactly this:
- **Starter / Standard / Premium** — productised. Fixed scope, fixed timeline, fixed price. The recipe parts.
- **Strategy & Brand workshops** — pure service. Variable scope, hourly logic, the judgement parts.
- **Maintenance subscriptions** — productised again. Predictable monthly value, predictable monthly fee.
That's not an accident. The services we offer follow the productisation logic above, which is why we can quote a Starter site in five minutes from the /get-started questionnaire.
Where to read more
- Servitization of Manufacturing — Baines et al., the canonical review of services-as-products in industry.
- The Mom Test (already mentioned in our customer-discovery post) — useful for figuring out which parts of your service customers will actually pay a fixed price for.
- Productizing Your Service — practical playbook from Eisaiah Engel that covers tier design and packaging.
This is also exactly how we'd frame an engagement together: figure out which parts of your business can become tiers, which need to stay bespoke, and how the website should reflect both.