agentsclimarketplace

Saas subscription pricing

Skill SylphxAI/skills/skills/saas-subscription-pricing

Public agent skills from SylphxAI — standards, product procedures, and one-command sync for Codex, Claude Code, and Grok Build

Install
npx -y skills add SylphxAI/skills --skill saas-subscription-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

  • 18 days oldThe repository was created 18 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.
  • 1 stars1 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

Design SaaS subscription pricing and packaging—plans, value metrics, trials, upgrades/downgrades, and packaging evidence. Use for pricing architecture. Not checkout implementation and not operating one price-increase rollout.

SKILL.md

3.9 KB, as published. Nobody here has run it

SaaS Subscription Pricing

Produce a Pricing and Packaging Decision that matches customer value, expansion, cost, and trust constraints.

Workflow

  1. Identify the decision, buyer, user, purchasing motion, value metric, cost driver, expansion path, constraints, and assumptions.
  2. Read references/pricing-packaging-patterns.md.
  3. Decide the packaging model: free trial, freemium, usage-based, seat-based, tiered, hybrid, or enterprise.
  4. Design plan boundaries, exact limits, upgrade moments, downgrade/cancel promises, and enterprise/procurement path.
  5. Run a pricing arithmetic pass before publishing: seat minimums vs included seats, included usage vs overage rates, gross margin, annual discount, and procurement terms must be internally consistent.
  6. Define exact usage rates, unit economics, margin guardrails, a bounded validation or rollout, sales enablement, objection handling, and kill criteria before proposing discounts.

Handoffs

  • Market Research Synthesis supplies current competitor, substitute, buyer, and demand evidence; this skill owns the resulting price/package decision.
  • Payment Platform Readiness owns billing, ledger, entitlement, invoice, collection, tax, reconciliation, and finance-close execution.
  • Store Listing Optimization and Interface Craft own channel copy, creative, and UI implementation after the commercial decision is stable.
  • An already-approved price increase needs a separate migration artifact for cohorts, notice, consent where required, grandfathering, retention, and rollback.

When not to use

  • Do not use when the primary artifact is billing, ledger, invoice, or access/entitlement state after provider events.
  • Do not use for an already-decided price increase whose main job is cohort migration, consent, grandfathering, and retention response.
  • Do not use for broad competitor/demand research whose output is not yet a price/package decision.
  • Do not use as accounting, tax, competition-law, or jurisdiction-specific pricing advice.

Source verification

  • Consume or research current competitor pricing, package boundaries, currencies, contract terms, and customer evidence at use; record source URL, access date, geography, and plan.
  • Obtain current internal cost, margin, usage, conversion, churn, and support data from the owning systems. Mark missing values as assumptions and make the recommendation a bounded experiment.

Guardrails

  • Do not mix "per seat" pricing with ambiguous "included base seats"; state either a minimum seat commitment or a bundled-seat package.
  • Do not set overage prices below marginal cost plus target gross margin.
  • Do not hide annual terms, usage caps, downgrade consequences, or procurement friction behind sales-only language.
  • Do not propose discounts without approval rules, CRM logging, renewal impact, and rollback criteria.
  • Do not let pricing copy or billing implementation silently change the approved value metric, limits, price, renewal, cancellation, or downgrade semantics.

Output format

Recommended model:
Value metric:
Plan architecture:
- Free/trial:
- Core paid:
- Team/business:
- Enterprise:
- Usage and overages:
- Procurement:
- Support and sales enablement:

Upgrade moments:
Cancellation/downgrade:
Metrics:
Unit economics:
- Gross margin target:
- CAC payback / NRR target:
- Cost and abuse controls:
Pricing arithmetic:
- Seat minimums / included seats:
- Included usage and overage rate:
- Annual discount and contract term:
- Margin sanity check:
Experiment/rollout plan:
- Test design:
- Handoff for any approved migration:
- Customer communications:
- Guardrails:
Risks:

Gives 0 of the 12 instructions most pricing monetisation skills give

Counted across 366 of the 366 authors here whose files we hold, read 2026-08-06

  • verify webhook signaturesin 23 of 366, across 19 files
  • differentiate tiers using features, limits, or supportin 15 of 366, across 4 files
  • read product marketing context before asking questionsin 14 of 366, across 6 files
  • base price on perceived value, not costin 14 of 366, across 3 files
  • use Van Westendorp to find acceptable price rangein 14 of 366, across 3 files
  • use MaxDiff to identify highly valued featuresin 14 of 366, across 3 files
  • choose a value metric that scales with customer valuein 14 of 366, across 9 files
  • handle webhook events idempotentlyin 12 of 366, across 6 files
  • understand the upgrade context before recommendingin 11 of 366, across 4 files
  • align the pricing metric with delivered valuein 10 of 366, across 4 files
  • install stripe packagein 10 of 366, across 5 files
  • calculate unit economics metricsin 10 of 366, across 5 files

Said here and by no other author read

  • Identify decision buyer user metric cost driver and constraints
  • Read pricing packaging patterns reference
  • Decide packaging model
  • Design plan boundaries limits upgrade and downgrade paths
  • Run pricing arithmetic pass before publishing
  • Define usage rates unit economics margin and kill criteria

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.