The standard advice is to book interviews with strangers. For an outsider that fails at roughly 0.1%. Here are three cheaper paths that work, and a worked example run on real data.
BigIdeasDB is the product-research platform that turns documented complaints into structured demand evidence. This guide is about the hardest version of validation: an industry where you know nobody and have never done the work. Everything below is tested against a corpus of 1M+ complaints, reviews and discussions, and the worked example is run live on real data rather than described in the abstract.
Our other validation guides assume you already understand your market. This one does not, because that assumption is what makes most validation advice useless to the person who needs it most.
Invert the usual order. Do not start by trying to book interviews, because that is precisely the step that fails for outsiders. Start with complaint mining, which needs nobody's permission. Then collect artifacts, meaning the actual spreadsheets and checklists people work off. Then shadow one person for an afternoon. Conversations come last, when you finally have something specific to ask about.
Short answer: the cheapest research first, the most expensive access last. Read the one-star reviews of the software those people already pay for, get two real working files, watch one person do the job, then have five conversations about specific past events rather than general problems. Never open with your idea. The thing you are listening for is a workaround somebody built by hand, and the same one appearing twice is your signal.
Any honest guide to this has to start with the strongest argument against doing it at all. Asked this exact question, the most upvoted answer in a founder community was blunt and got roughly triple the support of anything else in the thread:
“if you have zero experience in the industry, you have zero business trying to build a tool from scratch for it.” - r/startups
That deserves a real answer rather than a motivational one. The argument is not snobbery. It is that domain knowledge is a shortcut to knowing which problems are real, and without it you are likely to build something confident and wrong. Another commenter laid out the failure modes precisely:
“you may be trying to solve perceived problems instead of actual problems, solve problems that have already been solved, or solve problems that nobody actually wants to be solved (or more importantly, will pay to be solved).” - r/startups
Three distinct ways to fail, all of them invisible from the outside. That is the real risk, and it is worth holding rather than waving away. It is also the same failure CB Insights has found dominating startup post-mortems for years, with no market need cited in roughly 42% of cases. More context in why startups fail and the failure statistics.
Three situations where the sceptics are simply correct and more research will not fix it.
In all three the answer is a partner or an advisor from inside, covered in when to partner instead below and in the co-founder and equity guide. Everywhere else, the gap is closable with work.
Two real advantages, both of which insiders lose over time. Outsiders notice the workarounds insiders have stopped seeing, because familiarity turns absurd processes into just how it is done. And outsiders have no sunk cost in the current way of working, so they are not defending anything.
The evidence that outsiders build real businesses in unfamiliar markets is not anecdotal either. Looking at event-adjacent businesses currently listed for sale, one is a photo booth template service for event organisers with a seven-year operating history, $272,000 in trailing revenue and $240,000 in profit, listed at $1.6 million. That is a niche most people would never have thought of and few insiders would have bothered with.
The advantage is real but it is not free. It has to be paid for with research, and the rest of this article is the cheapest way to pay.
The standard advice is to email twenty strangers and ask for fifteen minutes. For an outsider this fails at a rate worth knowing before you spend a month on it. One founder attempting exactly this in logistics documented the result:
“I had about 200 people in my pipeline (email + LI messages) and didn't get a single meaningful reply... I estimate my success rate was at most 0.1%. I gave up.” - r/startups
Two hundred attempts, nothing. And their own diagnosis of why is more useful than the number:
“there is a difference between a cold email from a person you have something in common vs a dev messaging operations manager.” - r/startups
That is the whole mechanism. It is not that cold email does not work. It is that what you are asking for is different. An insider's email offers something. An outsider's email asks a busy stranger for unpaid tuition, and no amount of polish changes which of those two things it is. Related reading on outreach that does convert: getting your first customer and getting customers for a startup.
The usual fallback is a survey, and it is worse. One founder described running exactly the survey most people would design, previewing the product and asking whether people would use it:
“Hardly 100 responses, and that took months.” - r/startups
Months for under a hundred responses to a question that measures politeness rather than behaviour. What they changed is the instructive part:
“I led with their problems. No mentioning the app at all. Just asking what sort of problems they face... But they won't give me the info I need until they feel addressed.” - r/startups
Lead with their problem, never your solution. That principle runs through customer discovery questions and common validation pitfalls.
Ordered by cost. Run them in this order, because each one makes the next cheaper by giving you something specific to ask about.
| Path | What you get | What it costs | Why it beats cold outreach | Effort |
|---|---|---|---|---|
| Collect artifacts | The actual spreadsheet or checklist they work off | One favour, no money | Shows what they gave up on, which nobody says out loud | Low |
| Shadow a day | How the work really flows under pressure | A day of your time | People cannot hide their workflow when you are standing there | Medium |
| Mine the complaints | What hundreds already wrote about the incumbents | Free, and you can start now | No permission needed, and it never says yes to be polite | Lowest |
The single best idea in this whole space, and it came from someone who had done it in an unfamiliar market:
“Ask them to send you the actual file they work off. A planner's timeline spreadsheet or their client checklist tells you more in ten minutes than an interview does, because you can see which columns get filled in properly and which ones they gave up on halfway through the season.” - r/startups
And the payoff, stated plainly:
“I collected four of those before building anything for restaurants and two had the same hand made column for the same problem.” - r/startups
Two people, independently, building the same manual column to solve the same thing. That is a product requirement discovered without a single interview question, and it is the strongest pre-build signal available to anyone. The same logic drives finding real problems to solve, problem-led business ideas and uncovering real-world problems.
It works for the same reason shadowing works: it captures behaviour rather than recollection. Somebody describing their process gives you the version they intend. The file gives you the version they actually run, including the parts they are slightly embarrassed by. That distinction is the whole difference between ideas backed by real complaints and ideas backed by conversations.
Four rules that make this a reasonable request rather than an intrusive one. Ask for one real example rather than a general tour, since specific asks are easier to say yes to. Explicitly invite them to redact anything client-identifying, which removes the main objection before they raise it. Offer to pay, because you are asking for something real. And say what you will do with it, which is read it, not share it.
A workable version: "I am trying to understand how planners actually track a wedding. Would you send me one real timeline sheet with the client details stripped out? Happy to pay for your time. I just want to see how the columns are used."
The second-best idea in the thread, and it reframes the ask entirely:
“Skip the 15 minute call, ask one planner if you can tag along for an afternoon in peak season. People are terrible at describing their own workflow but they can't hide it when you're standing next to them.” - r/startups
A second commenter arrived at the same conclusion independently:
“the best research you could possibly do is actually shadow someone in the industry to really understand it because you may see it differently from their perspective.” - r/startups
The reason this works is not effort, it is that self-reported workflow is unreliable in a specific direction. People describe the process they intended, not the one they run. They omit the workaround they have done so many times it no longer registers as a workaround. Standing next to them removes both problems at once.
It is also the fastest correction available to an outsider, because you will be wrong about something within the first hour and you will see it happen rather than be told. One person who took the shadowing route put the reason plainly:
“You have to shadow and interview wedding planners. But this is true research.” - r/startups
True research, meaning it can return an answer you did not want. If that possibility is not on the table, what you are doing is confirmation, and keeping delusional thinking out of validation covers why that is the most common way this goes wrong.
Counterintuitively, ask for the busy period rather than the quiet one. Peak season is when the process actually breaks, which is what you came to see, and it is also when an extra pair of hands is genuinely useful. Offer to be useful, ask for a defined block rather than open-ended access, and stay quiet until afterwards.
The conference version of the same move works too:
“Go to an industry conference, talk to everyone, and get contacts, for every one interested be upfront about needing advice and get them lunch or coffee, pick their brains.” - r/startups
The cheapest path, the one to run today, and notably the one a stranger in that thread recommended without any prompting:
“FIRST FOCUS on the UNHAPPY CUSTOMERS. Skip the cold outreach and go straight to the 1 star or 2 star reviews of existing software in that space.” - r/startups
“People won't always tell you what they want on a call, but they will happily post online about what's currently breaking their workflow.” - r/startups
A third commenter made the same point from the interview angle:
“Established competitors help too; their 1-star reviews give you sharper interview questions.” - r/startups
And a fourth added a timing refinement worth stealing:
“looking at the most recent posts, ideally no more than 7 days old, because they're more likely to still be dealing with the problem.” - r/startups
Four structural reasons, and they all matter more when you have no standing in the industry.
Nobody has to say yes. The complaints are already written. Your access problem disappears entirely, which is the problem that stops most outsiders.
Nobody is being polite. A person on a call with you softens things. A person writing a one-star review at midnight does not, and that difference is the entire value.
The sample is large. Five interviews is five opinions. Complaint data across a category is hundreds of people who already self-selected for having a problem.
It gives you vocabulary. You learn what the work is called before you speak to anyone, which is the difference between sounding curious and sounding clueless. Tooling for this is compared honestly in tools to find customer pain points and complaint databases, with method in mining negative reviews and mining Capterra reviews, tools for turning reviews into ideas and finding ideas from real pain points. If you would rather see the output than run the process, the underserved markets study and the state of SaaS pain points are both built this way.
Abstract method is easy to agree with and hard to act on, so here is the concrete version, run on the exact idea that prompted the original question: software for wedding planners, by someone planning their own wedding and nothing else.
One honest note first. Wedding planning specifically is not a category we track, so everything below comes from the adjacent market that shares almost all of the same workflow: event planning and event management software. That substitution is a limitation and it is the sort of thing you should state rather than paper over.
Before knowing anyone, you can establish the shape of the market. Querying our own research tables for every event-adjacent software category returns 16 tracked categories covering 180+ products, against which we hold 3,600+ reviews, 550+ scored pain points and 570+ documented feature gaps. On the payments side, events and ticketing shows 830+ operating businesses with only 33 micro-SaaS products serving them.
That last ratio is the interesting one. Many operators, very little software built specifically for them. Density by category is mapped in the Stripe Index database and SaaS market saturation, with method in the Capterra analysis documentation.
Here is the finding that changes how you should read any unfamiliar market, and it is the strongest argument in this article for not trusting surface signals.
Across those 180+ event products, the average rating is 4.64 out of 5. An outsider glancing at that would reasonably conclude the market is well served and move on. Now look at what sits underneath it: 550+ scored pain points and 570+ feature gaps across the same products. Roughly three documented, unresolved problems per product, in a category averaging four and a half stars.
Of those 3,600+ reviews, fewer than 100 are rated one or two stars, which is under 3% of the total. That is not a limitation, it is an instruction. The complete set of angry reviews for an entire industry is small enough to read in a single evening. Most outsiders never do, because the 4.64 average told them not to bother.
This is why high ratings and unsolved problems coexist so comfortably. People rate the product they chose, having already accepted its limits, and put the frustration in the cons field rather than the score. The consistent pattern across every category we analyse is that the most credible criticism lives inside five-star reviews, which is exactly where nobody looks.
The practical rule for an outsider: never judge an unfamiliar market by its average rating. Read the cons fields and the small pile of one-star reviews, because that is where the product roadmap is hiding. The same method drives the most-hated software study, most-requested features and turning G2 reviews into ideas.
Now the useful part. Pulled from the lowest-rated reviews across those products, with no interviews and no contacts.
| Documented problem | Where | Signal strength | What it costs the user |
|---|---|---|---|
| Reliability and stability failures | Event Planning Software | 7 of 9 critical entries mostly negative | Crashes, broken exports, lost planning time |
| Setup and onboarding friction | Video and event platforms | 15 requests, high intensity | 30 to 45 minutes to set up an event, target is 10 |
| No multi-event dashboard | Multi-event organisers | 15 requests, high intensity | About 5 hours a week lost toggling between events |
| Day-of navigation chaos | Live event management | 14 requests, high intensity | Coordinators describe live events as chaotic to run |
| Manual reporting and reconciliation | Attendance and donation tracking | 12 requests, high intensity | 5 to 6 hours a month collating by hand |
| Alerts and emails not arriving | Event Planning Software | Cross-vendor theme | Spam and junk issues, missing alerts, no delivery status |
| Rigid templates and branding | Registration pages, proposals, menus | Cross-vendor theme | Cookie-cutter output, workarounds, separate events |
| Payout and refund delays | Box Office Software | 10 companies analysed | Delays reported up to five months, affecting cash flow |
Two rows are worth pausing on. Multi-event organisers report losing about five hours a week toggling between events because no centralised dashboard exists, which is exactly the "managing 10 to 20 weddings at once" problem the original asker guessed at. And in box office software, payout delays are documented as long as five months, affecting roughly a third of users in one scored opportunity. That is a cash-flow event, not an annoyance.
Feature requests are demand that has already been articulated. Across the category, the highest-intensity requests were a pre-event setup wizard (15 requests, with users reporting 30 to 45 minutes to set up an event against a 10-minute expectation), a multi-event dashboard (15 requests), a usable day-of management view (14 requests), and automated reporting (12 requests, with 5 to 6 hours a month spent collating data by hand).
The reviewer quotes behind those numbers are more useful than the counts:
“While managing multiple events, the need for a centralized dashboard is critical; switching back and forth between events is inefficient.” - Capterra review, event software
“Managing events on the day often felt chaotic due to the system's navigation challenges.” - Capterra review, event software
“We need easier ways to compile donation data, it's too manual right now.” - Capterra review, event and fundraising software
And, as always, the most credible criticisms sit inside five-star reviews:
“The check-in process is not the smoothest. We are still trying to tackle how to get this to work.” - Capterra review, rated 5 of 5 overall
“I wish the site designer was a little easier to use, as sometimes it is hard to move things around and can be a bit clunky.” - Capterra review, rated 5 of 5 overall
“Some of the features can feel a little limited if you're planning a larger or more complex event.” - Capterra review, event planning app
The step most people skip. Complaints prove frustration; only money proves a market.
| Event-adjacent business | TTM revenue | TTM profit | Asking | Notable |
|---|---|---|---|---|
| Photo booth template service for event organisers | $272,000 | $240,000 | $1,600,000 at 6.9x | 7-year operating history, SEO-led |
| Marketplace for event locations and film gear | $350,000 | $179,000 | $540,000 at 3.0x | 2,000+ listed locations |
| AI captioning for enterprise and events | $132,000 | $36,000 | $195,000 | Compliance and accessibility wedge |
On the services side, freelance demand shows what event operators pay humans to do: signage design and approval workflow recurs most often, followed by photography booking and project management, then all-in-one event coordination and sponsor procurement. Every one of those is a workflow somebody is paying to have handled manually today.
Without knowing a single wedding planner, that research produced: a map of 16 categories and 180+ products, the knowledge that a 4.64 average rating hides 550+ documented pain points, a readable pile of fewer than 100 one-star reviews, a ranked list of what breaks, four high-intensity feature requests with time costs attached, quantified pain (five hours a week, five to six hours a month, payout delays up to five months), operator density, and three real acquisition comps.
That is not validation. It is something more useful at this stage: it is enough to walk into a conversation and ask "how do you handle the gap between your booking system and your timeline sheet?" instead of "so what problems do you have?". The first question makes you worth twenty minutes. The second is why cold outreach fails.
Forty minutes of desk research does not make you an insider. It makes you a credible outsider, which is the thing that unlocks every other path in this article. Start at Discover, or go straight to pain points and complaints to run this on your own category.
The most useful reframe in the whole thread, and it explains why identical emails get wildly different response rates. One commenter separated two things people conflate:
“The first one is ‘I can save you time/money’, while the second one is ‘I want you to spend time/money on me’.” - r/startups
Validating a concept you already hold is one activity. Asking someone to teach you their industry is a completely different one, and only the second is what most outsiders are actually doing. Their description of how it lands is worth sitting with:
“Do they hear you tempting them with them being able to make more money and having an easier life, or do they hear this clueless inexperienced person wanting them to waste time/money/energy on yet another baseless fishing expedition?” - r/startups
And the posture that works:
“Validating a preconceived concept you do through networking with your mouth closed and your ears open... Be humble. Listen a lot.” - r/startups
This is exactly why the three paths run in the order they do. Complaint mining and artifact collection reduce how much teaching you need, which shrinks the ask, which is what makes people say yes.
A version that works, built from what practitioners in that thread reported actually landing:
“I'm trying to understand how planners juggle 10+ weddings. Could I pay you for 20 minutes to walk me through the last one?” - r/startups
Four things make it work. It names a specific thing you want to understand rather than asking for general wisdom. It offers payment, converting a favour into a transaction. It is time-boxed at twenty minutes. And it asks about one real past event, which is far easier to answer than an abstract question about their business.
Note what it does not do: it does not mention an idea, a product, or an opportunity you have spotted.
Any personal connection to the problem is worth using, because it converts you from a stranger into someone with a reason to ask:
“Cold DMs are fine here. Since you're planning a wedding, you have a natural opener... Let them redact client info.” - r/startups
If you have no such connection, manufacture a legitimate one by becoming a small customer first. Buying the thing, even at the cheapest tier, gives you standing that no email can. Related: discovery questions and building a repeatable outreach process.
Paying is not just about compensation. It changes what you are allowed to ask for and it changes the quality of what you get:
“Paying for screen sharing got me actual workflows instead of polished summaries.” - r/startups
Polished summaries are the default output of any unpaid conversation, because people describe their job the way they would describe it to a new colleague. Twenty to fifty dollars for twenty minutes is normal and it is trivially cheap against the cost of building the wrong product. Compare it against what starting a business actually costs.
“Most people are flattered someone wants to learn their craft. Start with the ones whose reviews mention friction points.” - r/startups
“Ideally offer some kind of incentive like taking them out for a free meal or giving them an Amazon voucher to thank them for their time.” - r/startups
Note the second half of the first quote. Starting with people whose public reviews already mention friction means you are approaching someone who has demonstrably wanted to talk about this problem, which is a far warmer lead than a cold list. That is the practical bridge between complaint mining and conversations, and it is why the paths run in the order they do. Tooling in Reddit research tools and market research tools.
The original question was whether asking to see someone's software or spreadsheets is too invasive. The consistent answer from people who have done it is no, provided you handle it properly: offer to pay, invite them to redact client information, and ask them to walk through one real job rather than giving you a tour of the tool.
The single best framing of what to ask while watching:
“Ask about one real wedding: what arrived late, which spreadsheet they reopened, what they copied between tools, and where something nearly got missed.” - r/startups
Four questions, all about observable past events, none of them answerable with a polite generality. That is what a good discovery question looks like, and the fuller set is in customer discovery questions.
After the desk work, five conversations is the right target. Enough to change your mind, few enough that you will actually do it. The recommended endpoint is not a decision to build:
“After five conversations, pick one repeated headache and offer to handle it manually for a planner. You'll learn more from that than from building the first version.” - r/startups
Doing the job by hand for one person is the strongest validation available to an outsider. It proves demand, teaches you the workflow properly, and produces a customer relationship. It is also the fastest way to discover the work is nothing like you imagined, which is worth finding out before you write code. That principle underpins validating before you build and the 8-stage framework. Y Combinator's library on how to talk to users covers the same discipline from the interview side. The doing-it-manually step is the same move recommended in getting your first customer and turning an idea into a startup, and it is how most service businesses in service business ideas actually started.
Never ask whether they would use your product. As an outsider you are especially vulnerable to that answer, because people are extra polite to someone who is clearly new.
Any two of those and you are not ready. All six and you have been researching the idea of the industry rather than the industry.
The corrective is uncomfortable and simple. Someone who has done this well described the posture it requires:
“You're humble af when you're asked about what you do and why you're there. Telling people that you have an idea about applying your expertise to their market, so you're there to listen and learn.” - r/startups
“you're not just some automaton parroting sales phrases and preconceived stereotypes about their industry, and how you're there to save them with your revolutionary new idea.” - r/startups
Sometimes the right answer is not more research. If three months of honest effort has produced no relationships, the constraint is access rather than knowledge, and no method fixes that. Same if the work is licensed, or if trust is the actual product being sold.
A partner brings credibility, a first customer set and pattern recognition you cannot buy. The cost is equity and coordination, covered in the co-founder and equity guide and when outside help is worth it. An advisor with a small stake is often enough and is much easier to arrange than a co-founder.
The original asker also wanted to know how not to get discouraged by established competitors. The reframe: competitors are the single best free research available to an outsider, and their existence proves people pay, which is the hardest thing to prove about any new idea.
The worked example above is entirely built out of competitors' weaknesses. Every one of those documented failures is a competitor telling you, at scale and for free, what they have not fixed. A market with no competitors is far more worrying than a crowded one.
The honest counterweight, from the same thread:
“But this is true research. You'd have to be open to the idea that there isn't room in the market for what you want to build.” - r/startups
That has to stay on the table or the exercise is theatre. Related: niche viability validation, competitor research tools and the underserved markets study.
Two weeks, mostly waiting. If you are at week six still researching, you have stopped validating and started avoiding the decision. For the general-purpose version of this sequence see how to validate a startup idea and the validation playbook library. The HBS Online guide to startup market research and the SBA's market research and competitive analysis guidance cover the formal versions. If your idea turns out to be local and physical rather than software, switch to the four-signal local demand check, which is the same discipline adapted for services sold within a radius.
Being honest about the ceiling matters, because overclaiming here is how outsiders get burned.
Every one of those is discoverable, and none of them from a desk. That is what the five conversations and the shadowing day are for.
There is one more thing desk research cannot give you, and it matters most for an outsider: whether you actually want to spend the next five years in this industry. Plenty of validated markets are miserable to work in. That question is worth asking honestly alongside the cost of starting and what bootstrapping actually demands.
Walk away when the complaint research turns up no repeated, costly problems; when five conversations produce nobody describing a workaround; when the problem is real but nobody controls a budget for it; or when access is genuinely closed and you cannot find a partner. Those are clean factual kills and taking them quickly is a skill.
Do not walk away because someone told you outsiders should not build here. That is the objection this article opened with, and the honest answer is that it is a warning about a real failure mode rather than a rule. Lessons from the other side in failed business ideas and what to do when you have no ideas. If the industry itself turns out to be the problem rather than your idea, pick a different one from the most profitable niches, niche opportunities by industry or boring industries begging for micro-SaaS, all of which are ranked by documented demand rather than by appeal.
Mistake five is the cheapest to fix and almost nobody does it. Mistake seven is the one that quietly costs years. If you recognise yourself in the second, the fastest cure is to price something and offer it this week, using pricing strategies and getting your first users as the next step rather than more reading.
Evidence is separated into layers so no figure is overstated. The 1M+ corpus figure is historical and cumulative and is never summed with the snapshots below it.
| Source | Records | Evidence | Limitation |
|---|---|---|---|
| Complaint corpus | 1M+ | Cross-source historical record | Historical and cumulative, never a live count |
| Capterra pain points | 39,000+ | Severity-scored software problems | AI-extracted subset, not every review |
| G2 event-category insights | 6 subcategories, 38 products | Where incumbents fail across a whole industry | Drawn from lowest-rated reviews, so skewed negative |
| Capterra feature gaps | 10 scored, with request counts | What buyers are actively asking for | Request counts are within our sample, not the market |
| Capterra reviews read in full | 10 | Praise and limits in reviewers' own words | Review sites skew positive |
| Scored opportunities | 5 | Where the gaps are big enough to build on | A score is not a revenue guarantee |
| Acquisition listings | 3 event-adjacent businesses | What this market actually pays | Seller-reported and unaudited |
| Upwork demand signals | 8 patterns | What buyers pay freelancers to solve | Frequency only, budget fields are empty |
| Stripe Index category | 830+ operators | Operator density in events and ticketing | Counts businesses taking payments, not all operators |
Source documentation lives under data sources overview, G2 review analysis, Capterra analysis and the SellSide database.
The three paths were selected from methods practitioners report working in unfamiliar industries, then ordered by access cost rather than by time cost, because access is the binding constraint for an outsider. The worked example was run live: G2 category insights across six event-software subcategories, severity-scored Capterra pain points and feature gaps with request counts, full Capterra reviews, scored opportunities, live acquisition listings, and Stripe Index operator density. Nothing in it required knowing anyone in the industry, which is the point being demonstrated.
Community material is used for voice and pattern identification only, is quoted anonymously by subreddit with no usernames or post identifiers, and is never treated as a statistic.
The limits matter here more than usual. The 0.1% outreach figure is one founder's self-estimate of their own failed campaign, not a measured benchmark, and it is quoted because it is specific and honest rather than because it is representative. Wedding planning specifically is not a category we track, so the worked example substitutes adjacent event-management data, which shares most of the workflow but is not identical. G2 category insights are drawn from lowest-rated reviews and therefore skew negative by design. Feature-request counts describe our sample, not the market. Acquisition listings are seller-reported, unaudited and self-selected, since only businesses being sold appear at all. Stripe operator density counts businesses taking card payments and undercounts cash and platform-mediated operators. And desk research of any depth still cannot tell you who signs the cheque, which is why the conversations remain mandatory. Base rates worth holding alongside all of this: US Bureau of Labor Statistics Business Employment Dynamics data has long shown roughly a fifth of new businesses closing in their first year and about half within five.
More method: the complaint analysis platform, the market research guide, using AI for market research and multi-signal validation. If you are earlier than this and still choosing a market, start with finding a profitable niche, how to decide what business to start or how to come up with a business idea. If you are further along, see turning an idea into a startup, getting your first 100 users and how to build a SaaS.
Stop trying to book interviews first, because that is the step outsiders fail at. Work in this order instead: mine the complaints and reviews about the incumbents, which needs nobody's permission and can start today; collect real artifacts, meaning the actual spreadsheets and checklists people work off; then shadow one person for an afternoon. Only after those three do you have enough context for a conversation to be worth anyone's time, and by then you will be asking specific questions instead of asking to be taught the industry.
It is a genuine advantage and pretending otherwise is dishonest, but it is not a requirement. What insiders have is a shortcut to knowing which problems are real, which is exactly the thing outsiders have to buy with research effort. The failure mode for outsiders is specific and avoidable: solving perceived problems rather than actual ones, solving problems already solved, or solving problems nobody will pay to fix. All three are catchable before you build, and the methods below are how you catch them.
Because of what you are actually asking for. An insider's cold email offers something. An outsider's cold email asks a busy stranger to spend unpaid time teaching them an industry, which is a much harder sell no matter how politely it is worded. One founder attempting exactly this in logistics reported building a pipeline of around 200 contacts across email and LinkedIn, receiving no meaningful replies at all, and self-estimating a hit rate of at most 0.1% before giving up. Nothing about that is a persistence problem.
Read the one and two-star reviews of the software those people already pay for. It costs nothing, needs no permission, and gives you a vocabulary and a problem list before you speak to anyone. In roughly forty minutes on the event and wedding planning market we pulled recurring failures across dozens of products: reliability and export failures, alerts not arriving, rigid templates, manual reporting eating five to six hours a month, and payout delays reported up to five months. That is a real briefing, assembled without knowing a single person in the industry.
Yes when you are asking for something substantial, which as an outsider you usually are. Paying reframes the ask from a favour into a transaction and it materially changes what you get, particularly if you want someone to share their screen. Practitioners consistently report that paying for a screen share produced actual workflows rather than the tidy summary people give when describing their own job from memory. Twenty to fifty dollars for twenty minutes is normal, and it is far cheaper than building the wrong thing.
Not if you ask properly, and it is the single highest-value thing you can request. Offer to pay, let them redact anything client-identifying, and ask for one real example rather than a general tour. The artifact tells you what an interview cannot: which columns get filled in properly, which ones they abandoned mid-season, and what they built by hand because the software would not do it. Somebody's hand-made workaround appearing twice across two different people is the strongest pre-build signal there is.
Five, and they should come after your desk research rather than instead of it. Five is enough to change your mind and few enough that you will actually do it. The difference for an outsider is what you ask: not what problems do you have, which invites a polished summary, but what happened during one specific recent job. What arrived late, which spreadsheet did you reopen, what did you copy between tools, and where did something nearly get missed.
Competitors are the best free research you will get, and their existence proves people pay, which is the hardest thing to prove about any new idea. Their one and two-star reviews hand you a ranked list of unsolved problems and a set of sharper interview questions. The honest caveat is that you must also stay open to the answer being no. Sometimes thorough research tells you there is no room for what you wanted to build, and finding that out in a week is the good outcome.
You can get much further than most people assume, and not all the way. Desk research reliably tells you what breaks, what people ask for, what the incumbents fail at, and roughly what the market pays. It cannot tell you what a person will actually buy, what their budget approval looks like, or the informal workarounds that never make it into a review. Treat desk research as the thing that earns you a good conversation, not as a replacement for one.
Anything that positions you as arriving with the answer. The difference people hear is between I have a better way and teach me, and the second one is a much bigger ask because it is you requesting their time rather than offering value. Do not lead with your idea, do not claim to have spotted an inefficiency they have missed, and do not describe the industry back to them. Say you are trying to understand how the work actually gets done, then be quiet.
It is one of the weakest options and the failure is well documented. One founder ran a survey that previewed their product and asked whether people would use it, gathered fewer than a hundred responses over several months, and got little usable signal. They then switched to leading with problems and never mentioning the product, which worked far better. Surveys that describe your solution measure politeness. Questions about what someone did last time measure behaviour.
About two weeks, and most of it is waiting rather than working. Budget roughly a day for complaint and review research, a week in the background for five conversations to actually get scheduled, and a day to collect and read two or three real artifacts. If you find yourself at week six still researching, you have stopped validating and started avoiding the decision, which is the most common way this process fails.
When the industry is licensed, when trust is the product, or when access itself is the barrier. Some markets will not talk to an outsider at any price, and no amount of research replaces someone who is already trusted in the room. The signal is simple: if three months of honest effort has produced no relationships, the constraint is access rather than knowledge, and a co-founder or advisor from the industry solves what more research cannot.
When you can predict the answer before you ask. If you can describe someone's workflow back to them and they correct only the details rather than the shape of it, you have enough. A second test: you can name the specific moment in their process where things go wrong, and at least two people independently described the same workaround. Until both are true, you are still guessing with better vocabulary.
Building for the problem they imagined rather than the one that exists. It usually happens because they went straight to building after a handful of encouraging conversations, and encouraging conversations are the easiest thing in the world to get. The second biggest is the opposite failure, which is researching indefinitely because research feels safer than selling. Both are avoided by the same discipline: gather evidence for two weeks, then go and try to charge someone.
Software review sites, app-store reviews, industry forums and community threads, filtered to the lowest ratings. BigIdeasDB aggregates these into a severity-scored corpus of 1M+ complaints so you can pull a category's recurring failures in one query rather than reading reviews for a week. What matters is not the source but that the text is real and specific enough to quote, because a complaint you can quote is a problem you can verify with a buyer later.
BigIdeasDB Research. (2026). How to Validate a Business Idea in an Industry You Know Nothing About. BigIdeasDB. Retrieved from https://bigideasdb.com/how-to-validate-a-business-idea-in-an-industry-you-dont-know