stg-designing-pricing

Identify pricing constraints and build a value-based pricing hypothesis for SaaS products.

37|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/BellaBe/leanos --skill stg-designing-pricing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stg-designing-pricing
Source: https://github.com/BellaBe/leanos/tree/main/.claude/skills/stg-designing-pricing
Command: npx skills add https://github.com/BellaBe/leanos --skill stg-designing-pricing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pricing strategy teams struggle to translate market data into a coherent, defensible unit-economics plan that aligns with growth architecture and channel constraints.

Core Features & Use Cases

  • Value anchor calculation and problem-cost grounding to set price ceilings with explicit T3 labeling.
  • Competitive pricing mapping and gap analysis across tiers with source citations.
  • Grounded Good-Better-Best tier architecture and channel viability checks to guide revenue model decisions.
  • Upgrade triggers and coherence validation to maintain LTV:CAC alignment under different growth modes.

Quick Start

Create a first-pass pricing design using value anchors, competitive benchmarks, and a Good-Better-Best tier plan.

Frequently Asked Questions about stg-designing-pricing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a value-based pricing model for a SaaS product?

To build a value-based pricing model, calculate value anchors from problem-cost grounding, map competitive benchmarks, and design a Good-Better-Best tier architecture. This approach enforces customer validation for willingness-to-pay estimates and uses price ranges instead of point estimates.

What is the best way to structure Good-Better-Best tier architecture for unit economics?

The best way to structure tier architecture is by grounding Good-Better-Best tiers in competitive gap analysis and value anchors. You then validate channel viability and configure upgrade triggers to maintain LTV:CAC alignment across different growth modes.

How do I set price ceilings for SaaS pricing using problem-cost grounding?

Set price ceilings by calculating value anchors based on the specific problem costs your product solves. All willingness-to-pay estimates used for these ceilings must be labeled as T3 assumptions requiring direct customer validation before finalizing.

Can I use competitive pricing mapping for both PLG and sales-assisted channels?

Yes, competitive pricing mapping applies to both PLG and sales-assisted channels. After mapping competitive gaps and designing tiers, you perform channel viability and coherence checks to ensure the revenue model aligns with your specific growth architecture.

Why do willingness-to-pay estimates need T3 labeling in a pricing hypothesis?

Willingness-to-pay estimates need T3 labeling because they are unvalidated assumptions. This constraint enforces that price ranges replace point estimates and ensures customer validation is completed before finalizing the unit-economics plan and upgrade triggers.

When do I need to perform channel viability checks during pricing design?

Perform channel viability checks after designing your Good-Better-Best tier architecture and upgrade triggers. This validation ensures your pricing hypothesis maintains LTV:CAC coherence and aligns with your chosen PLG or sales-assisted growth mode.