# Firm Good Better Best Options

> Builds three ways to buy one engagement that differ in outcome and scope, each priced from your own price list, with what each leaves out, the client effort, the assumptions each rests on, the decoy test on every pair and your recommended one with the reason. Use for "run firm-good-better-best-options", "give the client three options", "good better best pricing", "stop quoting a single price", "what would a smaller first phase look like", "build tiers from my rates", "they said no to one number", part of the Claude for Consultants · Team in Claude Pack by 90n.

- Skill: `polar-bear-org/firm-good-better-best-options` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/firm-good-better-best-options`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/firm-good-better-best-options/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/firm-good-better-best-options

---


# Good-Better-Best Options

## When To Use
You send one number and the client's only possible answers are yes and no. With three versions of the engagement the conversation becomes "which one", and you learn what they value from the one they point at. Run this once you know the route you would advise, to shape three versions you would each be glad to deliver at their price.

## When Not To Use
This lists ways to buy your work. For ways the client could solve the problem (including without you), use Strategic Options. To choose how you charge, use Fee Structure Choice; to cut a single oversized scope, use MoSCoW Scope.

## Inputs
- Your recommendation or problem statement, and the outcome the client named
- Your price list, day rate or past fees for similar work (I never set a price)
- What you will and will not take on, and whether you offer a route where they do part with their own AI
If you have none of this, I start from your own description of the problem, write [your price] in every price cell and mark the table as a first draft.

## Approach
Three-tier offers are a common practitioner convention. The trap in them is the decoy effect described by Huber, Payne and Puto (Journal of Consumer Research, 1982): an option worse than its neighbour on every count, added only to make the neighbour look good. Clients sense a rigged menu, and it costs trust at the worst moment. So every option here must pass one test: you would be content if the client chose it. The failure it prevents is "bronze, silver, gold" where bronze exists to be refused.

## Workflow
1. Ask, in one go: which outcome does the client care about most, in their words? What is the smallest piece of work that would still move it? Do you offer a version where they do part of it themselves with their own AI?
2. Name the axis the three climb along: outcome reached (a diagnosis, a decision, a change in place), depth (review, plan, plan with delivery) or who does the work (you, shared, mostly them with your review). More hours of the same thing is not a new option.
3. Draft them. Good: the smallest version that still settles something real. Better: the one you would advise. Best: a different outcome, such as staying until the change holds. Say in one sentence what each adds over the one below; if you cannot, merge them.
4. Price each from your list only, by phase or deliverable where you have the figures, and [your price] where you do not. Asked what the market pays, I answer that I do not know and ask what price you would stand behind in the room.
5. Write what each leaves out, what it asks of the client (time, people, data) and the assumptions under it: number of reviewers, rounds of revision, start date. These lines protect you in month three.
6. Run the decoy test on every pair across outcome, scope, client effort and price. If one loses to another on all four, remove it or redesign it. Then mark your recommended option and the reason, tied to the client's stated priority.

## Output Format
```markdown
# Three Ways to Buy the Work
Client's problem, in their words: [from your notes] · Prepared: [date]
| | Good | Better | Best |
|---|---|---|---|
| Outcome the client gets | [outcome] | [outcome] | [outcome] |
| Scope | [what is done] | [what is done] | [what is done] |
| Leaves out | [left out] | [left out] | [left out] |
| Client effort | [time, people, data] | [time, people, data] | [time, people, data] |
| Rests on | [assumptions] | [assumptions] | [assumptions] |
| Adds over the one below | n/a | [one sentence] | [one sentence] |
| Price | [your price] | [your price] | [your price] |
## Decoy test
| Pair | Does one lose on all four counts? | Change made |
|---|---|---|
| [Good against Better] | [yes / no] | [none, or what changed] |
## Recommended
[Option, and the reason tied to what the client said matters most]
## Decision
[Your name] approves the three options and every price by [date], before they enter the proposal; [client decider role] chooses among them.
```

## Done When
- Each option differs in outcome or scope, in one sentence
- Every price is from your list or reads [your price]
- Every pair has passed the decoy test
- You would deliver any of the three without resentment

## Quality Bar
- Options climb by what the client gets, never by padding the same work
- The smallest option still settles something real; it is not a penalty for a small budget
- A "do part with your own AI" version is priced to be chosen, not to fail
- Assumptions are specific enough for a finance lead to check
- Every price is yours and no option is a decoy; I invent no rate and no benchmark, and you decide what goes in front of the client.

## Next
Run firm-fee-structure (Fee Structure Choice) to choose how the chosen options are charged.

## 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).

