Principles
Distilled lessons from real founder journeys
Showing 138 principles in Product Strategy
Build minimal single-feature products rather than complex multi-feature apps
Start with the absolute minimum scope—one feature, one use case, one problem. Complex products take longer to build, are harder to market, and often solve problems users don't have. Single-feature apps are faster to ship, easier to explain, and simpler to iterate on.
Refine product based on customer feedback before scaling
Use early feedback to make product improvements before broad distribution
Resource constraints should drive niche focus
Overgeneralization requires huge budgets. Bootstrapped or constrained startups must niche down to compete—it's not optional, it's the only viable strategy.
Keep your team minimal to maximize margins and maintain agility
Insight from Spencer Patterson
Extract one feature from incumbent tools and make it dramatically better
Instead of building a comprehensive competitor, identify the single most painful feature in existing tools and make a standalone product that's 5x better at that one thing. Users switch for obvious improvements.
Build embarrassingly simple MVP then validate with immediate hard paywall
Ship the absolute minimum viable product - even if half-broken or ugly - then immediately test willingness to pay with a hard paywall. Give free access to early adopters for limited time to build traction, but make everyone else pay. Paying customers are the ultimate validation, not free users.
Build products so remarkable that users naturally spread the word without prompting
Design products that are inherently worth talking about. When users love the product enough to remark on it unprompted, you create organic word-of-mouth that compounds over time and reduces dependence on paid marketing or sales.
Launch with freemium model to lower barrier to entry and build large user base
Insight from Mitul Makadia
Use radical simplicity to set the market pace and force competitors to react
You can either set the pace in your market or be the one to react. By making your offering dramatically simpler, you force the market to respond to you rather than the other way around.
Products can identify real problems but still fail by providing wrong solutions
Describing a real problem accurately isn't enough—you must also provide the right solution. Problem-solution fit is as important as problem identification.
Focus on the problem first, then determine which technology enables the solution
Start with the user problem and desired outcome, then evaluate which technology best enables that solution. Don't lead with technology choices (AI, automation, etc.) before understanding the core problem.
Start as done-for-you service, then automate the proven process into software
Insight from Romàn Czerny
Tack to win. Build a fundamentally different product, not a better version of the leaders
To overtake an entrenched leader, change the definition of the market rather than compete head-on. Like sailors who tack to catch different wind, challengers succeed by building different products for the same customers, not incrementally better copies.
Resist chasing competitor features - stay true to your products character
Dont benchmark against how other companies operate.
Ship one key feature to early users and iterate in tight feedback loops
Rather than building in isolation, ship minimal functionality to early email subscribers and iterate based on their feedback. Build one feature, get reactions, improve, repeat. This prevents over-building features users don't need and keeps development focused on actual user needs.
Ship MVP quickly by repurposing code from previous projects
Insight from Mattia Pomelli
Open source plus managed hosting is a proven business model to significant recurring revenue
Insight from Jeff Atwood
Rebundle from feature to solution when enterprise buyers think in categories, not point products
Enterprise buyers managing large populations often view individual products as features within broader solutions they purchase. If your product is seen as a feature, pivot to become the solution that bundles multiple capabilities.
Enforce strict stack ranking - adding priorities requires removing others
Force explicit trade-offs on new requests.
Users want answers, not homework - simplify from DIY to done-for-you
Many products fail by making users do work (input data, configure settings, analyze results). Users facing complex decisions want recommendations they can review, not tools to do analysis themselves. 'Give them the right answers to the test' beats 'give them a calculator.' Done-for-you beats DIY.
Route support to social DMs until 10K MRR for daily user feedback flow
Instead of email support, direct support links to your Twitter/social DMs until product reaches 10K MRR. This forces daily conversations with users, creates personal connection, enables instant fixes (5-10 minutes) that create advocates. Email creates distance; DMs create relationships and learning velocity.
Build portfolio of complementary products serving same audience to maximize customer value
Instead of focusing on a single product, create multiple offerings that serve the same audience at different price points and use cases. This increases average revenue per customer and provides multiple paths to monetization from your audience asset.
Build composable systems that let customers configure 20% for differentiation in competitive markets
In supply-constrained markets where whichever company finds the talent wins, off-the-shelf software makes you a commodity. Instead of building fixed cookie-cutter features, create composable building blocks where customers start with 80-90% pre-built templates but can configure the remaining 20% to match their unique workflows and differentiators. This turns your software from a utility into their competitive advantage. The key insight: in competitive industries, companies need to stand out to attract talent/customers, and their secret sauce often lives in manual processes and spreadsheets. Giving them flexibility to encode that secret sauce into software creates stickiness and value that fixed products cannot match.
Pivot quickly through multiple experiments until you find real traction signals
Insight from Dominic Zijlstra
Evolve from selling products to selling complete business opportunities
Insight from Brandon Wong
Design for the least tech-savvy user in your target market, not the most advanced
Insight from Kevin Wagstaff
Reuse code and technical assets from past projects to accelerate time-to-market
Building multiple products in the same domain compounds your technical assets. Code libraries, UI components, and architectural patterns from previous projects can dramatically reduce time-to-market for new ventures.
Start naming with positioning work—your positioning statement generates naming candidates
Before any naming brainstorm, write a positioning statement explaining who your product is for, what it is, and what makes it different. Break this statement into nouns and verbs, then generate synonyms, antonyms, and associations for each. The name often emerges from this semantic exploration.
Pivot from sales-led to product-led growth when hitting capacity constraints
When demo volume exceeds founder capacity, pivot to self-serve rather than hiring salespeople. The bottleneck often signals that your product can sell itself with the right onboarding.
Choose a hard version of your problem to pressure-test your model and avoid over-fitting
Intentionally target a diverse segment early to stress-test your product against varied requirements. This prevents building a solution that only works for one specific use case and validates broader applicability.
Defer enterprise features to build foundational infrastructure that will last decades
Trading short-term enterprise revenue for long-term platform durability creates sustainable competitive advantage. Rebuild foundations when you see they will limit your next decade of growth, even if it means saying no to lucrative deals today.
Design content for participation and interaction rather than passive consumption
Content alone no longer has scarcity - context, intent, and interaction do. Live conversations, comments, and participatory formats retain value because machines can mirror static content but not evolving human dialogue.
When incremental experiments plateau, step back and consider a complete overhaul to reach a higher local maximum
Continuous small experiments can lead to a local maximum where further optimization yields diminishing returns. Recognizing when you've topped out on a small hill and need to descend before climbing a bigger one requires stepping back from the day-to-day experimentation mindset.
Remove authentication and use local storage to reduce friction and costs
For consumer apps, consider eliminating user accounts entirely by storing data locally on device. This removes signup friction and database costs. Data loss on device switching is rarely a concern in practice.
Maintain waitlist-only access post-launch to sustain scarcity
Keep your product behind a waitlist even after initial launch instead of opening to instant purchase. This maintains ongoing scarcity, exclusivity, and FOMO while allowing controlled growth and quality onboarding.
Build features users actually want, not just what goes viral in marketing
Use viral content to market features, but kill features that don't get used even if they performed well in content. Virality and utility are different - track actual usage and cut ruthlessly.
Make apps either highly sharable through assets or high retention through utility
Pick one: highly sharable (users share outputs/assets that contain CTAs back to app) or super high retention (utility that brings users back daily, like blocking their apps). Don't try both. Shareability drives top-of-funnel, retention drives LTV. Each requires different product architecture.
Build portfolio of apps serving same niche audience to compound marketing advantages
Instead of building disparate apps for different audiences, focus all products on one passion/niche. This creates audience overlap where users of one app become warm leads for others. Cross-selling to existing users is easier than cold marketing each time. Each product leverages shared audience, distribution channels, and domain expertise.
Design content funnels to move users one step at a time, not explain everything
Your marketing content doesn't need to explain every feature or benefit of your product. Each piece of content only needs to successfully move the user to the next step in your funnel. For apps, this means getting them from video view to app store install, not explaining the full product. Track which content drives actual conversions versus vanity metrics.
Launch with one core feature that delivers the aha moment, even if everything else is incomplete
Instead of building a complete product, focus your MVP on the single feature that creates the transformative experience users need. This core feature can remain unchanged for years because it captures the essential value. Launch with just that feature plus minimal supporting elements, knowing that design and additional features can evolve later while the core stays constant.
Build no-code versions of technical products to expand addressable market
After validating with technical users, create no-code or low-code versions of the same functionality to reach non-technical users. This dramatically expands your total addressable market without changing your core value proposition. Technical users want flexibility; non-technical users want simplicity for common use cases.
Partner 50/50 with co-makers who handle coding while you handle operations
Instead of hiring developers, find co-makers (essentially co-founders) and split ownership 50/50. You handle operations, legal, accounting, and the co-maker handles coding and support. This is more attractive than employment for talented developers because they get ownership, and it scales better than solo development. Build relationships with makers over months/years, then when you have a validated idea with presales done, pitch them to join.
Master one growth pillar completely before spreading resources across all pillars
Structure growth thinking into three distinct pillars: distribution (how users discover you), conversion (landing page to paid), and retention (how long they stay). Focus exclusively on conquering one pillar at a time rather than spreading resources across all three. Even mastering just one pillar (like distribution) can create a very profitable and valuable business. This prevents the common mistake of being mediocre at all three instead of excellent at one.
Build painkillers that solve urgent problems, not vitamins that are nice-to-have
Products that solve painful problems convert better than nice-to-have features. People actively search for pain relief and pay immediately. Vitamins (habit trackers, productivity tools) get users but struggle with monetization because users don't feel urgent need.
In boring industries, differentiate by doing the opposite of category norms
Commodity categories have established visual and operational norms that everyone follows. Deliberately break these norms to stand out. Use real people instead of models, show imperfection instead of polish, choose personality over professionalism. The goal is to be something for someone rather than everything for everyone. If you're not repelling 20% of people, you're probably too generic.
Choose high-demand, low-touch services to maximize solo leverage
Service selection determines solopreneur scalability. High-demand services command premium pricing because buyers perceive them as critical. Low-touch services deliver value in hours not days and require minimal ongoing maintenance or revisions. This combination maximizes revenue per hour worked while keeping client volume manageable for one person. Services that are high-touch (constant revisions, ongoing maintenance) or low-demand (nice-to-have) cannot support profitable solo operations.
Define specific service deliverables rather than unlimited offerings to manage margins and expectations
Productized services should specify exact outputs (e.g., 6 videos/month) rather than vague unlimited promises. This clarity helps customers understand value, helps operations plan capacity, and protects contribution margins from scope creep.
Invest disproportionate time researching your audience to deliver breakthrough value
Spending 5-20 hours researching each customer, guest, or user enables you to deliver value that surprises them. This applies to podcasters researching guests, consultants researching clients, or product builders researching users. The depth of research creates differentiation when everyone else does surface-level preparation.
Solve integration gaps that competitors leave for customers to figure out
When competitors provide partial solutions that require manual integration work, offering complete end-to-end solutions becomes a powerful differentiator. Many template/component libraries only handle the front-end, leaving developers to struggle with backend connectivity. Providing pre-integrated solutions reduces friction and commands premium pricing.
Focus on one genuinely hard problem beats building feature-complete tool that does everything mediocrely
When competitors are building broad platforms that try to do everything (no-code tools, full design-to-dev workflows, drag-and-drop everything), focus maniacally on solving one genuinely difficult problem exceptionally well. Resist the urge to add adjacent features just because competitors have them. The narrow focus lets you build depth that generalist tools cannot match, creates a technical moat, and makes your positioning crystal clear. Customers choosing between 'does everything okay' and 'does one thing exceptionally' will often choose depth over breadth when that one thing is critical to their workflow. You can always expand scope later after dominating the core problem.
Start with narrow AI use case that works today to fund expansive future vision
When building toward ambitious AI-powered future, start with narrowest use case that (1) current AI can execute well, (2) people will pay for today, (3) validates core thesis. Use revenue and learning from narrow execution to fund R&D toward bigger vision. This avoids 'build the future but starve getting there' trap. Focus on what AI can do well RIGHT NOW, not what it might do someday.
Prune profitable products to refocus all energy on your strongest offering
Counterintuitively, cutting profitable products can strengthen your business. When attention is spread across multiple products, none gets the team's full creative energy. Pruning back to one product lets you invest everything in making it exceptional.
Build a minimum delightful product instead of a minimum viable product when entering high-trust categories
In categories where trust is paramount (financial services, healthcare, legal), customers judge product quality as a proxy for reliability. Investing 12-18 months in polish, completeness, and delight before launch creates stronger first impressions and organic word-of-mouth than shipping fast and iterating. This approach requires conviction and capital but pays off in higher NPS, lower churn, and organic growth.
Rebrand when the company outgrows the original product scope to signal platform evolution
When a company expands from a single-feature tool to a comprehensive platform, rebranding signals to the market that the product has fundamentally evolved. The original name that described a narrow function becomes limiting when the platform serves multiple use cases and buyer personas. Timing the rebrand with a major funding round or product expansion amplifies the signal.
Insufficient moderation infrastructure will destroy a social platform regardless of product-market fit
Social platforms need scalable moderation from early stages, not as an afterthought when problems emerge
Build AI-native architecture rather than bolting AI onto legacy approaches
When entering markets being disrupted by AI, build AI-native from day one rather than adding AI to existing architecture. This creates fundamental advantages over incumbents.
Keep scope tight and solve one job well instead of expanding features. Appraiva focused solely on automating property discovery using street-level images + AI, resisting the urge to add complexity.
Based on experience from Arman Iranpour, Matt Aleali with Appraiva.
Switch from one-time courses to free recurring content to build audience and trust before monetizing
Insight from Chris Oliver
Invest in painful rewrites when they unlock long-term scale and capabilities
Insight from Cameron Adams
Pivot from consumer to B2B when you find product-market fit with developers
Insight from Immad Akhund
Choose boring, obvious ideas in established markets over novel concepts when you have deep domain expertise
Insight from John O'Nolan
Quality-first beats quantity-first in education businesses
Insight from Lane Wagner
Build in stealth if you need time for product-market fit without public opinion noise
Insight from Rahul Vohra
Let customers self-select their outcome to identify which converts easiest
For products serving multiple use cases, asking users their goal upfront helps identify which outcomes attract customers who convert most easily. This enables focused marketing and product investment.
Let distribution constraints drive product evolution - pivot the form factor when the core experience can't reach users
When your ideal product form (like a mobile app) creates insurmountable distribution friction, consider whether the core value can be delivered in a different format that removes that friction. The form factor is negotiable; the value proposition is not.
Apply speed tests: if users cannot complete main action quickly, it is a design problem
Use a simple benchmark: can someone finish the main action within 10 seconds of landing? If not, treat it as a design issue, not a marketing problem. This test reveals unnecessary friction that blocks users from experiencing value.
Organize teams around problems to solve, not products to build, to stay open to better solutions
When teams identify with a product name ('the Q&A team'), they become invested in that specific solution even when better alternatives emerge. Organizing around the problem ('helping celebrities engage with audiences') keeps teams flexible to pivot when research reveals superior approaches.
Map partner's existing processes before building to ensure integration fit
Understanding how your distribution partner currently operates lets you build something that fits their workflow and SOPs. This increases adoption and makes you more valuable to them.
Prioritize branding and polish even in MVP to signal professionalism
A polished UI and strong branding makes your MVP feel like a real product rather than a prototype. This affects partner perception and user willingness to pay.
Offer identical self-hosted version as zero-cost free tier for developer evaluation
Instead of a limited SaaS free tier, provide a fully-featured self-hosted version requiring users to handle deployment and OAuth setup. This filters non-paying developers while generating brand value through contributions, word-of-mouth, and SEO. Enterprise customers who need on-premise solutions become high-value support contract opportunities.
Catch emerging tool waves early by building adjacent services before competition
When a new developer tool gains traction, there's a window to build supporting services (directories, rule collections, integrations) before the market gets crowded. Being first to aggregate and organize community knowledge around a hot tool captures massive organic growth as the tool's popularity rises.
Design quality differentiates in commoditized AI-generated markets
As AI makes building websites trivial, most sites look identical and generic. Investing in distinctive, polished design becomes the primary differentiator. When functionality is commoditized, aesthetic quality and user experience become the moat.
High trial conversion with low paid conversion signals users love idea but hate execution
When users eagerly convert to free trials but don't convert to paid, they believe in the value proposition but find the actual product disappointing or too complex. This specific metric pattern (high trial, low paid) is early warning signal to stop marketing and rebuild product before scaling further.
Build reusable component library to ship apps in hours not weeks
Create library of reusable components (onboarding flows, paywalls, settings screens, authentication) that you can drag-and-drop into new apps. With 90% code reuse, you can go from idea to App Store submission in 2 hours instead of weeks. Speed compounds - each app adds components for next one.
Let App Store boost reveal winners, then double down with ads
New apps get temporary App Store visibility boost. Most will sink after boost fades. A few will stabilize or grow organically. Don't guess winners upfront - let data reveal them. Ship many MVPs, monitor which ones don't sink, then invest in polishing and paid ads for those proven winners only.
Treat simplicity as expensive separate feature requiring thousands of hours
Most founders think simplicity means doing less work. Opposite is true - making product feel effortless requires thousands of hours iterating across prototype, build, and post-release phases. Treat UX simplification as its own feature with dedicated budget and timeline. Delay feature releases to perfect simplicity even when users request features.
User experience multiplies all other metrics - onboarding, retention, conversion, referrals
UX isn't just one metric - it's multiplier affecting every funnel stage. Better UX simultaneously improves onboarding completion, user retention, sales conversion, and word-of-mouth growth. One UX improvement compounds across entire business. This makes simplicity highest-leverage investment despite being expensive.
Design onboarding for your actual usage context, not theoretical best practices
Users downloading a bus tracking app are often literally standing at a bus stop needing immediate value, not sitting at home willing to go through 20 screens of onboarding. Design your activation flow for the real physical and temporal context of first use, even if it means breaking conventional onboarding practices.
Compete on reliability and accessibility rather than technical features when entering established markets
In mature markets with existing solutions, differentiation often comes from solving operational pain points rather than adding features. If competitors' products break frequently or lack responsive support, you can win by simply being reliable and accessible. This is especially true for developer tools where downtime and poor communication frustrate users more than missing features.
Make value proposition instantly clear in headline - design polish is secondary
Landing pages with beautiful animations but unclear headlines fail to convert. If visitors don't immediately understand what your product offers from the headline, they won't scroll to learn more. Clarity beats visual sophistication.
Build one-click competitor data migration to reduce switching friction
Users hesitate to switch tools because migrating existing data is painful. Build a feature that imports competitor's data with a single click (paste URL, instant conversion). This removes the biggest switching barrier and lets prospects instantly see your product with their real data. The migration tool becomes both a conversion feature and proof of value.
Build for best-case scalability from day zero to avoid technical debt crises
Design your pricing model, infrastructure, and technical architecture assuming massive success from launch. If 100,000 users signed up tomorrow, your system should handle it without requiring a complete rebuild. This prevents the painful scenario where sudden growth forces you to rethink core decisions under pressure, creating technical debt that becomes expensive to fix later.
Make your product visually and experientially distinct instead of copying competitors
Inspired by Seth Godin's Purple Cow, resist the temptation to copy beautiful competitor websites. Instead, make your product feel totally different and unique. In crowded markets, differentiation through distinctive design and experience helps you stand out more than incremental feature additions. When users land on your site, they should immediately know it's different from everything else they've seen.
Use template-based design with minimal customization to ship faster
Don't design from scratch. Pick a clean template from design platforms (Framer, Webflow), change the font and button style, then ship. Spending 80% of effort on hero section clarity delivers more value than custom design. Templates provide professional polish without design time investment.
Tie product value directly to customer revenue metrics to associate your tool with success
When you connect your product's core value proposition to a revenue-generating metric customers care about (deals closed, meetings booked, sales made), the product becomes associated with their success rather than just another tool they pay for. This makes it stickier and easier to justify the cost.
Position on outcomes not outputs to differentiate from competitors
Reframe your offer from deliverables (outputs) to business results (outcomes). Instead of promising 'X posts per week', promise 'revenue from the channel'. This attracts higher-quality clients and makes pricing easier to justify.
Curate for quality over quantity in high-trust environments to build reputation moat
In markets where trust is critical (crypto, finance, security), aggressive curation that filters for only high-value signals differentiates you from competitors who overwhelm users with noise. Every notification or alert must be legitimate and valuable to build reputation. Competitors including too much low-quality information destroy trust even if they have more features.
Distribute existing products before manufacturing custom versions to test demand
When entering product sales, find and distribute an existing product rather than designing from scratch. This lets you validate demand, understand fulfillment, and learn customer needs before committing to custom manufacturing. Especially powerful when combined with an existing audience.
Pull-based UX beats push-based for user assistance
Surface assistance when users need it rather than interrupting them. Guide rather than interrupt, learn from actions, avoid distractions.
Expand product catalog within focused category to increase AOV and unit economics
Instead of launching unrelated products, expand within a single category (bathroom products, kitchen tools, etc.) with multiple low-priced items. Customers who buy one product often buy multiple items in the same category, dramatically increasing average order value while decreasing per-order shipping and processing costs. This strategy improves unit economics without requiring more customers.
Offer to solve customer problems manually in exchange for structured feedback calls
When customers contact you with problems your product can't solve, offer to do the work for free on a call with them. Use the call to ask detailed questions about what they like, dislike, and want from your product. This turns support requests into deep product discovery without formal user research programs.
Fix defective inventory manually when capital constraints prevent reordering
When your first inventory batch arrives defective and you have no money for replacement, find creative ways to fix products manually rather than shutting down. Even if it requires hundreds of hours of manual labor, making defective inventory sellable preserves your ability to start selling and generating revenue. This scrappy approach to quality control can save the business when perfection isn't affordable.
Build a cashflow business to fund your creative vision rather than monetizing the creative work
Instead of trying to make creative work profitable immediately, build or maintain a separate cashflowing business that funds the creative vision. This removes pressure to monetize creative work prematurely and allows focus on quality and experimentation. Treat the cashflow business as infrastructure for what you actually want to build.
Purchase and analyze competitor products to learn quality standards and structure
Instead of guessing what quality looks like, buy your competitors' products and study them systematically. This reveals structural patterns, quality benchmarks, and what customers expect. It's faster than trial-and-error and prevents launching with below-market quality.
Focus exclusively on highest-leverage revenue activities and kill everything else
Analyze which activities generate the most revenue per unit time. When one activity generates 80% of revenue while consuming only 20% of time, eliminate the other activities entirely to focus on scaling what works. This Pareto principle application prevents resource dilution.
Build operational tools that reduce supplier costs to secure premium partnerships
Creating technology that makes your business 10x easier to service for suppliers/partners creates loyalty and competitive advantage. Focus on tools that reduce their administrative burden and streamline workflows, not just customer-facing features.
Package services to address customer's end goal, not just deliverable
Instead of selling individual deliverables, bundle them into packages that solve the complete customer objective. This increases perceived value and average deal size by framing the offer around outcomes rather than outputs.
Identify the emotional outcome you sell, not just the functional feature
Users don't buy features, they buy how those features make them feel. A social skills app doesn't sell 'AI-generated conversation starters'—it sells confidence. A nutrition app doesn't sell 'barcode scanning'—it sells clear skin confidence. Framing your product around the emotional outcome helps with positioning, messaging, and understanding your true competitors.
Systemize content creation with AI and assistants to remove founder dependency
For content businesses like newsletters, blogs, or social media accounts, combining human assistants with AI tools like ChatGPT creates a content production system that doesn't require constant founder involvement. This makes the business more scalable and more valuable to potential buyers who want an asset that can run without the founder.
Diversify when your market shifts from physical to digital alternatives
If your core product category is being replaced by digital alternatives, you must either expand into the new category or find adjacent markets. Doubling down on the declining category, even if you're the market leader, leads to obsolescence. Market transitions from physical to digital (or analog to software) rarely reverse.
Design self-contained tools that function without your ongoing infrastructure
For tools meant to last or serve critical functions, architect them to work independently of your servers, services, or ongoing maintenance. Self-contained, offline-capable tools remain useful even if you shut down or disappear, which builds trust and removes dependency risks for users.
Provide experiential demos that let users verify tool behavior before commitment
For tools where trust is critical (especially security/privacy), offer interactive demos that show exactly what users and their collaborators would experience in real usage. This lets people verify behavior firsthand rather than relying on documentation or promises.
Build AI systems with traceability - require explanations for every decision not just outputs
AI that explains its reasoning reduces risk and enables iterative improvement. Add manual review gates for high-stakes decisions to maintain human oversight while automating routine cases. This prevents black-box AI problems and protects against legal, ethical, and brand risks.
Build feedback loops that compare AI predictions against actual outcomes to improve over time
Track whether AI predictions matched reality by logging actual outcomes in a feedback column. Review patterns weekly and update prompts based on misclassifications. Version prompts to separate accuracy improvements from data mix changes. This teaches the system what 'good' looks like.
Not knowing tech can be an advantage—naivety keeps you focused on outcomes instead of implementation constraints
James wasn't technical, but he looked at WordPress Multisite and thought 'I think that's got the same DNA as a SaaS product—central database, separate secure installs, user authentication.' His developer built a custom layer on top for £4,000. Technical founders would have said 'WordPress can't scale' or 'that's not the right foundation.' James just focused on the outcome: does it solve the problem? The product never creaked—not at 100 customers, not at 500, not at 1,000+. Naivety can be a superpower because you don't know what's 'impossible.' You just focus on getting to the outcome and figure out the path. Technical knowledge is valuable, but it can also create artificial constraints that prevent you from finding creative solutions.
Teach instead of build for infinite scale—shift from 'we will do it for you' to 'we will teach you how' unlocks product leverage
When a major retailer asked Cotera to build an AI solution for detecting stolen products on Poshmark, Ibby's response was: 'We are NOT going to build this for you. We will teach your team how to build it themselves.' They held a training session where the operations team built the agent together. Result: the entire ops team got excited and started building more agents on their own. The shift from 'we will build custom solutions for you' to 'we will teach you to build your own' is the difference between consulting (bounded by your time) and product (unbounded by customer capability). When you teach, customers can solve problems you didn't even know they had.
Being newer can be a technical advantage—skip legacy infrastructure and build for the future, not the past
Zapier and N8N are stuck with drag-and-drop workflow builders because that's what they built and what their customers expect. Cotera, being newer, went fully prompt-based from day one—users write what they want (like emailing a new hire) and AI figures out the workflow. This agentic approach handles ambiguous, judgment-based tasks that rigid workflows cannot. Example: 'Send Pagerduty alert if Google review mentions someone getting sick'—keyword approach either misses cases or pings constantly; AI understands intent. Being new means no technical debt, no legacy customers expecting the old interface, no sunken infrastructure costs preventing better approaches. Sometimes the best technical decision is being late enough to skip the interim solution everyone else is stuck with.
For enterprise AI, build on customer infrastructure—data gravity wins over convenience
Cotera's key differentiation from cloud-based competitors: AI agents run on top of enterprise data warehouses (Snowflake, Redshift, BigQuery). Series B+ companies don't want to send their data to third-party cloud solutions—they want AI that sits on their existing infrastructure, accesses internal data, calls LLM providers, and lands results back inside company infrastructure. Data gravity is real: enterprises have spent years building their data warehouse, setting up permissions, ensuring compliance. A product that works with that infrastructure wins over products that require data extraction. This unlocks deals that cloud-only tools cannot win—CIOs will choose 'runs on our Snowflake' over 'send data to our cloud' every time.
Filter custom deals by asking: will this integration generalize to 5+ future customers?
Custom deals and integrations can either become the blueprint for your next customer tier or hamstring your roadmap for years. The key question: does this custom work solve a problem multiple future customers will face, or is it a one-off that only benefits this deal? For Assembled, Robinhood wanted custom enterprise features. Ryan wrote a long doc to convince the team it was worth it because those features would generalize to the next tier of multi-100k customers—and they did. But a big airline wanted Microsoft Dynamics and Outlook integrations. Ryan declined because their core customers used Zendesk and Slack—that work wouldn't generalize. The filter: only say yes if the custom work stretches you toward your next customer segment. If it pulls you sideways into a different market, it's a trap. Custom work should be an investment in your future product, not a consulting project.
Dominate franchise verticals by templating entire AI workflow for specific industry
Instead of being horizontal AI agency serving all businesses, target specific franchise industries (restoration, home services, etc.) and build complete templatized workflows: industry-specific prompts, landing page templates, automation sequences, lead magnets, infographics. Approach local franchisees first to validate, then become official vendor with mother company to access entire franchise network. Scalable because same templates work for every franchisee with minimal customization.
Define your constants - the timeless customer needs that will never change
Bezos philosophy: invest in solving customer needs that will still exist in 10 years, not chasing trends. Run needs analysis to map functional, social, emotional needs across your ICPs. Rank by importance, frequency, and market size/competition. Identify 3-5 constants that will always matter. Filter all product decisions through this lens - only build features that improve your constants. This prevents shiny object syndrome and creates sustainable competitive advantage by going deeper on fundamentals.
For gift products, market to purchaser aspirations not recipient preferences
When building products primarily purchased as gifts (children's books, grooming products, etc.), your marketing must target the gift-giver's psychology, not the end user's stated preferences. Research shows surprising dynamics: women buy ~80% of men's razors, parents control all children's book purchases. This creates 'second degree aspirational' marketing where messaging is about what purchaser wants recipient to become, not what recipient currently wants. Changes entire GTM approach from user-focused to buyer-focused.
Build infrastructure for multiple revenue models simultaneously so you can flip between them
Don't just diversify revenue streams—build the full infrastructure (teams, systems, content) for each model before you need to rely on it. This enables rapid pivots when market conditions change. Create & Cultivate had podcast, membership, and e-commerce infrastructure 1-2 years before COVID, allowing them to flip from 70% events to 70% digital within months.
Live-code solutions during sales meetings to prove technical competence and speed
When selling technical products, demonstrate your ability to solve problems in real-time during demos by fixing issues or building features on the spot. This creates 'magical moments' that prove you can move faster than internal teams and overcomes the 'we can build it ourselves' objection.
Build every customer-requested feature to be generalizable across your entire user base
When building features in response to individual customer requests, design them as general-purpose capabilities that serve many customers rather than one-off customizations. This turns every customer interaction into a product improvement for all users.
Use frequent product updates as the primary growth driver instead of marketing campaigns
When product improvements directly correlate with subscriber increases, investing in rapid iteration delivers better ROI than marketing spend. Each noticeable update acts as its own marketing event by re-engaging existing users and converting free users to paid.
Turn down misaligned revenue early to protect product vision and team morale
When early customers offer significant revenue for work that doesn't align with your core mission, rejecting it protects long-term product coherence. Accepting off-mission work creates precedent and dilutes focus. The discipline to say no when cash-poor is a signal of conviction.
Structure portfolio with free traffic-driving products that funnel users to premium revenue generators
Build a portfolio where some products exist solely to generate traffic and build trust, while others are the premium revenue generators. Free products serve as acquisition channels - directories, open-source tools, and free utilities attract users who then discover and adopt paid products through native cross-promotion and integrations.
Act as the AI manually until data volume justifies automation
When building AI-powered products, founders can manually perform the work the AI will eventually do. This generates training data, reveals edge cases, builds customer relationships, and validates that the automated version will deliver real value. The transition from manual to automated is gradual and data-driven.
Write your product manifesto publicly before building to create alignment between vision and market demand
Publishing your product principles as a public essay before building creates two powerful effects: it validates developer/user interest in your thesis, and it becomes a permanent architectural north star that guides years of product decisions without requiring rewrites.
Add deliberate friction as a feature when your users want to be restricted from their own behavior
For products targeting self-control and behavior change, making the product harder to bypass is the core value proposition. Deliberately engineer friction that prevents users from easily disabling restrictions they set for themselves. This inverts the typical UX principle of removing friction — for self-restriction tools, difficulty IS the feature.
Design content for founder self-service submission using structured templates that guide non-writers to produce publishable content
Instead of conducting expensive interviews or hiring writers, create structured Q&A templates with sub-questions and prompts that guide anyone to write compelling content. This shifts production cost from the platform to the subject, enabling massive content scaling while maintaining quality through guided structure rather than editorial oversight.
Build features that unlock new customer segments rather than adding capabilities for existing users
Product features should serve as market expansion tools, not just functionality additions. Each major feature investment should open access to a new customer segment or price tier. Compliance certifications (SOC 2, HIPAA) unlock enterprise buyers. Bulk sending unlocks operations teams. API access unlocks developers. Evaluate features by asking 'what new market does this open?' rather than 'what do current users want?'
Build the context layer for AI tools rather than another AI tool itself
When an ecosystem of AI tools is exploding, build the infrastructure that makes all of them work better rather than competing as another tool. The documentation/context input layer has unique defensibility because it integrates with every tool in the ecosystem.
Radical niche reduction during a growth plateau can be the catalyst that unlocks explosive growth
When growth stalls, the counterintuitive move of dramatically narrowing your product scope - eliminating courses, features, or offerings that don't serve a hyper-specific niche - can accelerate growth faster than adding more. Narrowing makes positioning clearer, community building easier, and word-of-mouth more effective.
Position compliance as growth-enabling rather than risk-reducing to align with founder priorities
Instead of selling security through fear of breaches, frame compliance as a tool that unlocks enterprise deals, new markets (healthcare, government), and faster sales cycles. Founders care more about growth than risk avoidance, so positioning compliance as a competitive advantage rather than a cost center dramatically changes the buying conversation.
Productize a service by constraining delivery to sequential single-task execution with fixed turnaround times
Transform a traditional service into a scalable productized offering by enforcing strict delivery constraints: one task at a time, fixed turnaround window, async-only communication. These constraints that appear to limit value actually enable solo operators to serve many concurrent clients by preventing work from piling up and eliminating context-switching overhead.
Build native OS integrations that work everywhere rather than another standalone app
Instead of building yet another app users must switch to, integrate your tool at the OS level so it works within every application the user already uses. This eliminates context switching and makes your tool feel like a superpower rather than another tab to manage.
Add intentional friction to AI output to increase user engagement and conversion
Counterintuitively, adding deliberate delays or friction before showing AI-generated suggestions forces users to engage more actively with the content. This prevents passive acceptance of AI text and makes users feel like active participants in the writing process, which increases both quality and conversion rates.
Reduce integration time by orders of magnitude to remove the primary adoption barrier for infrastructure products
For API/infrastructure products, the biggest competitor is not another vendor but the customer building in-house. Continuously compress integration time (from years to weeks to hours) to make the build-vs-buy decision increasingly obvious. Each reduction in integration friction expands your addressable market.
Use a successful but unscalable product as a data-collection vehicle to power a venture-scale AI product
A smaller product that aggregates proprietary data over years can become the foundation for a dramatically more valuable AI-powered product. The first product's primary value shifts from its own revenue to the data asset it creates. When combined with emerging AI capabilities, this curated data becomes an unfair advantage that competitors cannot quickly replicate.
Use human operators to simulate AI capabilities while building automation, progressively replacing manual work
Start with humans doing the work your AI/automation will eventually do. This lets you serve customers immediately, learn what to automate, and ensure quality while building. Progressively replace manual steps with automation as each is proven. Only accept customers whose needs match your current automation level.
80% annual retention indicates exceptional product value
Insight from Buster Benson
Mac app customers expect lifetime deal options alongside subscriptions due to platform conventions
Insight from Aayush
Say no to deals that don't align with your future vision, even if lucrative
Insight from David Cramer
Autopilot blog management: customers pay subscription and get posts uploaded to their blog without lifting a finger. Simplicity of "set it and forget it" appealed to busy founders.
Based on experience from Mat Sherman with PubLoft.
Build value ladder with low-friction entry points that drive conversions to core product
Insight from Dominic Zijlstra
Focus on engagement metrics over completion rates to differentiate and justify premium pricing
Insight from Gagan Biyani