From cklph-architect
Price by value to the client, not cost-plus or hourly. Use when pricing a proposal, when mid-engagement scope creep justifies repricing, or when a client has pushed back on price and you need to hold or move with intention.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cklph-architect:priceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Your internal cost is the floor — below it, you lose money. Value to the client is the ceiling — above it, the math stops working for them. The right price sits closer to the ceiling than the floor. Most undercharging happens because people anchor on cost-plus and forget the ceiling exists.
Your internal cost is the floor — below it, you lose money. Value to the client is the ceiling — above it, the math stops working for them. The right price sits closer to the ceiling than the floor. Most undercharging happens because people anchor on cost-plus and forget the ceiling exists.
Ask, in this order:
When you can quantify, quantify. When you can't, bracket — low / likely / high. A bracketed estimate is honest and still useful as an anchor. "If this saves your ops team even 5 hours a week, that's [low] $50k / [likely] $120k / [high] $200k a year" beats refusing to estimate because it isn't precise.
The right price has the right kind of discomfort.
position).If a client asks "what's your hourly rate?", the answer is that you don't bill that way for this kind of work — and a short reason why. Hourly billing is the wrong unit for value work: it caps your upside, rewards inefficiency, and turns the relationship into time-watching. Even internally, only use hourly math to check your floor, not to set your price.
When a client pushes back on price, the first move is to stay quiet and listen. Most pushback is exploratory, not a rejection. The wrong move is to instantly drop the number — that signals you didn't believe it.
If they have a real ceiling, move on scope, not on price. "I hear you on the budget — at that number, here's the smaller shape we can do" preserves your rate, gives them agency, and protects the relationship.
Decide, before the conversation, the lowest price you'd accept and still feel right about the work. If "good outcome at fair price" can't be reached, decline. Under-pricing trains the relationship — and the market segment — to undervalue you. The lost revenue from declining one bad-fit deal is recovered on the next good-fit one; the lost credibility from a year of resentful, under-priced work isn't.
Pair with propose (each tier needs a price), scope (price moves on scope, not on number), position (the spine to hold the number), and engagement-shape (different shapes price differently).
npx claudepluginhub chykalophia/cklph-marketplace --plugin cklph-architectProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.