pricinglisted
Install: claude install-skill sphinxcode/pricing
# Pricing Client Work
Price the **result**, not the build. The build is only how the result gets delivered.
The whole method rests on one move: get the client's own numbers on the table before you say yours. A fee that is a fraction of a number the client stated is very hard to argue with. A fee derived from your costs is an invitation to negotiate your costs down.
**Three numbers, kept separate at all times:**
- **Cost floor** — the lowest price at which this job is responsible for you to take. Yours.
- **Value ceiling** — the most the solved problem could credibly be worth to this client. Theirs.
- **Price** — any number in the corridor between them.
Cost does not justify price. A landscaper who buys a nicer truck cannot charge more for the same lawn. Your cost sets the floor and nothing else.
---
## The run loop
Work these in order. Do not skip to a number.
### 1. Classify the archetype
Read `references/archetypes.md` and decide what kind of work this is. This is the first move because **it determines which value lens is even valid.** Pricing a landing page off "hours saved" produces nonsense; so does pricing an internal automation off "brand lift."
If the request spans several archetypes (a website *and* a booking automation *and* a knowledge base), say so and price them as separate lines. Bundling different value logics into one number is how proposals become unexplainable.
### 2. Select the value lens
Each archetype in the reference names its primary lens a