Market research for startups should reduce the risk of one near-term decision. It cannot certify that an idea will work. The useful output is a compact evidence trail, explicit unknowns, and a test that asks real people to do something costly enough to matter.
Frame a decision-sized research question
Is this a big market? is usually too broad for an early startup. Ask which customer has the problem most often, what workaround already consumes time or money, which buying trigger creates urgency, or which claim deserves the next week of product work.
Anchor the question to an artifact when possible: a landing page, demo, repository, deck, waitlist, or rough product. Research becomes more concrete when the audience can react to something real.
Use an evidence ladder
Higher rungs are not automatically perfect evidence, but lower rungs cannot substitute for them. A trend report may size a category; it cannot prove that a particular founder will adopt your workflow.
- Context: market definitions, regulations, category language, and credible reports explain where to look.
- Observed behavior: workflows, job posts, existing tools, budgets, and workarounds show that people already spend effort.
- Direct problem evidence: interviews and detailed complaints reveal frequency, consequence, and current alternatives.
- Commitment: a qualified person gives time, data, access, a referral, or agrees to a next step.
- Demand: repeated use or payment demonstrates stronger behavior than stated interest.
Run a seven-step startup research loop
- Write one decision and the riskiest assumption behind it.
- Define the target customer narrowly enough that two researchers would find similar people.
- Collect source-linked context and one deep competitor analysis.
- List the strongest evidence for, evidence against, and evidence still missing.
- Choose one outreach or product test that can produce a stronger signal.
- Set acceptance criteria, channel boundaries, cost, and a stop condition before acting.
- Record the returned signal and decide: continue, revise, or stop.
Keep research separate from demand validation
Secondary research can reveal language, competitors, communities, and plausible pain. It cannot tell you whether the people you can actually reach will change behavior. Treat the research report as the map and the demand test as the trip.
For Soloop today, approved research is live. X/Twitter publishing is live when OAuth is connected and the action is approved. Cold email is beta and requires Gmail. Reddit publication remains manual, ads are plan-only, and sandboxed coding runs behind approval. Choose a test that respects the real channel boundary instead of writing a plan as if every channel were automated.
Use this one-page research output
- Decision: the choice this research must inform.
- Target: the specific customer and situation.
- Known: source-backed observations with dates.
- Inferred: interpretations that remain contestable.
- Unknown: missing evidence that could reverse the conclusion.
- Next test: exact action, target, channel, owner, cost, and stop condition.
- Signal: what happened and how it changes the decision.