$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill ai-feature-monetizationUse this skill when the user asks specifically about "how to monetize AI features", "should AI be a separate tier", "pricing for AI capabilities", "how to charge for AI", "AI add-on vs. bundle", "AI feature pricing strategy", or is adding AI capabilities to an existing product an
| 1 | # AI Feature Monetization |
| 2 | |
| 3 | You are helping the user decide how to monetize AI features specifically — a distinct challenge from general pricing because AI features have meaningful variable costs (API inference) and often deliver value in a way that's hard to measure per-use. |
| 4 | |
| 5 | Framework: Palle Broe (How should you monetize your AI features, Lenny's Newsletter 2024 — analysis of 44 tech incumbents), Lenny Rachitsky (AI monetization patterns). |
| 6 | |
| 7 | Key data from Palle Broe: Of 44 leading tech incumbents: |
| 8 | - **59% bundle** AI features in existing packages — no separate charge |
| 9 | - **23% offer as an add-on** — separate AI tier or add-on price |
| 10 | - **18% build standalone AI products** — separate product entirely |
| 11 | |
| 12 | ## Step 1 — Load Context |
| 13 | |
| 14 | Read `memory/user-profile.md` for product stage, business model, and existing pricing. Read `context/company/competitors.md` for competitive pricing context. |
| 15 | |
| 16 | ## Step 2 — The Three Monetization Models |
| 17 | |
| 18 | **Model 1 — Bundle (59% of incumbents):** |
| 19 | AI features are included in existing plans. No separate pricing. |
| 20 | |
| 21 | When to use: |
| 22 | - AI feature is a product improvement, not a new product (enhances existing value rather than creating a new use case) |
| 23 | - The marginal cost of AI inference is low relative to subscription revenue |
| 24 | - Bundling protects against competitive unbundling (competitor offers AI for free) |
| 25 | - User acquisition and retention value of "AI included" outweighs direct monetization |
| 26 | |
| 27 | Risk: If AI inference costs are high and usage is uncapped, you lose money on high-usage customers. |
| 28 | Mitigation: Soft limits or fair use policies on AI feature usage. |
| 29 | |
| 30 | **Model 2 — Add-on (23% of incumbents):** |
| 31 | AI features are in a separate tier or add-on price point. |
| 32 | |
| 33 | When to use: |
| 34 | - AI feature is genuinely new value, not just a product improvement |
| 35 | - There's a clear segment willing to pay more specifically for AI |
| 36 | - AI inference costs are significant and variable |
| 37 | - You need to signal that AI is premium (price communicates value) |
| 38 | |
| 39 | Risk: Adds friction to adoption; users have to actively decide to pay for AI. |
| 40 | Mitigation: Free trial of AI features; show clear ROI before paywall. |
| 41 | |
| 42 | **Model 3 — Standalone (18% of incumbents):** |
| 43 | AI is a separate product with its own pricing. |
| 44 | |
| 45 | When to use: |
| 46 | - AI capability is a genuinely different product that serves a different (or expanded) use case |
| 47 | - The AI product can be sold to users who don't use the core product |
| 48 | - You want to build a separate go-to-market motion |
| 49 | |
| 50 | Risk: Splits focus; dilutes brand; harder to sell. |
| 51 | When it works: When the AI product has clear standalone value (like PM Copilot — it's a plugin that adds genuine PM capability, not just an AI wrapper on an existing feature). |
| 52 | |
| 53 | ## Step 3 — Variable Cost Analysis |
| 54 | |
| 55 | For AI-powered features, calculate the cost structure: |
| 56 | |
| 57 | **Cost per session / per use:** |
| 58 | - Average input tokens per request × input token cost |
| 59 | - Average output tokens per request × output token cost |
| 60 | - Tool calls / retrieval costs if applicable |
| 61 | |
| 62 | **At scale:** |
| 63 | - Estimated AI cost per active user per month |
| 64 | - What % of subscription revenue does this represent? |
| 65 | |
| 66 | **Threshold analysis:** |
| 67 | - At current pricing, how many AI uses per month can a customer make before they're unprofitable? |
| 68 | - Is a fair use policy (e.g., "X AI requests per month") needed to protect margins? |
| 69 | |
| 70 | ## Step 4 — Decision Framework |
| 71 | |
| 72 | Use this decision tree: |
| 73 | |
| 74 | 1. Is the AI feature a product improvement (enhances existing use case) or new value (entirely new use case)? |
| 75 | - Improvement → lean toward Bundle |
| 76 | - New value → consider Add-on or Standalone |
| 77 | |
| 78 | 2. Is the marginal cost per user per month < 10% of their subscription revenue? |
| 79 | - Yes → Bundle is financially sustainable |
| 80 | - No → Add-on or usage-based pricing needed |
| 81 | |
| 82 | 3. Is there a clear segment willing to pay more specifically for AI? |
| 83 | - Yes → Add-on or premium tier |
| 84 | - No → Bundle (treat as competitive necessity) |
| 85 | |
| 86 | 4. Is the AI product compelling enough to stand alone without the core product? |
| 87 | - Yes → consider Standalone |
| 88 | - No → Bundle or Add-on |
| 89 | |
| 90 | ## Step 5 — Output |
| 91 | |
| 92 | Produce: |
| 93 | - Recommendation (Bundle / Add-on / Standalone) with rationale |
| 94 | - Variable cost estimate (cost per active user per month at current model tier) |
| 95 | - Margin analysis (at what usage level does the current pricing become unprofitable?) |
| 96 | - Competitive context (what are competitors doing? Is "AI included" becoming table stakes?) |
| 97 | - Implementation recommendation: if Add-on, what's the upgrade trigger? If Bundle, what's the fair use policy? |