# Start Productized Offer

> Packages your expertise into one Productized Service Offer with the outcome in one sentence, a fixed scope and timeline, what the client provides, exclusions, a price worked from your own numbers and checked against your floor, and a small paid first step. Use for "run start-productized-offer", "productize my service", "what exactly do I sell", "package my consulting", "fixed price offer", "they said send me something", "define my first offer", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-productized-offer` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-productized-offer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-productized-offer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-productized-offer

---


# Productized Service Offer

## When To Use
Every conversation ends with "send me something", and you have nothing with a scope and a price. In a job, the work arrived already shaped. Now someone has to say where it starts, where it stops and what it costs, and that someone is you. This answers: what is the one piece of work you can name, scope and price once?

## When Not To Use
When a real client has a problem that does not fit, do not bend the offer; write a First Client Proposal for them. For the page a contact can forward, define the offer here and then run One-Page Offer.

## Inputs
- 2 or 3 pieces of past work that looked alike, from your Career Proof Inventory: what was delivered, how long it took, what the other side had to do
- Your floor per day from the Floor Rate Calculator, and your estimate of delivery days
- Your Ideal Client Profile or Positioning Statement, if you have them
If you have none of this, I start from one piece of work you have done more than once and mark the output as a first draft.

## Approach
A productised service is a practitioner convention: one repeatable piece of work with a named outcome, a fixed scope, a fixed timeline and a fixed price, so the client buys a result and the conversation leaves hours behind. The judgement is in what to leave out. Most first offers fail on exclusions nobody wrote down, and a new founder who is glad to have any client says yes to each small extra until the fixed price covers twice the work. The working draft can live in Claude Docs so you edit it in place.

## Workflow
1. Ask at most three questions: which piece of work you have done most often with the least surprise, what the other side holds in their hands at the end, and what usually creeps in.
2. Lay the past pieces side by side and find the common core: the steps every one had. Extras only some had become exclusions or a later phase. Note what your employer supplied then that you must now supply or exclude: a team, data, tools, a brand.
3. Write the outcome first, in the client's terms: what they can do or decide when you finish. If it takes more than one sentence, the offer is not ready.
4. Fix the scope as deliverables, the timeline in weeks, and what the client provides and does (access, people, decisions, turnaround). Then write the exclusions, each with where it goes: a second phase, a separate quote, not offered.
5. Work the price from your numbers, arithmetic shown: delivery days x the day price you choose, plus costs, plus a margin for risk you set. Beside it, the floor check: delivery days x floor per day = the minimum. If your price sits under it, I say so and show what scope would have to come out. I never propose the price.
6. Define a small paid first step the same way: a diagnostic or a short first phase, with its own outcome, scope, time and price.
7. List where the offer is the wrong answer, so you can say so on a first call.

## Output Format
```markdown
# Productized Service Offer
Name: [plain name that says what it does] | For: [role in a situation]
## Outcome
[What the client can do or decide at the end, one sentence]
## Scope and timeline
| Deliverable | Week | What the client provides or does |
|---|---|---|
| [deliverable] | [week] | [access, people, decisions] |
## Exclusions
- [excluded item]: [second phase / separate quote / not offered]
## Price (internal working, never on a client copy)
- [delivery days] x [my day price] + [costs] + [risk margin I chose] = [price]
- Floor check: [delivery days] x [floor per day] = [minimum] | Gap: [price minus minimum]
## Paid first step
[Name], [outcome], [scope], [weeks], [price]
## When this offer is wrong
- [situation]: [what I would say instead]
## Decision
[Your name] sets the price and the exclusions by [date], has the terms checked with a qualified adviser, and names the first [number] people to show it to.
```

## Done When
- The outcome is one sentence in the client's terms.
- Every price line traces to a number you gave, and the floor check is shown.
- Exclusions and client tasks are written out.
- At least one situation where the offer is wrong is named.

## Quality Bar
- Outcome before deliverables, deliverables before price.
- Scope that fits your worst week of delivery, not your best.
- Nothing assumes a former employer's team, data or templates.
- Payment and contract wording: check with a qualified adviser.
- The price comes from your own numbers and your floor, never a market rate; you set it.

## Next
Run start-voice-guide (Writing Voice Guide) so everything you write about this offer sounds like you.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

