agentsclimarketplace

Packaging strategy

Skill Dragoon0x/product-skills/skills/pricing-monetization/packaging-strategy

The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.

Install
npx -y skills add Dragoon0x/product-skills --skill packaging-strategy

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 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

Bundle features into plans that feel natural for each customer segment. Covers feature classification, tier design, upgrade triggers, and avoiding common packaging mistakes. Use when designing tier structure, adding major features, or when upgrade rates are stagnant.

SKILL.md

2.7 KB, 514 tokens by cl100k_base, as published. Nobody here has run it

Packaging Strategy

Bundle features into plans where each tier feels like a natural fit for a specific customer segment.

How to use

  • /packaging-strategy Apply packaging constraints to this conversation.
  • /packaging-strategy <product> Design packaging for the described product and feature set.

Constraints

Feature Classification

Classify every feature before assigning to tiers:

  • Table stakes: what every user needs for basic value. Goes in every plan including free.
  • Differentiating: what makes your product better than alternatives. Mid-tier and above.
  • Power features: what only sophisticated users need. Premium tier.
  • Platform features: admin controls, SSO, audit logs, API access. Enterprise gates.
  • NEVER gate table stakes features. It makes the bottom tier feel broken.

Tier Design

  • Start with who you're selling to, not with tiers. Define segments first.
  • Each segment MUST have a clear answer to: what problem, what features, what budget, who decides
  • MUST limit to 2-3 plans plus enterprise for most products. 5+ tiers is almost always wrong.
  • Each tier MUST be describable in one sentence: "This plan is for [who] who need [what]"
  • NEVER create a middle tier that's a confusing blend nobody picks

Upgrade Triggers

  • Each tier MUST have a natural trigger that makes someone upgrade
  • Good triggers: team size grows, needs a specific feature, usage volume exceeds limit, org requires compliance
  • Bad triggers: arbitrary limits uncorrelated with value, removing previously free functionality, gating quality-of-life features
  • SHOULD design triggers around genuine moments where the next tier becomes the obvious choice

Packaging Principles

  • Each tier MUST have one hero feature — one clear reason to upgrade
  • Feature comparison MUST be scannable in 10 seconds. Limit to 5-7 differentiating features.
  • NEVER punish growth. Cost should scale proportionally, not exponentially.
  • Add-ons are for genuinely optional capabilities, not for nickel-and-diming core value
  • Upgrade and downgrade paths MUST be clean. No data loss on downgrade.

Anti-Patterns

  • The Feature Hostage: one essential feature in premium to force upgrades. Users see through this.
  • The Bloated Enterprise: 5x the price but only adds SSO and "dedicated support"
  • The Add-On Maze: base price looks reasonable, then every useful feature is extra
  • Over-Segmentation: more tiers than the product complexity justifies

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.