Use-Case Workflows
How to do market research for a startup with a knowledge system — a practical guide for founders and PMs to gather customer intelligence, analyze
Market research for a startup is not a one-time deliverable. It's an ongoing intelligence operation that runs from pre-product through growth, constantly updating as the market shifts, competitors launch new products, customers reveal new use cases, and regulatory or macro conditions change.
Unlike enterprise market research (which can be handed to a research team and delivered in a formal report), startup market research is typically done by the founders and early PMs themselves, with limited time, no budget for expensive analyst subscriptions, and the highest possible stakes — decisions about what to build, who to sell to, and how to position the company.
The challenge is organizing ongoing market intelligence so it's accessible when needed: when you're preparing to pitch investors, when you're making a positioning decision, when a competitor launches a new product, when a prospect asks "why should I choose you over [alternative]?" A knowledge system that's actively maintained makes all of these moments faster and more informed.
Startup market research covers four interconnected areas:
1. Customer research: Who are the target customers? What problems do they have? How do they currently solve those problems? What would make them switch? What language do they use to describe their problems?
2. Competitor research: Who are the direct and indirect competitors? What do they offer? How are they positioned? Where do they win and lose? What are their pricing models?
3. Market dynamics research: How big is the market? Is it growing? What are the macro trends and tailwinds? What regulatory, technology, or behavior shifts affect this market?
4. Industry and ecosystem research: Who are the key influencers, publications, analysts, and communities in this space? What's the ecosystem of adjacent tools and potential partners?
Each area requires different sources and different update frequencies.
Create a primary Collection: "Market Research: [Company/Product Name]"
Sub-Collections:
By research type:
customer-pain — documented customer pain point or strugglecustomer-quote — verbatim customer language (valuable for positioning)customer-workflow — how target customers currently workcompetitor-product — competitor feature or capability documentationcompetitor-messaging — competitor marketing copy, headlines, positioningcompetitor-pricing — competitor pricing information (date this — it changes)market-size — market size data or estimatesmarket-trend — trend or dynamic affecting the marketanalyst-view — analyst or thought leader perspective on the marketfunding-signal — VC investment in this space (signals market activity)By freshness:
current — recently verified, reliable for current decisionsneeds-verification — captured but not recently verifieddated — known to be outdated (keep for historical context)No secondary research replaces direct customer conversations. Aim for:
Capture from customer conversations:
Create a note per interview with:
Interview date:
Customer profile: [role, company size, industry, stack]
How they discovered us / how connected:
Current workflow for [problem]: [step by step]
Current tools they use:
Pain points with current approach: [verbatim where possible]
What they've tried to solve this:
What makes those solutions inadequate:
What they'd need to change their behavior:
Willingness to pay: [amount / hesitation / "free for me"]
Key quotes for positioning: [verbatim]
Feature requests mentioned:
Red flags or risks surfaced:
Next steps:
Capture the interview note in WebSnips and tag with customer-pain, customer-quote, customer-workflow as appropriate.
When you can't interview directly, secondary sources reveal customer language and pain at scale:
Reddit: Search subreddit:[relevant community] [problem your product solves]. Look for "I need help with X," "frustrated by Y," "does anyone else struggle with Z" threads. These are unfiltered customer voice.
Quora and Stack Overflow: Questions about problems in your space reveal what people don't know how to solve and how they frame the question.
Product Hunt and G2 reviews of competitors: What do customers praise and complain about in tools that are adjacent to or competitive with yours?
App Store and browser extension reviews: Particularly useful for consumer or prosumer tools — reviews are more candid than B2B reviews.
Job postings from target customers: A job description for "Head of Operations" or "Marketing Analyst" at your target companies reveals what skills, tools, and problems they're dealing with.
Capture the most valuable community threads, review pages, and job postings with annotations noting:
Map competitors across two dimensions:
All three categories are real competition. "We have no competitors" always means "we haven't done the research."
For each significant direct competitor, maintain a live profile:
What to capture:
Competitor profile note:
Competitor: [Name]
Last updated: [date]
Current positioning headline: [their exact headline]
Target customer: [who they're clearly building for]
Key features/capabilities: [what they offer]
Pricing: [structure and amounts]
What customers love (from reviews): [patterns]
What customers complain about (from reviews): [patterns]
Recent moves: [last 3-6 months of changes, launches, news]
Where they win deals against us: [your hypothesis / intel from sales]
Where we win deals against them:
Key differentiation we should emphasize:
Their likely roadmap direction (based on job postings, blog, launches):
Update each competitor profile monthly at minimum, weekly if the market is fast-moving.
Their own materials: Website, blog, social posts, press releases, investor announcements. The most primary source for their positioning and what they're building.
Third-party coverage: Tech press (TechCrunch, VentureBeat, Axios Pro), vertical publications, analyst reports.
Customer review sites: G2, Capterra, Trustpilot, Product Hunt — filtered by "most helpful" or sorted by star rating. The 3-star reviews tell you the most.
Job postings: Job descriptions are a window into a company's roadmap and what customer types they're pursuing. "Senior Enterprise Account Executive" → moving up-market. "Head of EMEA" → international expansion. "ML Engineer — NLP" → building AI features in a specific direction.
LinkedIn: Who their executives follow and engage with reveals their intellectual influences. What their employees post reveals culture and priorities. Their follower count growth rate is a rough engagement proxy.
Funding announcements: New funding indicates market validation and incoming competitive threat. What VCs say about why they invested is often a useful articulation of the market narrative.
For investor conversations and strategic planning, you need a market size estimate. Sources:
Analyst reports: Gartner, Forrester, IDC publish market size estimates. These are expensive ($3,000-$15,000 per report) but often have executive summaries or press releases available for free that contain the headline number.
Industry associations: Trade associations often publish market data. Free or low-cost.
Bottom-up calculation: Build your own estimate: [target customer count] × [average contract value] × [addressable fraction]. This is often more credible with investors than citing a research firm's top-down number, because it demonstrates you understand who you're selling to.
Public company filings: If any public companies are in adjacent spaces, their 10-K filings contain market size discussions and their revenue can inform TAM estimates.
Capture all market size data points with their source, methodology, and date. Market size estimates vary wildly and become outdated — knowing which estimate came from where and when is critical.
Identify 3-5 macro trends that make your market more relevant or your solution more timely:
Examples:
For each trend, capture:
Trends you can cite in investor decks, sales conversations, and press — with evidence — are part of your market narrative.
Startup market research is not a one-time project. It's an ongoing practice. The knowledge system needs regular maintenance to stay useful.
The quarterly review produces a "market update" note that becomes your current state of market knowledge — useful for investor updates, board presentations, and when new team members join and need context on the market.
The scenario: Two founders are building a tool that automates the onboarding paperwork and workflow for remote employees. They're 6 months into development and preparing for their first investor meetings.
Customer research (ongoing):
customer-pain captures cluster around three themes: "onboarding is manual and error-prone" (29 of 47), "new hires feel lost in first week" (31 of 47), "IT provisioning delay creates day-one friction" (22 of 47)Competitor research (monthly updates):
Market dynamics (quarterly update, Q3 2026):
Investor pitch preparation:
Market research for a startup is a competitive intelligence operation that runs continuously from founding through growth. The founders and early PMs who do it well don't just research the market once for a pitch — they maintain a living system that keeps them informed about customer struggles, competitor moves, and market dynamics as they evolve. A knowledge system organized around customer research, competitor profiles, and market dynamics captures the intelligence as it's gathered, organizes it for retrieval when needed, and makes the accumulated knowledge accessible for product decisions, investor conversations, and positioning development. The system is the asset — not just the research at one moment in time.
Related reading: Building a Personal Knowledge Base.
More WebSnips articles that pair well with this topic.
How to build a teaching resource library with a knowledge system — a practical guide for teachers and educators to organize lesson materials, curate
How to organize sources for a documentary with a knowledge system — a practical guide for documentary filmmakers and journalists to manage research
How to analyze customer feedback with a knowledge system — a practical guide for product managers to collect, organize, tag, synthesize, and act on
How to assemble evidence for due diligence with a knowledge system — a practical guide for investors and acquirers to organize research, document
How to build a competitive landscape map with a knowledge system — a practical guide for product managers and founders to research, organize, and maintain
How to build a course with a knowledge system — a practical guide to organizing research, developing curriculum, managing content assets, and creating