← ClaudeAtlas

pricinglisted

Price a client project using value-based pricing — figure out what solving the problem is worth to the client, establish your own cost floor, and land on a defensible number you can explain in one minute. Works for any kind of client work: automations, AI agents, websites, UI/UX design, web apps, API and data integration, knowledge bases, content pipelines, audits, strategy and advisory, and retainers. Use whenever someone describes a client project and wants a price, a quote, an estimate, a proposal, or a sanity check on a number they already have — including phrases like "how much should I charge", "what's this worth", "help me price this", "am I undercharging", "the client says it's too expensive", "should I do hourly", "write me a proposal", "how do I justify this price", or when they paste a client brief and ask what to quote. Also use for pricing structure questions: three-tier options, milestone and payment schedules, change orders, scope creep, maintenance retainers, and who pays for production API/ho
sphinxcode/pricing · ★ 0 · Web & Frontend · score 65
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