pricing-strategy-5ae455 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pricing-strategy-5ae455 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Build pricing that reflects value delivered — not cost to build. Structure every pricing decision with customer segmentation, value metric identification, competitive context, and a packaging recommendation.
Three questions to answer before any pricing decision:
| Model | Best For | Risk |
|---|---|---|
| Per Seat | Collaboration tools, team software | Disincentivises adoption as team grows |
| Usage-Based | APIs, infrastructure, consumption tools | Revenue unpredictability for both sides |
| Flat Rate | Simple tools, early-stage | Leaves money on table from power users |
| Tiered | Products with clear user segments | Feature gatekeeping frustrates users |
| Freemium | Viral/PLG products with low marginal cost | Conversion to paid is hard to engineer |
| Value-Based | Enterprise, outcomes-driven products | Requires strong ROI story |
Use freemium when:
Avoid freemium when:
Recommended 3-tier structure for SaaS:
| Tier | Target | Price Signal | Key Features | Lock-in Mechanism |
|---|---|---|---|---|
| Free / Starter | Individual, early discovery | $0 | Core value, usage-limited | Invite colleagues, export limit |
| Pro / Growth | SMB, growing teams | $[X]/seat/mo | Full features, higher limits | Team collaboration, integrations |
| Business / Enterprise | Mid-market, enterprise | $[X]/seat/mo or custom | Admin, SSO, SLAs, dedicated support | Security, compliance, volume |
Tier design rules:
| Competitor | Model | Price | Key Differentiator |
|---|---|---|---|
| [Name] | [Model] | [Price] | [What they lead with] |
Positioning options:
Current State: [What pricing exists today, if any] Problem to Solve: [Why pricing is being reviewed]
Recommended Pricing Model: [Model name + rationale]
Value Metric: [The single unit that scales with customer value — e.g., "active users", "API calls", "documents processed"]
Proposed Tiers:
[Table using 3-tier structure above]
Free-to-Paid Upgrade Trigger: [Specific moment or threshold that creates natural upgrade pressure]
Competitive Position: [Premium / Parity / Value + reasoning]
Pricing Change Rollout (if applicable):
Risks:
Metrics to Monitor Post-Change:
Ask the user for these if not provided:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.