Principles
Distilled lessons from real founder journeys
Showing 127 principles in Validation
Build for your own acute pain point
When you experience a problem intensely yourself, you can validate faster and make simpler product decisions. Being your own target user simplifies decisions to 'do we like it and would we use it?'
Validate demand manually before building expensive automation
Insight from Krish Ramineni
Organic growth and emotional reactions indicate true product-market fit
PMF means you wake up with more users and don't know where they came from. Customers should viscerally react positively, not just say 'seems useful' with no emotion. If you're still hustling for every user or getting polite but unemotional responses, you may not have PMF yet.
Social validation doesn't equal product demand—viral engagement doesn't guarantee conversions
Insight from Mattia Pomelli
Offer services first to validate SaaS demand and understand the market
Before building a product, offer consulting or services in the same space to validate demand, understand pain points deeply, and generate revenue while learning. Service clients often become early product customers.
Product-market fit should feel like 'pulling a rope, not pushing a rope' - customers urgently wanting what you build
Insight from Tomer London
True validation requires risking rejection—diluted validation avoids the moment someone must commit or say no
Most founders don't actually skip validation—they do a safe, diluted version that avoids real rejection. The barrier isn't lack of research methods but fear of hearing 'no'. Surveys, friend feedback, and passive research feel like validation but avoid the hard moment of asking for commitment.
Listen for repeated pain points in customer conversations - pivot when you hear the same problem multiple times
When customers or prospects keep mentioning the same problem (security, speed, compliance), that's market pull. Pivot toward what the market is asking for rather than pushing what you planned to build.
Search community chat history to identify recurring pain points before building anything
Discord and Slack communities contain searchable conversations revealing what users struggle with most. Copy days or weeks of chat history into an LLM with the prompt 'list all pain points discussed' to identify recurring themes. The most common complaints signal the strongest demand.
Clone and improve proven apps rather than validate demand from scratch
Instead of validating an unproven idea, find a successful app and build a substantially better version. Analyze their design, features, and distribution, then execute better on all three. This transfers PMF risk to execution risk.
Compress MVP timeline to days/weeks using shortcuts to test 10x more ideas
With 90% failure rate, building each MVP in months/year means 9+ years to find winner. Use no-code, boilerplates, compromise code quality to compress builds to days/weeks. Ship new product every week. 10x iteration speed beats 10x product quality when failure rate is 90%.
Conduct 50-100+ customer conversations before building
Extensive upfront research prevents building the wrong product. Spend 1-3 months on user research and customer conversations before writing code. For hard problems, lawyers and investors offer surprisingly useful 30-min calls for free.
Build products to solve your own recurring problems - personal pain validates the need
Based on experience from Samuel Abebe with SpeakerSplit.
Dogfood your product daily to be your own use case for validation
Running your own operations on your product reveals flaws faster than user feedback. You feel the pain immediately and can iterate rapidly.
Invest as much effort in choosing what to work on as in the actual execution
Problem selection is a bigger determinant of outcome than effort. Working hard on the wrong problem yields worse results than average work on the right problem. Market forces are more powerful than individual effort - being at odds with larger trends means getting steamrolled regardless of execution quality.
Validate through rapid experimentation rather than searching for the perfect idea
Insight from Eugene Zolotarenko
Build the tool you wish existed after experiencing the pain yourself
Personal frustration with existing solutions validates the problem exists and gives you conviction to build. You become your own first customer and can test whether the solution actually solves the bottleneck.
Presell to 5+ customers at steep discount before building to validate willingness to pay
After generating waitlist interest, offer a 90% discount presale to all subscribers. If you can get 5 paying customers before building anything, you have validated that people will pay for the solution, not just express interest. This separates real demand from curiosity.
Build something you personally need and use daily before monetizing
Insight from Buster Benson
Validate product concepts by posting direct questions to target communities before building
Instead of building first, post your concept with a direct question ('too aggressive?', 'would you use this?') to communities where your target users hang out. The discussion reveals both interest level and critical feedback that shapes product decisions.
Research keywords with popularity >20 and difficulty <60 before building
For app store products, keyword research predicts discoverability. Target keywords with meaningful search volume (>20 popularity) but achievable competition (<60 difficulty) to validate demand before writing code.
Pre-sell with money-back guarantee before building to validate payment willingness
Only validation that matters is collecting money. Friends saying they'd pay is dangerous validation. Pre-sell licenses with tiered pricing for FOMO, offer full money-back guarantee during build and after delivery. This proves real willingness to pay before investing months building.
Build audience with free content for 6-12 months before monetizing to validate demand and create launch base
After validating that people want your solution (initial interest, messages, consulting requests), spend 6-12 months building an engaged audience through free content before asking them to pay. This approach validates that you can consistently attract your target audience, builds trust and expertise, and creates a launch base of pre-qualified prospects. You de-risk the product investment by proving distribution works first.
Deliver solution manually before coding to iterate without technical constraints
After getting presales, deliver the solution as a service manually instead of building a product. Iterate on what customers need by changing your own service routine rather than rewriting code. Once you find the sweet spot where customers are satisfied, then build the product. This separates finding product-market fit (through service) from building the product (engineering).
Build community before product to validate demand through engagement
Creating a community around a topic before building the product de-risks development and ensures you're solving real problems. By building audience and engaging with them first, you understand their needs deeply and can validate demand before writing code. When you do launch, you have built-in distribution to customers who already trust you.
Live in your target market as a customer/practitioner before building - deep immersion reveals real problems
Insight from Gagan Biyani
Read competitor app reviews like user interviews - patterns in complaints show gaps
Insight from Connor Burd
Extended beta periods help refine complex products
For complex B2B products, extended beta testing reduces post-launch churn. Listen to early users and improve the product before public launch.
Use cold email open rate to validate problem resonance and click rate to validate pitch quality
Cold email metrics can serve as diagnostic signals for rapid validation. High open rates indicate your subject line and problem framing resonates with the audience. Click rates indicate whether your pitch and solution communicate value. Separate these signals to iterate on the right element.
Validate that your differentiation creates switching costs, not just incremental convenience
Feature-based differentiation in commodity markets often fails because incumbents can easily add the same features. True differentiation must create reasons why users cannot or would not want to switch back.
Build products iteratively to learn unfamiliar markets - each pivot reveals constraints research cannot
When entering a market you don't understand, treat product building as a learning mechanism. Each version you ship and each pivot you make reveals market dynamics, buyer constraints, and incentive structures that desk research alone cannot uncover.
Test whether early wins generalize beyond your network before assuming product-market fit
Early customers won through warm network connections or credibility signals (notable investors, board members) may not indicate true product-market fit. Validate that wins would occur with customers who have no connection to you.
Pitch strangers instead of friends to get unbiased validation signals
Cold email strangers in your ICP - if you are truly solving a pain point strangers will invest their time.
Use pre-mortem black hat technique to surface hidden assumptions before investing months in execution
At program kickoff, ask: Assume it is one year from now and we have failed. What went wrong? This uncovers 5-10 major assumptions.
Decide to double down or move on after weeks not months - build feedback loop, not patience test
After shipping and getting early feedback, make an explicit decision in weeks (not months): if product shows traction, double down; if flat, move to next idea without guilt. The goal is learning fast, not proving you can endure. Every project teaches something even when it fails. This requires building small enough that weeks of feedback are meaningful.
Create fake product demo videos to validate viral demand before writing code
For consumer apps, create a video showcasing the value your app would provide using stock footage, AI demos, or mockups. Post it on platforms like TikTok to test if the concept resonates. Hundreds of comments requesting you build it proves demand exists before any development investment.
Validate business model through work experience before building product
Gain pattern recognition by working at or consulting for companies using the business model you want to replicate. Spending years seeing what works across multiple companies provides validation and playbook knowledge that de-risks your own product. Observe market timing signals like increasing company adoption of the model.
Mine social platform comments to find problems people openly discuss
Instead of guessing at problems, study comment sections on high-traffic social content in your target niche. People openly discuss their frustrations, questions, and needs in comments. Patterns in what people repeatedly ask for reveal validated demand before you build anything.
ASO-first validation: check keyword metrics and competitor revenue before building
Before writing code, validate market size using ASO tools. Check keyword popularity (20%+) and difficulty (60-70%). Verify top competitors make real revenue (€100-200/month minimum). If competitors can't monetize, market too small - don't build. This prevents wasting weeks on apps nobody will pay for.
Give SEO validation 'time to incubate' - serious buyers searching for solutions are worth the wait
When validating via SEO, resist the urge to abandon the strategy if you don't see immediate results. SEO-driven validation takes longer than other channels but delivers higher-quality buyers because they are actively searching for solutions to their problems. These are 'serious buyers' with intent, not casual browsers. Build your landing page, optimize for the right keywords, submit to Search Console, then give it weeks or months to incubate rather than days. The delay filters for genuine demand - if people are searching and finding you organically, that's stronger validation than virality or paid ads.
Research viral content in your niche before creating to validate format resonance
Before creating any content for your product, spend dedicated time researching what's already going viral in your target market. Analyze the hooks, storylines, and calls to action of the most successful content to understand what resonates with your audience. This validates your content approach before you invest time creating.
Paying customers provide more valuable feedback than free users because financial investment creates accountability
Free users will consume your product and ghost you when something breaks. Paying customers (even at discounted LTD prices) are financially invested and will provide brutal, specific feedback about what's broken. They tell you exactly what needs to be fixed rather than silently churning. This is especially true for lifetime deal customers who paid upfront - they're motivated to see the product improve since they can't get refunds.
Validate demand on distribution platform before building product
Research your intended distribution channel to confirm both market demand and content virality before writing code. If competitors have viral content on the platform, this proves two things: people want the product category AND content about it spreads on this channel. This de-risks both product-market fit and go-to-market strategy simultaneously.
Test positioning changes on sales calls first before updating all marketing materials
When repositioning your product, validate the new messaging in live sales conversations before committing to website redesigns and content overhauls. Sales calls provide immediate feedback on clarity, customer understanding, and conversion impact. If the new positioning leads to shorter calls with higher close rates, you have validation to expand the change.
Verify competitors exist before building - no competition signals no market
Finding competitors validates that a market exists and people will pay for solutions. No competitors usually means no market demand, not an untapped opportunity. Creating entirely new markets is extremely difficult.
Mine online communities with advanced search queries to extract authentic customer language
Use platform-specific search syntax to filter for problem-focused discussions in target communities. Extract exact quotes and pain point patterns to ensure your marketing speaks in customer language from day one. This creates product-market language fit before you've built anything.
Monitor audience questions and requests to identify products they will pay for
Your existing audience tells you what to build through their repeated questions and requests. When the same product or solution comes up consistently in comments, DMs, or conversations, that's demand validation without surveys or interviews. This signal is especially strong when you already have their attention through content or community.
Publish content to validate audience demand before building complex infrastructure
Instead of building product features first, create and publish content that addresses your target market's questions. Audience growth and engagement validate demand before you invest in product development. Content-first approach de-risks the investment and provides customer insights.
Practice your new identity daily while employed to validate the shift before quitting
Before making a major career change, establish a daily practice in your new direction while still employed. This validates both your sustained interest and your ability to perform the work, reducing risk and building evidence of commitment.
Unit economics that remain broken after pivots signal fundamental market mismatch
When conversion rates or other key unit economics remain poor despite business model pivots, it often indicates a fundamental market readiness or fit problem rather than just execution issues. Low conversion metrics (like 20%) that persist across different approaches suggest the market isn't ready for your solution, regardless of how you package it.
Use your first product to discover the real pain, not to solve it
Early products often fail commercially but succeed as discovery tools. Don't judge your first product solely by revenue—judge it by what you learned about the real problem. TeamBridge's initial scheduling tool generated almost no revenue for 2 years, but it revealed that connective tissue (automations, workflows) mattered more than core scheduling features. The first product's job is to get you close enough to customers to uncover the truth. Once you discover the real pain, you may need to throw out the original product entirely. This is success, not failure—validation is learning what to build, not building what you initially imagined.
Validate ICP budget through interviews before building—if they have no budget, pivot to where money is
Having a real problem isn't enough—your ICP must have budget to solve it. Many startups waste months building for users who love the solution but cannot pay for it. The validation process should explicitly ask about budget authority and purchasing power, not just pain level. If you discover your initial ICP has no budget (like customer success managers often don't), immediately pivot to the department or role where budget exists for that category of solution (like marketing for customer communication tools). Budget location drives ICP definition more than problem severity.
Build lead magnets as functional tools that showcase your product's core value
Instead of generic PDFs or checklists, create interactive calculators or tools that both capture leads AND demonstrate your product's actual capability. The lead magnet should be a simplified version of your core value prop, not just educational content. This validates demand while building trust in your ability to solve the problem.
Pivot quickly when you realize an internal tool is more valuable than your core product
When an internal tool or side feature generates more enthusiasm than your main product, recognize this as a pivot signal and act on it quickly. The market is telling you what it actually wants.
Customers signing up for free trials but not caring about results indicates the problem isn't burning enough
Insight from Rob Picard
De-risk new ventures by acquiring and refactoring existing products rather than building from scratch
Insight from Vedran Rasic
Build revenue projections with real market data to stress-test business model viability before committing
After collecting real-world data on sales cycle length and revenue per customer, build financial projections to see how long it takes to break even. If the timeline is unreasonable (e.g., 10 years), this is a clear signal to pivot before investing more resources.
Treat investor appetite vs skepticism for your idea as meaningful signal
When pitching investors, pay attention to the contrast between ideas that receive appetite versus skepticism. This differential signal is valuable data about market perception. Founders often dismiss rejection, but informed investors who tell you no are worth listening to.
Test ICP hypotheses through direct outreach and abandon them quickly when they fail
Start with a specific ICP hypothesis rather than throwing spaghetti at the wall. Test it through direct outreach (cold emails to LinkedIn groups, forums, etc.). When the hypothesis fails—low response rates, negative feedback—abandon it immediately and test the next hypothesis.
Write product principles publicly before building to create a blueprint for development
Document your product's core principles in public content before writing code. This creates a blueprint to build against and sets high standards. The principles become your direction when making difficult tradeoffs.
Launch with features you need yourself rather than waiting to collect feedback—if you need it, users likely do too
When dogfooding reveals you need a feature now, ship it rather than waiting to validate through user feedback. Your own urgent need is validation. Collecting feedback first adds delay when you already have evidence from your own usage.
Ideas may need multiple attempts and full commitment to succeed—failed side projects can become successful when prioritized
Some ideas fail as side projects but succeed with full commitment. Two failed launches don't mean the idea is wrong—they may mean the timing or commitment level wasn't right. Making it a priority with dedicated resources can unlock success.
When customers have abandoned a category entirely, you compete against perception not brands
In categories where poor products have driven customers away, your marketing challenge is rehabilitating category perception before selling product benefits. Address the 'I gave up on this' mentality first.
Map prospects across multiple dimensions in a spreadsheet to identify ICP patterns
After customer conversations, systematically track prospects across 5-7 dimensions (company size, stage, industry, buyer persona, current solution). Look for patterns in who gets excited about your product to define a precise, multi-dimensional ICP.
Use your most demanding customer as the quality bar before launch
Set your launch quality threshold at satisfying your most demanding potential customer. This forces production-grade quality and provides immediate social proof that attracts serious users.
Prototype with potential co-founders for months to test working compatibility before committing
Real collaboration on prototypes reveals working styles and compatibility better than conversations alone. Most co-founder breakups happen during this ideation phase when incompatibilities surface.
Use structured questionnaires filled out independently to surface co-founder misalignments
Filling out compatibility questionnaires separately then comparing prevents groupthink and surfaces true differences on critical topics like equity, fundraising philosophy, and working styles.
Define and test the atomic unit of your idea before building the full product
Break your idea down to its smallest testable unit and test that specific thing with your riskiest assumption.
Create marketing vignettes instead of prototypes to test sales and positioning
Build pitch decks that look like pared-down sales landing pages with feature bullet points to test concepts without building.
Pursue ideas that seem bad to others but good to you for less competition
High skepticism from others often indicates an underserved market with less competition.
Ask founders which idea they would start rather than asking customers if they would buy
Fellow founders have high empathy across personas and understand market evolution.
Share API specs with developers before building to reveal gaps
Share specs with users before implementation.
Remove account creation to validate demand faster - signup overhead delays learning
When launching a new product, account creation adds friction that slows down validation. Pay-per-use or pay-per-transaction models let users experience value immediately without signup overhead. This accelerates learning about whether users will actually pay.
Measure customer problem importance against solution satisfaction to find underserved opportunities
Survey your target market on two dimensions for each outcome they care about: how important is this outcome (1-10) and how satisfied are they with current solutions (1-10). The sweet spot is high importance combined with low satisfaction - these are your underserved opportunities where existing tools fail customers.
Screen-share silently in voice chats to gauge organic interest without pitching
Join voice calls in target communities, mute your microphone, and share your screen while using your MVP or prototype. Don't pitch or explain—just use it. If people get curious and ask 'what are you using?', that's genuine interest. If they ignore it, you haven't found product-market fit yet.
Validate willingness to pay separately from product-market fit using free users
Getting users to use a free product validates it works, but doesn't validate they'll pay. After proving product value with free users, add paid subscription and immediately test paid ads.
Build multiple small tools simultaneously and share publicly to see which resonates
Instead of betting months on one idea, build 4-5 small tools in one week and share them publicly while building. The market will tell you which one people care about through engagement, questions, and interest. This rapid parallel testing reveals product-market fit faster than sequential building.
Use social platforms as idea battlegrounds to validate before building
Post content expressing your product idea on social platforms as if it already exists. If the content explaining the concept goes viral, you've validated demand without building anything. Only invest in development after content proves people care about the problem and solution.
Stop marketing when product is broken to avoid corrupting your data
When analytics reveal fundamental product problems, continuing to spend on marketing wastes money and corrupts your data about what works. Better to shut down acquisition entirely, rebuild the product right, then restart marketing with clean metrics. Marketing spend on broken product teaches you nothing useful.
Build validated-but-poorly-executed ideas, not completely novel ones
Don't validate brand new ideas from scratch - it's expensive and risky. Instead, find ideas validated by competitors but poorly executed. Someone else proves demand exists, you win through superior execution and simplicity. Novel-but-validated beats completely-novel or completely-saturated.
Validate markets through geographic arbitrage - find successful products in one language/region and test parallel demand in underserved geographies
Instead of validating an unproven idea from scratch, identify successful products in established markets (like English-language apps) and validate parallel demand in underserved geographies using trend analysis and social proof. This transfers market risk from 'does anyone want this?' to 'do people in THIS market want this?' - a much lower-risk question. Use tools like Google Trends for keyword validation and social platforms to confirm organic conversation exists in the target market.
Study businesses for sale to find validated ideas with proven revenue and known distribution
Business marketplaces like Micro Acquire, Flippa, and Empire Flippers list real companies with verified revenue, customer counts, and acquisition channels. By filtering for profitable SaaS businesses in your domain, you can identify validated markets and proven distribution strategies before building anything. This de-risks product development by showing concrete evidence of demand.
Validate B2B ideas through job experience, not online research - business owners don't hang out where indie hackers do
The best source of B2B product ideas is direct exposure to business processes through employment, not browsing Reddit or online communities where indie hackers congregate. Business owners and decision-makers don't spend time in those spaces, so you won't discover their real pain points there. Having a job (or having had one) gives you insider knowledge of actual workflows, frustrations, and processes that businesses will pay to solve. This domain expertise is an 'absolute advantage' over builders who have never worked in a business because they don't understand what happens day-to-day.
Search social platforms for '[Tool] alternative' to discover systematic gaps in market leaders
Users actively searching for alternatives publicly discuss specific pain points competitors aren't solving. Search Twitter, Reddit, and product forums for '[Popular Tool] alternative' keywords to surface recurring feature gaps, pricing complaints, and unmet needs. This reveals validated demand beyond just price dissatisfaction—users detail exact features they want.
Reach out to alternative-seekers with landing page before building product to validate interest
Users publicly searching for alternatives are high-intent prospects. After identifying them through social listening, reach out with a basic landing page explaining your solution before building the full product. Messaging is critical—clearly articulate how you fill the gaps they're complaining about. Email signups or direct responses validate demand before development investment.
Test messaging in low-risk comment threads before high-visibility posts
Start engagement in existing thread comments rather than creating top-level posts. Comments have fewer eyeballs, are less permanent, and allow you to test if your messaging resonates with lower stakes. Once you see traction in comments and understand what works, graduate to top-level posts with confidence.
Identify paid manual tasks that emerging AI can automate, then time entry when technology becomes viable
Look for tasks people currently pay for that require significant manual effort, then track AI development to predict when automation becomes feasible. This lets you enter markets just as technology enables dramatic improvement over manual processes, capturing demand from existing paid solutions.
Build quiz-based waiting lists to validate demand while collecting qualification data
Instead of simple email signup forms, offer early access in exchange for answering questions about pain points and use cases. This validates that people will invest time, provides customer research data, and qualifies your waitlist. Set a numerical threshold (e.g., 100 qualified signups) before investing in development.
Validate product-channel fit before building - ensure your product can spark interest in your chosen distribution format
Different distribution channels require different product characteristics. TikTok requires products that can be explained and create desire in 10 seconds and are compulsive buys, not considered purchases. Before building, validate that your product's inherent characteristics (cheap, funny, controversial, visual) match the requirements of your primary distribution channel.
Share valuable knowledge freely, then productize if demand signal is overwhelming
When you share expertise through lightweight formats (videos, threads, docs) and receive strong positive signals that it's extremely valuable, consider packaging it as a paid product. The validation comes from the intense positive reaction, not from pre-planned monetization. This works because you're solving a proven pain point with content you've already created.
Triangulate demand validation across revenue tools, trend data, and viral content platforms
Don't rely on a single validation source. Cross-reference revenue estimation tools (like Sensor Tower), trend data (Google Trends), and content virality (TikTok/social) to confirm both market size and distribution channel viability. If all three signals align, you've de-risked the opportunity significantly.
Manually test competitor tools to validate technical feasibility before building
Before investing in product development, manually use and test existing solutions (especially technical ones like AI models or APIs) to understand if your approach is technically viable. Days or weeks of manual testing can validate whether the core mechanism works before you write code.
Design business model before choosing product to ensure founder-market fit
Instead of starting with a problem or product idea, first design the business model that fits your skills, resources, and desired lifestyle. Then choose a product that fits that model. This approach prioritizes founder-market fit (matching the business to your strengths) over traditional problem-solution fit, reducing execution risk.
Validate technical feasibility by showing samples to manufacturers before committing capital
Before investing in inventory or product development, confirm the product can actually be manufactured at scale. Take sample products to manufacturers and ask if they can make it. A manufacturer's 'yes' validates technical feasibility and gives you confidence to invest savings. This de-risks the production side of product-market fit.
Use incremental format testing to validate content before scaling production
Test demand incrementally by expanding format complexity only when the previous stage shows traction. Start with the smallest possible format (tweet), then expand to longer formats (thread, newsletter, video) only if engagement validates demand. This applies to both content and business validation.
Call every customer when sales drop to diagnose problems rather than guessing
When facing business crisis or sudden sales drops, systematically contact all customers to understand why behavior changed. Direct conversations reveal true problems that data alone cannot show. This works because customers often love your product but face specific situational issues (seasonality, compatibility, etc.) that prevent usage.
Match service offerings to what your partner is already known for teaching
When partnering with experts or creators, validate demand by aligning the service with their existing authority. If they teach something to thousands of people, those learners become natural customers for a done-for-you version of that skill.
Study successful incumbents' revenue and operations to validate market size before building
Meeting with established players in your target market reveals whether the opportunity is big enough to pursue. Understanding their revenue, customer volume, and operational simplicity helps you assess if you can build a competitive alternative with your unique advantage (like AI).
Ship early prototype to friends and watch for genuine excitement
Friends and family are often polite about your projects. But when they care about something you built for the first time—asking to use it, showing it to others, bringing it up unprompted—that's a strong signal you're onto something real. This authentic interest from people who know you is different from polite support.
Embed yourself with your first customer by living and working with them
To truly understand what your customer does and build the right product, you need extreme immersion—not just interviews or site visits, but actually living with them, working from their office, and being 'so in it' that you experience their workflow firsthand. This level of embedding reveals problems and nuances that no amount of user research can uncover. The investment in deep customer understanding early pays off in building exactly what they need.
Test competitor claims to discover what they're faking—reveals genuine technical opportunities
When you discover a potential product opportunity, test existing competitors claiming to solve it. Many products fake hard-to-solve features with workarounds (template swapping, manual processes behind the scenes, simplified versions) because the real technical challenge is too difficult. By actually using competitor products and probing their limitations, you can discover which claims are fake and which problems are genuinely unsolved. This reveals market opportunities where demand exists but real solutions don't. The technical difficulty that prevents competitors from solving it properly becomes your moat if you can crack it.
Buy credibility through strategic equity trades when you're an outsider in an industry
When James entered the accounting industry as a non-accountant consultant, he traded 10% of GoProposal for 10% of a respected accounting firm. This instantly solved his credibility problem—he could now speak as a vendor, a business owner, and as a director of an accounting firm. He had insider status and could speak to both sides of every issue. Strategic equity trades with established players in your target industry can buy you years of credibility-building in a single transaction. You're not just getting their brand association—you're getting their network, their insights, and the ability to speak from inside the industry.
Launch with audience, not just product—create content asset that builds waitlist while MVP is being built
While GoProposal's £4,000 MVP was being built (3-month timeline), James wrote and published 'Selling to Serve' in two weeks. The book was the recipe book for how to do what his software enabled—how to price and sell accounting services more effectively. He made it an Amazon bestseller and used it to drive people to a waitlist. By the time the product launched, he had hundreds of people ready to try it and had established himself as the thought leader in the space. The book was a better lead generation asset than any ad campaign could be. Most founders wait until the product is done to start marketing. Better approach: create a content asset (book, course, video series) that solves part of the problem and builds your audience while you build.
Early revenue can be a local maxima—recognize when you're succeeding at the wrong thing before it's too late to pivot
Ibby hit $150K ARR over 18 months and it felt like validation. But customers weren't logging in—they'd ask questions, get answers, disappear. Analytics dashboards lack stickiness because once you answer the question, the job is done. The revenue created a false sense of security and made pivoting psychologically harder because they had customers, employees, salaries, and momentum to protect. The local maxima trap: you're succeeding enough to feel validated, but not enough to actually win. You're stuck in a position that's better than zero but worse than what you could build. Having some success makes it harder to make necessary changes than having no success at all.
Watch for the 100-lines-of-code moment—when simple new technology replaces your complex solution, pivot immediately
A customer asked Cotera to extract topics from support tickets. Ibby built a data science solution using gigabytes of custom infrastructure—it was slow, clunky, bloated. His co-founder tried the newly released OpenAI API and solved the same problem with 100 lines of code—better, faster, more elegant. That was the wake-up call: when new technology makes your entire stack obsolete overnight, everything is about to change. Technology shifts create opportunities to leapfrog incumbents, but only if you recognize them and move. If 100 lines of API code can replace gigabytes of your custom infrastructure, you're solving the problem the hard way and someone else will solve it the easy way.
Fire customers to force product focus—revenue prevents necessary changes, so cut it to build what you need
When Ibby pivoted from customer analytics to AI agents, he deliberately fired consulting-heavy customers. Having those customers created inertia—the temptation to keep serving them, doing custom work, making money the old way. But keeping them would prevent building the real product. Revenue is supposed to be a good signal, but when it comes from the wrong business model, it's an anchor preventing you from swimming to where you need to go. Firing customers is counterintuitive and scary, but sometimes it's the only way to force yourself to build what actually needs to exist rather than what currently pays the bills.
When users tolerate painful onboarding, you've found real demand worth pursuing aggressively
Most advice says optimize onboarding to reduce friction and increase conversion. But sometimes painful friction is a feature, not a bug—it proves demand strength. If users are willing to jump through hoops (manual multi-step installs, copying tokens, complicated setup), you've validated that the value proposition is strong enough to justify the pain. This signal is more valuable than easy signups with high churn. In mobile apps, each additional step typically causes 80% drop-off, so if you're seeing high completion rates on painful flows, you've found something people desperately want. Don't optimize the onboarding yet—focus on building more of what they came for.
When different customers show you identical workarounds, you've found universal pain worth solving
The strongest product-market fit signal isn't customers saying they have a problem—it's independently inventing the same messy solution without knowing others did too. When you find yourself across Stripe, Casper, Grammarly, and GoFundMe and they all show you a color-coded spreadsheet (different colors, different week starts, but identical structure), you've discovered a universal pain point hiding in plain sight. This is more valuable than survey data because it proves: (1) the pain is real enough they built something, (2) the solution is non-obvious enough existing tools don't solve it, (3) it generalizes across different scales and industries. Look for organic convergent solutions—they reveal the shape of the real problem better than any customer interview.
Use humans to do AI's work as pre-launch validation
Before building AI/automation features, have humans manually perform those tasks for early customers. This validates that (1) customers will pay for the outcome, (2) the work can be done reliably, (3) you understand all edge cases and data requirements. Document what context, data, and judgment the humans use - this becomes your AI training ground. Better than building AI in vacuum and discovering it doesn't work. Creates hybrid model where humans bridge gaps while you automate incrementally.
Use thesis-driven outreach with specific hypotheses about target customer problems
Before reaching out to prospects, build specific hypotheses about what problems they likely face based on their business model. Frame outreach as 'comparing notes' on a shared problem rather than selling. This demonstrates domain expertise and makes conversations educational rather than transactional.
Pressure-test products hands-on against competitors before committing
Install your product and competitors products in a real production environment. Break things deliberately. Test whether solutions actually work. This hands-on validation builds deep conviction about whether you can win and should be worth years of effort.
Use webinars to validate demand and educate potential customers simultaneously
Organizing webinars for your target market serves dual purposes: validating that people care enough to attend (demand signal) while educating them about the problem your product solves. Webinars create warm leads who already understand the value proposition.
Trade equity for insider access to your target industry when entering as an outsider
When building software for an industry you don't belong to, exchange equity in your company for a stake in a practitioner's business. This gives you the credibility to speak as an insider, access to real workflows, and the ability to test your product in a live environment. The equity swap aligns incentives without requiring cash and creates a partnership deeper than a typical advisory relationship.
Systematize idea generation into a timed framework to compress validation from weeks to minutes
Create a structured, repeatable process with specific steps and time constraints that takes founders from broad market selection to validated landing page. The time constraint forces efficient decisions and prevents analysis paralysis.
Validate user willingness to pay at scale before committing massive production budgets
When entering a new content or product category, test whether your target audience will actually pay before investing heavily in supply. Raising capital and securing content deals validates investor interest, not consumer demand. Run small-scale experiments with real users before scaling production.
Build a smaller-scale version of your vision as a standalone business to validate the core hypothesis before scaling
Before building the full product, create a narrower version targeting a specific vertical to validate the core user experience and business model. Run it as a real business for years - generating revenue and learning from customers - so you accumulate proof of concept, user insights, and operational experience before attempting the larger vision. This de-risks the bigger bet by proving the fundamental hypothesis works in a constrained environment.
Build 10+ products in rapid succession to force-learn a new skill domain before committing to one
Rather than studying AI coding tools theoretically, commit to building many real products in a compressed timeframe. The high failure rate is expected - the goal is mastery through repetition, which reveals genuine pain points that become product opportunities.
A large waitlist with zero conversions signals product-market mismatch, not distribution failure - pivot the product, not the funnel
When you build a significant waitlist (1,000+ signups) but convert zero to paying customers, the problem is not your sales funnel or pricing - it is a fundamental product-market mismatch. The waitlist proves people find your category interesting but your specific solution does not match what they will pay for. Instead of optimizing conversion, pivot the entire product concept while keeping the market insight about where demand exists.
Personally fly to your customer's most critical moment to ensure success and learn the full workflow
For the very first time your product delivers its promised outcome, physically show up. This means attending the audit, the demo, the go-live - whatever the make-or-break moment is. This reveals workflow gaps your product missed and builds extreme customer loyalty.
Use design partners as co-builders with weekly feedback sessions for months before public launch
Instead of building in isolation and launching to the public, recruit 3-5 design partners from target companies and engage them in weekly feedback sessions for 3-6 months. These partners shape the product through real usage while providing enterprise validation. The key is choosing partners who will dedicate significant time (like Hotwire's 6-month weekly engagement) because their commitment level signals genuine need.
Convert info products into SaaS to validate demand before writing code
Selling an ebook, template, or digital product around a problem validates both willingness to pay and the specific solution shape before investing in software development. If users pay $19 for a static resource, they will likely pay $29+/month for an automated version. The info product serves as both revenue and market research.
Build a services business around your product when the market isn't ready, then spin out the product when timing aligns
If the market isn't ready for your product vision, don't abandon it. Instead, build a services business that uses early versions of the tool to serve clients. This validates the product with real use cases, generates revenue to sustain development, and creates a customer base ready for the product launch.
Separate ICP problems from persuasion problems when deals stall to diagnose correctly
When prospects feel the pain you solve but still don't buy, the problem is your narrative, not your targeting. When they don't even recognize the problem, you're talking to the wrong people. Diagnosing which type of problem you have prevents wasting resources on the wrong fix.
Physically embed yourself with your first customer to learn their industry from the inside out
Instead of conducting user interviews or surveys, move into your first customer's workspace for weeks or months. The depth of understanding from daily immersion far exceeds what research can provide.
Sell to companies your own size first to build feedback loops, then use those wins to land enterprise deals
Starting with customers similar in size to your own company creates fast feedback loops and reduces the trust barrier. Those early wins then serve as credibility proof points when pursuing larger enterprise accounts through formal processes.
Start a business in the industry you're building software for to gain domain expertise
Insight from Amar Ghose
Commit to co-founders quickly when vision and chemistry align - complementary skills matter
Insight from Cameron Adams