Solution guides
ICP, channel, and GTM playbooks. Every URL is a real page with its own title and description for search — not a duplicate template with a keyword swapped. Start with your situation, or jump to comparisons and the Demand Graph brief.
ICP
- → Customers for vibe-coded products — from public intent, not ads
Shipped with Lovable, v0, or Cursor? Capture Reddit, HN, and IH threads where people ask for tools like yours — reply in-thread, per-signal landing page, full attribution.
- → B2B SaaS: intent capture without the Apollo seat tax
Replace a fraction of your prospecting budget with in-market demand: threads comparing incumbents, budget threads, and Ask HN. Human-approved replies and tracked pages — no seat tax on a four-person team.
- → Dev tools: win the technical thread, not the inbox
Engineers evaluate in public. Meet them on HN, Stack Overflow, GitHub, and r/devops with technical replies, not generic nurture.
- → AI app builders: ride comparison threads, not only launches
“Which AI for X?” is asked thousands of times per day. Capture the comparison threads, ship contextual replies, and attribute signups to the specific question.
- → OSS to revenue: follow production urgency, not the star list
Willing-to-pay language in issues and r/selfhosted — not cold email to every stargazer. Per-signal pages for hosted and commercial plans.
- → Agencies & productized services: be present when the RFP is a Reddit post
r/forhire, r/startups, Indie Hackers “need help with” — be the team that shows up in the thread, with a case-built page in minutes.
- → Micro-SaaS: distribution in the niche, not the broad funnel
When your TAM is a slice of a slice, the open web is often where 100% of the conversation already lives — scan it, do not only blog into the void.
- → Indie hackers: be systematic about “building in public” inbounds
Ship where IH, Reddit, and HN already debate tools and pricing — with a system, not a bookmark folder of tabs.
Channels
- → Reddit for B2B: treat threads as in-market, not as “social”
Scalable scanning of B2B subreddits, relevance to your ICP, and human-in-the-loop replies. No subreddit list you maintain by hand every week.
- → Hacker News: show up in the right Ask HN threads on purpose
Stay on the threads that mention your space: alternatives, dev workflows, and founder questions. Draft in HN tone, approve, ship.
- → Stack Exchange: the anti-hype channel for B2B truth
Product-comparison and workflow questions in communities your buyers trust. Replies with technical specificity and measured tone.
- → Show HN is day one. The graph is the next ninety.
Launch day is a spike; category threads are continuous. Map ongoing Ask HN and dev discussions to the same ICP and attribution.
- → Product Hunt success is not the only public signal you have
When buyers compare in comments and on Twitter, treat it as a signal class — not only upvotes and badges.
- → Developer marketing that reads like a peer, not a banner ad
A practical approach to r/programming, Dev.to, and Lobsters — with tone-aware drafts and a compliance posture that does not get you banned for spam.
- → Win the “any alternative to …?” thread honestly
Comparison and migration questions are a distinct signal class — the Demand Graph is tuned to find them in your space.
- → B2B Reddit: strategy, not a bag of “growth hacks”
A founder-grade view: subreddits, timing, and value-first replies, backed by a system that does not let good threads disappear.
- → X: fast, noisy, sometimes gold — for the right ICP
A channel where speed and context collide. Use scanning and scoring to avoid drowning, not to turn into an auto-reply account.
Motions & concepts
- → Public buying intent: the unit of a Demand Graph
Define the difference between a keyword mention and a purchase-ready thread — and how a Demand Graph operationalizes the second.
- → Signal-to-Page: one URL per ask, in under 30 seconds
Why a unique, fast-generated page beats a generic site for a hot thread — and how attribution works end to end.
- → Pipeline without a cold email machine
A different GTM that does not start from purchased emails — for teams that refuse deliverability roulette and list ethics debt.
- → Bootstrapped SaaS: replace spray-and-pray with in-market
A free tier, no per-seat tax for a three-person team, and intent from the open web — for capital-efficient growth.
- → Founder-led sales: the queue is the strategy
A queue of high-intent discussions so the founder’s selling time is spent in context, not in CRM hygene.
- → Attribution for startups: thread → signup, not just ad click
Link a public post to a signup without duct tape. Webhooks, tracked links, and one funnel view.
- → The open web is the largest unpriced demand surface
A single system that refreshes on a schedule — so you are not one founder with 25 browser tabs pretending that is a “stack”.
- → Outreach with a human in the loop — on purpose
Why we approve before post: brand safety, platform TOS, and the fact that founders still close better than a bot in public.
- → From “great thread” to a tracked next step
A discussion is not a lead in CRM terms until there is a next step and measurement — the Demand Graph bakes in both.
- → First 100 customers: in-market, not in-database
A practical lens on early B2B traction — the conversations that are cheap to join and possible to measure.
- → PLG meets public intent: free trial from a public question
For products with self-serve, the open web is often the top of the true funnel, not a random blog hit.
- → GTM when you are not going to “just run ads”
A realistic path for teams that are not going to outbid Series B budgets on the same three keywords for five years.
- → A different first input than a 200M-row contact file
A category contrast: you do not start with who to email, you start with who asked. Different funnel math and different software.
- → Real time here means: refresh, score, and queue on a schedule you can plan around
Continuous scanning, scoring, and a human-in-the-loop queue — a concrete definition of “real time” in GTM, not a marketing buzzword.