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 2 of 10
“niche down as much as possible I only need 0.1% of the market and I'm good”
Niche Down Until You Only Need 0.1% of a Validated Market
Fernando targets already-validated markets (resume builders, carousel tools) but narrows the scope so sharply that giant competitors can't follow without alienating their broad user base. Because he needs a tiny slice to be profitable, he can out-specialize any VC-backed competitor who must serve a broad audience to justify their scale.
“to the outside world it's really boring, but I was living and breathing Microsoft Intune”
Scratch Your Own Itch in the Domain You Already Live and Breathe
Thomas found his idea not by browsing trend lists but by noticing a recurring pain he experienced daily as an IT admin — application packaging taking up to an hour per app. Because he had deep domain credibility, he could see exactly what competitors were missing and build something that felt right to practitioners. Building in an area you already inhabit removes the need to fake expertise and lets product intuition replace guesswork.
“the way we got it off the ground was we would share it with some people people would use it in like Discord communities a little bit to help out we kept on improving it we kept on listening to the customers and it grew to 10K a month fairly organically as it got to a much better place and to a good place where we felt pretty confident we reached out to a couple people on YouTube to make videos about it”
Stay in Communities Listening Until Organic Growth Reaches Ten K MRR
Before turning on any paid or influencer channels, Sebastian's team spent months seeding the product quietly in Discord servers and iterating on feedback. They treated $10K MRR as the proof threshold that the core product experience was genuinely worth recommending. Only then did they greenlight external promotion.
“A friend told me about how he was struggling to stay on task and motivated So that sparked an idea I didn't want another boring habit tracker So I gamified the whole experience with leaderboards XP badges and even characters”
Gamify Your Core Loop to Make Behavior-Change Apps Actually Sticky
Evan saw a crowded habit-tracker market and chose differentiation through gamification rather than features. The result was character selection on onboarding, XP rewards for completing tasks, and a leaderboard — elements borrowed from games that drive compulsive return visits and make the app feel nothing like its competitors.
“I think the key thing about this idea is that it's not an idea at all it's a validated market which was first validated with the tweet by Peter levels I saw and then by sales I got from my Reddit post”
Build for Proven Demand by Targeting a Shutting-Down Giant's Market
Dennis explains why Yaphone succeeded where his previous projects failed. The market for international calling was proven by Skype's decades of users, and the shutdown created immediate, urgent demand. He saw idea validation twice — first from Peter Levels' tweet, then from first-minute sales on Reddit.
“I think for both apps really what we're selling was confidence”
Extrapolate the Deeper Desire Your App Fulfills and Sell That Instead
Kishi noted that both Social Wizard and Clean Eats were fundamentally selling confidence, not features. Understanding the emotional outcome — not the functional description — is what drives conversions. He reframed a nutrition app as a skincare tool and immediately unlocked a more motivated audience.
“I was doing computer vision and then music a lot And turns out that these two can meet in the field of AI animation for music videos”
Combine Skills From Unrelated Fields to Find Your Unique Product Idea
Nico describes what he calls the 'around find' principle: scatter your efforts across many random domains, then watch for moments when two of them collide. In his case, his physics-era work in computer vision and his lifelong passion for music converged naturally into an AI music video generator nobody else was building.
“the thing I noticed about the app developers is that there's like solo developers indie hackers and I thought that they lack great user experience All of their apps are kind of technical and a bit complex for regular users And the other type of apps was VC backed or like huge corporations The user experience were was great But the problem about them was that they actually move pretty slow”
Target the Gap Between Indie Hackers and Slow Enterprise Software
Ericas identified a structural gap in the Shopify app marketplace: indie developers shipped fast but had poor UX, while large companies had great UX but moved slowly. By combining a designer's eye for experience with a small team's speed, he found a lane neither competitor could occupy. This positioning let him compete against both categories and win.
“I've been very very tempted to expand into adjacent markets just because apps there were doing very well, but I've consciously stuck to doing the simple stuff well. I think that slow consistency is what has worked for me.”
Resist Adjacent-Market Expansion Because Pointy Features Beat Feature Parity
With $15K MRR and a 200K-user base, Lewis watched competitors stack features and stayed pointy. Audio Pen does voice-to-clean-text and nothing else — that focus is the moat against bigger tools trying to do everything. Slow consistency on one job is what kept users renewing.
“Fastest way to make some money right now is to do one-to-one copy of a very successful app... I change black by pink I replace add content by sugar and then done.”
Clone The App Screen-For-Screen But Switch The Niche So You Inherit The Playbook Not The Audience
David found a $200K/month app for quitting porn (Quittr), cloned every screen and word, then swapped the niche to quitting sugar for Gen Z women. The 1% different change wasn't the product — it was the customer base, which meant inheriting proven onboarding and paywall mechanics without competing for the original's audience.
“After that first app I quickly realized that apps that are social are super hard to scale so I eventually moved on to utilities and tools and these are much more easy to scale as a oneman person.”
Pivot From Social Apps To Utilities Because A Solo Founder Cannot Bootstrap Two-Sided Liquidity
Connor's first app, a social events app, took 6-8 months and failed because social apps require network effects to scale. He pivoted to utilities and tools, which a solo founder can grow without coordinating two-sided liquidity, and that pivot is what unlocked seven figures in subscription revenue across his portfolio.
“Step three is making sure that it hits a natural upgrade path. So this goes okay I want to send cold emails I got to get more customers. But okay now I want to connect Mail Lead to these other apps I use. So boom you click the automation button and it's task magic. Built right in seamlessly.”
Engineer A Natural Upgrade Path So Hitting A Wall In The Satellite Drops Users Into The Tentpole
Each satellite product must dead-end into the next product in the ecosystem. Mail Lead users who wanted to connect their cold emails to other apps clicked an 'automation' tab that was literally Taskmagic embedded — converting them without any sales motion. The usage limit is the upgrade trigger.
“Directories still are incredibly successful in 2025 especially if you build something for the right audience... the directory solves a timeless problem like you need to find something that you're interested in and in this new AI world where we live in like cursor, people are starting to look through how to do things... if you can catch that wave you're really going to find a lot of visitors.”
Directories Aren’t Dead — They Win By Catching A New Platform Wave First
The directory model still works when it rides a new platform wave (Cursor, then MCPs) before anyone else has aggregated the content. Pontus added a second adoption spike by making MCPs searchable on the site right when that ecosystem emerged — owning the canonical reference for a hot new category compounds traffic over time.
“every mobile app that you build should be approached from a marketing first standpoint because as long as you can market your product you will make money and if your product is not marketable you could have the best product in the world but if no one knows about it you're never going to make any money”
Approach Every Mobile App As Marketing-First — Marketable Beats Best
Steven argues every mobile app must start from a marketing-first standpoint. A marketable product makes money even if it isn't the best, while an unmarketable product fails no matter how good it is.
“we didn't have the energy pills but even if we did I think sharing it with people you had just met would be like oh no I'm okay that was the aha moment of like what if we can make supplementation more accessible and approachable by putting these great ingredients instead of pill form into gum and mints”
Repackage The Pill Into Gum When Strangers Would Never Accept It
While getting scuba certified with strangers, Ryan realized nobody would accept a random pill from someone they had just met. That insight reframed the product: take the dorm-room nootropic formulas and put them into gum and mints so supplementation felt approachable and social.
“The first prototype of Rooted was essentially the panic attack button that would walk you through a panic attack and that actually hasn't changed a ton over the years because it's really the core of Rooted it's the aha moment that really resonates with users.”
Keep The Core MVP Feature Untouched Through Four Million Downloads
Anya's first build was a single button that guided a user through a panic attack in real time. Years and millions of downloads later, that exact feature is still the heart of the app while the surrounding design evolved around it.
“I was in my friend's studio and he used this very old flash app on a on an old laptop and he remote controls everything from his nice table and then to start a timer he has to get up walk into the other room and hit a button and walk back and my web developer mind immediately says surely there's a better way... you find that they waste hours and they do things in the most awkward ways that you would have automated long ago these are the really the simple ideas that you can turn into a lot of money”
Find Million-Dollar SaaS Ideas By Watching People Do Their Job Awkwardly
The stage timer idea came from watching a friend in a studio physically walk into another room to press start on an old flash app. Lucas's framework for finding more million-dollar niches: go observe non-developers doing their jobs and look for the awkward manual workarounds they've never thought to automate.
“Start small. Start with an actual problem either you or someone else experienced because I guarantee you if you have this problem there's at least one more person on this earth with the same problem and that should be enough to start this project.”
Pick A Real Problem You Or A Friend Already Has — One Other Person Is Enough
Chris validated his wishlist app by scratching his own itch, since he was still tracking his Christmas list in an Excel sheet. He argues that if you personally have a problem, at least one other person on earth shares it, and that's enough signal to start.
“I look at ones like Ladder or AllTrails or Strava and they all associate with a person's identity and then it's something they repeat frequently. To us we felt like we were capturing a student's identity — going to class and recording as something you do daily or a few times a week.”
Build for identity + daily frequency — like Strava, AllTrails, Ladder
Brett's product filter for consumer apps: does it tie to identity ('I am a student / runner / lifter') AND get used at high frequency? Coconote pinned itself to going to class — daily ritual + identity behavior — which builds a personal corpus (physics 1, 2, 3) that creates compounding switching costs.
“You can't really plan for virality but you can at least sow the seeds and see if they germinate. If you don't cultivate the right conditions for virality to occur it never will. If you have the ability to share content, put those share features in — then at least you can see the natural predilection of users to share.”
Plant the seeds of virality even if you can't plan for it
Andy's pragmatic take on viral loops: build the cheap share/referral surfaces during the growth phase so you can observe whether organic sharing happens. Even small amounts lower blended CAC; occasionally you'll catch fire. Don't engineer virality, but don't preclude it either.
“You should always have TAM in the back of your mind because as a product leader, your product is going to continue to evolve. Serviceable for me in the future is different than what it is today. It's always important to figure out what the delta is between your TAM and your currently serviceable addressable market.”
SAM evolves as your product evolves — keep TAM in view as the ceiling
Today's SAM is bounded by today's product. As you build, the line moves. Keep TAM in view as the ceiling you're building toward — not the number you plan against — and watch the delta close as new features make previously-non-serviceable users serviceable.
“Giving people control, putting them at the center, making them feel like they have control is one of the better ways to build trust. The subscriptions I know will be a pain to cancel — those I really avoid.”
Cancel flow should respect them — pause, monthly, MCAT 3-month bundle
Instead of a friction-heavy retention wall, Quizlet's cancel flow offers pause, shorter monthly durations, and use-case-matched bundles (e.g. 3-month MCAT prep). Respecting the user's actual reality reduces the 'never subscribe again' reaction and keeps the door open for future re-engagement.
“We kind of have two parts of the business. One is surf forecasting. The second piece are the cameras and the camera technology that we're developing. There are interesting synergies between the camera technology we're developing and surf parks.”
Cams + forecasts — physical camera network is the actual moat
Surfline's real moat isn't software — it's a 38-year-old proprietary camera network at thousands of breaks worldwide. Competitors can copy forecast models; they can't copy the physical infrastructure. The same cam tech now extends into surf-park partnerships, turning consumer infrastructure into B2B leverage.
“My understanding from reading this is that because it's an amendment to the developer agreement, that is probably per developer. So you can't opt in some of your apps, opt out some of the others. And right now the documents Apple released say it's a one-way decision.”
The new terms are likely per-developer (not per-app) and probably irreversible
Two huge structural details developers miss: the choice binds your entire account (every app you ship), and Apple's docs suggest it can't be reversed. That makes the decision tree dramatically more consequential than headline analyses suggest. Treat this as a one-way door at the developer-account level, not a per-app experiment.
“The section or like the topics that they like in the app, they're not the one that brought them in... it's like I'm driven to a certain product in an app because I think that I'm interested in this but then I end up using it for something else, but if I use that message in the ads it doesn't actually work.”
The feature that hooks the install isn't the feature that retains — split your messaging
Paired's user research showed the features users love most aren't what initially pulled them in. Testing the retention-driving messages in acquisition ads flopped. Treat acquisition copy and onboarding emphasis as separate problems — they answer to different audience moments. Don't naively port your top-retained feature into your ad hook.
“He was like 'yeah pretty much everybody else works on the website.' I was like 'oh so the app must just be some sort of add-on here.' And he was like 'no no, 95% of our sales are through the app.'”
20-person team, 1.5 devs on mobile, 95% of revenue from mobile
Charlie recounts a 20-person dev team where one and a half engineers worked on the app while the rest built the website — yet 95% of sales came through the app. Teams habitually allocate dev resources by what's easy to hire (web), not where revenue actually happens (mobile). For subscription apps, hard-prioritizing mobile is usually the obvious unlock no one takes.
“If you create really high quality content that's SEO searchable or eventually will be AI searchable the consumer will find you... then you have to convince them to do a purchase... the most passionate ones will want something more with you... that's the community and what we've seen is people that monetize those communities with subscriptions.”
The 3 Cs: content, commerce, community map directly to AARRR
Crowley's investment thesis maps cleanly to acquisition, conversion, retention. Content pulls users in via SEO and AI-search; commerce converts them with subscriptions or trials; community keeps the most passionate ones generating UGC that refills the top of the funnel. Missing any leg is a buy signal — acquire it rather than build it.
“we can try to build ML models and then use that to predict users willing to pay and then we can surface the best product they might most likely to buy”
ML predicts willingness to pay and serves each user their best-fit SKU
Like Netflix's top picks eliminating scroll paralysis, Tinder's ML dynamically matched each user to the subscription tier most likely to convert. The team replaced one universal paywall with personalized offers — the resulting revenue lift was measured in the multi-millions annually. Shawn frames this as the industry shift from stale to dynamic pricing.
“the travel mode also aka passport mode it's allowed any users to see anyone globally... that feature is a great candidate as like a unbundled feature stand alone so that's how we think about what features make sense to be unbundled”
Unbundle features that have standalone value not all users need all the time
Tinder's Passport Mode — browse profiles in any city globally — was locked in the subscription but used only when users planned to travel. The framework: if a feature has a self-contained use case with variable demand, it is a candidate for unbundling. Selling it standalone captures non-subscriber revenue without cannibalizing the core bundle.
“don't treat your users as they are logical human beings... they don't follow your user experience they don't just read everything to make decision so they are like us you know we make emotional decisions”
Design paywalls for emotional, not logical, users — they skip your features list
The most common paywall design mistake is assuming users will read a feature comparison and reason their way to a purchase. Shawn's framing: real users scan, feel, and decide in a moment. The real unlock at Tinder was not better pricing tiers — it was better decision design, structuring the choice architecture so users landed on the right product without cognitive work.