Your users can leave while the account stays
A worked account-and-user example shows how team turnover, concentrated use and new participants can tell different stories about retention.
Strategy, retention, and the business of product
Find the guide for your next product decision.
Reading collection: Growing a marketplace
Showing 1–12 of 40 articles · Newest first
A worked account-and-user example shows how team turnover, concentrated use and new participants can tell different stories about retention.
A worked AI task-cost model includes retries, failed work, tools and human review, showing how success rates and difficult jobs change contribution margin.
A reproducible hypothetical comparison separates annual-plan cash timing, monthly-normalized value and the renewal decisions a team can actually observe.
Build a task ledger for background products: expected work, completion, freshness and delivery. Distinguish quiet success from automation that has stopped.
Compare 20 monetization consultancies and specialists for ad-supported products, from stack audits and product decisions to yield operations and advertising strategy.
Compare 20 product growth and subscription lifecycle specialists for recurring value, retention research, renewal decisions, CRM and pricing, with engagement limits.
Use a cancellation-reason coding example to separate customer explanations, observed behavior and follow-up questions before changing pricing or the roadmap.
A subscriber-access guide separates app identity, store account, purchase record and entitlement across reinstall, new-device, anonymous-purchase and duplicate-account cases.
Plan feature retirement around customer dependencies, replacement workflows and migration completion, with a practical register and shutdown criteria.
Separate expired authorization from lost customer demand. A recovery plan follows the connection, missed work and downstream result before calling an account restored.
Give temporary feature grants a clear scope, accountable owner and exit plan. Prevent a short exception from becoming an unexplained permanent entitlement.
Figma and Slack illustrate why a pricing migration needs separate rules for product access, administrator controls, legacy features and renewal charges.