Price Productized Service

---
name: price-productized-service
description: Turns the service you deliver most often into one fixed offer, producing a Productized Service Sheet with the name, who it is for, the outcome, scope in and out, timeline, a fixed price checked against your own floor, and what triggers a change. Use for "run price-productized-service", "productise my service", "turn my project into a fixed offer", "stop custom quoting every job", "fixed price package", "make a standard offer", "price stops following the hours", part of the Pricing Under AI Pressure Pack by Polar Bear.
---

# Productized Service Sheet

## When To Use
Every project is custom-quoted and the price follows the hours, so every time AI makes you faster, you earn less for the same result. Use this when you deliver one kind of work often enough in a similar shape that it could be sold as one fixed offer. It answers: what exactly do I sell, for what fixed price, and where does it stop?

## When Not To Use
If the work changes shape with every client, a fixed offer will be broken by the second sale; shape options for that one client with the Three-Option Proposal instead. If you already have the offer and want to know whether it pays, go to Offer Unit Economics.

## Inputs
- Three to five recent jobs of the same kind: what was delivered, what was asked for on top, what it took
- Your floor per day from the Floor Rate Calculator and delivery days per job from the AI Activity Map
- How you use AI in this work today, in your own words
If you have none of this, I start from one recent job and your description of it, and mark the sheet as a first draft.

## Approach
A productised service is a practitioner convention: one named offer, a fixed scope, a fixed timeline and a fixed price, sold the same way each time. The judgment is in the edges. Most productised offers fail because "scope out" was left blank, and the third client treats the fixed price as the price of unlimited rounds. This sheet makes the edges explicit and checks the owner's price against the floor; Claude never suggests the price.

## Workflow
1. Ask at most three questions: which service do you deliver most often, what do clients most often add on top, and what price are you considering, if any?
2. Lay the recent jobs side by side and find the common core: the steps every job had, the extras only some had. The core is the offer; the extras become add-ons or scope out. If fewer than three jobs share a core, say so and stop.
3. Write the name (plain, says what it does), who it is for (a role, never a company type) and the outcome in one sentence the client would recognise as their own goal.
4. Write scope in and scope out as two lists, then a fixed timeline in steps with the client's inputs and their due dates. Every item a past client argued about goes on one of the two lists.
5. Run the floor check: measured delivery days per job x floor per day = the minimum. Show the owner's price beside it and the gap. Unmeasured days are marked "estimate". If the price sits under the floor, say so plainly and show what scope would have to come out.
6. Write what triggers a change request (an item from scope out, a missed client input, an extra round) and one plain line on how AI is used in the offer, matching how the person works.
7. Hand the sheet to the owner to set the price and decide when to offer it first. The client copy, without the price check, can be written up in Claude Docs (beta) or any document.

## Output Format
```markdown
# Productized Service Sheet
**Offer name:** [name] | **For:** [role] | **Outcome:** [one sentence]
## Scope
| In scope | Out of scope |
|---|---|
| [item] | [item] |
## Timeline
| Step | What happens | Client provides | By when |
|---|---|---|---|
| [1] | [step] | [input] | [day or week] |
## Price check (internal, never on the client copy)
| Delivery days per job | Floor per day | Minimum | Owner's price | Gap |
|---|---|---|---|---|
| [days, measured or estimate] | [floor] | [days x floor] | [price] | [price minus minimum] |
## Change triggers
- [trigger] -> change request
## How AI is used in this offer
[One plain line, consistent with your practice]
## Decision
[Owner] sets the fixed price and the first client to offer it to by [date].
```

## Done When
- Scope out has at least as much thought in it as scope in
- The floor check uses measured days or marks every estimate
- The price on the sheet is the owner's, with the gap to the floor shown
- The AI line matches how the person actually works

## Quality Bar
- Built from real recent jobs, never from an imagined ideal client
- No example prices, market rates or "typical" fees anywhere on the sheet
- The floor and the price check stay off anything a client sees
- The offer is named for what it does, with no false scarcity or launch deadline
- The price is the owner's, checked against your own floor; the offer never hides that AI is used.

## Next
Run price-service-blueprint (Service Blueprint) to show how the offer is delivered and where AI works.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).