Product Management Monetization

Product Management — Monetization

When to Use

• Define pricing strategy, packaging, and plan differentiation
• Write PRDs for checkout, upgrades, usage limits, entitlements, or billing settings
• Design paywall and upgrade journeys (what to gate, when, and why)
• Plan monetization experiments (price tests, packaging, trial length)
• Specify usage meters and fair-use policies for usage-based models
• Improve expansion paths (seats, add-ons, consumption tiers)
• Set monetization metrics and dashboards for product decisions
• Align with finance/legal on list price, discounts, and recognition flags

When NOT to Use

• ASC 606, deferred revenue schedules, audit → senior-revenue-accountant
• Support refunds, dunning, subscription ops → customer-ops-specialist
• TAM/SAM, competitor monetization research only → business-model-researcher
• CPQ, order forms, signature routing → deal-operations-administrator
• Stripe/webhook implementation → fullstack-software-engineer
• Visual-only paywall mockups → product-designer

Related skills

Core Workflows

1. Pricing and packaging

Value metrics, tiers, fences.

See `references/pricing_packaging.md`.

2. Monetization model selection

Subscription, usage, hybrid, marketplace.

See `references/monetization_models.md`.

3. Metrics and experiments

North star, test design, guardrails.

See `references/metrics_experiments.md`.

4. Paywalls and conversion

Gating, trials, upgrade triggers.

See `references/paywall_conversion.md`.

5. Billing platform requirements

Entitlements, meters, proration rules.

See `references/billing_platform_requirements.md`.

6. Launch and governance

Rollout, comms, price change policy.

See `references/launch_governance.md`.

Output standards

• Every monetization change states target segment and metric
• Experiments have hypothesis, guardrails, and stop rules
• Packaging maps features → plans with clear upgrade path
• Flag recognition/billing dependencies for finance before GA
• No list price commitments in PRD without deal desk/finance sign-off

When to load references

• Pricing → references/pricing_packaging.md
• Models → references/monetization_models.md
• Experiments → references/metrics_experiments.md
• Paywall → references/paywall_conversion.md
• Billing → references/billing_platform_requirements.md
• Launch → references/launch_governance.md

Billing Platform Requirements

PM vs engineering boundary

Entitlements model

| Capability | Free | Pro | Enterprise |
|------------|------|-----|------------|
| SSO | — | — | ✓ |
| API calls/mo | 1k | 50k | custom |

Requirements:

• Source of truth (billing provider vs internal DB)
• Propagation latency SLA
• Grace on payment failure

Subscription lifecycle events

Product must define behavior for:

Ops execution: customer-ops-specialist.

Usage metering PRD fields

• Event name and payload schema
• Aggregation window (calendar month vs rolling)
• Idempotency key
• Backfill and correction policy
• Customer-visible usage dashboard
• Dispute process

Integrations checklist

• [ ] Tax/VAT display by region
• [ ] Invoices and receipt emails
• [ ] Admin: comp accounts, credits, extensions
• [ ] Webhooks to CRM for sales alerts
• [ ] Sandbox for sales demos

Finance alignment

Before GA provide finance:

• SKU list and list prices
• Discount types
• Performance obligation mapping flag → senior-revenue-accountant
• Refund and credit accounting treatment

Security and compliance

• PCI scope minimized (hosted checkout)
• Role for viewing billing vs changing payment method
• Audit log on entitlement overrides

Anti-patterns

• Hard-coded plan checks scattered without entitlement service
• Meter events without idempotency
• Promising invoice terms product cannot provision

Launch and Governance

Monetization launch tiers

Launch checklist (Tier 1+)

• [ ] PRD approved; entitlements documented
• [ ] Finance SKU and recognition notes
• [ ] Legal: terms, tax, region availability
• [ ] Analytics events live in staging
• [ ] Support macro and KB (customer-ops-specialist)
• [ ] Sales enablement (battlecard, FAQ)
• [ ] Rollback plan (feature flag, price revert)
• [ ] Customer comms if existing users affected

Price change governance

Grandfathering policy template

**Existing customers:** [keep legacy / migrate on renewal / opt-in migrate]
**New customers:** [new price effective DATE]
**Enterprise contracts:** [honor MSA through term]

Conflict resolution

Documentation deliverables

• Internal pricing playbook (plans, fences, objections)
• Public pricing page brief (not legal terms)
• Changelog entry for transparency

Retrospective

After major monetization launch:

• Conversion vs forecast
• Support ticket themes
• Unintended downgrade/churn
• Playbook updates for references/pricing_packaging.md

Related programs

• Large cross-team price migrations → technical-program-manager
• Company-wide customer messaging → communication-lead

Metrics and Experiments

Monetization metric stack

Define one north star per initiative (e.g. paid conversion, expansion ARPU).

Funnel diagnostics

Instrument: page views, plan selection, checkout steps, entitlement changes.

Experiment design

## Experiment: [name]

**Hypothesis:** If we [change], then [metric] will [direction] because [reason].
**Segment:** [who]
**Variants:** Control vs treatment
**Primary metric:** …
**Guardrails:** churn, support volume, revenue per user
**Duration / sample:** power assumption
**Stop rules:** harm threshold on guardrail
**Ship criteria:** stat sig + practical significance

Price testing constraints

• Legal: price discrimination rules by region
• Contract: grandfathered customers
• Sales: conflict with quoted enterprise deals
• Brand: public price transparency

Prefer new cohorts or geographies when full A/B on list price is blocked.

Packaging experiments

• Add/remove fence on tier
• Bundle vs unbundle feature
• Trial length or credit card upfront
• Annual default vs monthly

Reporting cadence

Anti-patterns

• Optimizing clicks without revenue outcome
• Ending tests early on novelty effect
• Shipping price change without finance model update

Monetization Models

Model comparison

Hybrid pattern (common B2B)

Platform fee (seats or flat) + included quota + overage per unit

Specify in PRD:

• What resets monthly vs annual
• Overage price and caps
• Grace period before hard block

Freemium design

Usage-based specifics

• Meter definition: billable event schema (idempotent, auditable)
• Rating: tiered blocks vs linear
• Preview: estimated bill in product UI
• Alerts: 50/80/100% thresholds

Pair with product-management-human-data-platform for labeling-volume pricing.

Enterprise vs self-serve

Product defines entitlement parity between channels where possible.

Marketplace (if applicable)

• Take rate and payout timing
• Seller onboarding and KYC product requirements
• Dispute and refund split rules
• Search ranking and monetization conflict policies

Model migration

When changing models (e.g. seat → usage):

• Customer impact segments
• Parallel run period
• Legacy plan sunset timeline
• Finance recognition impact → senior-revenue-accountant

Paywalls and Conversion

Gating strategies

Choose gate based on where value is realized, not where eng is easiest to block.

Paywall moment design (PM spec)

For each gate document:

**Trigger:** User attempts [action]
**State shown:** Modal / full page / inline banner
**Copy intent:** What they gain by upgrading (not feature list only)
**Primary CTA:** Upgrade to [plan]
**Secondary:** Compare plans / contact sales
**Escape hatch:** What still works free
**Analytics:** paywall_viewed, upgrade_clicked, plan_selected

product-designer owns visual execution.

Trial design

Upgrade paths

Expansion triggers (in-product)

• Approaching limit (80% usage)
• Team size growth (invite blocked)
• Feature discovery (locked preview with tooltip)
• Success milestone ("You saved X hours—unlock reports")

Churn prevention product hooks

• Cancel flow with save offers (policy with finance)
• Downgrade vs pause vs export data
• Win-back offers post-cancel (coordinate customer-ops-specialist)

Enterprise considerations

• Same SKU in product as order form
• No self-serve downgrade below contracted minimum
• Custom entitlements flag in admin

Ethics and trust

• Clear renewal price before annual charge
• No dark patterns on cancel
• Disclose usage metering before consumption

Pricing and Packaging

Value metric selection

Pick one primary value metric; secondary metrics for add-ons only.

Packaging principles

Tier definition template

## Plan: Pro

**Persona:** Team lead, 5–50 users
**Price:** $X / seat / month (annual -Y%)
**Core value:** [one sentence]

**Included:**
- …

**Limits:**
- …

**Not included (upgrade to Enterprise):**
- …

**Upgrade trigger:** Needs SSO, audit logs, >N seats

Discount policy (product input)

Product documents eligibility rules; deal desk executes custom deals.

Competitive positioning

Use business-model-researcher for benchmarks; PM decides position (premium, parity, penetration).

Document:

• Reference competitors (public list prices only)
• Differentiation worth paying for
• Where you will not compete on price

Price change communication

• Grandfather vs migrate: policy per segment
• Notice period (contract and regulatory minimums)
• In-product messaging and email templates (communication-lead if company-wide)

Anti-patterns

• Feature parity across tiers with price-only difference
• Unlimited usage on usage-priced product without cost model
• Packaging driven by sales one-offs without platform abstraction