Product Playbooks
Decisions that shape the product itself — what to build next, when to say no, and how founders used real feedback to steer the roadmap without losing focus.
277 tactics · page 4 of 10
“This head of support reports to our head of product. I want a mirror in front of the product team right there. Growth comes from product decisions and not just from marketing campaigns.”
Put Support Inside the Product Team for a Faster Feedback Loop
Super Unlimited routes customer support directly into the product org — not a monthly KPI review but a live signal feed. Service quality tickets from Uganda surface immediately in the sprint backlog. Tanuj frames it simply: support is the fastest feedback loop a product team can have, and adding organizational distance between them slows the company down by months per iteration cycle.
“The first 85% is very easy. But after that every 1% is hard work. Sometimes differentiating great products from commodities is — do they just always work?”
The Last 10% Is the Entire Product — Edge Cases Define Who Wins in Commoditized Categories
VPN is a commodity in the first 85% — open source stacks exist, the core tunnel functionality is a known problem. Super Unlimited won the category by obsessing over the edge cases: reconnecting after a dropped cell tower transition, serving a user whose hotel blocks their IP, handling 3G in Nepal. Their QA engineer walked elevator shafts with debug builds to simulate real-world disconnects. In any category where competitors stop at 85%, the 15% of edge cases is the actual moat.
“Apps choose one hook, one viral killer feature within their app that will go viral on TikTok... I've seen apps create features just to go viral on TikTok and then use that as a funnel to their main ecosystem.”
Design Features Specifically to Go Viral on TikTok — Virability Is a Feature Requirement
A health analytics app that normally pitches 'improve your biometrics' created a single graph showing anxiety levels throughout the day — and it blew up on TikTok. Joseph's framework: if you can't identify a single feature of your app that's funny, controversial, or has wow-factor enough to be shared, that's a product gap, not just a marketing gap. The most virally-designed features also tend to be the most emotionally resonant ones for retention.
“When we're talking about messaging and integrating it we need to be looking at every single visual we do every single message we do like how can we bring this across to the user in a way that it then resonates with them.”
Visual Execution Must Reinforce the JTBD — Copy Alone Is Not Enough
Once the winning JTBD angle is confirmed in copy, every visual asset must carry the same message. Daphne's integration step isn't just swapping out headline text — it's auditing every screenshot, every illustration, every push notification icon against the validated job. Misalignment between copy and visuals is a common reason a message that tested well in ads underperforms when integrated into the product.
“LTV for us is a little too wishy-washy and too macro to make decisions on... we manage the day-to-day business on payback period which is a far cleaner very tangible metric that we can talk to the entire team about.”
Manage Day-to-Day Growth on Payback Period, Not LTV — It Is More Actionable
LTV requires years of cohort data to measure and changes as the product evolves, making it nearly useless for in-the-moment decisions. Ladder uses payback period — how much revenue is recouped at day 30, day 90, month 6, year 1 — as the operational metric. It is real-time, legible to the whole team, and directly connects spend decisions to cash flow dynamics.
“If you stacked up all the time on iteration between activation in the product and using our product and levers that we know are correlated to workout completions versus iteration on deals it would probably be 90% product 10% deals.”
Spend 90% on Product Activation, 10% on Discounts — The Ratio Matters
Greg's team allocation ratio is a useful benchmark: 90% of iteration effort on product activation (increasing the percentage of users who complete their first and second workout) and only 10% on discount and coupon mechanics. Most teams invert this, mistaking conversion-rate lifts from price cuts for product-market fit. The activation-first approach builds durable retention; discount-first builds churn-prone cohorts.
“free-to-play works if you have really significant network effects... you want as many people using it as possible”
Free Tier Expands Network Effects — Gating Access Kills Both Sides Of The Market
Dating is a market with two-sided network effects — women who get lots of matches and men who want more. Gating both sides behind a paywall collapses the network. Tinder let in 85-90% for free so the people others want to match with are definitely there, then monetized the 10-15% who want a better experience. The same logic applies to any app where user density is part of the value.
“it was pretty organic so I wish I could say you know we had this graphic... I think it was more of an organic process of launching one subscription seeing how it does figuring out what are the things that people really value in that bundle”
Build Tiers Organically From User Behavior — Tinder Did Not Plan A Three-Tier Model
Tinder Plus came first; Gold followed when the team identified what users valued most in that bundle; Platinum was created after noticing heavy spenders who wanted more utility, not just status. Start with one tier, study what people value and what they skip, and build the next tier from real usage signals — not a whiteboard model drawn before launch.
“goals are a three-legged stool you need the what you need the why you need the how and OKRs only have two of the legs”
NCT Framework Adds The Strategic Why That OKRs Always Miss
At TripAdvisor and with startup clients Ravi found OKRs repeatedly breaking down — not because the framework is bad, but because it assumes the strategic 'why' already exists. His NCT alternative adds Narratives (why), Commitments (what, not just metrics), and Tasks (how). The word 'commitment' acts as a natural limiter: people scope down to 3-5 things they will genuinely deliver, avoiding the goalpost-moving typical of classic OKRs.
“develop something totally new that's super exciting that people want and that they're like oh yeah heck yeah i'm going to subscribe... instead of locking features that users have been using behind the subscription”
Use The Carrot Not The Stick — Put New Features Behind Subscription, Not Features Users Already Have
Apps that switch to subscriptions and lock previously free features behind a paywall create instant outrage. Astropad launched a second binary as a subscription-only product with genuinely new capabilities built over two years. Existing app users kept what they had; subscribers got something new. This carrot-based approach keeps advocates advocating instead of churning into critics — the psychology of choice versus coercion makes all the difference.
“Repeat purchase mechanics are great for that consumable transaction that you want users to do so it is a little harder when you're trying to offer like here's this paintbrush for a lifetime then you don't have much left to offer and so you're kind of limiting the use there.”
Repeat-Purchase Mechanics Make Consumables Work — Avoid the Lifetime Item Trap
Consumables generate LTV through repetition, not one-time purchase — that's the entire mechanism. Selling a feature 'for life' destroys the monetization loop because there's nothing left to sell. The dating-app model (boosts that expire, flowers that get spent) is the archetype: each use is inherently temporary, naturally driving repeat purchase without feeling coercive.
“If you can look at metrics and KPIs and your performance across these two separate platforms or other platforms you'll notice that the behavior is very different no one solution fits all users.”
Split iOS/Android KPIs — Platform Behaviour Differences Are Not a Rounding Error
Tammy's first principle: analyse iOS and Android as entirely separate products. User behaviour, willingness to pay, preferred SKUs, and retention curves diverge meaningfully by platform. Blending them into a single dashboard hides which strategies actually work where. Platform-specific funnels are prerequisite to platform-specific monetization optimisation.
“I built a simple N agent which takes an idea or creative hypothesis generates a full creative brief founded on user psychology core value propositions and jobs to be done Then generates a prompt and creates that video with Sora 2.”
Build an N8N Agent That Turns a Hypothesis Into a Sora 2 Video in One Form Submission
Nathan built a fully automated n8n workflow: a creative strategist fills in a form with a hypothesis, and the agent generates a JTBD-rooted brief, turns it into a Sora 2 prompt, creates the video, polls for completion, uploads to Google Drive, and logs the result in Google Sheets. The entire loop runs unattended. Non-engineers on the team can trigger it directly, collapsing production to ideation time only.
“The product really has to be solved in a problem first and so you can't bring monetization in if there isn't like value that the user is finding that they're willing to pay for... for folks who are struggling with monetization that really is genuinely like the first troubleshooting step.”
Solve the Problem First — Monetization Problems Are Usually Product Problems in Disguise
Before optimizing any monetization lever, verify you have genuine product-market fit. Brandon frames monetization struggles as often being upstream product problems — if users aren't finding value, no paywall or upsell mechanic will fix it. This reset is the diagnostic first step, not an afterthought.
“If we were to tomorrow wake up and say all right we're gonna charge for all of our great features very likely in two years another great app will do it for free.”
Protect the Free Core: Charging for Everything Invites a Free Competitor in 2 Years
Duolingo's strategic moat is its free tier. Locking the best features behind a paywall is a direct invitation for a well-funded rival to undercut on price. With AI lowering build costs, the window before a competitor arrives has shrunk dramatically. Protecting the free experience is not charity; it is competitive defense.
“He was in our Discord and he was super active off hours — people would ask questions and he would answer them and he'd link to our help center — after a week I DM'd him and said who the hell are you.”
Hire Customers as Support Agents — They Know the Product Better Than Anyone
Captions found two of its best support agents by recruiting from its own user community. One power user was flagging bugs and requesting features so enthusiastically that Eli offered him a job. Another was voluntarily answering off-hours Discord questions from India. Recruiting from the customer base eliminates almost all product training, and these hires arrive with genuine passion for the product they are supporting.
“We're currently at 58 seconds as time to first reply... contact rate which is the percentage of customers of subscribers who reach out in a given month — right now we're at like a 3% which I think is a healthy number.”
Target 58-Second First Response and Track Contact Rate as Your Support Health Metric
Two metrics matter most for support operations: time to first response (Captions targets under 60 seconds) and contact rate (the percentage of subscribers who reach out per month, ideally around 3%). Contact rate is especially useful as a leading indicator — a spike from 1.5% to 4% in a month signals a release failure, outage, or poorly executed promotion before revenue numbers show it.
“They're not just trying to get through the queue and answer questions they have maybe two or three or four times as much time with each interaction to build rapport and maybe create more of a human connection.”
AI Agent as Tier-One Support Frees Humans to Build Rapport With High-Value Customers
The real value of AI-powered tier-one support is not headcount reduction — it is reallocation. When AI handles repetitive queries, human agents have 3-4x more time per interaction with the customers who actually need them. Captions uses a YC-backed AI agent to handle simple queries 24/7, freeing the human team to do the high-touch work of converting hesitant trial users and salvaging at-risk subscribers.
“If you're not in customer support listening to this tell your customer support people you're about to do a promotion — sales gets the party support gets the hangover.”
Tell Support About Campaigns Before They Launch — Sales Gets the Party, Support Gets the Hangover
Marketing promotions, billboard campaigns, Super Bowl ads, and feature launches all create an immediate spike in support volume. Not informing the support team before these events forces agents into reactive firefighting without the right macros, staffing, or preparation. Rule: support must be in the loop on any outbound marketing activity so they can update documentation, add temporary capacity, and prepare for the specific question types the campaign will generate.
“The best way to get their attention the editorial team is to build an incredible app have a very high user rating... that is what we look for in featuring because we know that typically is what will actually work really well.”
High App Ratings Are a Hard Prerequisite for Google Play Editorial Featuring
Google's editorial team starts with app quality signals — most importantly, user rating — before considering any app for featuring. Low ratings are a signal of product problems, not just a ranking issue. Reaching out for featuring while sitting at sub-4-star ratings wastes everyone's time; the product work must come first.
“Apps that find solid secondary product market fit have almost triple the minutes with their daily active users and almost double the daily active user to monthly active user ratio... what Calm did really well is they were out to solve a set of user problems that have some common symptoms.”
Secondary Product-Market Fit Nearly Triples DAU Minutes and Doubles DAU/MAU Ratio
Google's internal data shows apps that find a secondary use case — Calm expanding from meditation to sleep stories — see engagement metrics nearly double and triple. The insight is to think about the underlying user problem (poor sleep, anxiety) rather than the feature category (meditation app). Secondary PMF comes from solving adjacent symptoms of the same problem, not from bolting on unrelated features.
“we have a roadmap... people can submit requests they can view the road map... we have I think over 15,000 votes on different items and people write like dissertations around their theory of how they budget.”
Build a Public Voteable Roadmap So Customers Co-Create the Product With You
Monarch uses ProductBoard to run a fully public, voteable roadmap any user can access from the settings menu. Beyond feature prioritization, the system lets the team reach out directly to voters of a specific feature and walk a clickable prototype past them before any full build begins. This tight feedback loop means fewer wasted iterations and a customer base that feels invested in the product's direction.
“it's a combination I think of having a the talent the team that's able to move quickly and the sort of urgency and the wherewithal to make those decisions and just get aligned as a group... when good stuff happens it was the same thing.”
Speed of Execution Is a Muscle — Build It in Crises So It Is Ready for Opportunities
Monarch had lived through SVB collapsing, COVID disruptions, and California wildfires displacing team members before the Mint shutdown arrived. Each fire drill built the team's capacity to triage fast and realign. When the positive black swan came, they launched a full Chrome extension rebuild in 48 hours while competitors took six-plus weeks. The crisis response muscle is the same one that captures windfalls.
“I didn't even have to talk to Brock to launch that second experiment I changed the price on App Store Connect I already had two SKUs and I set it all up in Revenue cat to run this subsequent experiment without touching code without updating the app.”
Run Paywall Experiments Without a Developer by Using Backend-Driven Paywall Tools
David is a non-technical founder who works with a developer partner. The old workflow for A/B testing a paywall meant involving the developer for every variant — days of work. By using a backend-driven paywall, he could change pricing, pre-selected plans, and run scheduled experiments entirely from the dashboard — no code change, no App Store update required. For any founder without a full-time developer, this unblocks a critical growth lever.
“Our CPI limits are like 50 times less in some cases than iOS CPI limits — basically it's like you can drive installs to Android and you can keep getting more and more monthly active usage but the percentage that converts to paying users is like super super low.”
Android monetizes 20x less than iOS — your CPI limits and LTV/CAC model must reflect that
Even Microsoft — with global distribution, pre-install deals, and six+ Android app stores in China — sees Android in-app purchase revenue lagging iOS by roughly 20:1. Android drives installs but not LTV. This means CPI limits for paid Android campaigns must be drastically lower, and every platform spend (tooling, MMP data points, engagement) must be weighed against dramatically smaller per-user revenue.
“Developers need to think more than just straight up expensive subscriptions — some of the price points may need to go down, some new business models may need to be there, there has to be much more thought that has to go in to monetize that platform.”
Android needs its own monetization strategy — you cannot copy-paste iOS
Android's lower monetization rate isn't a bug that patience will fix — it reflects different user economics, particularly outside North America. High-priced iOS-style subscription tiers underperform. Microsoft treats Android as a separate strategy requiring lower price points, alternative business models, and regional monetization thinking rather than a carbon copy of what works on iOS.
“Existing does not mean anything — congratulations — the bar is even higher now. Solid design that uses Apple's robust design frameworks looks pretty good these days — but once you reach that point you've just reached zero.”
Get to zero first — a well-built app is table stakes, not your pitch hook
A working, well-designed app that uses platform conventions and spellings correctly is no longer a differentiator — it's the minimum bar to be taken seriously. From 500 pitches a day, about 100 look like real companies; of those, maybe a dozen are in the writer's beat; of those, one has something genuinely above the baseline. Your pitch should lead with that thing above zero, not with the fact that you built it.
“The fundamental experience of the App Store is pretty much the same 16 years on it's like three screenshots a description a user icon you can scroll and get more screenshots but what do people actually see... what I want to do is say hey this person saw this ad so in onboarding I want to ask them this set of questions.”
App Store Barely Changed in 16 Years — Web Gives Full Ad-to-Paywall Funnel Control
Since 2008 the App Store funnel has barely changed: screenshots, a description, and hope. Web lets you wire the entire journey together — a specific ad creative triggers a matching landing page, which feeds into a personalized onboarding flow, which leads to a paywall tuned to what the user saw top-of-funnel. This full-stack integration is impossible through the App Store. Custom product pages are the biggest App Store innovation in 16 years — and they still don't close the gap.
“I couldn't tell you what our daily active user number is or our monthly active user number because it's not what drives our growth model we are very focused on helping our users achieve their goal which is to learn a language and so at Babel we do have a proprietary metric that we optimize for it's called learner success.”
Optimize for Your Customer's Goal Metric, Not DAU/MAU — Babbel Uses "Learner Success"
Babbel deliberately doesn't track DAU or MAU — not because they can't, but because it's not the customer's goal. The customer's goal is to learn a language, so Babbel invented a 'learner success' metric that measures that directly. Stephen's principle: every app should define a metric aligned with what customers actually want to achieve. Optimizing for a metric that isn't in the customer's best interest puts the business on the wrong path, regardless of how large the numbers get.
“You have to think about neutralization… you have to keep differentiating then you have to keep incubating and you have to keep maintaining… for example Apple releases dark mode Apple release Vision Pro so we always maintain a leadership position in the sense that our apps are already on Vision Pro day one.”
Neutralize, Differentiate, Maintain, Incubate — the Four-Part Framework for Staying Ahead
Ramit's VP ran a four-part competitive framework: neutralize any competitor move before it erodes position, differentiate continuously, maintain core quality, and incubate the next wave. The allocation shifts as the app matures — early-stage apps spend more on neutralization; mature apps can invest more in incubation. Startups and giants both need this loop.