Files
skills/public/tier-structure.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
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]>
2026-09-15 01:27:26 -07:00

7.0 KiB

Tier Structure and Packaging

Contents

  • How Many Tiers?
  • Good-Better-Best Framework
  • Tier Differentiation Strategies
  • Example Tier Structure
  • Packaging for Personas (Identifying Pricing Personas, Persona-Based Packaging)
  • Freemium vs. Free Trial (When to Use Freemium, When to Use Free Trial, Hybrid Approaches)
  • Enterprise Pricing (When to Add Custom Pricing, Enterprise Tier Elements, Enterprise Pricing Strategies)

How Many Tiers?

2 tiers: Simple, clear choice

  • Works for: Clear SMB vs. Enterprise split
  • Risk: May leave money on table

3 tiers: Industry standard

  • Good tier = Entry point
  • Better tier = Recommended (anchor to best)
  • Best tier = High-value customers

4+ tiers: More granularity

  • Works for: Wide range of customer sizes
  • Risk: Decision paralysis, complexity

Good-Better-Best Framework

Good tier (Entry):

  • Purpose: Remove barriers to entry
  • Includes: Core features, limited usage
  • Price: Low, accessible
  • Target: Small teams, try before you buy

Better tier (Recommended):

  • Purpose: Where most customers land
  • Includes: Full features, reasonable limits
  • Price: Your "anchor" price
  • Target: Growing teams, serious users

Best tier (Premium):

  • Purpose: Capture high-value customers
  • Includes: Everything, advanced features, higher limits
  • Price: Premium (often 2-3x "Better")
  • Target: Larger teams, power users, enterprises

Tier Differentiation Strategies

Feature gating:

  • Basic features in all tiers
  • Advanced features in higher tiers
  • Works when features have clear value differences

Usage limits:

  • Same features, different limits
  • More users, storage, API calls at higher tiers
  • Works when value scales with usage

Support level:

  • Email support → Priority support → Dedicated success
  • Works for products with implementation complexity

Access and customization:

  • API access, SSO, custom branding
  • Works for enterprise differentiation

Example Tier Structure

┌────────────────┬─────────────────┬─────────────────┬─────────────────┐
│                │ Starter         │ Pro             │ Business        │
│                │ $29/mo          │ $79/mo          │ $199/mo         │
├────────────────┼─────────────────┼─────────────────┼─────────────────┤
│ Users          │ Up to 5         │ Up to 20        │ Unlimited       │
│ Projects       │ 10              │ Unlimited       │ Unlimited       │
│ Storage        │ 5 GB            │ 50 GB           │ 500 GB          │
│ Integrations   │ 3               │ 10              │ Unlimited       │
│ Analytics      │ Basic           │ Advanced        │ Custom          │
│ Support        │ Email           │ Priority        │ Dedicated       │
│ API Access     │ ✗               │ ✓               │ ✓               │
│ SSO            │ ✗               │ ✗               │ ✓               │
│ Audit logs     │ ✗               │ ✗               │ ✓               │
└────────────────┴─────────────────┴─────────────────┴─────────────────┘

Packaging for Personas

Identifying Pricing Personas

Different customers have different:

  • Willingness to pay
  • Feature needs
  • Buying processes
  • Value perception

Segment by:

  • Company size (solopreneur → SMB → enterprise)
  • Use case (marketing vs. sales vs. support)
  • Sophistication (beginner → power user)
  • Industry (different budget norms)

Persona-Based Packaging

Step 1: Define personas

Persona Size Needs WTP Example
Freelancer 1 person Basic features Low $19/mo
Small Team 2-10 Collaboration Medium $49/mo
Growing Co 10-50 Scale, integrations Higher $149/mo
Enterprise 50+ Security, support High Custom

Step 2: Map features to personas

Feature Freelancer Small Team Growing Enterprise
Core features ✓ ✓ ✓ ✓
Collaboration — ✓ ✓ ✓
Integrations — Limited Full Full
API access — — ✓ ✓
SSO/SAML — — — ✓
Audit logs — — — ✓
Custom contract — — — ✓

Step 3: Price to value for each persona

  • Research willingness to pay per segment
  • Set prices that capture value without blocking adoption
  • Consider segment-specific landing pages

Freemium vs. Free Trial

When to Use Freemium

Freemium works when:

  • Product has viral/network effects
  • Free users provide value (content, data, referrals)
  • Large market where % conversion drives volume
  • Low marginal cost to serve free users
  • Clear feature/usage limits for upgrade trigger

Freemium risks:

  • Free users may never convert
  • Devalues product perception
  • Support costs for non-paying users
  • Harder to raise prices later

When to Use Free Trial

Free trial works when:

  • Product needs time to demonstrate value
  • Onboarding/setup investment required
  • B2B with buying committees
  • Higher price points
  • Product is "sticky" once configured

Trial best practices:

  • 7-14 days for simple products
  • 14-30 days for complex products
  • Full access (not feature-limited)
  • Clear countdown and reminders
  • Credit card optional vs. required trade-off

Credit card upfront:

  • Higher trial-to-paid conversion (40-50% vs. 15-25%)
  • Lower trial volume
  • Better qualified leads

Hybrid Approaches

Freemium + Trial:

  • Free tier with limited features
  • Trial of premium features
  • Example: Zoom (free 40-min, trial of Pro)

Reverse trial:

  • Start with full access
  • After trial, downgrade to free tier
  • Example: See premium value, live with limitations until ready

Enterprise Pricing

When to Add Custom Pricing

Add "Contact Sales" when:

  • Deal sizes exceed $10k+ ARR
  • Customers need custom contracts
  • Implementation/onboarding required
  • Security/compliance requirements
  • Procurement processes involved

Enterprise Tier Elements

Table stakes:

  • SSO/SAML
  • Audit logs
  • Admin controls
  • Uptime SLA
  • Security certifications

Value-adds:

  • Dedicated support/success
  • Custom onboarding
  • Training sessions
  • Custom integrations
  • Priority roadmap input

Enterprise Pricing Strategies

Per-seat at scale:

  • Volume discounts for large teams
  • Example: $15/user (standard) → $10/user (100+)

Platform fee + usage:

  • Base fee for access
  • Usage-based above thresholds
  • Example: $500/mo base + $0.01 per API call

Value-based contracts:

  • Price tied to customer's revenue/outcomes
  • Example: % of transactions, revenue share