# welaunch.sh: full text > Do buyers find you, or your competitor? See where you show up on ChatGPT, Google, Reddit and X, who gets recommended instead, and what to fix first. > welaunch gets your SaaS named when buyers ask ChatGPT, Perplexity, Gemini and Google AI. It asks your buyers' questions several times a week on each engine, shows every answer, finds the pages the engines cite, and does the work to get you onto them from your own accounts: you review and press submit. > Index: https://www.welaunch.sh/llms.txt ## AI visibility, by engine Hub: https://www.welaunch.sh/ai-visibility ### ChatGPT SEO: how ChatGPT picks the products it names URL: https://www.welaunch.sh/ai-visibility/chatgpt ChatGPT names products from a short list of pages it finds through its own search crawler, so the job is to be readable by OAI-SearchBot and to be on the few pages it cites for your category. What ChatGPT cited in 110 live answers to buyer questions: fewer sources than other engines, Reddit in only 6%, and the same brands in every run only 28% of the time. The crawlers to allow and the fixes that matter. ### Perplexity SEO: how Perplexity picks what to cite URL: https://www.welaunch.sh/ai-visibility/perplexity Perplexity cites more pages per answer than any engine we tested, and it leans on Reddit and LinkedIn, so it rewards being mentioned in many places rather than ranking one page. Perplexity cited 10 sources per answer in our test of 103 live answers, with Reddit in 31% and LinkedIn in 12%. What it reads, the crawlers to allow and the fixes that matter. ### Gemini SEO: what Gemini reads before it names a product URL: https://www.welaunch.sh/ai-visibility/gemini Gemini grounds its answers in Google's search index, so a page Google cannot index is a page Gemini cannot cite, and Google-Extended controls whether it may use your content at all. What Gemini cited in 110 live answers to buyer questions: about 9 sources per answer, Reddit in 20%, and the Google-Extended control explained. The crawlers to allow and the fixes that matter. ### Google AI Mode and AI Overviews SEO: what Google cites URL: https://www.welaunch.sh/ai-visibility/google-ai-mode Google AI Mode and AI Overviews cite pages from the normal Google index, and in our test AI Mode leaned on Reddit and YouTube more than any other engine. Google AI Mode cited Reddit in 40% and YouTube in 18% of 111 live answers to buyer questions. Google's own eligibility rule for AI Overviews and AI Mode, the crawler to allow and the fixes that matter. ## Use cases ### AI visibility for SaaS: get named when buyers ask ChatGPT URL: https://www.welaunch.sh/ai-visibility/for/saas GEO and AI SEO for a small SaaS: which buyer questions to track, why one answer is not a measurement, and the fixes that get a product from 0 answers to named. ### AI visibility for agencies: client reports they cannot argue with URL: https://www.welaunch.sh/ai-visibility/for/agencies How an SEO or marketing agency can measure and report AI visibility honestly: every raw answer, how many runs named the client, the pages AI cites, and fixes drafted for review. ### AI share of voice: how often AI names you vs competitors URL: https://www.welaunch.sh/ai-visibility/for/share-of-voice Measure AI share of voice honestly: how many answers name you and each competitor across ChatGPT, Perplexity, Gemini, Google AI Mode and Claude, from repeated runs with every answer kept. ## Free tools - AI visibility checker: https://www.welaunch.sh/scan - AI crawler checker: https://www.welaunch.sh/tools/ai-crawler-checker - llms.txt generator: https://www.welaunch.sh/tools/llms-txt-generator ## Guides ### How to run an AI visibility audit in an hour URL: https://www.welaunch.sh/blog/ai-visibility-audit An AI visibility audit is a one-hour check of five things: whether crawlers can read your site, what ChatGPT, Perplexity, Gemini and Google AI answer for your top ten buyer questions, which pages they cite, whether you're one of them, and the single fix to make first. Run the steps in order. Don't try all of it at once. ## 1. Confirm the crawlers can read your pages Start here, because everything after it is wasted if the answer is no. Open your robots.txt and read it line by line. Look for blanket disallows, and look for rules that name AI crawlers specifically. Then load one of your key pages with JavaScript disabled, or fetch the raw HTML, and check that the actual product description, pricing and comparison text is in the source rather than painted in by a client-side script after load. Add llms.txt if you don't have one. Agency audits now treat [llms.txt deployment, crawler governance and LLM readiness](https://www.whitelabeliq.com/white-label-website-audit-services/ai-visibility-audit/) as part of the same technical pass as a [technical SEO overview for extractability and citation readiness](https://www.whitelabeliq.com/white-label-website-audit-services/ai-visibility-audit/). How to check it worked: fetch the page as plain HTML and search for your own product name and your pricing. If you can't find them in the raw text, a model probably can't either. Common mistake: assuming a page that ranks in Google is therefore readable by every engine. Different crawlers, different rules, different rendering budgets. Check the raw file, not the rendered one in your browser. Time budget: ten minutes. ## 2. Write ten buyer questions the way people actually ask them Not keywords. Questions, in the words a buyer would type into a chat box at 11pm. The standard approach is to start with your [ten highest-value transactional keywords and write three to five natural-language versions of each](https://www.yotpo.com/blog/ai-visibility-audit-steps/). That's stage one of a four-stage audit that runs [query identification, manual prompting, source mapping, then automated execution](https://www.yotpo.com/blog/ai-visibility-audit-steps/), and the whole point of stage one is [mapping intent rather than matching keywords](https://www.yotpo.com/blog/ai-visibility-audit-steps/). Group them across three intent types: [informational queries, comparative prompts, and direct brand questions](https://www.yotpo.com/blog/ai-visibility-audit-steps/). Aim for [a roughly even split, and include at least two prompts where a competitor is named alongside your brand](https://www.yotpo.com/blog/ai-visibility-audit-steps/). So for an invoicing tool, you'd end up with things like "best invoicing software for freelancers", "is [you] or [competitor] better for recurring billing", "does [you] do multi-currency invoices". How to check it worked: read your ten questions out loud. If any of them sounds like a search query rather than a sentence, rewrite it. Common mistake: writing only questions you'd win. The uncomfortable ones are the audit. Time budget: fifteen minutes. ## 3. Run each question on four engines and save every answer Stage two is [manual prompting and sentiment analysis, probing the engines directly](https://www.yotpo.com/blog/ai-visibility-audit-steps/). Open ChatGPT, Perplexity, Gemini and Google AI Mode side by side. Paste question one into each. Save the full answer text and every source link, not a summary. Log four columns per answer: engine, prompt, brands named in order, sources cited. One run per prompt is not enough, and this is the part most people skip. In welaunch's test of live AI answers (27 Sep 2026, variance section), only 9 of 32 brand appearances in ChatGPT answers (28%) were named in all four runs of the same prompt, and 6 of 21 brand appearances in Perplexity answers (29%) survived all four runs. Measured as set overlap, the brand lists ChatGPT returned for the same prompt across four runs matched at a mean Jaccard similarity of 0.54, and Perplexity at 0.57, per the same test. That means a brand you see once might be a coin flip. Forbes puts it mildly: results from manual queries vary, but [consistent patterns should emerge across prompters and query types](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/). In an hour you can realistically run each prompt twice per engine. Do that, and flag anything that appeared only once as unconfirmed. How to check it worked: every row in your sheet has a full answer saved, not a yes/no. You will want to re-read the wording later. Common mistake: logging "mentioned: yes". Position matters, context matters, and whether the model called you "a cheaper option" matters more than the tick. Time budget: twenty minutes, and this is the step worth stealing from the others. ## 4. Find the pages each engine is citing Stage three is [mapping source citations and tracking down the exact origins of what the models cite](https://www.yotpo.com/blog/ai-visibility-audit-steps/). Take every URL from step three and paste it into a second tab of your sheet. Count how often each domain appears. The engines behave very differently here, so a result on one tells you little about the others. How the four engines differ on sourcing, from welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US: | Engine | Avg. sources per answer | Answers with no source | Share citing reddit.com | |---|---|---|---| | ChatGPT | 5.8 across 110 answers | 7 of 110 | 6% (7 of 110) | | Perplexity | 10.1 across 103 answers | 0 of 103 | 31% (32 of 103) | | Gemini | 9.2 across 110 answers | 11 of 110 | 20% (22 of 110) | | Google AI Mode | 3.4 across 111 answers | 21 of 111 | 40% (44 of 111) | Perplexity hands you roughly three times the source list Google AI Mode does, and never came back empty in that test. Google AI Mode went sourceless in 21 of 111 answers. If you only audit one engine, you'll build a plan for a sourcing pattern the other three don't share. Don't assume your Google rankings carry over either. Only [16.7% of sources cited in Google AI Overviews overlap with the first page of organic results](https://www.yotpo.com/blog/ai-visibility-audit-steps/), and AI Overviews now appear on [48% of all tracked search queries](https://www.yotpo.com/blog/ai-visibility-audit-steps/). How to check it worked: sort your domain list by frequency. The top five domains are your actual target list. Common mistake: collecting citations and never counting them. The count is the finding. Time budget: ten minutes. ## 5. Check if Reddit, YouTube or a competitor is crowding you out Now look at what's on that top-five list instead of you. Across all 434 answers in welaunch's test (27 Sep 2026), 106 answers (24%) cited reddit.com. The weighting is lopsided by engine: Google AI Mode at 40% of answers, Perplexity at 31%, Gemini at 20%, ChatGPT at just 6%, per the same test. For buyer questions about choosing an AI visibility tool specifically, 22 of 80 answers cited reddit.com. For AI-visibility buyer questions, 12 of 63 answers cited reddit.com and 12 of 63 cited youtube.com. So "get mentioned on Reddit" is a sensible plan if your buyers use Google AI Mode or Perplexity, and close to irrelevant if they live in ChatGPT. Your citation table from step four tells you which. Then check which competitors keep showing up. In welaunch's test, Profound was named in 23 of 63 answers to AI-visibility buyer questions, with Otterly and Peec at 17 each. The pattern you want is not "who is biggest" but "which page about them is the engine reading". How to check it worked: for each of your ten questions you can name the one page an engine would have to read to mention you. Common mistake: treating a competitor's presence as a branding problem. It's usually a page problem. They're on a listicle, a directory, or a thread. You're not. ## What counts as the one fix to make first You will finish this audit with more things to fix than you can do at once. Pick one. The question to ask: across your ten prompts, which single missing source appears most often? If a comparison roundup gets cited by three engines for six of your questions, getting named in that roundup is worth more than ten blog posts. Three patterns, in the order they usually pay off: - You're absent from a source cited repeatedly across engines. Fix: get onto it. - You're named but described wrong. Fix: correct the page the model is reading, not your own homepage. - You're nowhere, on anything, for every prompt. Fix: start with directories, because they're the fastest index to get into. On that last one, welaunch's directory database lists [273 launch and listing directories](https://www.welaunch.sh/directories), of which [198 accept a free listing](https://www.welaunch.sh/directories). It breaks down into [163 SaaS and startup directories](https://www.welaunch.sh/directories), [95 AI tool directories](https://www.welaunch.sh/directories) and [15 agent and developer directories](https://www.welaunch.sh/directories), with [100 that accept AI products only](https://www.welaunch.sh/directories). Submitting to the handful that already appear in your citation table beats submitting to all of them. ## Do a free or low-cost version of this ai visibility check The whole audit above costs nothing but an hour and a spreadsheet. If you want a second opinion, free analyses exist: Amplitude's free AI visibility analysis gives [a visibility score and sentiment across top AI platforms including ChatGPT and Google AI Overview](https://amplitude.com/try-ai-visibility), plus [competitive rankings, critical topics and related prompts](https://amplitude.com/try-ai-visibility) and [personalised recommendations for AI discoverability](https://amplitude.com/try-ai-visibility). What a spreadsheet can't do is run itself. That's why the four-stage framework ends with [moving from audit to automated execution, turning passive findings into continuous updates](https://www.yotpo.com/blog/ai-visibility-audit-steps/). Your sheet is a snapshot of one afternoon. ## How often to repeat the audit Given the variance numbers from step three, once a quarter is too slow and once a day is more than most founders will sustain. Weekly is about right for a small prompt set. Two reasons. First, the same prompt returns different brand sets run to run: mean overlap of 0.54 on ChatGPT and 0.57 on Perplexity in welaunch's test, with only 28% and 29% of brand appearances holding across all four runs. A weekly run averages that noise out. Second, if you lean on a scoring tool instead, note that [tool scores are not universal across tools and the metrics behind them keep changing](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/). Compare a tool's score to its own previous score, never to another tool's. ## What a realistic timeline looks like after you fix something A new directory listing or a thread reply doesn't move an answer the same day. The honest expectation is that you're watching for a pattern, not an event, and [consistent patterns emerge across prompters and query types](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/) rather than in a single check. Practically: make one fix, keep running the same ten prompts weekly, and judge it on whether your name shows up in more runs per prompt over several weeks. Don't recheck an hour later and conclude it failed. Also don't swap your prompt list while you're measuring, or you've lost your baseline. ## Turning a one-hour audit into a standing habit The spreadsheet version works. It just decays, because nobody keeps rerunning the same prompts by hand every week. If you want it to keep running, that's what welaunch does: it asks your buyer questions on ChatGPT, Perplexity, Gemini and Google AI several times a week, keeps every answer in full so you can read exactly what each engine said, finds the pages the engines cite, and drafts the reply, listing or page that gets you onto one of them. It works from your own accounts, you review every draft and press submit, and on Reddit or Quora it names the product with disclosure rather than stuffing links. The method is the same five steps. The difference is that it happens whether or not you remember. ## FAQ ### How do you measure AI visibility? Count appearances across repeated runs, not single checks. Run the same ten buyer questions on each engine several times, log which brands are named and which sources are cited, then track how often your name appears per prompt over weeks. Core components of an audit include presence in AI responses, accuracy of positioning, and [competitive visibility](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/). ### What's the difference between an AEO audit and a GEO audit? In practice, very little. A GEO audit (generative engine optimisation) and an AEO audit (answer engine optimisation) both check what the engines say about you and which pages they're reading to say it. An LLM visibility audit is the same work under a third name. Pick whichever label your team uses and run the five steps. ### Can ChatGPT do an SEO audit on itself? You can ask it what it says about your category, and that's step three of this audit. What it can't do is tell you reliably whether it would name you, because the same prompt returns different brands across runs: in welaunch's 27 Sep 2026 test, only 28% of ChatGPT brand appearances held across all four runs of the same prompt. Run the prompt multiple times instead of asking the model to introspect. ### What is AI visibility, in plain terms? Whether an AI engine names your product when a buyer asks it a question, and whether it describes you correctly when it does. It depends heavily on which pages the engine cites, which is why source mapping matters more than your own site copy. ### Do backlinks still help with AI search citations? Less directly than in classic search. Forbes argues brands are [no longer beholden to backlinks the way they are in traditional SEO](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/), with AI platforms weighting [contextual relevance, brand authority and consistency across sources](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/) more heavily. Being named on a page the engine already cites is the more direct route. ### Can you pay to be cited in chat-based search results? Not from the engines themselves. You can pay for placement on sources the engines read, which is a different thing, and some directories charge for a listing. Your citation table from step four tells you whether that specific source is worth paying for. ## Sources - [AI Visibility Audit for Agencies — White Label IQ](https://www.whitelabeliq.com/white-label-website-audit-services/ai-visibility-audit/) - [AI Visibility Audit: Step-by-Step | Yotpo](https://www.yotpo.com/blog/ai-visibility-audit-steps/) - [How To Audit Your Brand’s AI Visibility](https://www.forbes.com/councils/forbesbusinesscouncil/2026/04/24/if-ai-cant-find-you-neither-can-your-customers-how-to-audit-your-brands-ai-visibility/) - [welaunch.sh](https://www.welaunch.sh/directories) - [Get Your Free AI Visibility Report](https://amplitude.com/try-ai-visibility) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [AI Overviews tracker comparison 2026: how to see whether Google's AI names you](https://www.welaunch.sh/blog/ai-overviews-trackers) - [AEO vs GEO: the same job, two names, and where they actually differ](https://www.welaunch.sh/blog/aeo-vs-geo) - [AI search optimization: a 7-step guide for SaaS teams](https://www.welaunch.sh/blog/ai-search-optimization) --- ### AEO vs GEO: the same job, two names, and where they actually differ URL: https://www.welaunch.sh/blog/aeo-vs-geo AEO vs GEO is mostly a naming argument, not a strategy split. AEO (answer engine optimization) started as formatting content for Google's snippets and AI Overviews. GEO (generative engine optimization) is the newer term for earning citations from ChatGPT, Perplexity and Gemini. In practice most teams run one strategy: clear, evidence-backed, structured content any answer engine can extract and cite. ## What is answer engine optimization (AEO)? AEO is [structuring content so search engines can extract and display it as a direct answer](https://business.adobe.com/blog/aeo-vs-geo). The term is older than the current AI search wave. It [emerged as Google began displaying featured snippets and knowledge panels](https://www.tryprofound.com/blog/aeo-vs-geo), back when the goal was to own the box at the top of the page rather than the blue link below it. The tactics were never a break from SEO. AEO [builds on traditional SEO principles and prioritizes formats search engines can extract](https://business.adobe.com/blog/aeo-vs-geo) into answer-style SERP features: featured snippets, People Also Ask boxes, AI Overviews. Progress describes it the same way, as [tactics that help content appear in more prominent parts of the SERP](https://www.progress.com/blogs/aeo-geo-seo-whats-difference) with added detail in the result itself. So: same crawling, same indexing, same pages. Different formatting discipline. Write the answer in the first two sentences under a question-shaped heading, and a parser can lift it. ## What is generative engine optimization (GEO)? GEO is the practice of [creating content that LLMs and AI search systems will reference, synthesize and cite](https://business.adobe.com/blog/aeo-vs-geo) when they generate a response. Jasper puts it more plainly: [optimizing content so models like ChatGPT and Gemini cite it as a trusted source](https://www.jasper.ai/blog/geo-aeo). Profound calls GEO [the newer term for optimizing content for AI-driven search tools](https://www.tryprofound.com/blog/aeo-vs-geo) like Google's SGE, Bing Chat and ChatGPT. The practical difference is what earns the citation. There is no position to win, so distinctiveness does the work. Adobe's framing: your content has to [offer something distinctive enough to be referenced, which means original research, unique data, authoritative perspectives and clearly stated claims supported by evidence](https://business.adobe.com/blog/aeo-vs-geo). A page that restates what six other pages already say gives a model no reason to name it. ## AEO vs GEO: what actually differs Three real distinctions survive once you strip the marketing out. The unit retrieved. AI search engines [do not index or retrieve whole pages; they break content into passages or chunks and retrieve the most relevant segments](https://www.tryprofound.com/blog/aeo-vs-geo). A featured snippet also pulls a passage, but from one page. In AI answers, [responses are often synthesized from multiple sources rather than pulled from a single page](https://business.adobe.com/blog/aeo-vs-geo). The query itself. Google AI Mode uses [query fan-out, where a complex query is broken into multiple related subqueries and executed in parallel](https://www.tryprofound.com/blog/aeo-vs-geo). You are not competing for one keyword. You are competing across a set of subquestions you never see. The success signal. Snippet work has a position. Citation work has a mention, or no mention. AI engines [cite content when it is perceived as factually accurate, up to date, well structured and authoritative](https://www.tryprofound.com/blog/aeo-vs-geo). ### SEO vs AEO vs GEO vs AIO at a glance | Term | Target surface | What it optimizes for | Success signal | Origin | |---|---|---|---|---| | SEO | Google and Bing result pages | Ranking a page for a query | Position on page one; [91% of searches never go past the first page](https://www.progress.com/blogs/aeo-geo-seo-whats-difference) | Not stated | | AEO | [Featured snippets, People Also Ask, AI Overviews](https://business.adobe.com/blog/aeo-vs-geo) | [Extractable direct answers](https://business.adobe.com/blog/aeo-vs-geo) | Appearing in the answer feature | [Google's featured snippets and knowledge panels](https://www.tryprofound.com/blog/aeo-vs-geo) | | GEO | [ChatGPT, Gemini and AI search systems](https://www.jasper.ai/blog/geo-aeo) | [Being referenced, synthesized and cited](https://business.adobe.com/blog/aeo-vs-geo) | Being cited or named in the generated answer | [Newer term for AI-driven search tools](https://www.tryprofound.com/blog/aeo-vs-geo) | | AIO | Not stated | Not stated | Not stated | Not stated | AIO is used loosely as a catch-all for AI optimization. There is no settled definition worth printing, which is part of the point. ## Is AEO part of GEO, or are they the same thing? Depends who you ask, and the disagreement is partly about branding rather than practice. Profound argues for keeping AEO and dropping GEO, on the grounds that [GEO is not ownable as a term and searching for it returns results about geography and geology](https://www.tryprofound.com/blog/aeo-vs-geo). Their second point is the same: [AEO is unique in search marketing, while GEO conflicts with geography, geology and geo-targeting](https://www.tryprofound.com/blog/aeo-vs-geo). That is a naming problem, not a methodology problem. Adobe takes the other route and keeps both labels, noting that [AEO and GEO do not negate each other and work together as connected elements of one content strategy](https://business.adobe.com/blog/aeo-vs-geo). Both positions describe the same workday. If your team is arguing about the difference between AEO and GEO in a planning doc, you have found a vocabulary dispute, not a strategic fork. ## Seo vs geo vs aeo: how do they differ from traditional SEO? Classic SEO assumed a click. That assumption is the part under pressure. Backlinko's research found [91% of Google searches never go past the bottom of the first page](https://www.progress.com/blogs/aeo-geo-seo-whats-difference), and only [0.44% of people click through to the second page](https://www.progress.com/blogs/aeo-geo-seo-whats-difference). Half of users [click a page within 9 seconds of seeing results](https://www.progress.com/blogs/aeo-geo-seo-whats-difference). And [more than half of all searches now end in no click at all](https://www.progress.com/blogs/aeo-geo-seo-whats-difference). Then the AI layer compounds it. Ahrefs found AI Overviews [cut click-through rates for top-ranking Google content by 58%, up from 34.5% the previous year](https://www.jasper.ai/blog/geo-aeo). And chat interfaces send far less traffic in the first place: ChatGPT has a [96% lower CTR than Google](https://www.jasper.ai/blog/geo-aeo). The implication is not "SEO is dead". It is that the measurable outcome moved. Ranking still matters because crawlable, trusted pages are what gets retrieved. But being named inside the answer is now a separate thing to track, and traffic alone will not tell you whether it happened. ## Is GEO taking over SEO, or is AEO replacing it? Neither, but the volume is real. ChatGPT [processes 2.5 billion prompts daily, 65% of which qualify as search](https://www.jasper.ai/blog/geo-aeo). That is a search surface with no ten blue links on it. At the same time, nothing in the GEO playbook replaces the basics. The engines still need to reach and parse your pages. Adobe's point holds: [AEO and GEO work together](https://business.adobe.com/blog/aeo-vs-geo) rather than cancelling each other. The honest version is that SEO became the delivery layer, and the thing you now optimize for sits on top of it. ## What ranking factors do LLMs actually use, and how do they differ from SEO signals? There is no public ranking algorithm to reverse-engineer here, but two structural facts matter. First, retrieval happens at [passage level, not page level](https://www.tryprofound.com/blog/aeo-vs-geo). A long guide is not one entry. It is dozens of candidate chunks, each of which has to make sense alone. Write sections that stand up without the paragraph above them. Second, the number of sources an engine pulls varies a lot, which changes your odds per answer. In welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US: Perplexity cited 10.1 sources per answer on average across 103 answers and gave no source in 0 of them; Gemini cited 9.2 sources across 110 answers with 11 unsourced; ChatGPT cited 5.8 sources across 110 answers with 7 unsourced; Google AI Mode cited 3.4 sources across 111 answers with 21 unsourced. Ten slots is a different game from three. On Perplexity, a decent third-party mention has a reasonable chance of making the set. On Google AI Mode, only the handful of sources it trusts most get in. The qualitative signal, per Profound, is content that reads as [accurate, current, well structured and authoritative](https://www.tryprofound.com/blog/aeo-vs-geo). That maps closely to what Adobe calls [evidence-backed, clearly stated claims](https://business.adobe.com/blog/aeo-vs-geo). ## How consistent are AI answers, and what does that mean for measuring GEO success? This is the part most GEO advice skips. The same prompt does not return the same answer. Per welaunch's test of live AI answers, 27 Sep 2026 (06-aeo-live.md, variance section): only 9 of 32 brand appearances (28%) in ChatGPT answers were named in all 4 runs of the same prompt. For Perplexity it was 6 of 21 (29%). Measured as set overlap, the brand sets ChatGPT named across 4 runs of the same prompt had a mean Jaccard similarity of 0.54 across 7 prompts that named any brand; Perplexity's was 0.57 across 5 prompts. So roughly a coin flip on whether a brand that showed up once shows up again. Two consequences. One: a single check proves nothing. If you ask ChatGPT whether it mentions you, ask four times before you draw a conclusion. Two: the metric is frequency, not presence. "Named in 3 of 4 runs this week" is a number you can move. "We appeared in ChatGPT" is not. ## Which AI engines should you prioritize first? Start with where your buyers actually ask, then look at how each engine sources. Forum content carries uneven weight. In welaunch's test of live AI answers, 27 Sep 2026 (05-differentiation.md, section 4): Google AI Mode cited reddit.com in 40% of answers (44 of 111), Perplexity in 31% (32 of 103), Gemini in 20% (22 of 110), and ChatGPT in just 6% (7 of 110). Across the full set, 106 of 434 answers (24%) cited reddit.com. Read that against the source counts above. Google AI Mode has the fewest slots and leans hardest on Reddit, which means a strong thread is disproportionately valuable there. ChatGPT barely touches Reddit, so the path in is editorial and listing pages instead. Perplexity's ten-ish sources per answer make it the easiest surface to break into early. If you only have time for one engine this quarter, pick the one your buyers name in sales calls. If nobody has told you, start with Perplexity because it always cites something, which makes the feedback loop legible. ## Do schema markup and structured data work the same for AEO and GEO? As far as the available evidence goes, yes, and for one reason: both depend on extraction. If a machine has to find the answer inside your page, clean headings, explicit question phrasing, tables and FAQ blocks all help it. There is no evidence that structured data needs a different shape per engine. Treat schema as hygiene rather than a GEO tactic. It makes your content parseable, and parseable content is the precondition for every surface in the table above. ## How AEO and GEO work together in one content strategy Jasper splits the tactics cleanly, which is useful even if the labels blur. AEO tactics: [directness over cleverness, structure for extraction, machine-readable language](https://www.jasper.ai/blog/geo-aeo). GEO tactics: [evidence-backed authority, clear structure, transparency signals](https://www.jasper.ai/blog/geo-aeo). Notice that "clear structure" appears on both lists. The combined instruction is short: - Answer the question in the opening lines, under a heading that matches how a person asks it. - Make every section self-contained, because retrieval happens per chunk. - Put a real number, a date or a source behind every claim that matters. - Say who you are and when you last updated the page. That is one workflow, not two. Which is why Adobe's conclusion that [AEO and GEO do not negate each other](https://business.adobe.com/blog/aeo-vs-geo) is the practical read. ## What should a small SaaS team actually do this week? Monday, three hours, in this order. Ask the engines what they currently say. Take the five questions your buyers actually ask before buying. Run each one four times on ChatGPT and Perplexity. Record which brands get named and how often. Given the variance numbers above, four runs is the minimum that tells you anything. Read the citations, not the answer. The sources under the answer are your target list. In welaunch's test (06-aeo-live.md), 12 of 63 answers to AI-visibility buyer questions cited reddit.com, and 12 of 63 cited youtube.com. For questions about choosing an AI visibility tool, 22 of 80 answers cited reddit.com. The cited pages are where the competitors you keep seeing got their mentions. In that same test, Profound was named in 23 of 63 answers to AI-visibility buyer questions, with Otterly and Peec at 17 each. Get onto the sources that appear repeatedly. Listings are the unglamorous version of this. welaunch's directory database lists [273 launch and listing directories](https://www.welaunch.sh/directories), of which [198 accept a free listing](https://www.welaunch.sh/directories) and [163 are SaaS and startup directories](https://www.welaunch.sh/directories). Pick the ones that already show up in your category's answers rather than submitting to all of them. If you would rather not run the prompts by hand every week, welaunch does that part: it asks your buyer questions on ChatGPT, Perplexity, Gemini and Google AI several times a week, keeps every answer in full, finds the pages those engines cite, and drafts the reply or listing that gets you onto them. The drafts go out from your own accounts after you review and press submit. On Reddit and Quora it names the product only, with disclosure, and never posts under an account of its own. ## FAQ ### What is the difference between GEO, AEO, and SEO? SEO aims at ranking a page in results. AEO [structures content so search engines can extract it as a direct answer](https://business.adobe.com/blog/aeo-vs-geo) in features like snippets and AI Overviews. GEO aims at [being referenced and cited by LLMs](https://business.adobe.com/blog/aeo-vs-geo) when they generate a response. The underlying work overlaps heavily. ### Is AEO a part of GEO? Some practitioners treat them as the same discipline under different names. Profound argues for keeping AEO because [GEO collides with geography, geology and geo-targeting](https://www.tryprofound.com/blog/aeo-vs-geo) as a search term. Adobe keeps both labels and says [they work together as connected parts of one strategy](https://business.adobe.com/blog/aeo-vs-geo). Pick whichever word your team will use consistently. ### How do you do SEO, AEO, and GEO at the same time? Write one page per buyer question, answer it in the opening lines, keep each section self-contained, and back every claim with a number or a source. That covers extraction for answer features and the [evidence-backed authority](https://www.jasper.ai/blog/geo-aeo) that LLM citation depends on. There is no second content calendar. ### How does generative engine optimization (GEO) actually work? Engines retrieve [passages rather than whole pages](https://www.tryprofound.com/blog/aeo-vs-geo) and synthesize an answer from several sources. Your page gets cited when it is accurate, current, structured and says something the other sources do not. Measuring it means running the same prompt repeatedly and tracking how often you are named. ### Why do Reddit threads show up so often in AI answers? They show up unevenly. In welaunch's test of live AI answers, 27 Sep 2026 (05-differentiation.md, section 4), Google AI Mode cited reddit.com in 40% of answers and Perplexity in 31%, while ChatGPT cited it in only 6%. If Google AI Mode matters to your buyers, forum presence matters more than it does elsewhere. ### Do I need separate content for ChatGPT versus Google AI Overviews? Not separate content, but different distribution. The page quality signals are the same across engines. What differs is sourcing behaviour: in welaunch's 27 Sep 2026 test, Google AI Mode cited 3.4 sources per answer on average while Perplexity cited 10.1, so the same page has very different odds of making the cut. ## Sources - [AEO vs. GEO: Differences and Examples](https://business.adobe.com/blog/aeo-vs-geo) - [AEO vs. GEO: Why they're the same thing (and why we prefer AEO)](https://www.tryprofound.com/blog/aeo-vs-geo) - [AEO, GEO & SEO: What’s the Difference?](https://www.progress.com/blogs/aeo-geo-seo-whats-difference) - [What is Generative Engine Optimization? GEO vs AEO vs SEO Guide 2026 | The Jasper Blog](https://www.jasper.ai/blog/geo-aeo) - [welaunch.sh](https://www.welaunch.sh/directories) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [AI search optimization: a 7-step guide for SaaS teams](https://www.welaunch.sh/blog/ai-search-optimization) - [AI Overviews tracker comparison 2026: how to see whether Google's AI names you](https://www.welaunch.sh/blog/ai-overviews-trackers) - [SaaS content marketing: the content types to write, in order, to get ranked and cited](https://www.welaunch.sh/blog/saas-content-marketing) --- ### SaaS content marketing: the content types to write, in order, to get ranked and cited URL: https://www.welaunch.sh/blog/saas-content-marketing Write SaaS content marketing in this order: one proprietary data or product-experience piece, then bottom-funnel comparison and definition pages, then pillar and cluster hubs, then distribution to the pages engines already cite. This order follows how buyers and AI engines tend to encounter content, proof first, then comparison, then broader context, which is not how content calendars usually get built. ## 1. Pick one buyer question your product experience answers best Before you open a keyword tool, pick the single question your team can answer better than anyone else because of what the product does and what you've seen customers do with it. FinTech writer Vivek Shankar put it plainly in Semrush's guide: ["Many SaaS companies begin with SEO and then focus on the rest, getting it all backward. Your product comes first--get that story in place before doing anything else."](https://www.semrush.com/blog/saas-content-marketing/) Webflow is a useful model here, because its content [positions the platform as a tool for achieving much more than just a visually appealing site](https://www.semrush.com/blog/saas-content-marketing/). The content argues the product's point of view, not just its feature list. How to check it worked: write the question as a sentence a buyer would actually type or say out loud. If a competitor could publish the identical answer word for word, it isn't your question yet. The common mistake: starting with a 60-topic keyword map before anyone has written down what the product is for. You end up with pages that rank for terms your buyers don't convert on. ## 2. Write a proprietary data or teardown piece before any generic guide Your first published piece should contain something nobody can copy: your own numbers, your own analysis of someone else's numbers, or a teardown of a real thing. ProfitWell built this into a format. They create [Pricing Page Teardowns that use well-known brands and tear down their pricing strategy](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). The brands supply the interest, ProfitWell supplies the judgement. Ahrefs runs the other model. Their blog posts [present an SEO problem and a solution, are founded on keyword research, and feature their software as part of the solution](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). That approach took them past [$40m in ARR with no outside funding](https://thedigitalelevator.com/blog/saas-content-marketing-examples/), at roughly [$800k in revenue per employee](https://thedigitalelevator.com/blog/saas-content-marketing-examples/), with [no paid spending on Google Ads](https://thedigitalelevator.com/blog/saas-content-marketing-examples/) and [no conference attendance](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). Both models work. Pick one and keep the format, so the second piece is faster than the first. How to check it worked: can someone quote one sentence of it with a number in it and have that sentence make sense on its own? That is what an AI answer does with your page. The common mistake: publishing "what is X" as piece one. Nobody links to it, no engine needs it from you, and you've spent a week proving you can write. ## 3. Build the objective comparison page, competitors included Buyers comparing tools search for comparisons. If your page only argues for you, they bounce to one that doesn't. Dacast's strategy includes a [25-company roundup post that shows all of their pros and cons](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). The site now ranks for [over 106,000 keywords according to Ahrefs](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). A comparison page that gets reused by an engine usually has: one line saying what each tool is for, a price or plan name where it's public, who it suits, and who it doesn't. Tables help, as long as every cell is true. Write "Not stated" where you don't know, instead of guessing. How to check it worked: ask ChatGPT and Perplexity your category's "best X for Y" question and see whether your page is among the sources. If an engine cites a competitor's roundup instead of yours, read theirs and find what it covers that you skipped. The common mistake: a "comparison" where every competitor has a vague weakness and you have none. Readers spot it instantly, and so do the people who write the roundups engines actually cite. ## 4. Turn your best page into a pillar with cluster posts Once one page performs, build around it instead of starting a new topic. HotJar uses a [pillar and cluster (hub and spoke) format for their heatmaps content](https://thedigitalelevator.com/blog/saas-content-marketing-examples/), and the heatmaps page [ranks #1 for the keyword 'heatmaps'](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). Atlassian's Kanban page shows how much one hub can hold: a [definition resource, video, hub and spoke sidebar menu, in-body featured content section, screenshots, infographics, grids, and free resources](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). Most of that is reused material, not new writing. ProfitWell's library reaches [over 55,500 keywords according to Ahrefs](https://thedigitalelevator.com/blog/saas-content-marketing-examples/), which is what happens when one format gets repeated across a topic for years. How to check it worked: the hub should gain rankings when you publish a spoke. If it doesn't move after three spokes, your spokes are probably on a different topic than you think. The common mistake: ten unconnected posts with no hub, each linking to the homepage. ## 5. Check keyword difficulty before you commit a writer to it Big volume is not the same as a winnable page. 'Kanban' has [47,000 searches per month at keyword difficulty 86/100](https://thedigitalelevator.com/blog/saas-content-marketing-examples/), with an [equivalent PPC value of $94.4K per month](https://thedigitalelevator.com/blog/saas-content-marketing-examples/). That PPC number tells you why the page is hard: everyone wants it. A term that expensive is a year-two target with a hub behind it, not a solo blog post. Spend the first quarter on the questions your competitors' pages answer badly. How to check it worked: keep a short kill list of terms you deliberately skipped and why. Review it each quarter and move one item up when your domain can carry it. The common mistake: assigning a difficulty-86 term to a freelancer with a short, generic brief and calling the result a failure of content marketing for SaaS. ## 6. Set a realistic timeline and team size for your stage Content results arrive in quarters, not weeks, and the published examples are all multi-year. Webflow's SEO traffic grew [from 25k visitors a month to 500K a month, a 1,900% increase](https://www.marketermilk.com/blog/saas-content-marketing). Zapier drives [over 2.6 million organic visits per month as of May 2025](https://www.semrush.com/blog/saas-content-marketing/). A smaller and more relatable benchmark: Marketer Milk reached [50,000 visitors a month from Google search within one year and 60 blog posts](https://www.marketermilk.com/blog/saas-content-marketing). Sixty posts in a year is roughly five a month. One competent writer with a subject matter expert to interview can do that. You do not need a large content team to start. Budget isn't always the constraint either. Semrush documents one SaaS content project that [brought in over $400K from a $1K content budget](https://www.semrush.com/blog/saas-content-marketing/) and another that drove [200K+ product sign-ups with no ad spend](https://www.semrush.com/blog/saas-content-marketing/). How to check it worked: measure early on leading indicators like pages indexed, impressions and first rankings, then check pipeline impact further out. The common mistake: hiring four writers in month one and firing the program in month five. ## 7. Measure pipeline influence, not traffic or post count Traffic is the easiest number to report and the least useful one to act on. Directive's position is blunt: [most B2B content strategies fail because they prioritize easy-to-create content over high-converting content that directly influences purchase decisions](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/). Their claim is that [revenue-first content prioritization delivers 2-3x higher conversion rates than traditional awareness-first approaches](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/). Measurement has to match how people buy. Directive notes that [B2B buyers research in non-linear patterns across multiple stakeholders](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/), and recommends tracking [deal velocity and pipeline influence through multi-touch attribution](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/). How to check it worked: every month, list the five pages that appear most often in the journeys of closed-won deals. Write more like those. The common mistake: a dashboard with sessions at the top. Nobody in a board meeting can act on sessions. ## 8. Distribute to the pages AI engines already cite Publishing on your blog is one of two jobs. The other is getting named on the pages engines pull from when they answer your buyers' questions. In welaunch's test of 434 live AI answers to buyer questions across seven software categories (27 Sep 2026, US), 106 of 434 answers (24%) cited reddit.com. The split by engine matters, because the engines behave nothing alike. ### Where each engine actually cites its sources | Engine | Avg sources per answer | Share citing reddit.com | Answers with no source | |---|---|---|---| | ChatGPT | 5.8 (110 answers) | 6% (7 of 110) | 7 of 110 | | Perplexity | 10.1 (103 answers) | 31% (32 of 103) | 0 of 103 | | Gemini | 9.2 (110 answers) | 20% (22 of 110) | 11 of 110 | | Google AI Mode | 3.4 (111 answers) | 40% (44 of 111) | 21 of 111 | Source: welaunch test of live AI answers, 27 Sep 2026. Google AI Mode cites the fewest sources and leans hardest on Reddit. Perplexity cites the most and always shows them. That changes your distribution plan: a roundup placement is worth more for Perplexity, a genuine Reddit presence is worth more for Google AI Mode. How to check it worked: run your top ten buyer questions through all four engines and write down every URL cited. That list is your distribution target list. The common mistake: treating a blog post as distribution. Publishing is production. Distribution is getting onto the third-party pages already in the citation set. ## 9. Track whether you're named consistently, not just once A single AI answer naming your product proves very little, because the same prompt returns different brands on different runs. In welaunch's test, only 9 of 32 brand appearances (28%) in ChatGPT answers were named in all 4 runs of the same prompt, and 6 of 21 (29%) in Perplexity. Measured as set overlap, ChatGPT's brand lists across 4 runs matched at a mean Jaccard similarity of 0.54, and Perplexity's at 0.57 (welaunch test of live AI answers, 27 Sep 2026). Consistency is what separates the leaders from the occasional mentions. In the AI-visibility category in that same test, Profound was named in 23 of 63 answers, with Otterly and Peec at 17 each. How to check it worked: ask each question four times, on each engine, and record the share of runs that name you. Track that share over months. The common mistake: screenshotting one good answer and declaring the channel solved. ## 10. Get your product onto the specific pages engines cite The last step is mechanical. Take the citation list from step 8 and work through it: the roundups that need your tool added, the comparison pages with an outdated entry, the directories that feed both. Directories are the easiest starting point because the work is bounded. welaunch's directory database lists [273 launch and listing directories](https://www.welaunch.sh/directories), of which [198 accept a free listing](https://www.welaunch.sh/directories), [16 are free with a badge or backlink](https://www.welaunch.sh/directories), and [56 charge](https://www.welaunch.sh/directories). By category it splits into [163 SaaS and startup directories](https://www.welaunch.sh/directories), [95 AI tool directories](https://www.welaunch.sh/directories), and [15 agent and developer directories](https://www.welaunch.sh/directories), with [100 accepting AI products only](https://www.welaunch.sh/directories). That is also the part welaunch does for you. It asks your buyer questions on ChatGPT, Perplexity, Gemini and Google AI several times a week, keeps every answer in full, finds the pages those answers cite, and drafts the reply, listing or page that gets you onto them. Everything goes out from your own accounts after you review it and press submit. On Reddit and Quora it names the product only, with disclosure, and never stuffs in links. How to check it worked: re-run the same questions a month later and count how many of your target pages now mention you, then how many answers name you. The common mistake: buying 200 directory listings in a week and skipping the ten pages that actually appear in the citations. ## FAQ ### What is SaaS content marketing? It means creating and sharing content like blogs, videos and more to [attract, convert and retain users for subscription-based software products](https://www.semrush.com/blog/saas-content-marketing/). In practice it covers your blog, comparison pages, documentation-adjacent guides and original research. The difference from general content marketing is that the product usually appears in the answer, not just the footer. ### How is content marketing for B2B SaaS different from regular content marketing? The buying group is the main difference. Directive notes that [B2B buyers research in non-linear patterns across multiple stakeholders](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/), so one person reads the pricing teardown while another reads the security page. That pushes measurement toward [deal velocity and pipeline influence through multi-touch attribution](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/) rather than last-click. ### How many writers does a SaaS company need to start a content program? Fewer than most teams assume. Marketer Milk reached [50,000 visitors a month from Google search within one year and 60 blog posts](https://www.marketermilk.com/blog/saas-content-marketing), which is about five posts a month. One strong writer plus regular access to someone who knows the product can hold that pace. ### Is ChatGPT considered SaaS? It's sold as a subscription software product delivered over the web, which is the usual definition of SaaS. For a content marketing SaaS plan, what matters more is that it's also a channel: in welaunch's test, ChatGPT cited 5.8 sources per answer on average across 110 buyer-question answers (27 Sep 2026). Those sources are pages you can get onto. ### What is the 3 3 2 2 2 rule of SaaS? For a SaaS content marketing strategy, the figures in steps 6 and 7 are more useful targets. ### How long before SaaS content marketing shows revenue impact? Plan on quarters. Webflow's content-driven SEO traffic grew [from 25k to 500K visitors a month](https://www.marketermilk.com/blog/saas-content-marketing), a multi-year curve. Judge the early period on indexing and impressions, the following months on rankings and sign-ups, and only then on closed revenue. ## Sources - [SaaS Content Marketing: The 9-Step Roadmap for Success](https://www.semrush.com/blog/saas-content-marketing/) - [5 SaaS Content Marketing Examples to Use in 2026 | Digital Elevator](https://thedigitalelevator.com/blog/saas-content-marketing-examples/) - [My best SaaS content marketing strategy guide for 2025 | Marketer Milk](https://www.marketermilk.com/blog/saas-content-marketing) - [A Guide to Content Marketing for B2B SaaS - Directive](https://directiveconsulting.com/blog/guide-to-b2b-saas-content-marketing/) - [welaunch.sh](https://www.welaunch.sh/directories) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [SaaS marketing in 2026: the channels that still work for a small team](https://www.welaunch.sh/blog/saas-marketing) - [The 'X Alternative' Page Playbook: How Early-Stage Startups Steal Search Traffic From Bigger Competitors](https://www.welaunch.sh/blog/the-x-alternative-page-playbook-how-early-stage-startups-steal-search-traffic-fr) - [The 90-Day SEO Content Plan for a Startup That Just Launched](https://www.welaunch.sh/blog/the-90-day-seo-content-plan-for-a-startup-that-just-launched) --- ### Lovable SEO: why AI crawlers see a blank page on your site, and the fix URL: https://www.welaunch.sh/blog/fix-javascript-only-sites-for-ai-crawlers Lovable and Vite apps built with client-side rendering often ship an empty HTML shell with one div and a script tag, because the page is built in the browser. Most AI crawlers, including GPTBot, ClaudeBot and PerplexityBot, do not run JavaScript, so they read nothing. Lovable SEO starts with fixing that: server-side rendering or prerendering, so finished HTML goes out instead. The steps below are in the order you should do them. ## 1. Check which stack your app is actually running Before you change anything, find out what you built on. There are [three Lovable stacks in circulation](https://encited.com/blog/is-lovable-seo-friendly): Vite client-side rendered built before April 2026, Vite client-side rendered built after April 2026, and TanStack Start, which renders on the server. That matters because [most Lovable apps are single-page applications that rely on client-side rendering](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/), and because Lovable's own server-rendering support [only went out for sites deployed after April 20, 2026](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/). A project you started last year is on the old path whether or not your editor looks modern. How to check it worked: open your project files and look for the TanStack Start entry points versus a plain `index.html` plus `main.tsx`. If you see an `index.html` with one root div, you are on Vite. Common mistake: assuming an app is server-rendered because Lovable shipped SSR at some point. The deploy date of your project is what decides, not the date you last edited it. ## 2. View source to see what crawlers actually receive This is the real diagnostic. Load your live page, then view source (not the inspector, which shows the DOM after JavaScript has run). Ctrl+U in most browsers. Or run `curl https://yoursite.com` in a terminal. [On Vite projects, the HTML that arrives first is close to empty](https://encited.com/blog/is-lovable-seo-friendly): an empty div with id root and a script tag. That is the whole document. [On TanStack projects, actual headings and paragraphs appear in the source HTML](https://encited.com/blog/is-lovable-seo-friendly). How to check it worked: search the raw source for your H1 text and the first paragraph of your page. If they are there as plain text, a crawler can read them. If they are not, nothing on that page exists for a bot that does not execute scripts. Common mistake: using the browser devtools Elements panel and seeing your full page, then concluding you are fine. The Elements panel runs your JavaScript for you. Crawlers often do not. ## 3. Understand why this breaks AI search visibility specifically Google is more forgiving here than the AI engines. [Google splits crawler work into two passes](https://encited.com/blog/is-lovable-seo-friendly): the first fetches HTML and indexes what it finds, and a second pass runs JavaScript, but only if the page is queued for it. So a client-rendered page can eventually get indexed. AI crawlers mostly skip that second pass entirely: | Crawler | Runs JavaScript? | |---|---| | [OAI-SearchBot (ChatGPT Search)](https://encited.com/blog/is-lovable-seo-friendly) | No | | [GPTBot (OpenAI training)](https://encited.com/blog/is-lovable-seo-friendly) | No | | [PerplexityBot](https://encited.com/blog/is-lovable-seo-friendly) | No | | [ClaudeBot](https://encited.com/blog/is-lovable-seo-friendly) | No | | [Applebot (Apple Intelligence)](https://encited.com/blog/is-lovable-seo-friendly) | Limited | | [Google-Extended (Gemini)](https://encited.com/blog/is-lovable-seo-friendly) | Yes, via Googlebot | This is not theoretical. [Encited tested more than 50 live Lovable sites and found that ChatGPT, Claude and Gemini returned responses carrying no page content](https://encited.com/blog/is-lovable-seo-friendly) when asked about pages on Vite projects. The model had nothing to summarise, so it said nothing useful. So javascript seo is now two problems, not one. Ranking in classic search is the old problem. Being readable by a bot that fetches once and leaves is the new one. How to check it worked: once you have a fix in place, paste a page URL into ChatGPT or Perplexity and ask it to summarise the page. If it describes your actual content instead of guessing from the URL, the fix landed. Common mistake: treating Google Search Console's rendered screenshot as proof that AI engines can read the page. Those are different crawlers with different budgets. ## 4. For new Lovable apps: confirm server-side rendering is on If you started the project recently, this step may already be done. [New Lovable apps ship with server-side rendering that renders pages as complete HTML before they reach the browser](https://lovable.dev/seo-aeo). How to check it worked: repeat step 2. View source on a deployed page and look for your H1 and body copy in the raw HTML. That is the only confirmation that counts. Common mistake: testing on the preview URL inside the editor rather than the deployed domain. Test what the public gets. ## 5. For existing Vite apps: check the prerendered snapshot reaches AI crawlers, not just Google Lovable did not leave older projects without anything. [Apps built on the previous tech stack get pre-rendered snapshots so crawlers can access content](https://lovable.dev/seo-aeo). The open question is which crawlers. A snapshot that serves to Googlebot and not to GPTBot or ClaudeBot solves half your problem. The documentation does not spell out which user agents are covered, so verify it yourself rather than assuming. How to check it worked: fetch your page with a changed user agent string and compare the output to a normal fetch. In a terminal: ``` curl -A "GPTBot" https://yoursite.com curl -A "Googlebot" https://yoursite.com curl https://yoursite.com ``` If the Googlebot response has your headings and the GPTBot response is an empty root div, you have found the gap. Fix it in step 6. Common mistake: running this once on your homepage and calling it done. Test a blog post and a deep product page too. Snapshot coverage is often uneven across routes. ## 6. Decide: migrate to server-side rendering, or add a prerendering service Two real options for an existing Vite or Bolt project. The right one depends on how much of your app you are willing to touch this month. | Option | What it does | Setup time | Best for | |---|---|---|---| | Migrate to a server-rendered stack | Renders pages as complete HTML before they reach the browser, as [new Lovable apps do](https://lovable.dev/seo-aeo) | Not stated | Apps you plan to keep for years, content-heavy sites, anything where the marketing pages matter more than the app shell | | Prerender.io | [Crawlers receive pre-rendered pages instead of waiting for JavaScript to load](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/) | [30 to 45 minutes](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/) | Existing projects you do not want to rebuild, sites deployed before the SSR rollout | A migration rewrites routing and data loading, which takes real time on an AI-built app as the agent works through the changes. The prerendering route leaves your code alone and puts a layer in front of it. How to check it worked: whichever path you take, run the curl commands from step 5 again against three different routes. Raw HTML with real content, or it did not work. Common mistake: picking the migration because it sounds cleaner, then stalling halfway with half the routes converted. If you are not going to finish it in one sitting, take the prerendering route first and migrate later. A half-migrated app is worse than a prerendered one. ## 7. Check that data fetched after load is not invisible Server-side rendering does not automatically cover your data. [On TanStack projects, data from Lovable Cloud, Supabase or a remote API is fetched in the browser after the initial HTML](https://encited.com/blog/is-lovable-seo-friendly), so it is not in what a crawler reads. This is the one that catches people who think they are done. Your layout, nav and static copy render on the server. Your blog posts, your pricing tiers and your directory listings load from the database a moment later, in the browser, where the crawler is not watching. How to check it worked: view source on a page whose main content comes from your database. A blog post is the clearest test. If you see the shell but no post body, your data is client-side. Common mistake: fixing the homepage, which is usually hardcoded, and never testing a database-driven route. Those are your long-tail pages and they are the ones AI engines are most likely to surface. ## 8. Verify the built-in SEO features behave on your stack Meta tags, structured data and sitemaps all sit downstream of rendering. On a server-rendered stack, titles and descriptions are in the HTML that goes out. On a client-rendered Vite app, anything written into the head by JavaScript after load is subject to the same problem as your body copy, unless it is covered by the [pre-rendered snapshot](https://lovable.dev/seo-aeo). How to check it worked: curl a few pages and grep for `` and `og:` tags. Each page should have its own, not the same default title repeated across the site. Common mistake: setting per-page meta tags through a React head component and assuming every crawler picks them up. Confirm in raw source, page by page, for at least a sample. ## 9. Run an SEO and AI search review as a checkpoint Once the plumbing is right, get a second opinion. [Lovable's SEO and AI search review is free on all tiers](https://lovable.dev/seo-aeo), which makes it a reasonable checkpoint rather than a purchase decision. [Chatting with Semrush data comes at no extra cost through September 15, 2026](https://lovable.dev/seo-aeo). How to check it worked: run the review before and after your rendering change and compare what it flags. The issues that disappear are the ones your fix actually addressed. Common mistake: running the review first and treating its checklist as the work. A perfect meta description on a page no crawler can read is worth nothing. Rendering first, review second. ## 10. Go beyond crawlability: get cited once engines can read you Being readable is the floor, not the goal. An AI engine reading your page does not mean it will name you when a buyer asks which tool to use. There is real run-to-run variance in which brands get named. In welaunch's test of live AI answers on 27 Sep 2026, only 9 of 32 brand appearances (28%) in ChatGPT answers were named in all four runs of the same prompt, and 6 of 21 (29%) in Perplexity. The brand sets ChatGPT returned for the same prompt across four runs overlapped by a mean Jaccard similarity of 0.54, and Perplexity by 0.57, in the same test. Ask the same question twice and you often get a different shortlist. Which means the work after crawlability is about the sources those answers pull from: comparison posts, directory listings, forum threads, review pages. Those get cited whether or not your own site does. That second half is what welaunch handles. It asks your buyers' questions on ChatGPT, Perplexity, Gemini and Google AI several times a week, keeps every answer in full so you can read what each engine said, finds the pages the engines cite, and drafts the reply, listing or page that gets you onto one. You review each draft and press submit, from your own accounts. It never posts under an account of its own, and on Reddit and Quora it names the product only, with disclosure, rather than stuffing links. How to check it worked: ask your top buyer question on each engine, four times, a week apart, and record whether you are named. One run is noise. Common mistake: fixing rendering, seeing no change in AI answers after three days, and concluding the fix failed. Crawl and re-index cycles are slower than that, and naming depends on sources beyond your own domain. ## FAQ ### Does Lovable support SEO out of the box? Partly, and it depends on your stack. [New Lovable apps ship with server-side rendering that produces complete HTML before the browser gets involved](https://lovable.dev/seo-aeo), and [older apps on the previous tech stack get pre-rendered snapshots](https://lovable.dev/seo-aeo). Lovable also includes a [free SEO and AI search review on all tiers](https://lovable.dev/seo-aeo). Check your own raw HTML before trusting any of it. ### Is there an AI tool that can do SEO for me? No tool does the whole job unattended, but parts of it are automatable. Lovable's own review tool runs checks on your pages for free, and [chatting with Semrush data is included at no extra cost through September 15, 2026](https://lovable.dev/seo-aeo). For AI search specifically, welaunch runs your buyer questions across the engines on a schedule and drafts the work to get you onto the pages those engines cite, with you approving each submission. ### Is Lovable good for building websites that rank? It can be, once rendering is sorted. The default problem is that [most Lovable apps are single-page applications relying on client-side rendering](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/), and client-rendered pages ship an empty shell. Server-rendered builds put real headings and paragraphs in the source, which is what both Google and AI crawlers need. ### What is the 80/20 rule in SEO? For a React or Vite app, the 80/20 is rendering. If crawlers cannot read your pages, keyword work, internal linking and schema markup produce nothing. Confirm raw HTML contains your content, then spend time on everything else. This is the single biggest difference between react seo on a client-rendered app and on a server-rendered one. ### Can I migrate an existing Lovable project to server-side rendering? Yes, though [Lovable's built-in SSR was rolled out only for websites deployed after April 20, 2026](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/), so an older project needs either a stack migration or a prerendering layer. [Prerender.io integration with Lovable sites usually takes 30 to 45 minutes](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/) and leaves your code untouched. Migrating is more work but removes the dependency. ### Which Lovable stack am I actually on? There are [three](https://encited.com/blog/is-lovable-seo-friendly): Vite client-side rendered built before April 2026, Vite client-side rendered built after April 2026, and TanStack Start with server rendering. The fastest test is view source on a live page. [An empty div with id root and a script tag means Vite](https://encited.com/blog/is-lovable-seo-friendly); [visible headings and paragraphs mean TanStack](https://encited.com/blog/is-lovable-seo-friendly). The same test works for bolt seo and vite seo audits on any other builder. ## Sources - [Is Lovable SEO Friendly in 2026? Vite vs TanStack Explained | Encited Blog](https://encited.com/blog/is-lovable-seo-friendly) - [How To Make Lovable Website SEO-Friendly (A Tested Guide)](https://prerender.io/blog/how-to-make-lovable-websites-seo-friendly/) - [SEO and AI search for apps built with AI | Lovable](https://lovable.dev/seo-aeo) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [AI search optimization: a 7-step guide for SaaS teams](https://www.welaunch.sh/blog/ai-search-optimization) - [SaaS marketing in 2026: the channels that still work for a small team](https://www.welaunch.sh/blog/saas-marketing) - [AI Overviews tracker comparison 2026: how to see whether Google's AI names you](https://www.welaunch.sh/blog/ai-overviews-trackers) --- ### AI search optimization: a 7-step guide for SaaS teams URL: https://www.welaunch.sh/blog/ai-search-optimization AI search optimization is the work of getting your product named and cited when buyers ask ChatGPT, Perplexity, Gemini or Google AI for a recommendation. Seven steps, in order: confirm crawler access, map the buyer questions, test for repeated answers, find the cited pages, get onto those pages, build your own answer pages, then re-measure. Most of the numbers below come from a test run on 27 Sep 2026 that pulled 434 live AI answers from ChatGPT, Perplexity, Gemini and Google AI Mode, covering buyer questions across seven software categories (welaunch test of live AI answers, 27 Sep 2026, 06-aeo-live.md). ## 1. Verify that AI crawlers can access your content Start here because every later step depends on it. Open your robots.txt and look for the bots that actually feed AI answers. Semrush lists [OAI-SearchBot, GPTBot, ChatGPT-User, CCBot, ClaudeBot, Claude-User and Claude-SearchBot](https://www.semrush.com/blog/ai-search-optimization/) among the crawlers commonly blocked there. Many SaaS sites block them by inheritance, not by decision: a security plugin, a CDN rule, or a robots.txt copied from a template three years ago. The second access problem is rendering. AI crawlers [often skip JavaScript-heavy, client-rendered pages](https://www.walkersands.com/about/blog/ai-search-optimization/). If your pricing table or comparison page only exists after hydration, it may as well not exist. How to check it worked: fetch your key pages with JavaScript disabled and confirm the text you care about is in the raw HTML. Then check your server logs for hits from those crawler user agents over a two-week window. Common mistake: treating this as a one-time fix. A new firewall rule or bot-management setting can reintroduce the block months later, silently. ## 2. Map the buyer questions AI engines are actually answering You are not optimizing for keywords. You are optimizing for the questions a buyer types in full sentences, like "best tool for a small team" or "alternatives to Y for a small team". Write out twenty to forty of these from sales calls, support tickets and your own churn interviews. Two mechanics matter here. Google's guidance describes [retrieval-augmented generation, also called grounding](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), which pulls fresh material through core Search ranking systems to answer a prompt. And [query fan-out](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), where the model fires off a set of related queries of its own to gather more. So one buyer question can trigger several searches you never wrote down. Cover the sub-questions: pricing, integrations, limits, who it is not for. How to check it worked: every question on your list should be one a real buyer asked out loud, and each should produce a meaningfully different answer when you run it. Common mistake: writing prompts that contain your brand name. "Is [your product] good for teams?" tells you nothing. The questions that matter are the ones where you are not mentioned yet. ## 3. Test whether your brand is named consistently, not just once Run each question at least four times per engine. The answers move. In the 434-answer test, only 9 of 32 brand appearances (28%) in ChatGPT answers were named in all four runs of the same prompt, and 6 of 21 (29%) in Perplexity (welaunch test of live AI answers, 27 Sep 2026, variance section). Measured as set overlap, the brand lists ChatGPT produced for the same prompt across four runs matched at a mean Jaccard similarity of 0.54 across seven prompts that named any brand; Perplexity came in at 0.57 across five such prompts (same test, variance section). How to check it worked: you have a count, not a screenshot. Per question, per engine: named in how many of four runs. Common mistake: celebrating a single screenshot. Being named once in four runs is a 25% hit rate, and it is not the same thing as being the default answer. ## 4. Find the pages each AI engine is actually citing This is the step that turns measurement into a to-do list. For each buyer question, collect the URLs cited in the answer. Those pages are your targets. The engines do not behave alike: | Engine | Avg sources per answer | Answers with no source | Share citing reddit.com | |---|---|---|---| | ChatGPT | 5.8 (110 answers) | 7 | 6% (7 of 110) | | Perplexity | 10.1 (103 answers) | 0 | 31% (32 of 103) | | Gemini | 9.2 (110 answers) | 11 | 20% (22 of 110) | | Google AI Mode | 3.4 (111 answers) | 21 | 40% (44 of 111) | Source: welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US. Across the whole set, 106 of 434 answers (24%) cited reddit.com (welaunch test of live AI answers, 27 Sep 2026). Reddit is not a side channel. On Google AI Mode it appeared in 40% of answers (44 of 111). Category changes the mix too. Among 63 answers to AI-visibility buyer questions, 12 cited reddit.com and 12 cited youtube.com; among 80 answers about choosing an AI visibility tool, 22 cited reddit.com (same test). How to check it worked: a ranked list of domains by how often they appear across your questions, with the specific URLs under each. Common mistake: optimizing for the engine you personally use. Google AI Mode cites few sources and leans hard on Reddit. Perplexity cites roughly three times as many per answer. The same work does not pay off equally on both. ## 5. Get your SaaS onto the pages that get cited Now go down the ranked list. Three kinds of target, usually: listicles and review roundups, directories and listings, and community threads. Directories are the least glamorous and the most tractable. welaunch's public directory database lists [273 launch and listing directories](https://www.welaunch.sh/directories), of which [198 accept a free listing](https://www.welaunch.sh/directories), [16 are free with a badge or backlink](https://www.welaunch.sh/directories) and [56 charge](https://www.welaunch.sh/directories). By type it splits into [163 SaaS and startup directories](https://www.welaunch.sh/directories), [95 AI tool directories](https://www.welaunch.sh/directories) and [15 agent and developer directories](https://www.welaunch.sh/directories), with [100 accepting AI products only](https://www.welaunch.sh/directories). Pick the ones that already show up in your citation list first. Community threads need a different hand. On Reddit and Quora, write an actual answer to the question being asked, name your product once, and say you built it. welaunch handles this step by drafting the reply, listing or page, then having the founder review and submit it from their own account; on Reddit and Quora it names the product with disclosure and does not stuff in links. How to check it worked: the page you targeted now contains your product, and it still appears in the citation list for that question a month later. Common mistake: going after the biggest-name page instead of the cited page. A high-traffic roundup that no engine cites for your questions does nothing for this project. ## 6. Build your own pages that AI engines can quote directly AI engines [extract responses at the paragraph level](https://www.walkersands.com/about/blog/ai-search-optimization/). Write so a single paragraph can be lifted and still make sense: claim, number, qualifier. No paragraph that depends on the three above it. Structure helps the parser. Use [semantic HTML5 elements like article, section and footer](https://www.walkersands.com/about/blog/ai-search-optimization/), and add [Article, Organization, FAQ and Author schema](https://www.walkersands.com/about/blog/ai-search-optimization/). Substance matters more. Google's own guidance warns that commodity content like ["7 Tips for First-Time Homebuyers"](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) is typically built on common knowledge and adds little, and contrasts [a first-hand review, which carries a perspective from personal experience, with a summary that restates what already exists](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). Your own usage data, your own benchmark, your own failure cases: that is the part no one else can restate. One small mechanical point: AI crawlers [will not click links, so name your sources in the text](https://www.walkersands.com/about/blog/ai-search-optimization/) rather than hiding the attribution in an anchor. How to check it worked: paste a paragraph of your page into an engine and ask what it says. If the answer is vague, the paragraph is not self-contained. Common mistake: publishing twenty thin comparison pages at once. That is the fast route to the problem described in step 11 below. ## 7. Re-measure: track citation frequency over time, not a single snapshot Set a cadence. Weekly is enough for most teams. Run the same question set, on the same engines, and log how many runs named you and which sources were cited. Share of voice is the useful number. In the 434-answer test, Profound was named in 23 of 63 answers to AI-visibility buyer questions, with Otterly and Peec at 17 each (welaunch test of live AI answers, 27 Sep 2026). That shape, one leader and a cluster behind, is what you are trying to move. This is the step teams skip, so it is worth automating. welaunch runs the founder's buyer questions on all four engines several times a week, keeps each answer in full, and tracks which pages the engines cite over time. How to check it worked: you can plot your named-in-X-of-4 rate by month and by engine. Common mistake: changing the question wording between runs. You lose the comparison. ## What is AI search optimization, and how is it different from SEO? AI search optimization is the practice of making your content [frequently referenced and prominently featured by AI search systems](https://www.semrush.com/blog/ai-search-optimization/) like ChatGPT, AI Overviews and Perplexity. It targets [mentions and citations rather than rankings](https://www.semrush.com/blog/ai-search-optimization/), and goes by other names too: [generative engine optimization (GEO), or SEO for AI search](https://www.semrush.com/blog/ai-search-optimization/). It is not a replacement for SEO. Google states that its generative features are [rooted in core Search ranking and quality systems](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), which is why [SEO best practices remain relevant](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), and ranking well in ordinary results [improves your odds of being used as grounding content](https://www.walkersands.com/about/blog/ai-search-optimization/). The reason to care: G2's 2025 Buyer Behavior Report found [29% of buyers now use AI-powered search tools more often than Google](https://www.walkersands.com/about/blog/ai-search-optimization/), Walker Sands reports [almost 60% of searches ending without a click](https://www.walkersands.com/about/blog/ai-search-optimization/), and visitors arriving from non-Google AI systems like ChatGPT [convert 4.4 times better than organic search visitors](https://www.semrush.com/blog/ai-search-optimization/). ## How content formats and recency affect what gets cited Two things shape what gets pulled. First, format: extraction happens [at the paragraph level](https://www.walkersands.com/about/blog/ai-search-optimization/), so a direct answer near the top of a section beats a long wind-up. Second, the content has to be worth quoting. A [first-hand review](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) gets picked over a restatement, and [commodity tip-list content](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) adds little. Traditional rank is not the gate it is in classic search. Semrush reports ChatGPT cited pages ranking [at position 21 or worse almost 90% of the time](https://www.semrush.com/blog/ai-search-optimization/). A page that never cracks page one can still be the one quoted. ## B2B vs B2C SaaS: does AI search optimization differ? The mechanics are the same; the weighting changes. For B2B, third-party credibility does the heavy lifting: where backlinks were the SEO signal, [mentions from reputable outlets, analysts and reviewers carry even more weight](https://www.walkersands.com/about/blog/ai-search-optimization/) in AI search. Analyst coverage, review sites and category roundups are the pages worth chasing. For both, write the way buyers speak. AI search optimization [rewards natural language and context rather than keyword matching](https://www.walkersands.com/about/blog/ai-search-optimization/). And for B2B especially, the smaller volume is offset by quality: AI-referred visitors [convert 4.4 times better than organic](https://www.semrush.com/blog/ai-search-optimization/). ## How long until you show up in AI answers? Longer than a campaign, shorter than classic SEO in some cases. Because ChatGPT cites pages ranking [21 or worse nearly 90% of the time](https://www.semrush.com/blog/ai-search-optimization/), you do not have to win page one first. But grounding still runs through search, so [ranking well improves your odds](https://www.walkersands.com/about/blog/ai-search-optimization/), and that takes months. Also plan for the surface itself moving. AI Overviews appeared on [about 16% of searches as of November 2025, down from a peak near 25% in July](https://www.semrush.com/blog/ai-search-optimization/). Volumes shift under you. ## Common mistakes that waste the effort Mass-producing near-identical pages. Google is explicit: creating separate content mainly to [manipulate rankings or generative AI responses violates the scaled content abuse policy](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), and AI-assisted drafts still have to [meet the Search Essentials and spam policies](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). Assuming a link is a citation. Crawlers [will not click through, so name sources in text](https://www.walkersands.com/about/blog/ai-search-optimization/). Ignoring variance. With only 28% of ChatGPT brand appearances and 29% of Perplexity ones holding across all four runs (welaunch test, 27 Sep 2026), a single good answer is noise until you repeat the prompt. ## FAQ ### What is the 30% rule for AI? There is no official rule by that name, but the number comes up in consistency testing. In a run of 434 live answers, 28% of ChatGPT brand appearances and 29% of Perplexity ones held across all four runs of the same prompt (welaunch test of live AI answers, 27 Sep 2026). Treat roughly a third as the share of mentions you can count on repeating, and test everything four times. ### What is the 80/20 rule in SEO? It is the Pareto principle applied to search: a small share of your pages and queries produces most of your results. In AI search optimization the same shape holds for cited sources. A handful of domains will account for most of the citations across your buyer questions, so rank them by frequency and work from the top. ### Is SEO still worth it in 2026? Yes. Google says its generative features are [rooted in core Search ranking and quality systems](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), and ranking well [improves your odds of being used as grounding content](https://www.walkersands.com/about/blog/ai-search-optimization/). The twist is that ChatGPT cited pages ranking [21 or worse nearly 90% of the time](https://www.semrush.com/blog/ai-search-optimization/), so poor rank does not disqualify you. ### What is AI search optimization called? It also goes by [generative engine optimization (GEO), or simply SEO for AI search](https://www.semrush.com/blog/ai-search-optimization/). Some teams say AI visibility optimization or answer engine optimization. The work is the same: get named and cited in AI answers rather than ranked in blue links. ### Are there tools to track AI visibility and citation frequency? Yes, and the engines will name some for you. In 63 answers to AI-visibility buyer questions, Profound was named 23 times, with Otterly and Peec at 17 each (welaunch test of live AI answers, 27 Sep 2026). Whatever you pick, the minimum useful output is: how often each question named you, per engine, over time. ### What is the ideal word count for content AI engines cite? Word count is the wrong unit. Engines [extract at the paragraph level](https://www.walkersands.com/about/blog/ai-search-optimization/), so the question is whether any single paragraph answers a question on its own. Write self-contained paragraphs with the claim and the number in them, and let the page be as long as the topic needs. ## Sources - [How to optimize for AI search results in 2026](https://www.semrush.com/blog/ai-search-optimization/) - [AI Search Optimization: How to Make Your Brand AI-Visible | Walker Sands](https://www.walkersands.com/about/blog/ai-search-optimization/) - [Google's Guide to Optimizing for Generative AI Features on Google Search | Google Search Central | Documentation | Google for Developers](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) - [welaunch.sh](https://www.welaunch.sh/directories) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [SaaS marketing in 2026: the channels that still work for a small team](https://www.welaunch.sh/blog/saas-marketing) - [AI Overviews tracker comparison 2026: how to see whether Google's AI names you](https://www.welaunch.sh/blog/ai-overviews-trackers) - [The Founder's Referral Program Playbook: Turning Your First 100 Users Into a Launch Growth Engine](https://www.welaunch.sh/blog/the-founder-s-referral-program-playbook-turning-your-first-100-users-into-a-laun) --- ### SaaS marketing in 2026: the channels that still work for a small team URL: https://www.welaunch.sh/blog/saas-marketing SaaS marketing is the promotion of subscription software, and in 2026 it runs on two tracks at once: classic search, and AI answer engines like ChatGPT and Perplexity that answer the buyer's question directly. Those engines often cite Reddit threads, review sites and comparison posts when answering buyer questions. For a small team, that pushes content, SEO, directories and community presence ahead of paid ads and big outreach teams. ## What is SaaS marketing, and how is it different from product marketing? SaaS marketing is [promoting software sold on subscription](https://qualaroo.com/blog/saas-marketing-strategies/). The difference from traditional marketing is the revenue shape: traditional marketing [chases a one-time sale, SaaS marketing is built around a long-term relationship and a recurring subscription](https://www.simpletiger.com/blog/saas-product-marketing). You can win the sale and still lose the money, three months later, to churn. SaaS product marketing is a narrower job inside that. A product marketing manager usually [keeps launches and campaigns tied to customer needs, runs market and competitor research, writes messaging frameworks and sales material, coordinates launches across teams, and feeds customer data back into strategy](https://www.simpletiger.com/blog/saas-product-marketing). A [2024 McKinsey and Company report found companies with product marketing managers grow faster than those without](https://www.simpletiger.com/blog/saas-product-marketing). In a four-person company, that role is usually the founder on Tuesday afternoons. The funnel most teams work from has [four stages: top, middle, bottom and retention](https://www.artisan.co/blog/saas-marketing). At the top you [create content that addresses common customer pain points](https://www.artisan.co/blog/saas-marketing). In the middle, leads [know they have a problem and are comparing solutions](https://www.artisan.co/blog/saas-marketing). At the bottom you reach for [testimonials, case studies, live demos, free trials and consultations with sales](https://www.artisan.co/blog/saas-marketing). After purchase, marketing keeps going to [increase adoption, prevent churn and move people onto higher plans](https://www.artisan.co/blog/saas-marketing). Google has a name for the mess in the middle of all this. It calls the stretch where buyers explore and evaluate many options at once [the messy middle](https://qualaroo.com/blog/saas-marketing-strategies/). In 2026, a growing share of that exploring happens inside a chat window. ## Why buyers now ask AI before they search, and what that changes A buyer who used to type "best helpdesk software for small teams" into Google now types it into ChatGPT, and gets back a short list of tools with reasons. They never see your landing page. They see whatever the model read. So the question becomes: what does the model read? In welaunch's test of 434 live AI answers to buyer questions across seven software categories (27 Sep 2026, US), 106 of the 434 answers, 24%, cited reddit.com. Not a vendor blog. Reddit. The engines also differ wildly in how much they cite at all. ### How often each AI engine cites reddit.com and how many sources it gives per answer | Engine | Answers tested | Average sources cited | Answers citing reddit.com | |---|---|---|---| | ChatGPT | 110 | 5.8 | 7 (6%) | | Perplexity | 103 | 10.1 | 32 (31%) | | Gemini | 110 | 9.2 | 22 (20%) | | Google AI Mode | 111 | 3.4 | 44 (40%) | All figures from welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US. In the same test, ChatGPT gave no source at all in 7 of its 110 answers, Gemini in 11 of 110, Google AI Mode in 21 of 111, and Perplexity in none of its 103. Read the table sideways and the strategy falls out. Google AI Mode shows few sources and leans hardest on Reddit, so the thread that ranks matters enormously there. Perplexity shows many sources, so there are more slots to be in and a single citation carries less weight. ChatGPT barely touches Reddit but still cites sources for most answers. ## Which marketing channels actually deliver ROI for a small SaaS team in 2026? Rough order, for a team with more time than money. Content first. [Helpful, solution-focused resources educate your audience, build credibility and attract qualified visitors](https://www.simpletiger.com/blog/saas-product-marketing). This is also the raw material the AI engines chew on, and the thing you can point at from a Reddit reply without being a nuisance. SEO second, and treat it as the same job as content. SEO [creates a steady source of inbound traffic by helping people find your brand when they search for solutions](https://www.simpletiger.com/blog/saas-product-marketing). That is what SaaS inbound marketing is: the traffic arrives because the answer was already there. Email third. It [builds relationships, keeps users engaged, and gives you a direct way to guide customers through the lifecycle](https://www.simpletiger.com/blog/saas-product-marketing). It is the cheapest channel you own outright. Then the paid and push channels, which work but cost either money or hours. [PPC brings immediate visibility and lets you test ideas quickly](https://www.simpletiger.com/blog/saas-product-marketing). [Cold email is reps emailing leads to sell the value of your solution, with the goal of booking a meeting](https://www.artisan.co/blog/saas-marketing). [LinkedIn social selling is reps engaging target decision-makers, mostly by interacting with posts and sending DMs](https://www.artisan.co/blog/saas-marketing). The honest case for both: [direct outreach is a fast way to generate leads because it is proactive instead of waiting](https://www.artisan.co/blog/saas-marketing). The honest cost: it stops the day the person doing it stops. ## How much time and team does each channel need? Pick channels by who owns them on Monday morning, not by a spreadsheet of potential. One person can realistically own content and SEO together, because they are the same work: pick the question, write the answer, publish it, keep it current. One person can own email, if the sequences are written once and edited rarely. Directory listings are a project, not a channel. Someone blocks out a few sessions, works through a list, and then it is done apart from occasional updates. Reddit and community presence need a named human with a real account and some standing in the subreddit. You cannot rota this. A brand new account dropping links risks being removed, and the thread you wanted to be in stays the thread that ranks. Paid ads and cold outreach are the two that scale with headcount and stop without it. If you have no one who can watch an ad account weekly, you do not have a paid channel, you have a leak. ## What conversion rates and CAC should you actually expect? Be suspicious of any benchmark quoted at you without a sample size. The numbers that matter are the ones from your own account. Three to track from week one. [CAC is the dollar amount it costs you to gain a new paying customer on a given marketing channel](https://kinsta.com/blog/saas-marketing/). [CLV is how much a single paying customer is worth to your business on average](https://kinsta.com/blog/saas-marketing/). [Churn rate is the percentage of paying customers who cancel during a period](https://kinsta.com/blog/saas-marketing/). Calculate CAC per channel, not in aggregate. An aggregate CAC hides the fact that one channel is carrying the other four. And watch churn next to CAC: a channel that brings cheap customers who leave in two months is worse than an expensive channel that brings customers who stay. ## Which free or low-cost tools can a small team use across channels? Directories are the cheapest distribution a new SaaS has, and most of them cost nothing. welaunch's directory database lists [273 launch and listing directories](https://www.welaunch.sh/directories). Of those, [198 accept a free listing](https://www.welaunch.sh/directories), [16 are free if you display a badge or backlink](https://www.welaunch.sh/directories), and [56 charge](https://www.welaunch.sh/directories). For everything else, the pattern that works on a small budget is: free tier of a keyword tool, your own analytics, a cheap email sender, and a writing habit. The spend is time. ## Should you focus on new customers or expanding existing ones? Both, but measure the expansion side properly. [Monthly recurring revenue is the total fees paid by all your paying customers each month, excluding flat sums for annual or quarterly subscriptions and one-time payments](https://kinsta.com/blog/saas-marketing/). Expansion shows up there without any new logos at all. Net Promoter Score is the quick read on whether expansion is even available to you. A customer scoring [9 or 10 is a promoter](https://kinsta.com/blog/saas-marketing/), [7 or 8 is neutral](https://kinsta.com/blog/saas-marketing/), and [1 to 6 is a detractor](https://kinsta.com/blog/saas-marketing/). Detractors are the churn you are about to pay for. If acquisition and retention are competing for the same week, retention usually wins on arithmetic. You already paid the CAC. ## How should a small team use SaaS directories and review portals? Directories do two jobs now. They send a trickle of direct traffic, and they are pages that AI engines read when someone asks for options in your category. Work by category rather than alphabetically. welaunch's database has [163 saas and startup directories](https://www.welaunch.sh/directories), [95 ai tool directories](https://www.welaunch.sh/directories), and [15 agent and developer directories](https://www.welaunch.sh/directories). [100 of the directories accept AI products only](https://www.welaunch.sh/directories), so if you are not an AI product, a large block of the list is not for you and you should skip it rather than waste a session on rejections. Start with the [198 free ones](https://www.welaunch.sh/directories). Decide separately whether you are willing to run a badge for the [16 that require one](https://www.welaunch.sh/directories). Only consider the [56 paid listings](https://www.welaunch.sh/directories) once you have seen whether the free ones send anything. Write the listing copy once, properly, with the same positioning line everywhere. Consistent wording across many pages is what makes a model confident about what your product is. ## Why does Reddit matter so much more now, and what should you do about it? The citation numbers again, per engine, from welaunch's 27 Sep 2026 test: Google AI Mode cited reddit.com in 40% of answers (44 of 111), Perplexity in 31% (32 of 103), Gemini in 20% (22 of 110), ChatGPT in 6% (7 of 110). It holds inside narrow categories too. In the same test, 12 of 63 answers to AI-visibility buyer questions cited reddit.com, as did 22 of 80 answers to questions about choosing an AI visibility tool. For the AI-visibility questions, youtube.com also appeared in 12 of 63 answers, which is worth noting if you have ever wondered whether a plain screen recording is worth the afternoon. What to actually do: Find the threads that already rank for your category question. Those are the pages being read. Reply in them as a real person with a real account, answer the question that was asked, and disclose that you built the thing. Do not drop a link. A link gets you removed, and removal takes the comment out of the index you were trying to enter. Answer the questions nobody answered well. Old threads with one thin reply are easy to improve and often sit high in search. Be consistent about your product's one-line description so the model keeps seeing the same claim. This is the slow part, and it is what welaunch does: it asks your buyers' questions on ChatGPT, Perplexity, Gemini and Google AI several times a week, finds the pages those engines cite, and drafts the reply or listing that puts you on one. You review it and press submit from your own account. On Reddit and Quora it names the product only, with disclosure, and never adds a link. ## How do you get named when buyers ask ChatGPT, Perplexity or Gemini about your category? First, accept that a single check tells you very little. In welaunch's test, only 9 of 32 brand appearances in ChatGPT answers (28%) were named in all four runs of the same prompt, and in Perplexity only 6 of 21 (29%). Measured as overlap between the brand sets returned across four runs, ChatGPT scored a mean Jaccard similarity of 0.54 across 7 prompts that named any brand, Perplexity 0.57 across 5. So if you ask ChatGPT once and see your name, you have learned almost nothing. Ask the same question repeatedly over weeks and count how often you appear. Second, know who you are up against. In the AI-visibility category in that test, Profound was named in 23 of 63 answers, with Otterly and Peec named in 17 each. The leaders in any category are the ones whose names turn up in the sources the engines read. Third, work on the sources rather than the model. You cannot edit ChatGPT. You can get into the ranked comparison post, the review portal page, the directory listing and the Reddit thread that it reads. ## How do SaaS companies stand out from the competition? Not on price. Price is the easiest thing for a competitor to match and the fastest way to attract customers who churn. What holds up: being clearly the tool for one specific kind of buyer, and saying so in the first line of every page and listing. A narrow claim is easier for a human to remember and easier for a model to repeat. "Scheduling for dental clinics" beats "scheduling for teams." The other thing that holds up is evidence a stranger can check. [Testimonials, case studies, live demos and free trials](https://www.artisan.co/blog/saas-marketing) do the work that adjectives cannot. So does a real person answering a hard question in public under their own name. ## FAQ ### What exactly is a SaaS product? It is software you pay for on a subscription rather than buying once, usually accessed through a browser and hosted by the vendor. [SaaS marketing is the promotion of software sold this way](https://qualaroo.com/blog/saas-marketing-strategies/). The defining feature for marketers is that the customer can leave every month, so retention is part of marketing rather than something that happens after it. ### What is the 3-3-3 rule for marketing? It is a copywriting guideline, not a SaaS-specific framework, about grabbing attention quickly and making your case fast. For a SaaS landing page it mostly means your first line should say who the product is for and what it does, with no preamble. ### Is Netflix a SaaS model? Netflix is a subscription business, and it shares the mechanics that matter here: recurring revenue, churn, and lifetime value. Most people classify it as streaming or media rather than software as a service, since the product is content rather than a tool you work in. The marketing maths is the same either way. ### What are the 5 key marketing strategies for SaaS? In rough order of return for a small team: content, SEO, email, directory and review-site presence, and community presence where your buyers already discuss the category. [Content educates and builds credibility](https://www.simpletiger.com/blog/saas-product-marketing), [SEO produces steady inbound traffic](https://www.simpletiger.com/blog/saas-product-marketing), and [email guides customers through the lifecycle](https://www.simpletiger.com/blog/saas-product-marketing). The last two now feed AI answers as well as humans. ### Which B2B SaaS marketing channels should a small team use first? Content and SEO, because they compound and because they are what AI engines read. Then free directory listings, since [198 of the 273 directories in welaunch's database accept a free listing](https://www.welaunch.sh/directories). Add email once you have signups. Hold off on paid ads until you know your CAC by channel. ### What are the different types of SaaS marketing strategies? They sort by funnel stage. Top of funnel is demand generation through [content addressing customer pain points](https://www.artisan.co/blog/saas-marketing). Middle of funnel serves people [comparing solutions](https://www.artisan.co/blog/saas-marketing). Bottom of funnel uses [case studies, demos and free trials](https://www.artisan.co/blog/saas-marketing). Retention marketing works after purchase to [drive adoption, cut churn and sell upgrades](https://www.artisan.co/blog/saas-marketing). ## Sources - [16 Successful B2B SaaS Marketing Strategies: Ultimate Guide](https://qualaroo.com/blog/saas-marketing-strategies/) - [SaaS Product Marketing: A Comprehensive Guide for Marketers](https://www.simpletiger.com/blog/saas-product-marketing) - [What is SaaS marketing? Everything you need to know to start](https://www.artisan.co/blog/saas-marketing) - [7 Key Principles of SaaS Marketing (With Formulas, Examples, and Tools)](https://kinsta.com/blog/saas-marketing/) - [welaunch.sh](https://www.welaunch.sh/directories) - welaunch test of live AI answers, 27 Sep 2026 - welaunch's test of 434 live AI answers to buyer questions in seven software categories, 27 Sep 2026, US ## Related on welaunch - [The Best Startup Directories to Submit Your Product to in 2026 (Ranked by Traffic and SEO Value)](https://www.welaunch.sh/blog/the-best-startup-directories-to-submit-your-product-to-in-2026-ranked-by-traffic) - [AI Overviews tracker comparison 2026: how to see whether Google's AI names you](https://www.welaunch.sh/blog/ai-overviews-trackers) - [Launch Teardown 2026: We Tracked One Product Across Product Hunt, Reddit, and Hacker News for 30 Days](https://www.welaunch.sh/blog/launch-teardown-2026-we-tracked-one-product-across-product-hunt-reddit-and-hacke) --- ## Definitions ### A/B Testing URL: https://www.welaunch.sh/glossary/a-b-testing ## What A/B Testing Is A/B testing (also called split testing) splits traffic randomly between two versions of something, a landing page, an email subject line, a pricing table, an onboarding flow, and measures which version wins on a metric you define ahead of time, like signup rate or click-through rate. Version A is usually the current experience (the control) and version B is the change you're testing (the variant). Whichever version produces a statistically significant lift gets rolled out to everyone. The core idea is isolating one variable at a time so you know the outcome was caused by your change, not by chance, seasonality, or who happened to visit that day. ## Why It Matters for Early-Stage Founders Early on, you have almost no data and every decision (headline, CTA copy, pricing, onboarding steps) is a guess. A/B testing replaces opinion-driven debates ("I think the blue button converts better") with evidence. It's also one of the few growth tools available before you have a large team or big budget: you don't need new features, just traffic and a hypothesis. That said, A/B testing has a floor. If you get 50 visitors a week, you'll wait months for a valid result. Early-stage founders should mostly use A/B testing for high-traffic, high-leverage pages (your homepage, signup flow, pricing page) and use qualitative methods (user interviews, session recordings) everywhere else until traffic grows. ## How It Works: The Basic Steps 1. **Pick one metric** that matters (e.g., signup conversion rate, not "engagement" broadly). 2. **Form a hypothesis**: "Changing the CTA from 'Get Started' to 'Start Free Trial' will increase signups because it removes ambiguity about cost." 3. **Build variant B** and randomly split traffic 50/50 between A and B. 4. **Run the test** until you hit your required sample size, not just "until it looks like a winner." 5. **Check for statistical significance** before declaring a winner. 6. **Ship the winner** (or, if flat, learn and move to the next test). ## Calculating Sample Size and Significance The two numbers founders most often skip are minimum sample size and confidence level, which is how most "winning" tests turn out to be noise. **Simple formula for required sample size per variant:** ``` n ≈ 16 * p * (1 - p) / d² ``` Where `p` is your baseline conversion rate and `d` is the minimum detectable effect (the smallest lift you actually care about), both as decimals. **Example:** Your signup page converts at 5% (p = 0.05) and you want to detect a lift to 6% (a 1 percentage point, or 20% relative, improvement, so d = 0.01). ``` n ≈ 16 * 0.05 * 0.95 / (0.01)² ≈ 7,600 visitors per variant ``` That means roughly 15,200 total visitors needed before you can trust the result, at a standard 95% confidence level. If your site gets 2,000 visitors a week, that's nearly two months just to detect a modest lift. This is why founders with low traffic should test bigger, bolder changes (a full page redesign, not a button color) that might produce a 2x lift instead of a 20% one, since bigger effects need smaller samples. ## A Worked Example Suppose you A/B test two homepage headlines over three weeks: | Variant | Visitors | Signups | Conversion Rate | |---|---|---|---| | A (control) | 4,800 | 240 | 5.0% | | B (variant) | 4,750 | 285 | 6.0% | B shows a 20% relative lift. Before rolling it out, run these numbers through a significance calculator (many are free online). At this sample size, a jump from 5.0% to 6.0% typically clears the 95% confidence threshold, meaning there's less than a 5% chance the difference is due to random variation. Only then do you ship B to 100% of traffic. ## Common Mistakes - **Peeking and stopping early.** Checking results daily and stopping the moment B "pulls ahead" inflates false positives dramatically. Decide your sample size in advance and stick to it. - **Testing too many variables at once.** Changing headline, image, and CTA simultaneously means you won't know what actually drove the result. That's multivariate testing, a different (and more data-hungry) method. - **Ignoring statistical significance entirely.** A 5.2% vs 5.4% conversion rate on 300 visitors is noise, not a winner. - **Testing low-traffic pages.** A pricing page with 40 visitors a month will never reach significance in a reasonable timeframe. Prioritize your highest-traffic funnel steps. - **Optimizing a metric that doesn't matter.** A headline that boosts clicks but not paid signups isn't a real win. Always tie the test metric to a business outcome. ## Benchmarks and Rules of Thumb - Run tests for at least one full business cycle (usually 1 to 2 weeks minimum) to smooth out day-of-week effects. - Aim for at least a few hundred conversions per variant before trusting results; thousands is safer for small effect sizes. - Use 95% confidence as the standard bar before shipping a change; some teams use 90% for low-risk, easily-reversible tests. - If you're pre-product-market-fit with limited traffic, prioritize qualitative feedback and big directional bets over formal A/B tests, and save rigorous split testing for after you have consistent traffic, something teams often revisit around launch time, which is also where a checklist from a resource like welaunch.sh can help sequence what to test first. --- ### Activation Metric URL: https://www.welaunch.sh/glossary/activation-metric ## What Counts as an Activation Metric An activation metric is not a vague feeling of "engagement." It is a single, well-defined action (or short sequence of actions) that reliably predicts a user will stick around because they have experienced your product's core value. If a user completes this action, they are "activated." If they don't, they are just a signup, not a customer. Examples across different products: - **Slack**: A team sends 2,000 messages - **Dropbox**: A user saves one file to a folder - **Duolingo**: A user completes their first lesson - **Calendly**: A user shares their scheduling link and gets a meeting booked Notice the pattern. None of these are "signed up" or "logged in." They are the moment the product actually does the thing it promised. ## Why Activation Matters for Early-Stage Founders Most startups die from a leaky bucket, not a lack of top-of-funnel traffic. You can spend heavily on ads or land a great launch on Product Hunt, but if 90% of signups never activate, none of that traffic converts into a real business. Activation is the bridge between acquisition and retention. It answers the question every founder should be obsessed with: **"Are new users actually getting value, or are they just poking around and leaving?"** Tracking activation forces founders to get specific about what value even means for their product. Vague goals like "improve onboarding" become measurable: "increase the percentage of signups who create their first project within 24 hours." ## How to Define Your Activation Metric A good activation metric usually satisfies three conditions: 1. **It correlates with retention.** Users who complete this action come back later at a much higher rate than users who don't. 2. **It is achievable early.** Ideally within the first session or first day, not week three. 3. **It reflects real value, not busywork.** "Filled out profile" is usually a vanity step. "Sent first invoice" or "invited a teammate" is real usage. ### Finding It With Data If you already have some users, run a simple correlation analysis: 1. Pick a retention window (e.g., users still active at day 30). 2. List candidate actions users take in their first session (created a project, uploaded a file, connected an integration, invited a collaborator). 3. For each action, compare the day-30 retention rate of users who did it versus users who didn't. 4. The action with the widest retention gap is your activation metric candidate. **Example:** | First-session action | Day-30 retention (did action) | Day-30 retention (didn't) | |---|---|---| | Created a project | 48% | 6% | | Invited a teammate | 71% | 15% | | Uploaded a file | 22% | 18% | Here, "invited a teammate" has the biggest retention gap, suggesting collaboration is your real activation moment, not the individual project creation step. ### Calculating Your Activation Rate Once defined, track it as a simple ratio: **Activation Rate = (Number of users who complete the activation action) / (Number of new signups) x 100** Example: 1,000 signups in a month, 280 complete the activation action within 7 days. Activation Rate = 280 / 1,000 = 28% ## Benchmarks (Directional, Not Gospel) Activation rate benchmarks vary wildly by product complexity, but rough ranges founders use as sanity checks: - **Simple consumer apps**: 40 to 60% activation is healthy - **B2B SaaS with some setup required**: 20 to 40% is common - **Complex enterprise tools**: 10 to 25%, often because onboarding requires configuration or a second user If you're under 15% for a self-serve product, that's usually a signal your onboarding flow, not your product, is the problem. ## Common Mistakes - **Picking a metric too early in the funnel.** "Completed signup" is acquisition, not activation. It doesn't tell you if value was delivered. - **Picking a metric too late.** If activation requires five steps and three days, you're measuring power users, not new-user success. - **Never revisiting it.** As your product evolves (new features, new ICP), your activation metric can go stale. Revisit it every 6 to 12 months. - **Optimizing the metric instead of the value.** Teams sometimes nudge users to complete the tracked action without actually improving the underlying experience, inflating the number without improving retention. ## Using It in Practice Once defined, your activation metric becomes a north star for the onboarding team specifically (distinct from a company-wide North Star Metric). Product, growth, and support teams should all be able to answer: "What percentage of this week's signups activated, and why didn't the rest?" Tools like session replays, funnel analytics, and cohort dashboards make this trackable without heavy engineering lift, and it's one of the first things investors and advisors will ask a founder to define clearly during early fundraising conversations. --- ### Activation Rate URL: https://www.welaunch.sh/glossary/activation-rate ## What Is Activation Rate? Activation rate is the percentage of new users who complete a defined action within a set timeframe that indicates they have experienced the core value of your product. It is one of the earliest and most reliable predictors of whether a user will stick around, pay, or churn. Unlike signups or downloads, activation is not a vanity metric. It measures whether people actually got value, not just whether they showed up. ## Why Activation Rate Matters for Early-Stage Founders Most startups obsess over top-of-funnel growth (signups, downloads, waitlist joins) while ignoring what happens right after. That is a mistake. If your activation rate is low, every dollar you spend on acquisition is being poured into a leaky bucket. Activation rate matters because: - **It predicts retention.** Users who hit your activation event are dramatically more likely to return and convert. - **It exposes onboarding friction.** A low activation rate almost always points to a confusing first-run experience, not a bad acquisition channel. - **It is fixable fast.** Unlike acquisition or brand awareness, activation improvements can often be shipped and tested within days. - **It is a leading indicator.** You will know within hours or days if activation is broken, versus weeks or months for retention or revenue metrics. For founders running a launch on Product Hunt, Hacker News, or a cold outreach campaign, activation rate tells you whether the traffic you worked hard to earn is actually converting into real users, or just bouncing. ## How to Calculate Activation Rate **Formula:** ``` Activation Rate = (Number of users who complete the activation event / Total new users) x 100 ``` **Example:** Say you run a project management tool. You define your activation event as "user creates their first project and invites one teammate within 3 days of signup." - 1,000 people sign up in a month - 280 of them create a project and invite a teammate within 3 days ``` Activation Rate = (280 / 1,000) x 100 = 28% ``` That 28% is your baseline. Every onboarding change you make should be measured against this number. ## How to Define Your Activation Event The hardest part of activation rate is not the math, it is choosing the right event. A good activation event should be: 1. **Tied to core value.** It should reflect the moment the user understands why your product exists. 2. **Achievable early.** Ideally within the first session or first few days. 3. **Correlated with retention.** Look at your data: what action do retained users take in week one that churned users do not? ### Examples by Product Type - **Slack:** Team sends 2,000 messages (a proxy for real team adoption) - **Dropbox:** User uploads a file to at least one folder - **Notion:** User creates a page and adds a block of content - **A newsletter tool:** User sends their first campaign - **welaunch.sh:** A founder publishes their first launch page and gets their first visitor click Notice these are not "signed up" or "logged in." Those are vanity events. Real activation events require the user to *do* something meaningful. ## Benchmarks Activation rate varies wildly by product category, so treat these as directional, not gospel: | Product Type | Typical Activation Rate | |---|---| | B2B SaaS (self-serve) | 20% to 40% | | Consumer mobile apps | 25% to 60% | | Developer tools / APIs | 10% to 30% | | Freemium products | 15% to 35% | If your activation rate is under 15% for a self-serve product, that is usually a sign of a confusing onboarding flow, unclear value proposition, or a mismatch between what you marketed and what the product actually does. ## Common Mistakes - **Picking too easy an event.** "User logs in" is not activation, it is just login. - **Picking too hard an event.** Requiring five actions before someone is "activated" sets an unrealistic bar and hides real signal. - **Never revisiting the definition.** As your product evolves, your activation event should too. Re-validate it against retention data every few months. - **Ignoring the timeframe.** Activation almost always needs a time window (24 hours, 3 days, 7 days). Without one, you cannot act on the data quickly. - **Optimizing activation in isolation.** A trick that spikes activation rate but tanks retention (like forcing an action before it makes sense) is a false win. ## How to Improve Activation Rate - Simplify onboarding to remove every step that is not essential to reaching the core value moment - Use progressive disclosure: don't ask for everything up front, reveal features as needed - Add contextual nudges or checklists that guide users toward the activation event - Personalize the first-run experience based on signup source or stated goal - Run funnel analysis to find the exact step where users drop off before activating Activation rate is the metric that tells you whether your product's first impression actually works. Get it right, and every other growth lever, from retention to referrals, becomes easier to pull. --- ### Annual Recurring Revenue (ARR) URL: https://www.welaunch.sh/glossary/annual-recurring-revenue-arr ## What ARR Means Annual Recurring Revenue (ARR) is the standardized way subscription businesses report the size of their recurring revenue base. It strips out one-time fees, professional services, and anything non-recurring, leaving only the revenue you can reasonably expect to repeat year over year from active subscriptions. ARR is the default metric investors, boards, and benchmarking reports use to compare SaaS companies, because it normalizes revenue into a single annual number regardless of billing cadence (monthly, quarterly, annual). ## The Formula The simplest and most common calculation is: **ARR = MRR x 12** Where MRR (Monthly Recurring Revenue) is the sum of all recurring subscription charges normalized to a monthly value. A more complete version, used once you have multiple plan types and contract lengths, is: **ARR = (Sum of all active annualized subscription contract values)** For annual contracts, you use the contract value directly. For monthly contracts, you annualize by multiplying by 12. For multi-year contracts, most companies use the annualized value (total contract value divided by number of years), not the full multi-year total. ### Worked Example Say your company has: - 200 customers on a $50/month plan - 40 customers on a $500/year plan - 10 customers on a $2,000/year enterprise plan Calculate each segment: - Monthly plan: 200 x $50 = $10,000/month -> annualized: $10,000 x 12 = $120,000 - $500/year plan: 40 x $500 = $20,000 - $2,000/year plan: 10 x $2,000 = $20,000 **Total ARR = $120,000 + $20,000 + $20,000 = $160,000** This is the number you'd put in a pitch deck, board update, or SaaS benchmarking survey. ## Why ARR Matters for Early-Stage Founders ARR is often the single most important number in a fundraising conversation. Investors use it to: - Size the company (seed, Series A, Series B thresholds are often expressed in ARR) - Calculate valuation multiples (e.g., "10x ARR") - Track growth rate (ARR growth year over year, or even quarter over quarter early on) - Benchmark efficiency metrics like burn multiple and CAC payback against ARR For founders, ARR is also a forcing function for clarity. It requires you to define what counts as "recurring" and be honest about it. Founders who inflate ARR by including one-time services, upfront implementation fees, or non-binding pilots create a credibility problem the moment a serious investor asks for a breakdown. Many indie hackers and bootstrapped founders track ARR even before raising, simply because it's a cleaner proxy for "is this a real business" than total revenue or signups. ## Common Benchmarks While every category is different, rough public benchmarks as of 2026 look like: - **Pre-seed / seed**: $0 to $250K ARR, often used to show early product-market fit signal - **Series A**: typically $1M to $3M ARR with strong month-over-month growth - **Series B**: often $5M to $15M+ ARR with proof of repeatable go-to-market motion - **"Good" growth rate**: roughly tripling ARR in year one after initial traction, doubling in year two, per common SaaS growth benchmarks (the "T2D3" pattern), though this has softened somewhat as capital efficiency has become more valued than raw growth. These numbers shift by category, geography, and market conditions, so treat them as reference points, not rules. ## Common Mistakes When Calculating ARR 1. **Including non-recurring revenue.** Setup fees, one-time consulting, or hardware sales should never be counted in ARR. 2. **Counting unsigned or trial revenue.** Only committed, paying customers count. A verbal "yes" or a free pilot is not ARR. 3. **Ignoring churn and downgrades in real time.** ARR should reflect current run-rate, not a snapshot from three months ago. Stale ARR overstates the business. 4. **Double-counting expansion revenue incorrectly.** If a customer upgrades mid-year, update their contribution to ARR immediately rather than waiting for renewal. 5. **Confusing ARR with bookings.** A signed 3-year, $300K contract is $100K in ARR, not $300K, unless it's genuinely front-loaded and collected annually as $300K. ## ARR vs. MRR: When to Use Which MRR is better for early-stage, fast-moving companies tracking month-to-month momentum, especially pre-seed and seed stage products iterating quickly. ARR becomes more useful once you have some revenue stability and are communicating with investors, board members, or using industry benchmarking tools that report in annual terms. If you're preparing a fundraising narrative or launch retrospective, tools like welaunch.sh can help you frame ARR and growth metrics clearly for investors and press, alongside the rest of your traction story. --- ### Beachhead Market URL: https://www.welaunch.sh/glossary/beachhead-market ## What Is a Beachhead Market? A beachhead market is the first, tightly scoped customer segment a startup chooses to attack, not because it's the biggest opportunity, but because it's the one the company can realistically win outright. The term comes from military strategy, where an invading force secures a small strip of coastline before pushing further inland. Startups use the same logic: get total dominance in a small area first, then expand from a position of strength rather than spreading thin across an entire market. The concept was popularized by Geoffrey Moore in *Crossing the Chasm*, which argued that early-stage tech products fail not from lack of demand, but from trying to serve too many customer types at once with a product that's optimized for none of them. ## Why It Matters for Early-Stage Founders Most startups die from spreading resources too thin, not from picking a market that's too small. A beachhead strategy forces focus on three scarce resources every early team is short on: - **Engineering time.** You can build deeply for one workflow instead of shallow features for ten. - **Marketing budget.** A narrow ICP means cheaper, more targeted acquisition (specific keywords, specific communities, specific events). - **Founder credibility.** Word-of-mouth and referrals compound fastest inside a tight, well-connected community. A beachhead also gives you a defensible answer to "who is this for?" which sharpens your positioning, your landing page copy, your pricing, and your sales pitch all at once. Investors and early customers trust specificity more than broad claims. ## How to Identify a Good Beachhead Market A strong beachhead market usually satisfies most of these criteria: 1. **Small enough to dominate.** You should be able to realistically become the obvious choice for this segment within 12 to 24 months. 2. **Reachable.** The segment congregates somewhere identifiable (a subreddit, a trade association, a Slack community, a conference, a specific job title on LinkedIn). 3. **Acute pain.** The problem is urgent and expensive enough that people are already paying for a workaround (a competitor, a spreadsheet, an agency, or manual labor). 4. **Referenceable.** Customers in this segment talk to each other, so wins spread by word of mouth. 5. **A logical path outward.** Winning this segment should naturally unlock the next, larger segment (an adjacent vertical, a bigger company size, a related use case). ### A Simple Sizing Check A useful gut-check formula: `Beachhead size = Number of reachable target accounts x Realistic win rate x Average contract value` Example: 400 identifiable mid-size logistics companies in your target region x a realistic 15% win rate in year one x $6,000 average annual contract = roughly $360,000 in reachable first-year revenue. That's small on paper, but it's a market you can actually capture, measure, and use as proof for expansion. ## Example Facebook didn't launch to "everyone with an email address." Its beachhead was Harvard undergraduates, a segment of roughly 6,000 students who already knew each other, shared a campus network, and had an acute desire to connect socially online. Only after dominating that segment did it expand to other Ivy League schools, then universities broadly, then the public. Slack's early beachhead wasn't "all companies," it was small, technical, distributed teams already frustrated with email and IRC. That segment gave Slack its first passionate advocates, who then pulled the product into larger organizations. ## Common Mistakes - **Picking a beachhead that's actually a whole market.** "Small businesses" or "developers" is not narrow enough; "solo Shopify store owners doing under $50k/month in the US" is. - **Choosing based on TAM size instead of winnability.** A huge addressable market is meaningless if you can't reach or beat incumbents in it on day one. - **Never leaving the beachhead.** Some founders fall in love with their first niche and never expand, capping growth artificially. The beachhead is a starting point, not a destination. - **Ignoring the expansion path.** If winning your beachhead doesn't logically lead anywhere bigger, you've picked a niche, not a beachhead. ## Quick Benchmark A beachhead is sized right if you can list, by name, most of the potential customers in it. If you can't name at least 20 to 50 specific companies or a specific, addressable community for a consumer product, the segment is still too broad. Tools like welaunch.sh can help founders map and validate a beachhead before spending on broader go-to-market efforts. --- ### Bootstrapping URL: https://www.welaunch.sh/glossary/bootstrapping ## What Bootstrapping Means Bootstrapping is the practice of starting and scaling a business without venture capital or institutional funding. Instead, founders rely on personal savings, freelance or consulting income, credit cards, and, most importantly, revenue from paying customers to fund operations and growth. The term comes from the phrase "pulling yourself up by your bootstraps," meaning you get moving using only what you already have. No pitch decks required, no board seats given away, no term sheets to negotiate. ## Why It Matters for Early-Stage Founders Bootstrapping changes almost everything about how you run a company: - **You keep full ownership.** No dilution means no cap table negotiations and no investor pressure to grow faster than the business can handle. - **You answer to customers, not investors.** Revenue becomes the only validation that matters, which forces earlier discipline around pricing and retention. - **You control the exit timeline.** There's no fund lifecycle pushing you toward an acquisition or IPO on someone else's schedule. - **You accept slower, more constrained growth.** Without outside capital, you can't outspend competitors on ads, hiring, or infrastructure. Growth is generally gated by how much cash the business itself generates. For a first-time founder testing a risky idea, bootstrapping is often the lowest-friction way to get to a real launch. You're not spending months fundraising before you've even validated demand. ## How Bootstrapping Works in Practice Most bootstrapped companies follow a similar sequence: 1. **Fund the MVP personally.** Savings, a part-time job, or freelance work covers early development costs (often $0 to $20,000 depending on the product). 2. **Get to first revenue fast.** Charge customers early, even if the product is rough. Revenue is the fuel that replaces investor capital. 3. **Reinvest profit into growth.** Instead of a large funding round, you reinvest monthly profit into marketing, hires, or tooling. 4. **Grow at the pace cash flow allows.** Hiring and spending decisions are tied directly to what the business earns, not what a term sheet promises. ### A Simple Bootstrapping Runway Example Say a founder has $15,000 in savings and monthly expenses (personal + business) of $3,000. **Runway = Savings / Monthly Burn** $15,000 / $3,000 = 5 months That gives the founder 5 months to either reach breakeven revenue or find a part-time income source to extend the timeline. Many bootstrapped founders stretch this by keeping a day job or consulting on the side until MRR covers living expenses, sometimes called the "ramen profitable" stage. ## Bootstrapping vs. Raising Capital | | Bootstrapping | Venture-Backed | |---|---|---| | Ownership | 100% founder-held (initially) | Diluted across investors | | Growth speed | Constrained by revenue | Accelerated by capital | | Risk tolerance | Lower burn, lower failure cost | High burn, high growth expectations | | Decision control | Founder-only | Board and investor influence | | Exit pressure | None | Often required within 7-10 years | Neither path is universally better. Capital-intensive businesses (hardware, biotech, marketplaces needing liquidity on both sides) are hard to bootstrap. Software tools, agencies, content businesses, and niche SaaS products are often well-suited to it. ## Common Mistakes - **Underpricing to get early customers.** Bootstrapped founders often charge too little because they're desperate for traction, which starves the very cash flow they depend on. - **Confusing busy with profitable.** Revenue without margin discipline can still leave you broke. Track profit, not just top-line sales. - **Waiting too long to charge.** Some founders spend months building for free users before testing willingness to pay. Bootstrapping requires charging early, even a small amount, to validate the model. - **Ignoring personal runway.** Business runway and personal financial runway are different. Many bootstrapped founders fail not because the business died, but because they ran out of personal savings first. - **Trying to bootstrap a capital-intensive idea.** If your business requires large upfront infrastructure or inventory spend, bootstrapping may not be realistic without a hybrid approach (small angel round, revenue-based financing, etc). ## Benchmarks Worth Knowing - Many successful bootstrapped SaaS companies reach $10k to $30k MRR within 12 to 18 months of consistent, focused effort. - A common early milestone is "ramen profitable": revenue covers the founder's minimum living expenses, removing the countdown clock entirely. - Profitable bootstrapped companies typically reinvest 30 to 50 percent of net profit into growth (ads, content, hiring) once they clear basic operating costs. Bootstrapping isn't about avoiding investors forever. Many founders bootstrap to a point of leverage, strong revenue, clear metrics, and only then raise capital on better terms, or skip fundraising entirely because the business no longer needs it. Tools like welaunch.sh can help bootstrapped founders launch faster and validate demand without burning limited runway on unnecessary overhead. --- ### Bottom-Up Adoption URL: https://www.welaunch.sh/glossary/bottom-up-adoption ## What Bottom-Up Adoption Means Bottom-up adoption flips the traditional enterprise sales motion on its head. Instead of a vendor pitching a VP or procurement team first, a single engineer, designer, or analyst signs up for a tool to solve their own problem. If it works, they tell a teammate. Soon a whole team is using it, and eventually someone asks finance to formalize the contract. Slack, Figma, Notion, Dropbox, and Zoom all grew this way. No CIO mandated their use on day one. A developer wanted better file sharing, a designer wanted a shared canvas, a team wanted to stop emailing screenshots back and forth. The product spread person to person, team to team, until leadership had no choice but to notice. ## Why It Matters for Early-Stage Founders For a founder without a sales team, a brand name, or a warm network of enterprise buyers, bottom-up adoption is often the only realistic path into large organizations. It matters because: - **It shortens time to first value.** Individual users can start using a self-serve product in minutes, no procurement cycle required. - **It builds a distribution engine you don't have to pay for.** Every satisfied user is a potential internal evangelist. - **It de-risks enterprise sales later.** By the time you talk to a decision-maker, there's already usage data, internal champions, and proof the tool solves a real problem. - **It's the natural fit for PLG (product-led growth) startups**, where the product itself, not a sales deck, does the convincing. The tradeoff: bottom-up adoption is slower to convert into revenue and harder to forecast than top-down sales, because you're relying on grassroots pull rather than a signed contract. ## How It Actually Works Bottom-up adoption typically moves through four stages: 1. **Individual discovery.** One person finds the product, often through search, a recommendation, or a free trial, and solves an immediate personal problem. 2. **Team spread.** That person invites collaborators, shares files, or simply talks about the tool in Slack or standups. Usage multiplies inside a team. 3. **Cross-team visibility.** Other teams notice the tool being used, or the product's collaborative features force them to join (a shared doc link, a Figma file, a Slack channel). 4. **Executive sponsorship.** Once usage crosses a threshold (departments, seat count, or spend), an admin or finance leader steps in to negotiate an official plan, add security review, or centralize billing. ### A Simple Example A startup building a code review tool launches with a free tier for individual developers. One backend engineer at a 200-person company signs up to try it on a side project. She likes it, shares it with her four-person squad. Three months later, 40 engineers across six teams are using free accounts. The engineering director notices duplicate spend and shadow IT risk, and reaches out to the startup to consolidate everyone under one paid enterprise contract. The startup never ran a single outbound sales call to get there. ### Key Formula: Internal Expansion Rate A useful way to track bottom-up momentum is internal seat expansion: **Internal Expansion Rate = (New seats added within existing accounts this period / Total seats at start of period) x 100** Example: an account starts the quarter with 10 seats and ends with 25 seats (all organic, no sales-assisted upsell). That's a 150% internal expansion rate, a strong signal the product is spreading bottom-up inside that organization without your team pushing it. ## Benchmarks and Signals to Watch - **Seat growth without sales touch**: if accounts are growing seats without any sales-assisted activity, that's a healthy bottom-up signal. - **Multi-team penetration**: users from 3+ distinct teams inside one company is a strong indicator the product is spreading organically, not just being used by one enthusiastic individual. - **Time-to-second-user**: how quickly does a new signup invite a colleague? Under a week is a good benchmark for collaborative tools. - **Free-to-paid conversion inside accounts**: track what percentage of free bottom-up accounts eventually convert to paid within 6 to 12 months. ## Common Mistakes - **Gating collaboration too early.** If users can't invite teammates or share output without hitting a paywall, you kill the viral loop that makes bottom-up adoption work. - **Ignoring internal champions.** Founders often fixate on landing the "decision-maker" and miss that the real growth lever is the individual power user already inside the account. - **No visibility into usage.** Without basic analytics on seats, teams, and accounts, founders can't spot when an account is ready for a top-down sales conversation. - **Overbuilding for enterprise too soon.** Adding SSO, admin consoles, and procurement-friendly features before you have organic pull can slow down the very motion that got you traction. For early-stage teams, the practical takeaway is simple: make the product easy to start alone, easy to share, and impossible to ignore once a few teammates are hooked. That's the engine behind almost every modern PLG success story, and it's a pattern worth designing for from day one, something teams launching on welaunch.sh often build directly into their first release. --- ### Build in Public URL: https://www.welaunch.sh/glossary/build-in-public ## What Does Building in Public Mean? Building in public means treating your company's journey, not just its finished product, as the content. Instead of a polished announcement dropping out of nowhere, followers watch the revenue numbers, the failed experiments, the design pivots, and the customer conversations unfold in real time, usually on X, LinkedIn, or a personal newsletter. It started as a niche indie hacker habit and is now a standard growth channel for early-stage founders who can't outspend competitors on ads but can out-share them on authenticity. ## Why It Matters for Early-Stage Founders Most startups fail from lack of distribution, not lack of product. Building in public solves distribution problems before you have a product to distribute: - **Free audience compounding.** Every post is a small deposit into an audience you'll later launch to. By the time you ship, hundreds or thousands of people already know your name and your problem space. - **Trust before the pitch.** People buy from founders they feel they know. Sharing struggles and numbers builds parasocial trust that a sales page never can. - **Free market research.** Public feedback on your roadmap, pricing, or landing page copy comes in faster and cheaper than any user interview you'd schedule. - **Recruiting and fundraising side effects.** Investors, co-founders, and early hires often find founders through their public build threads, not cold outreach. For a solo founder or small team with no marketing budget, this is often the highest-leverage channel available, and it costs time, not money. ## How to Build in Public: The Core Loop Building in public works as a repeatable loop, not a one-off announcement: 1. **Do something.** Ship a feature, hit a revenue milestone, lose a customer, run an experiment. 2. **Share the specific, not the vague.** "We hit $4,200 MRR this month, up from $2,900" beats "great month for the business." 3. **Show the reasoning.** Explain why you made a decision, what you expected, and what actually happened. 4. **Invite reaction.** Ask a question, request feedback, or post a poll to turn broadcasting into conversation. 5. **Repeat weekly.** Consistency matters more than any single viral post. ### Example Cadence A solo founder building a Chrome extension might post: - Monday: a screenshot of a new feature in progress - Wednesday: a revenue or signup update ("127 signups this week, 9 conversions") - Friday: a lesson from a failed experiment ("Our onboarding email had a 4% open rate, here's what we're changing") Over a year, that's roughly 150 data points showing a real business growing, which is far more persuasive than a single launch-day post. ## What to Share (and What to Skip) ## Good candidates for public sharing: - MRR, user counts, churn, conversion rates - Product screenshots and demo videos - Pricing changes and the reasoning behind them - Mistakes, failed features, and what you learned - Behind-the-scenes decisions (tech stack, hiring, positioning pivots) ### Usually best kept private: - Exact customer names or private conversations without consent - Legal, cap table, or contract details - Anything that would hand a real edge to a fast-following competitor The rule of thumb: share the story and the trend, not always the raw sensitive data. ## Common Mistakes - **Vanity-metric theater.** Posting follower counts or "excited to announce" updates with no substance trains your audience to scroll past you. - **Inconsistency.** One viral thread followed by three months of silence kills momentum. A modest, steady cadence beats sporadic bursts. - **Only sharing wins.** Audiences trust founders who show losses too. A feed of nothing but good news reads as marketing, not building. - **No call to action.** Sharing progress without ever inviting people to try the product, join a waitlist, or give feedback wastes the audience you're building. - **Treating it as a launch tactic instead of a habit.** Build in public works best started months before launch, not the week of it. ## Benchmarks and What Good Looks Like There's no single metric for "success" here, but founders who build in public effectively tend to see: - A meaningful share of launch-day signups (often 20 to 50 percent) coming directly from their existing audience, not cold discovery - Engagement (replies, not just likes) growing steadily month over month as followers start to feel invested in the outcome - Warm inbound (press, investors, partnership offers) that founders with a purely private build rarely get For founders preparing a launch, pairing a public-building habit with a structured checklist, like the ones on welaunch.sh, helps make sure the audience you've built actually gets converted on launch day instead of just watching from the sidelines. --- ### Burn Rate URL: https://www.welaunch.sh/glossary/burn-rate ## Why Burn Rate Matters Burn rate is the single number that tells you how much time you have left. Every founder, whether bootstrapped or venture-backed, needs to know this figure cold. It drives hiring decisions, fundraising timelines, and whether you can afford that next marketing hire or ad spend push. Investors ask about burn rate in almost every pitch meeting because it signals discipline. A founder who can't answer "what's your monthly burn" instantly raises a red flag about financial control. ## Gross Burn vs Net Burn There are two versions of burn rate, and mixing them up leads to bad decisions. ### Gross Burn Gross burn is total monthly operating expenses, full stop. It ignores any revenue coming in. ``` Gross Burn = Total Monthly Cash Expenses ``` ### Net Burn Net burn subtracts revenue from expenses. This is the number that actually determines runway. ``` Net Burn = Total Monthly Cash Expenses - Monthly Revenue ``` **Example:** A startup spends $80,000 a month on salaries, tools, and office costs. It brings in $25,000 in monthly recurring revenue. - Gross Burn = $80,000 - Net Burn = $80,000 - $25,000 = $55,000 If that company has $660,000 in the bank, its runway is: ``` Runway = Cash in Bank / Net Burn 660,000 / 55,000 = 12 months ``` That 12-month number is what matters for planning a fundraise, not the gross figure. ## How to Calculate It Yourself 1. Pull your bank balance from the start and end of the month. 2. Add back any new funding that came in during that period (it inflates the ending balance but isn't burn). 3. Subtract the adjusted ending balance from the starting balance. 4. That difference is your net burn for the month. Most founders track this in a simple spreadsheet or lightweight finance tool, updated monthly. Average it over the last 3 months to smooth out one-off expenses like annual software renewals or a big contractor invoice. ## Benchmarks: What's a Healthy Burn Rate There's no single right answer since burn depends on stage, team size, and business model. But rough guardrails: - **Pre-seed / idea stage:** Burn should be minimal, often under $15k to $30k/month, mostly founder salaries and basic tools. - **Seed stage (small team):** $40k to $100k/month is common for a 3 to 8 person team. - **Series A and beyond:** Burn scales with headcount and go-to-market spend, often $150k to $500k+/month, but should be justified by growth metrics (revenue growth rate, CAC payback). A common rule of thumb from investors: your burn multiple (net burn divided by net new revenue added that month) should ideally stay under 2x. A burn multiple of 1x or lower signals efficient growth; above 3x tends to worry later-stage investors. ## Common Mistakes **Confusing gross and net burn.** Reporting gross burn to investors when you have real revenue understates your efficiency. Reporting net burn when you have almost no revenue can hide how fast you're actually spending. **Not accounting for lumpy expenses.** A single large payment (annual insurance, a conference sponsorship) can spike one month's burn and scare you into a wrong decision. Always look at a 3-month rolling average. **Ignoring burn rate until it's urgent.** Founders who only check their bank balance when it feels low often end up fundraising from a position of weakness. Track burn monthly, even when things feel fine. **Forgetting taxes and one-time costs.** Payroll taxes, annual software license renewals, and equipment purchases all count as cash out the door, even if they don't feel like "burn." ## Burn Rate and Fundraising Strategy Most investors expect a startup to raise enough to cover 18 to 24 months of runway at the current burn rate, with a plan to hit specific milestones (revenue targets, user growth, product launch) before the next round. If your calculated runway is under 6 months, that's typically considered a fundraising emergency, and terms tend to get worse the closer you are to running out of cash. Tools like welaunch.sh can help founders plan launch timing and growth milestones so that burn rate decisions (when to hire, when to spend on marketing) are tied to actual traction rather than guesswork. ## Quick Reference | Term | Formula | |---|---| | Gross Burn | Total monthly expenses | | Net Burn | Expenses - Revenue | | Runway | Cash in bank / Net burn | | Burn Multiple | Net burn / Net new revenue | Knowing these four numbers cold, and updating them monthly, is one of the simplest habits that separates founders who raise on their own terms from those who don't. --- ### CAC Payback Period URL: https://www.welaunch.sh/glossary/cac-payback-period ## Quick Definition CAC Payback Period measures how long it takes for a customer's revenue, adjusted for gross margin, to pay back what you spent to acquire them. Shorter payback means faster cash recovery and less capital tied up in growth. It is one of the clearest signals of whether a startup's growth engine is efficient or burning cash faster than it can replace it. ## Why It Matters for Early-Stage Founders Growth costs cash before it returns cash. Every dollar spent on ads, sales reps, or content that turns into a customer is a dollar out the door today, with revenue trickling back over months. CAC Payback Period tells you exactly how many months that trickle takes to become whole. For a founder deciding how hard to push on paid acquisition, this number answers a simple question: can I afford to keep spending at this rate, or will I run out of runway before the customers I already bought pay me back? Investors ask about it too, because it is a proxy for capital efficiency and a leading indicator of whether unit economics can scale. ## The Formula ``` CAC Payback (months) = CAC / (Monthly Revenue per Customer x Gross Margin %) ``` Breaking that down: - **CAC**: fully loaded cost to acquire one customer (ads, sales salaries, tools, commissions), averaged over a cohort. - **Monthly Revenue per Customer**: average revenue that customer generates each month (ARPA for SaaS). - **Gross Margin %**: revenue minus cost of goods sold (hosting, support, payment processing), divided by revenue. You use gross margin, not raw revenue, because only the margin portion is actually available to offset the acquisition spend. Revenue that gets eaten by hosting costs was never real payback. ### Worked Example Say your SaaS company spends $6,000 in sales and marketing to close one new customer. That customer pays $500 per month, and your gross margin is 80%. ``` CAC Payback = $6,000 / ($500 x 0.80) CAC Payback = $6,000 / $400 CAC Payback = 15 months ``` It takes 15 months of that customer's margin-adjusted revenue to recoup the $6,000 spent acquiring them. If they churn before month 15, you never fully recovered the cost. ## Benchmarks There is no universal number, but general ranges for B2B SaaS: - **Under 12 months**: strong, typical of efficient self-serve or PLG motions. - **12 to 18 months**: healthy for mid-market sales-led SaaS. - **18 to 24 months**: acceptable if net revenue retention is high (customers expand over time) and churn is low. - **Over 24 months**: risky, especially for early-stage companies with limited cash and higher churn uncertainty. Enterprise deals with long contracts and low churn can tolerate longer payback because the revenue is more durable. Usage-based or low-price consumer products usually need payback under 6 to 12 months because customer lifetimes are shorter and less predictable. ## Common Mistakes - **Using raw revenue instead of gross margin.** This makes payback look faster than it really is and hides the true cash impact of COGS. - **Averaging across very different segments.** Blending self-serve and enterprise customers into one CAC payback number hides which motion is actually efficient. - **Ignoring churn.** A 12-month payback means nothing if 30% of customers churn before month 12. Pair payback with retention data, not just the average. - **Excluding real costs from CAC.** Founders often forget sales tools, onboarding time, or a founder's own selling hours, understating CAC and making payback look artificially short. - **Treating it as static.** CAC payback shifts as channels saturate, pricing changes, or your sales team gets more efficient. Recalculate it monthly or quarterly, not once and forget it. ## How to Improve It - Raise prices or improve packaging to increase revenue per customer without raising CAC. - Improve gross margin by automating support or renegotiating infrastructure costs. - Shift spend toward channels with lower CAC, like organic content, referrals, or product-led growth loops. - Improve onboarding and activation so customers start paying sooner and churn less in the critical early months. Founders launching a new product or channel should track CAC payback from day one, even with small sample sizes. Tools like welaunch.sh can help you validate channels and messaging before you scale spend, which keeps your CAC low while you are still figuring out what payback period you can actually sustain. --- ### CAC vs LTV Ratio URL: https://www.welaunch.sh/glossary/cac-vs-ltv-ratio ## Quick definition The CAC vs LTV ratio, often written as LTV:CAC, measures how much revenue a customer generates over their relationship with your business compared to how much you spent to acquire them. It is the single fastest gut check for whether a startup's growth engine actually makes money or is quietly burning cash on every new signup. A ratio of 3:1 (LTV is three times CAC) is the commonly cited healthy benchmark. Below 1:1, you are losing money on every customer. Above 5:1, you might actually be underinvesting in growth. ## Why founders should care Early on, it's tempting to chase growth for growth's sake: more signups, more users, more logos. But growth funded by unsustainable unit economics is a countdown clock, not a milestone. Investors scrutinize LTV:CAC because it answers the question that matters most: does this business get better or worse as it scales? If your CAC exceeds your LTV, every new customer digs the hole deeper. That's fine for a few months while you're testing channels and messaging, but it's fatal as a permanent state. Founders who track this ratio early catch broken economics before they've scaled the problem with paid ads. ## The formula **LTV:CAC ratio = Customer Lifetime Value / Customer Acquisition Cost** To use it you need both inputs calculated first: **CAC** = Total sales and marketing spend / Number of new customers acquired in that period **LTV** = Average revenue per customer x Gross margin % x Average customer lifespan (or, for subscription businesses, Average Revenue Per Account / Churn Rate) ### Worked example Say your SaaS product charges $50/month, has 80% gross margin, and customers stick around for 20 months on average (5% monthly churn). LTV = $50 x 0.80 x 20 = $800 Now say you spent $12,000 last quarter on marketing and sales and acquired 40 customers. CAC = $12,000 / 40 = $300 LTV:CAC = $800 / $300 = 2.67:1 That's below the 3:1 benchmark, which signals the business needs to either raise prices, reduce churn, or lower acquisition costs before pouring more fuel on paid channels. ## Benchmarks to know - **Below 1:1** - You lose money on every customer. Unsustainable, full stop. - **1:1 to 3:1** - Marginal. Common in early-stage products still finding product-market fit, but a red flag if it persists past 12-18 months. - **3:1** - The widely cited healthy target for SaaS and subscription businesses. - **5:1 or higher** - Strong economics, but also worth checking whether you're being too conservative with growth spend. If your ratio is very high and growth is slow, you may be leaving market share on the table. Benchmarks shift by industry. Marketplaces and hardware businesses often run thinner ratios than SaaS because margins and repeat purchase dynamics differ. ## Common mistakes **Ignoring payback period.** A 3:1 ratio looks great on paper, but if it takes 36 months to recoup CAC, you'll run out of cash before the value materializes. Always pair LTV:CAC with CAC payback period (how many months until a customer's cumulative revenue covers acquisition cost). **Using revenue instead of gross margin.** LTV should reflect the profit a customer generates, not top-line revenue. Skipping the margin adjustment inflates LTV and makes the ratio look healthier than reality. **Averaging across very different customer segments.** A single blended LTV:CAC can hide the fact that your enterprise customers are wildly profitable while your self-serve tier is bleeding cash. Segment the analysis by channel, plan tier, or acquisition source. **Calculating LTV too early.** If you only have three months of retention data, projecting a 3-year customer lifespan is guesswork. Early-stage founders should use conservative, cohort-based estimates and revisit quarterly as real data accumulates. **Forgetting that CAC should include everything.** Salaries, tools, ad spend, content costs, even founder time spent on sales, all belong in the CAC calculation if you want an honest number. ## How to improve a weak ratio - Reduce churn (even small churn improvements compound heavily into LTV) - Increase average revenue per customer through upsells, higher pricing tiers, or annual plans - Improve acquisition efficiency by doubling down on channels with organic or referral-driven CAC - Shorten sales cycles to reduce the cost of closing each deal Tracking LTV:CAC isn't a one-time exercise. Revisit it every time you launch a new channel, change pricing, or notice churn shifting. It's one of the clearest signals of whether your business model, not just your product, actually works. Tools like welaunch.sh can help founders track acquisition metrics alongside launch performance so the ratio isn't just a spreadsheet exercise buried until the next board meeting. --- ### Churn Rate URL: https://www.welaunch.sh/glossary/churn-rate ## What Churn Rate Measures Churn rate tells you how much of your customer base or revenue disappears in a given window, usually a month for early-stage SaaS companies. It's the mirror image of retention: if 5% of customers churn, 95% stick around. There are two main flavors: - **Customer churn rate**: percentage of customers lost - **Revenue churn rate**: percentage of revenue lost (can be gross or net) Both matter, but revenue churn tells a richer story, especially if you have customers on different pricing tiers. ## Why Churn Rate Matters for Founders Churn is often the single most important number for an early-stage subscription business. Here's why: - **It caps your growth speed.** If you're adding 20 customers a month but losing 15, your net growth is anemic no matter how good your top-of-funnel marketing is. - **It's a leading indicator of product-market fit.** High churn almost always means the product isn't delivering enough value to enough people, no amount of onboarding polish fixes that. - **It determines your real CAC payback.** A customer who churns in month 3 never lets you recoup a 6-month CAC payback period. - **Investors scrutinize it.** During fundraising, churn rate (alongside retention curves) is one of the first things a serious SaaS investor will ask to see. For founders using welaunch.sh or similar tools to plan a product launch, thinking about churn early, even before you have paying customers, shapes onboarding, pricing, and support decisions that reduce churn later. ## How to Calculate Churn Rate ### Customer Churn Rate Formula ``` Customer Churn Rate = (Customers Lost During Period / Customers at Start of Period) x 100 ``` **Example:** You start the month with 200 customers. 10 cancel during the month. ``` Churn Rate = (10 / 200) x 100 = 5% ``` ### Revenue Churn Rate Formula ``` Gross Revenue Churn = (MRR Lost from Cancellations + Downgrades) / MRR at Start of Period x 100 ``` **Example:** You start the month with $50,000 MRR. You lose $2,000 from cancellations and $500 from downgrades. ``` Revenue Churn = ($2,000 + $500) / $50,000 x 100 = 5% ``` Net revenue churn subtracts expansion revenue (upsells, upgrades) from the losses, and can even go negative, meaning your existing customers are generating more revenue over time despite some churn. Negative net revenue churn is the holy grail for SaaS companies. ## Benchmarks: What's a "Good" Churn Rate? Benchmarks vary heavily by customer segment: | Segment | Monthly Churn Benchmark | |---|---| | Enterprise SaaS | 0.5% to 1% | | Mid-market SaaS | 1% to 2% | | SMB / self-serve SaaS | 3% to 7% | | Consumer subscription apps | 5% to 10%+ | A common rule of thumb: monthly churn above 5% for a B2B product is a red flag worth investigating immediately. For consumer products, higher churn is more tolerable if acquisition costs are low and volume is high. Annualized churn is not simply monthly churn times 12, because of compounding. A rough approximation: ``` Annual Churn ≈ 1 - (1 - Monthly Churn)^12 ``` So a 5% monthly churn rate compounds to roughly 46% annual churn, not 60%. ## Common Mistakes When Tracking Churn 1. **Ignoring cohort analysis.** A blended churn number hides the fact that new customers often churn much faster than customers who've stuck around 6+ months. Segment churn by signup cohort to see the real pattern. 2. **Only tracking customer churn, not revenue churn.** Losing your smallest customer and your biggest customer both count as "1 churned customer" but have wildly different revenue impact. 3. **Confusing churn with cancellation requests.** Some customers pause, downgrade, or go delinquent on payment before formally canceling. Involuntary churn (failed payments) is often 20-40% of total churn and is fixable with better dunning/retry logic. 4. **Measuring churn too early.** With under 50 customers, churn percentages are noisy and can swing wildly month to month. Look for trends over several months, not single data points. 5. **Optimizing churn in isolation.** Reducing churn by discounting aggressively can hurt LTV even while the churn number improves. Always look at churn alongside expansion revenue and CAC payback. ## Reducing Churn: Where to Start - Interview churned customers directly, exit surveys rarely surface the real reason - Fix onboarding first, most early churn happens because users never reach an "aha moment" - Set up automatic payment retry and dunning emails to cut involuntary churn - Build a simple health score based on product usage to flag at-risk accounts before they cancel - Segment churn by acquisition channel, some channels bring in lower-intent users who churn faster regardless of product quality --- ### Cohort Retention URL: https://www.welaunch.sh/glossary/cohort-retention ## What Cohort Retention Actually Shows Cohort retention groups users by the date (or week, or month) they signed up, then tracks what percentage of that group is still active at fixed intervals afterward: day 1, day 7, day 30, and so on. Instead of asking "how many users do we have," it asks "do the users we get actually stick around," which is a far more honest question for an early-stage product. A "cohort" is simply a batch of users who share a start date. "Retention" is the share of that batch still doing meaningful activity later. Put together, cohort retention turns a single vanity metric (total signups) into a curve that reveals the real health of your product. ## Why It Matters for Early-Stage Founders Aggregate metrics lie. If you look at total weekly active users, growth can mask a leaky bucket: you might be adding 500 new users a week while losing 480 old ones, and the top-line number still goes up. Cohort retention exposes this immediately because it isolates each signup group and shows exactly where they drop off. For founders, this matters in three concrete ways: - **It's the clearest signal of product-market fit.** If a meaningful share of users from every cohort keeps coming back on their own, without you nudging them, you have something people want. - **It tells you whether growth spend is worth it.** Paid acquisition into a product with poor retention just buys you a faster churn cycle. - **It shows if the product is improving.** Comparing cohort curves month over month tells you if new features and onboarding changes are actually helping people stay, not just guessing. Investors ask for retention curves specifically because they can't be gamed the way "total users" can. A flattening curve is one of the strongest pieces of evidence you can put in a pitch deck. ## How to Calculate It Pick a cohort (e.g., everyone who signed up in the first week of March), pick an activity definition (e.g., "logged in" or "completed a core action"), and pick your time intervals (day 1, day 7, day 30, day 90 are common). **Formula:** Cohort Retention (Day N) = (Users from the cohort active on Day N / Total users in the cohort) x 100 **Example:** Say 200 users sign up for your app in Week 1 (this is your cohort). You track how many of those same 200 people log in during each following week: - Week 1 (signup week): 200 active (100%) - Week 2: 90 active (45%) - Week 4: 60 active (30%) - Week 8: 48 active (24%) - Week 12: 44 active (22%) Plotted, this forms a retention curve that drops sharply at first, then flattens. The flattening point matters more than the initial drop: it represents your "resilient" user base, the people who found real value and are likely to stay long-term. Run this same analysis for every weekly (or monthly) cohort, lay the curves side by side, and you can see whether newer cohorts retain better than older ones, which is the clearest proof that your product (or onboarding) is actually improving. ## Reading the Curve: What Good Looks Like There's no universal "good" number since it varies wildly by product category, but the shape matters more than the absolute number: - **Smiling curve (retention dips then rises):** Rare and excellent. Usually seen in social or network products where value compounds over time. - **Flattening curve (drops then levels off):** Healthy. Signals a durable core user base has formed. - **Curve that keeps declining toward zero:** Bad. The product isn't sticky; you're renting users, not keeping them. For consumer apps, a day-30 retention of 25-40% is often considered decent; for B2B SaaS with weekly-use products, 60%+ month-over-month retention within an engaged segment is a stronger benchmark. Always benchmark against your specific category rather than generic numbers. ## Common Mistakes - **Using signups instead of activated users as the cohort base.** This dilutes the data with people who never really tried the product. Cohort on "activated" users when possible for a cleaner signal. - **Picking a weak definition of "active."** If "active" just means opening the app, you'll overstate retention. Tie it to a core action that reflects real value (posting, completing a task, making a purchase). - **Only looking at blended retention.** Averaging all cohorts together hides whether things are getting better or worse. Always compare cohort by cohort. - **Giving up too early.** Retention curves take a few weeks or months of data to show a real pattern; judging from day 1 and day 7 alone is premature. ## The Bottom Line Cohort retention is the single best early-warning system for whether you've built something people want to keep using. Before you pour money into acquisition channels or plan a splashy launch on welaunch.sh, make sure your retention curve is flattening, not falling. Growth on top of weak retention just accelerates how fast you find out the product isn't sticky. --- ### Cold Email Sequence URL: https://www.welaunch.sh/glossary/cold-email-sequence ## What Counts as a Cold Email Sequence A cold email sequence is not one email. It is a chain of 3 to 7 messages sent over 1 to 3 weeks to someone who has never interacted with your company. Each email in the chain builds on the last: a first-touch pitch, a follow-up with new information or social proof, a breakup email that tries one last angle. The goal of the sequence is not to sell in email one. It is to get a reply, a meeting, or a click that moves the prospect into a real conversation. This differs from a newsletter or nurture sequence, which goes to people who already know you. Cold sequences are outbound: you are interrupting someone's day, so every word has to earn the next line. ## Why It Matters for Early-Stage Founders Before you have inbound traffic, warm intros, or brand recognition, cold email is often the fastest and cheapest way to get your first 10 to 50 customer conversations. It does not require ad spend, an audience, or SEO rankings that take months to build. A well-run sequence can generate qualified pilot users, design partners, or early revenue in the same week you send it. It also forces clarity. Writing a cold sequence that has to work in 60 seconds of a stranger's attention strips away vague positioning. If you cannot explain your value in three short sentences, your sequence will fail, and that is useful signal for your whole pitch. ## How a Sequence Is Structured A standard high-performing structure looks like this: 1. **Email 1 (Day 0):** Short, specific, one clear ask. Reference something true about the prospect (their role, a recent post, a shared context). State the problem and a one-line value prop. End with a low-friction question, not a demo request. 2. **Email 2 (Day 3-4):** Add a new angle: a case study, a stat, or a different pain point. Reply to the same thread, do not start a new one. 3. **Email 3 (Day 7-8):** Social proof or a resource (a short guide, a comparison, a relevant result). 4. **Email 4 (Day 12-14):** The breakup email. "Should I close the loop on this?" This often gets the highest reply rate of the sequence because it removes pressure. ### Example Email 1 > Subject: quick question about [specific process] > > Hi Maya, saw your team is hiring for ops, guessing [specific pain] is getting harder to manage manually. > > We built [product] so teams like yours can [specific outcome] without adding headcount. > > Worth a 2-line reply if this is on your radar right now? ## Key Metrics and Benchmarks Reply rate is the primary metric, not open rate (open tracking is increasingly unreliable due to privacy features in email clients). **Reply Rate = Total Replies / Total Emails Delivered x 100** Example: you send 500 emails across a sequence, 40 people reply. Reply rate = 40 / 500 = 8%. Rough 2026 benchmarks for a reasonably targeted B2B list: - **Positive reply rate:** 3-8% is solid for a cold list with decent targeting. - **Total reply rate (including "not interested"):** 8-15%. - **Meeting booked rate:** 1-3% of total sends. - **Bounce rate:** should stay under 3-5%; higher signals a stale or scraped list. If your positive reply rate is under 1%, the problem is almost always targeting or the offer, not the subject line. ## Common Mistakes - **Sending to a bad list.** A perfectly written sequence to the wrong audience gets ignored. Spend more time on list quality than on email copy. - **Making email 1 do too much.** Long emails with three asks and a full pitch deck attached get deleted. One idea, one ask. - **No follow-up.** Most replies come from emails 2 through 4, not email 1. A sequence that stops after one send is not a sequence. - **Ignoring deliverability.** Sending high volume from a brand-new domain with no warmup gets you flagged as spam and can damage your main domain's sending reputation. Use a separate sending domain and warm it up gradually. - **Generic personalization.** Inserting {{firstName}} into a template that is obviously mass-produced is worse than no personalization at all. - **No clear next step.** Every email should end with one specific, easy-to-answer question, not "let me know if you're interested." ## Tools and Compliance Most founders run cold sequences through tools like Instantly, Smartlead, Apollo, or Lemlist, which handle scheduling, warmup, and reply detection. Be aware of regional rules: CAN-SPAM (US) and GDPR (EU) both require an easy opt-out and prohibit misleading subject lines, and B2B cold email is treated differently than B2C outreach in several jurisdictions. Check local requirements before sending at volume. A tight cold email sequence, paired with a clear one-line pitch and a simple landing page, is often the fastest way for a solo founder to validate demand before building anything at scale, which is exactly the kind of early-traction motion tools like welaunch.sh are built to support. --- ### Cold Outreach URL: https://www.welaunch.sh/glossary/cold-outreach ## What Is Cold Outreach? Cold outreach is the practice of proactively contacting people who don't know you yet, typically via email, LinkedIn messages, or cold calls, with the goal of starting a conversation that leads to a sale, partnership, or hire. Unlike inbound marketing, it doesn't wait for someone to find you. You find them. For early-stage founders, cold outreach is often the fastest way to get first customers before any brand awareness or inbound pipeline exists. It's manual, unscalable, and unglamorous, but it works when other channels haven't caught up yet. ## Why Cold Outreach Matters for Early Founders Most startups have zero traffic and zero trust in month one. Cold outreach lets you skip that waiting period and talk directly to the exact people you think will pay you. It matters because: - **It's controllable.** You choose who to contact and when, unlike SEO or paid ads that depend on algorithms or budgets. - **It surfaces real feedback fast.** Talking to 50 prospects in a week teaches you more about your pitch than a month of passive analytics. - **It validates willingness to pay.** A cold email that converts to a paid pilot is stronger signal than a landing page that converts to an email signup. - **It's cheap.** No ad spend required, just time and a decent list. The tradeoff is scale and reputation risk. Overdo it or do it poorly, and you burn your domain reputation or your name in a niche community. ## How Cold Outreach Works A basic cold outreach motion has four parts: 1. **List building.** Identify a specific, narrow list of people who match your ICP (ideal customer profile). Quality beats quantity here. 2. **Message crafting.** Write a short, personalized message that references something specific about the recipient and states a clear, low-friction ask. 3. **Sending and sequencing.** Send the first message, then follow up 2-4 times over 1-2 weeks if there's no reply. 4. **Tracking and iterating.** Measure open rate, reply rate, and conversion rate, then adjust subject lines, messaging, or targeting. ### Example Cold Email Structure - **Subject:** Specific and short ("Question about [their process]") - **Opener:** One sentence showing you did homework on them - **Value:** One sentence on why you're reaching out and what's in it for them - **Ask:** A single, easy yes/no question, not "let's hop on a call for 30 minutes" Example: > Subject: Quick question about your onboarding flow > > Hi Sam, noticed [Company] just launched a self-serve signup flow. We built a tool that cuts onboarding drop-off by 15-20% for teams like yours. Worth a 2-minute look? ## How to Measure Cold Outreach Performance Track these core metrics per campaign: - **Open rate** = opens / emails sent - **Reply rate** = replies / emails sent - **Positive reply rate** = interested replies / emails sent - **Conversion rate** = meetings booked or deals closed / emails sent ### Rough Benchmarks (2026) - Open rate: 40-60% (with a good subject line and clean list) - Reply rate: 5-15% for well-targeted, personalized outreach - Positive reply rate: 2-5% is solid for cold B2B - Meeting conversion: 1-3% of total emails sent If your reply rate is under 2%, the problem is almost always targeting or messaging, not volume. Sending more of a bad email just gets you more ignored emails. ### A Simple Formula for Pipeline Planning If you need 10 qualified meetings this month and your positive reply rate is 3%, you need roughly: 10 / 0.03 = 334 emails sent This is why list quality matters so much. Sending 334 emails to a loosely-defined "business owners" list will convert far worse than 334 emails to a tightly-defined niche (for example, "Shopify store owners doing $1-5M revenue using a specific app"). ## Common Mistakes - **Generic mass blasts.** No personalization signals low effort and gets ignored or marked as spam. - **Asking for too much too soon.** "Can we schedule 30 minutes?" converts worse than a simple yes/no question. - **Ignoring deliverability.** Sending too many emails from one domain without warmup can tank your sender reputation for months. - **No follow-up.** Most replies come from the 2nd or 3rd touch, not the first. - **Not segmenting the list.** One message rarely fits every persona; tailor by role or use case. ## Cold Outreach vs. Inbound Cold outreach and inbound marketing aren't competitors, they're sequential. Many founders use cold outreach to get the first 10-50 customers, generate case studies and testimonials, then shift budget toward content, SEO, or paid channels once there's proof the product works. Tools like welaunch.sh can help founders coordinate outreach alongside a broader launch plan so cold contact isn't the only growth lever running. Done well, cold outreach is a founder-led sales motion, not a spray-and-pray tactic. Treat every message like it's going to a real person, because it is. --- ### Cold Start Problem URL: https://www.welaunch.sh/glossary/cold-start-problem ## What the Cold Start Problem Actually Is Every product that depends on other people to be valuable, a marketplace, a social app, a marketplace of content, a B2B tool with team collaboration, faces the same trap at launch: nobody wants to join an empty room. Buyers won't show up without sellers. Sellers won't show up without buyers. Users won't post without an audience, and there's no audience without posts. This is the cold start problem. It's not a bug in your strategy, it's a structural feature of any business built on network effects. The product literally cannot demonstrate its core value proposition until a critical mass of participants exists. ## Why It Matters for Early-Stage Founders Most startup failures in marketplace and social categories aren't caused by bad ideas, they're caused by founders underestimating how hard the first 100 to 1,000 users are to acquire and retain. A product with genuine long-term potential can die in month two because early visitors saw an empty feed, an empty catalog, or a marketplace with three listings and no buyers, and never came back. Understanding the cold start problem early forces founders to answer a harder, more useful question before writing growth-stage go-to-market plans: how do we manufacture value artificially until real network effects can take over? ## How Startups Solve It There is no single fix, but there are repeatable patterns: ### 1. Single-player mode first Build something useful to one user even with zero network. Instagram worked as a photo filter app before it worked as a social network. This buys time to accumulate users without needing the network effect on day one. ### 2. Seed supply or demand manually Many marketplace founders act as the first sellers or buyers themselves. Airbnb's founders photographed listings by hand. DoorDash founders delivered orders themselves. This is unscalable by design, and that's the point, it's a temporary bridge, not the business model. ### 3. Concentrate on a narrow niche Rather than trying to reach critical mass across an entire market, focus on one city, one university, one industry vertical, or one small community where density is achievable quickly. Facebook launched at a single university before expanding. A tight niche needs far fewer total users to feel "full." ### 4. Subsidize one side of the market Pay or incentivize the harder-to-acquire side (usually supply) until the easier side (usually demand) follows. Uber subsidized drivers early. This costs money and should be modeled with a clear sunset plan, not run indefinitely. ### 5. Import an existing network Launch by piggybacking on a platform, community, or existing user base rather than building density from zero. Early Airbnb hosts cross-posted to Craigslist to tap into its existing demand. ## A Simple Way to Think About the Threshold While there's no universal formula, it helps to define your own "minimum viable density" before launch: **Minimum Viable Density = the smallest ratio of supply to demand (or contributors to consumers) at which a first-time visitor sees enough value to return.** Example: a local services marketplace might need at least 5 active providers per requested category in a given city before a customer search returns a satisfying result. If you only have 1 provider per category, most searches will look empty, and users churn immediately. Your entire early go-to-market plan should be built around hitting that density in the smallest possible geography or niche, not spreading thin across a whole country. ## Common Mistakes - **Launching too broad.** Trying to serve "everyone everywhere" from day one guarantees the network stays thin in every segment simultaneously. - **Measuring vanity growth instead of density.** 10,000 signups spread across 200 cities is worse than 500 signups concentrated in one city. - **Ignoring the supply side.** Founders often over-invest in demand-side marketing while supply (sellers, content, listings) remains too thin to support it. - **No sunset plan for manual seeding.** Founders who play matchmaker or seller forever never build a scalable product; the manual work should shrink as real network effects take over. - **Underpricing the subsidy cost.** Paying to seed one side of the market without modeling the payback period can burn runway fast. ## Benchmark to Watch Track **retention within your seeded segment**, not total signups. If users in your first city, niche, or cohort are returning and transacting without your manual intervention, you've likely cleared the cold start threshold and can expand. If retention is weak even in your most concentrated segment, expanding further will only dilute density and make the problem worse. Founders using welaunch.sh to plan a marketplace or network launch should treat the cold start problem as the first strategic decision, not an afterthought: pick the smallest viable market where density is achievable, seed it manually if needed, and only expand once retention proves the network effect is real. --- ### Community-Led Growth URL: https://www.welaunch.sh/glossary/community-led-growth ## What Is Community-Led Growth? Community-led growth (CLG) is a go-to-market motion where a company invests in a group of engaged users, builders, or fans first, and lets that group become the primary engine for awareness, feedback, referrals, and adoption. Instead of buying attention through ads, the company earns it by giving people a place to talk, help each other, and shape the product. The community usually exists before the product is finished, and it keeps compounding after launch. It is the difference between renting an audience for a campaign and owning a relationship that outlasts any single launch day. ## Why It Matters for Early-Stage Founders Early-stage founders rarely have big budgets, brand trust, or a sales team. Community-led growth solves all three at once: - **It replaces paid distribution.** A few hundred engaged members in a Discord or Slack can outperform a five-figure ad spend because they share, answer support questions, and vouch for you publicly. - **It compresses the feedback loop.** You ship a feature, ask the community, and get honest signal in hours instead of weeks of surveys. - **It de-risks the launch.** By the time you go live on Product Hunt or send a launch email, you already have people who will show up, comment, and upvote because they helped build the thing. - **It creates durable moat.** Ad channels can be copied overnight. A community with real relationships and inside jokes is much harder for a competitor to replicate. This is why so many successful indie products (Notion, Figma, Superhuman, ConvertKit in its early days) point to a small, obsessive community as the real unlock, not a viral ad. ## How Community-Led Growth Works A basic CLG loop looks like this: 1. **Seed** a small group of ideal users (often 20 to 200 people) around a shared problem or identity, not around your product. 2. **Give before you ask.** Share resources, answer questions, host office hours, and let members help each other. 3. **Involve them in building.** Beta access, roadmap votes, and naming decisions turn users into co-owners. 4. **Let them tell the story.** Members post screenshots, write reviews, answer "has anyone tried X" threads, and bring in their own network. 5. **Formal launch amplifies, it does not create, the momentum.** Your Product Hunt day or press push rides on a wave the community already built. ### A Simple Example A solo founder building a habit-tracking app starts a small Discord six months before launch, focused on "accountability for indie hackers" rather than the app itself. She posts weekly progress, asks members what they are struggling with, and gives early builds to the 30 most active people. By launch day she has: - 400 community members, of whom 120 have used a beta build - 60 people who agreed to leave a review or comment on launch day - A backlog of feature requests already validated by real usage Her Product Hunt launch gets 200 upvotes in the first two hours purely from the community, which pushes it to the front page and pulls in organic traffic on top. ## Measuring Community-Led Growth Unlike a pure metric like CAC, CLG is measured through a mix of activity and outcome signals: **Engagement rate** `Engagement Rate = (Active Members in Period / Total Members) x 100` A healthy early community often sees 15 to 30 percent weekly active engagement; anything under 5 percent usually signals a community that is more of a list than a community. **Community-attributed signups** Track how many new users or customers cite the community, a member referral, or a community post as their source. If this is below 10 percent of new signups once the community has a few hundred members, the community is not yet driving growth, it is just a support channel. **Time to first response** How quickly a question or post gets a reply from anyone, not just the founder. Fast peer response (under a few hours) is the clearest sign the community has its own gravity. ## Common Mistakes - **Building the community around the product instead of the problem.** People join communities for identity and progress, not to hear about your roadmap. - **Launching the community and the product on the same day.** CLG needs runway; six to twelve months of community-building before launch is common among founders who use this approach well, including many who plan their timeline with tools like welaunch.sh to sequence community milestones against launch day. - **Founder does all the talking.** If every valuable reply comes from you, the community has not taken ownership yet. - **No clear ritual.** Weekly office hours, a Monday check-in thread, or a recurring "ship report" gives members a reason to return. - **Treating community size as the goal.** A tight 300-person community with real relationships outperforms a silent 10,000-member list every time. Community-led growth is slower to start than a paid campaign, but it compounds. Each new member increases the value of the community for everyone already in it, which is the opposite of how paid acquisition behaves. --- ### Customer Acquisition Cost (CAC) URL: https://www.welaunch.sh/glossary/customer-acquisition-cost-cac ## What CAC Measures CAC tells you how much it costs, on average, to turn a stranger into a paying customer. It bundles together every dollar spent on marketing and sales over a period, divided by the number of new customers that period produced. It is one of the two or three metrics investors will ask about in almost any early-stage pitch, because it reveals whether your growth engine is actually economical or just loud. A low CAC relative to what a customer is worth (LTV) suggests a business that can scale profitably. A high CAC relative to LTV suggests a business that is buying revenue at a loss, which can work for a while with venture funding but eventually has to flip. ## The Formula ``` CAC = Total Sales & Marketing Spend / Number of New Customers Acquired ``` **What counts as spend:** - Paid ad spend (Google, Meta, LinkedIn, etc.) - Content, SEO, and PR costs - Salaries and commissions for marketing and sales staff - Tools and software used for acquisition (CRM, email platforms, ad tech) - Agency or freelancer fees tied to acquisition **What counts as "new customers":** paying customers only, acquired within the same time window as the spend. Free trial sign-ups or leads do not count unless you are calculating a separate metric like cost per lead. ## Worked Example Say a SaaS startup spends $20,000 in a month on: - $9,000 in paid ads - $6,000 in salary for one marketer and one SDR (prorated) - $3,000 on content and tools - $2,000 on a freelance ads consultant That same month, 40 new customers convert to paid plans. ``` CAC = $20,000 / 40 = $500 per customer ``` If that customer's average LTV is $2,000, the LTV:CAC ratio is 4:1, generally considered healthy. If LTV were only $600, the business would be losing money on every customer it acquires, even before accounting for product costs or overhead. ## Why It Matters for Early-Stage Founders 1. **It exposes fake growth.** A startup adding users by spending unsustainably on ads looks impressive on a dashboard but can be quietly burning cash faster than it can ever earn back. CAC forces the question: is this growth or is this a subsidy? 2. **It shapes fundraising conversations.** Investors compare CAC against LTV and payback period to judge unit economics, especially at Series A and beyond. Founders who can't state their CAC clearly signal that they aren't tracking the business closely. 3. **It guides channel decisions.** Calculating CAC per channel (paid search vs. content vs. outbound vs. referral) shows which channels are actually worth scaling and which are quietly draining budget. 4. **It's a pricing signal.** If CAC keeps rising as you scale a channel, that's often a sign of market saturation, weak targeting, or a pricing/positioning mismatch that needs fixing before you pour in more spend. ## Blended CAC vs. Channel CAC **Blended CAC** includes all spend and all new customers, organic and paid together. It's the simplest number to report but hides where the real cost is coming from. **Paid CAC** or **channel CAC** isolates spend and customers from a single channel (e.g., only Facebook ads, only outbound sales). This is more useful operationally because it tells you exactly where to double down or cut back. Early-stage founders should track both: blended CAC for the big picture, channel CAC for tactical decisions. ## Common Mistakes - **Leaving out salaries.** Many founders only count ad spend and ignore the cost of the humans running campaigns or closing deals, which understates CAC significantly. - **Counting trial sign-ups as customers.** This inflates apparent efficiency and hides the true cost of paying customers. - **Ignoring time lag.** If your sales cycle is 60 days, spend in January may produce customers in March. Matching spend and customers in the same short window can distort the number, especially for longer B2B cycles. - **Comparing CAC across very different business models.** A $50 CAC is great for a $10/month app and terrible for a $9/month one. CAC only means something next to LTV and payback period. - **Optimizing CAC in isolation.** Cutting CAC by targeting only the cheapest, lowest-intent traffic can quietly wreck retention and LTV. Always look at CAC and LTV together. ## Rough Benchmarks There is no universal "good" CAC since it depends entirely on price point and margins, but as a starting sanity check: - **LTV:CAC ratio of 3:1 or higher** is commonly cited as healthy for SaaS. - **CAC payback period under 12 months** is a common benchmark investors look for in B2B SaaS; under 5 to 7 months is considered strong. - Anything below 1:1 (spending more to acquire a customer than they're worth) is unsustainable without a clear path to fixing it. For early-stage founders planning a launch, tools like welaunch.sh can help you get initial traction through organic channels before you start spending heavily on paid acquisition, which keeps your first CAC calculations honest rather than inflated by early ad experiments. ---