Four MIT collections ported — growthOS, openclaw-marketing-skills, Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45 commands, each naming its origin in its own frontmatter so the tree can be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names appeared in more than one collection and none of the copies were identical; the longest wins, which lands on the more developed text where they genuinely diverge. A fifth collection is deliberately absent. awesome-growth-hacking-skills carries NO licence, which leaves its author every right by default — and it is a list of links rather than a collection of skills, so there is nothing in it to port and no permission to port it with. It is cited as a directory to read. THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing vendor SDKs, running OAuth flows of their own, and ending with long-lived credentials in JSON files under .agents/ and ~/.growthos/ at mode 600. That is a secret on a disk with no rotation path, protected from other users and not from the agent — and one auth implementation per skill. Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect` is the one home for the flow and the platform skills defer to it by provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a tool and a curl cannot disagree. Two had nothing real behind them and now say so. There is no search_console provider, so that skill names what does answer the same questions (google_analytics, google_bigquery) and states that the remedy is a provider in hanzoai/cloud rather than a vendor SDK here. And getxapi-connect was a wrapper around a paid reseller of X's public data with the vendor's key in an env var; it is `listen` now, on our own x connector — a skill named after a vendor makes the vendor the capability and dies with it. The skills referenced paths that only existed inside the source repo, so the shared material they read is ported to reference/ and the paths rewritten. Three skills need the growthOS APPLICATION rather than its data; per the estate's own split an application belongs in hanzoai/ads, social, email or sms as a cloud plugin, so those three say what they need instead of carrying an import that resolves to nothing. Third-party product names are out of our prose and kept in the notices, which is where the licence requires them and the only place they belong. A skill's persona names a role, not somebody else's product. Co-authored-by: Hanzo Dev <[email protected]>
7.1 KiB
name, description, metadata, source
| name | description | metadata | source | ||
|---|---|---|---|---|---|
| pricing | When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers. |
|
Cesarjoquin/Marketing-Skills |
Pricing Strategy
You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Before Starting
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Business Context
- What type of product? (SaaS, marketplace, e-commerce, service)
- What's your current pricing (if any)?
- What's your target market? (SMB, mid-market, enterprise)
- What's your go-to-market motion? (self-serve, sales-led, hybrid)
2. Value & Competition
- What's the primary value you deliver?
- What alternatives do customers consider?
- How do competitors price?
3. Current Performance
- What's your current conversion rate?
- What's your ARPU and churn rate?
- Any feedback on pricing from customers/prospects?
4. Goals
- Optimizing for growth, revenue, or profitability?
- Moving upmarket or expanding downmarket?
Pricing Fundamentals
The Three Pricing Axes
1. Packaging — What's included at each tier?
- Features, limits, support level
- How tiers differ from each other
2. Pricing Metric — What do you charge for?
- Per user, per usage, flat fee
- How price scales with value
3. Price Point — How much do you charge?
- The actual dollar amounts
- Perceived value vs. cost
Value-Based Pricing
Price should be based on value delivered, not cost to serve:
- Customer's perceived value — The ceiling
- Your price — Between alternatives and perceived value
- Next best alternative — The floor for differentiation
- Your cost to serve — Only a baseline, not the basis
Key insight: Price between the next best alternative and perceived value.
Value Metrics
What is a Value Metric?
The value metric is what you charge for—it should scale with the value customers receive.
Good value metrics:
- Align price with value delivered
- Are easy to understand
- Scale as customer grows
- Are hard to game
Common Value Metrics
| Metric | Best For | Example |
|---|---|---|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
Choosing Your Value Metric
Ask: "As a customer uses more of [metric], do they get more value?"
- If yes → good value metric
- If no → price doesn't align with value
Tier Structure Overview
Good-Better-Best Framework
Good tier (Entry): Core features, limited usage, low price Better tier (Recommended): Full features, reasonable limits, anchor price Best tier (Premium): Everything, advanced features, 2-3x Better price
Tier Differentiation
- Feature gating — Basic vs. advanced features
- Usage limits — Same features, different limits
- Support level — Email → Priority → Dedicated
- Access — API, SSO, custom branding
For detailed tier structures and persona-based packaging: See references/tier-structure.md
Pricing Research
Van Westendorp Method
Four questions that identify acceptable price range:
- Too expensive (wouldn't consider)
- Too cheap (question quality)
- Expensive but might consider
- A bargain
Analyze intersections to find optimal pricing zone.
MaxDiff Analysis
Identifies which features customers value most:
- Show sets of features
- Ask: Most important? Least important?
- Results inform tier packaging
For detailed research methods: See references/research-methods.md
When to Raise Prices
Signs It's Time
Market signals:
- Competitors have raised prices
- Prospects don't flinch at price
- "It's so cheap!" feedback
Business signals:
- Very high conversion rates (>40%)
- Very low churn (<3% monthly)
- Strong unit economics
Product signals:
- Significant value added since last pricing
- Product more mature/stable
Price Increase Strategies
- Grandfather existing — New price for new customers only
- Delayed increase — Announce 3-6 months out
- Tied to value — Raise price but add features
- Plan restructure — Change plans entirely
Pricing Page Best Practices
Above the Fold
- Clear tier comparison table
- Recommended tier highlighted
- Monthly/annual toggle
- Primary CTA for each tier
Common Elements
- Feature comparison table
- Who each tier is for
- FAQ section
- Annual discount callout (17-20%)
- Money-back guarantee
- Customer logos/trust signals
Pricing Psychology
- Anchoring: Show higher-priced option first
- Decoy effect: Middle tier should be best value
- Charm pricing: $49 vs. $50 (for value-focused)
- Round pricing: $50 vs. $49 (for premium)
Pricing Checklist
Before Setting Prices
- Defined target customer personas
- Researched competitor pricing
- Identified your value metric
- Conducted willingness-to-pay research
- Mapped features to tiers
Pricing Structure
- Chosen number of tiers
- Differentiated tiers clearly
- Set price points based on research
- Created annual discount strategy
- Planned enterprise/custom tier
Task-Specific Questions
- What pricing research have you done?
- What's your current ARPU and conversion rate?
- What's your primary value metric?
- Who are your main pricing personas?
- Are you self-serve, sales-led, or hybrid?
- What pricing changes are you considering?
Related Skills
- churn-prevention: For cancel flows, save offers, and reducing revenue churn
- cro: For optimizing pricing page conversion
- copywriting: For pricing page copy
- marketing-psychology: For pricing psychology principles
- ab-testing: For testing pricing changes
- revops: For deal desk processes and pipeline pricing
- sales-enablement: For proposal templates and pricing presentations