plugins/pm-consulting/skills/rate-card/SKILL.md
Build a consulting/freelance rate card and pricing structure — and the floor rate to not go broke. Use when asked to set freelance/consulting rates, build a rate card, decide what to charge, package services, or move off hourly billing. Produces a rate card — your minimum viable rate (from real targets), tiered packages, pricing models (hourly/day/project/retainer/value), and how to present and defend it.
npx skillsauth add mohitagw15856/pm-claude-skills rate-cardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Most freelancers and consultants underprice because they pick a number that "sounds okay" instead of one the math supports — and they bill hourly, which caps income and punishes efficiency. This skill builds a rate card grounded in your real targets (income, billable capacity, costs), then packages it into tiers/models that move you toward value-based pricing — with the language to present and hold it.
Ask for these only if they aren't already provided:
1. Your floor rate (the math) — derive the minimum viable rate: target income + costs + tax, divided by realistic billable days/hours. This is the number below which you lose money — most people's "gut" rate is under it. Show the calc.
e.g. (£90k target + £20k costs + 30% tax buffer) ÷ 130 billable days ≈ £1,200/day floor.
2. Rate models — present the options and when each fits:
3. Packaged tiers — 3 productised offers (e.g. Audit / Sprint / Partner) with what's included and a price each — so clients choose "which," and you sell outcomes not hours.
4. Presenting & defending it — how to state the rate without flinching, anchor on value, handle "that's expensive" (it's about ROI, not cost), and when to hold vs. walk. Raise rates on new clients first.
Freelance/consulting pricing practice — minimum-viable-rate math, value-based & productised pricing, rate-anchoring.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.