# Proof usually beats promotion in the early stage > Why young products often grow faster when they publish progress, show the team, close the customer loop, and let quality do the talking. - Canonical HTML: https://growth.iangoh.com/blog/proof-usually-beats-promotion-in-the-early-stage/ - Published: 2026-05-24 - Updated: 2026-05-24 - Categories: brand trust, SEO, operator-led distribution - Niches: SaaS, AI products, creator tools, marketplaces, community-led growth ## On this page - A changelog can be a growth page - Quality is not separate from growth - Keep the user's sentence attached to the work - Listen to the users you want more of - Put real people on the domain - Where this applies ## Start with these related tactics - [Weekly public changelog proof loop](/growth-ideas/weekly-public-changelog-proof-loop/): Publish a short public changelog every week, even before you have many users, so progress itself becomes a trust and retention surface. - [Quality-first product experience flywheel](/growth-ideas/quality-first-product-experience-flywheel/): Use product quality as a distribution strategy by fixing obvious friction fast and letting delighted users carry the product into other teams. - [Customer request linkback close loop](/growth-ideas/customer-request-linkback-close-loop/): Attach support threads, Slack posts, and other customer conversations directly to product issues, then push the resolution back into the original conversation when it ships. A lot of early teams spend on promotion before they have built enough proof. That is backwards. Attention is expensive. Proof is reusable. When a product is young, strangers are not really asking whether the market category is big. They are asking smaller questions. Is this team alive? Do they ship? Do they listen? Do they know who they are building for? Can I trust what I am seeing on this domain? ## A changelog can be a growth page Linear is refreshingly blunt about this. The [weekly public changelog proof loop](/growth-ideas/weekly-public-changelog-proof-loop/) works even when the user base is small because the page itself becomes evidence. It shows that the company ships, that the product is changing, and that there is a rhythm behind the thing. Founders sometimes think a changelog is a support artifact. Early on it is often closer to a trust artifact. A stranger reading it can tell whether the company has pulse without booking a demo or joining a webinar. ## Quality is not separate from growth This is why I like the [quality-first product experience flywheel](/growth-ideas/quality-first-product-experience-flywheel/) framing. Karri Saarinen's argument is simple: in a crowded market, quality can do the job people usually assign to marketing. Linear says that choice helped it become profitable by year two and pass 10,000 paying customers by year four with almost no traditional marketing. That is not an excuse to ignore distribution. It is a reminder that some distribution starts only after the product feels safe to recommend. People share quality faster than they share slogans. ## Keep the user's sentence attached to the work Another proof surface is less visible from the outside but just as important. The [customer request linkback close loop](/growth-ideas/customer-request-linkback-close-loop/) keeps the original support thread, Slack post, or bug report attached to the issue. Then, when the work ships, the team can reply where the request started. This sounds operational, but it changes the growth story. Users stop feeling like they sent feedback into a cave. They see movement. Support gains specifics. Product keeps the actual words instead of an internal paraphrase. Over time, that kind of follow-through becomes reputation. ## Listen to the users you want more of The [right-user feedback filter](/growth-ideas/right-user-feedback-filter/) matters for the same reason. Feedback is only useful if it pulls you toward the market you want. Linear's Method makes the point cleanly: if you are building for early-stage startups, enterprise feedback can teach you the wrong lessons. I would go one step further. The fastest way to ruin a good early growth surface is to make it serve the wrong buyer. A clean message to the right user compounds. A broad message that pleases everybody usually makes the product feel blurrier. ## Put real people on the domain Ahrefs makes a practical SEO version of the same argument. The [team profile pages for brand SERP control](/growth-ideas/team-profile-pages-for-brand-serp-control/) tactic is not glamorous, but it gives branded search and AI answers first-party evidence about who is behind the company. That matters more than people think. Buyers, partners, journalists, and curious lurkers all do little background checks. If your own site cannot explain who the operators are, some third-party directory will do it badly for you. ## Where this applies For SaaS, this means treating changelogs, support follow-up, and profile pages as acquisition infrastructure, not housekeeping. For AI products, it means showing concrete progress and real builders instead of hiding behind a vague frontier story. For creator tools and marketplaces, it means the cleanest brand page is often the one that proves somebody careful is behind the product. The trap is trying to sound bigger than you are. I would rather look legible than loud. In the early stage, proof usually travels further than promotion. ## Related GrowthDex tactics - [Weekly public changelog proof loop](/growth-ideas/weekly-public-changelog-proof-loop/) - Content, Website, Lifecycle - [Quality-first product experience flywheel](/growth-ideas/quality-first-product-experience-flywheel/) - Product, Referrals, Word of Mouth - [Customer request linkback close loop](/growth-ideas/customer-request-linkback-close-loop/) - Customer Support, Lifecycle, Product - [Right-user feedback filter](/growth-ideas/right-user-feedback-filter/) - User Research, Product, Community - [Team profile pages for brand SERP control](/growth-ideas/team-profile-pages-for-brand-serp-control/) - SEO, AI Search, Website ## Essay chronology - [Newer essay: Credibility is usually built before the big launch](/blog/credibility-is-usually-built-before-the-big-launch/) - trust, SEO, early-stage growth - [Older essay: Support often becomes the growth surface first](/blog/support-often-becomes-the-growth-surface-first/) - support-led growth, activation, retention ## Keep reading - [A weak domain should borrow trust before it demands attention](/blog/a-weak-domain-should-borrow-trust-before-it-demands-attention/) - SEO, brand trust, operator-led distribution - [Credibility is usually built before the big launch](/blog/credibility-is-usually-built-before-the-big-launch/) - trust, SEO, early-stage growth - [The page after the spike matters more than the spike](/blog/the-page-after-the-spike-matters-more-than-the-spike/) - launch strategy, SEO, operator-led distribution ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Linear Method](https://linear.app/method/build-in-public) · [GrowthDex source hub](/sources/linear-method-linear-app/) - [Linear](https://linear.app/now/why-is-quality-so-rare) · [GrowthDex source hub](/sources/linear-linear-app/) - [Linear](https://linear.app/now/fast-growing-startups-are-built-on-linear/) · [GrowthDex source hub](/sources/linear-linear-app/) - [Linear Method](https://linear.app/method/build-with-users) · [GrowthDex source hub](/sources/linear-method-linear-app/) - [Ahrefs Blog](https://ahrefs.com/blog/brand-seo/) · [GrowthDex source hub](/sources/ahrefs-blog-ahrefs-com/) ## Editing notes - Cut grand claims about brand building and stayed on inspectable proof surfaces. - Removed checklist language so the piece reads like one argument instead of a content template. - Kept the tone plain, slightly opinionated, and concrete around what a stranger can actually verify. - Used short sections and internal links to avoid repetitive transitions and AI-style signposting. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.