Your user wants an upgrade, but someone else controls the budget
Help an existing user get an upgrade approved without losing the work that created demand. Design the request, authority check and return to the product.
Strategy, retention, and the business of product
Find the guide for your next product decision.
Reading collection: Growing a marketplace
Showing 13–24 of 40 articles · Newest first
Help an existing user get an upgrade approved without losing the work that created demand. Design the request, authority check and return to the product.
Design the product experience between a failed renewal and final subscription loss, using Stripe and Paddle rules to separate retries, access and recovery.
Define eligible accounts, exposure and repeat use before judging a feature launch. A worked example shows why the denominator changes the decision.
A six-person example shows how valid identity joins change retention counts, plus a practical way to reconcile raw events with resolved customer histories.
Use stable assignment, a useful return outcome and an honest comparison window to measure whether a lifecycle reminder changes product behavior.
Follow marketplace incentives through first orders, repeat demand and contribution. Learn what a cohort comparison can show and where shared supply limits causal claims.
Use failed demand by location, time and job to decide whether a marketplace needs more supply, better matching or more accurate availability.
Read buyer, seller and buyer-seller recurrence from the same transaction ledger. A worked example shows repeat GMV growing while seller participation narrows.
Compare retained marketplace fees with refunds, payment costs, incentives and support. A checked transaction model shows how take rate can rise while contribution falls.
Separate access, proration and payment in a mid-cycle upgrade, with a worked plan-and-seat adjustment and clear behavior when the extra payment fails.
Build a shared notification policy that resolves competing campaigns, respects preferences and drops stale messages before a retry becomes an interruption.
Define prepaid-credit behavior with a worked paid-and-promotional balance ledger, including expiry, reservations, corrections and what carries into renewal.