agentsclimarketplace

Saas pricing

Skill Amey-Thakur/AI-SKILLS/skills/business-growth/saas-pricing

Plug-and-play skills and prompts for every AI coding agent

Install
npx -y skills add Amey-Thakur/AI-SKILLS --skill saas-pricing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Price SaaS around a value metric with tier design, seat-vs-usage decisions, and low-risk price testing. Use when setting or revisiting software pricing and packaging.

SKILL.md

3.7 KB, as published. Nobody here has run it

SaaS pricing

Pricing is the exchange rate between the value you create and the revenue you keep, and it is the highest-leverage number in the business: a 10% pricing improvement beats a 10% cost cut in nearly every model. Treat it as a designed product surface, revisited on a schedule.

Method

  1. Anchor on a value metric. The unit price scales with: seats, usage (requests, GB, messages), or outcomes (bookings, orders). Test: does the customer's cost grow roughly with the value they receive, is it predictable enough to budget, and simple enough to explain in a sentence? A wrong value metric (per-seat for a product where one seat automates a team) caps revenue exactly where value explodes (see product-metrics' north-star logic: the value metric is its commercial twin).
  2. Design three tiers around customer segments, not feature piles. Entry (self-serve, one clear job), growth (the default: price-anchored where most should land), enterprise (SSO, audit, SLAs, contracts: sold, not clicked: see multi-tenancy's isolation tiers for what enterprise actually buys). Gate by who the customer is becoming (limits, collaboration, controls), not by crippling the core job at entry: a free/entry tier that cannot demonstrate the product's value recruits nobody (see user-activation).
  3. Blend seats and usage deliberately. Seats are predictable and understood; usage tracks value and monetizes automation; hybrids (seats + usage allowance + overage) are the modern default. Whatever the mix: customers need a dashboard of where they stand and alerts before overage (bill shock is churn with an invoice attached: see churn-analysis).
  4. Research willingness-to-pay before printing prices. Segment interviews with price-laddering questions, Van Westendorp surveys for range-finding, win/loss data on price objections (see customer-interviews' honesty rules: stated willingness inflates), competitor anchor-mapping (what does the buyer compare you to?). Cost-plus is a floor check only; value-based is the method.
  5. Test with grandfathering, measure whole-funnel. New prices apply to new customers first (existing customers grandfathered or migrated with generous notice: see feature-sunsetting's trust mechanics); measure conversion x ARPU x retention together, not conversion alone (a price cut that lifts signups of never-activating users lost money: see ab-test-design's guardrails; pricing tests are often cohort-based rather than strict A/B for fairness and legal reasons).
  6. Raise prices on a cadence, with value framing. Annual review; increases land with the value shipped since ("here is what was added"), notice, and an option path (see roadmap-communication's change-loudly rule). Underpricing compounds silently: the earliest-stage companies' most common pricing error is an order of magnitude of timidity.

Boundaries

  • Pricing is constrained by strategy (land-and-expand vs premium positioning), not just optimization; a price war you can win may still be a war you should not enter (see technical-seo's content-vs-tricks ethic: durable beats clever).
  • Discounting policy is pricing's shadow system: unmanaged sales discounts rebuild your real price list in salesforce; cap and instrument them (see saas-metrics' ARPU honesty).
  • Regulated, marketplace, and open-source-adjacent models carry their own pricing physics; transplant this method's questions, not its defaults.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.