<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>GrowthDex Blog</title>
    <link>https://growth.iangoh.com/blog/</link>
      <description>Short, useful essays about how founders get early attention, trust, and revenue from real growth examples.</description>
    <language>en</language>
    <lastBuildDate>Tue, 09 Jun 2026 15:35:52 GMT</lastBuildDate>
    <generator>GrowthDex static generator</generator>
    <item>
      <title>The local page should sound like the neighborhood before the call</title>
      <link>https://growth.iangoh.com/blog/the-local-page-should-sound-like-the-neighborhood-before-the-call/</link>
      <guid>https://growth.iangoh.com/blog/the-local-page-should-sound-like-the-neighborhood-before-the-call/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on local search trust: intent-shaped GBP categories, call-transcript Q&amp;A, review systems, real location proof, neighborhood page discipline, and cross-platform NAP consistency.</description>
    </item>
    <item>
      <title>The first search engine should be small enough to finish</title>
      <link>https://growth.iangoh.com/blog/the-first-search-engine-should-be-small-enough-to-finish/</link>
      <guid>https://growth.iangoh.com/blog/the-first-search-engine-should-be-small-enough-to-finish/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on a micro-SaaS SEO case: directory seeding, three core pages, one persona use case, high-intent posts, Search Console refreshes, and tracking before scale.</description>
    </item>
    <item>
      <title>Zero ad spend is still a marketing budget</title>
      <link>https://growth.iangoh.com/blog/zero-ad-spend-is-still-a-marketing-budget/</link>
      <guid>https://growth.iangoh.com/blog/zero-ad-spend-is-still-a-marketing-budget/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on FlowMapp, organic SaaS growth, owned content, Medium, landing pages, reviews, Product Hunt, co-promo, and why signup volume still needs cohort discipline.</description>
    </item>
    <item>
      <title>The answer should be easy to quote before you chase the mention</title>
      <link>https://growth.iangoh.com/blog/the-answer-should-be-easy-to-quote-before-you-chase-the-mention/</link>
      <guid>https://growth.iangoh.com/blog/the-answer-should-be-easy-to-quote-before-you-chase-the-mention/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why PostHog&apos;s AEO playbook starts with plain prompts, quoteable chunks, owned-surface cleanup, prompt capture, stitched reporting, and the willingness to throw away a bad prompt set.</description>
    </item>
    <item>
      <title>The link should sell the infrastructure quietly</title>
      <link>https://growth.iangoh.com/blog/the-link-should-sell-the-infrastructure-quietly/</link>
      <guid>https://growth.iangoh.com/blog/the-link-should-sell-the-infrastructure-quietly/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Cal.com, open-source positioning, Product Hunt timing, booking-link loops, and why infrastructure growth often starts with one useful shared link.</description>
    </item>
    <item>
      <title>The product should keep a visible pulse</title>
      <link>https://growth.iangoh.com/blog/the-product-should-keep-a-visible-pulse/</link>
      <guid>https://growth.iangoh.com/blog/the-product-should-keep-a-visible-pulse/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Resend-style momentum comes from an open-source wedge, founder-led launch motion, real-device launch discipline, a visible heartbeat, and soft-launched feature weeks.</description>
    </item>
    <item>
      <title>The group should know you before the link</title>
      <link>https://growth.iangoh.com/blog/the-group-should-know-you-before-the-link/</link>
      <guid>https://growth.iangoh.com/blog/the-group-should-know-you-before-the-link/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on WhatsApp B2B groups, trust, micro-value, manual replies, and why closed communities punish lazy launch posts.</description>
    </item>
    <item>
      <title>The route should stay yours after the click</title>
      <link>https://growth.iangoh.com/blog/the-route-should-stay-yours-after-the-click/</link>
      <guid>https://growth.iangoh.com/blog/the-route-should-stay-yours-after-the-click/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on owned routes, brand trust, redirects, crawl policy, and why early links should keep compounding on your domain.</description>
    </item>
    <item>
      <title>The extension should earn the second use</title>
      <link>https://growth.iangoh.com/blog/the-extension-should-earn-the-second-use/</link>
      <guid>https://growth.iangoh.com/blog/the-extension-should-earn-the-second-use/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Chrome extension growth, Readdit Later, MeetAssist, simple jobs, paywall probes, onboarding, and telemetry-led quality work.</description>
    </item>
    <item>
      <title>The demo should arrive before the pitch</title>
      <link>https://growth.iangoh.com/blog/the-demo-should-arrive-before-the-pitch/</link>
      <guid>https://growth.iangoh.com/blog/the-demo-should-arrive-before-the-pitch/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on VideoMule, Reddit founder threads, keyword alerts, personalized demos, directories, and why proof beats a cold ask.</description>
    </item>
    <item>
      <title>The developer tool should launch like a series, not a stunt</title>
      <link>https://growth.iangoh.com/blog/the-developer-tool-should-launch-like-a-series-not-a-stunt/</link>
      <guid>https://growth.iangoh.com/blog/the-developer-tool-should-launch-like-a-series-not-a-stunt/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Supabase-style developer growth compounds when the team uses early public proof, repeated launches, channel-fit distribution, prelaunch freeze discipline, and community day loops.</description>
    </item>
    <item>
      <title>The plugin should prove the work before the marketplace scales it</title>
      <link>https://growth.iangoh.com/blog/the-plugin-should-prove-the-work-before-the-marketplace-scales-it/</link>
      <guid>https://growth.iangoh.com/blog/the-plugin-should-prove-the-work-before-the-marketplace-scales-it/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Figma plugin growth, marketplace data, demo launches, output quality, and why platform distribution only works when the workflow is already useful.</description>
    </item>
    <item>
      <title>The Notion connection should earn the first workspace</title>
      <link>https://growth.iangoh.com/blog/the-notion-connection-should-earn-the-first-workspace/</link>
      <guid>https://growth.iangoh.com/blog/the-notion-connection-should-earn-the-first-workspace/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Notion public-connection growth depends on scope choice, template-led auth, page-picker reality, post-install seeding, and owned-domain link previews.</description>
    </item>
    <item>
      <title>The social account should arrive with a map</title>
      <link>https://growth.iangoh.com/blog/the-social-account-should-arrive-with-a-map/</link>
      <guid>https://growth.iangoh.com/blog/the-social-account-should-arrive-with-a-map/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Bluesky growth gets easier when the profile arrives with a starter pack, a feed, a trusted handle, and a clear path into the right room.</description>
    </item>
    <item>
      <title>The community app should make the subreddit more alive</title>
      <link>https://growth.iangoh.com/blog/the-community-app-should-make-the-subreddit-more-alive/</link>
      <guid>https://growth.iangoh.com/blog/the-community-app-should-make-the-subreddit-more-alive/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Reddit-native apps grow when they create new posts, respect the feed, stay mobile-first, and treat moderation as part of the product.</description>
    </item>
    <item>
      <title>The affiliate program is a product surface</title>
      <link>https://growth.iangoh.com/blog/the-affiliate-program-is-a-product-surface/</link>
      <guid>https://growth.iangoh.com/blog/the-affiliate-program-is-a-product-surface/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on affiliate growth, partner pages, fraud filters, tiered attribution, and why partner programs need product discipline before scale.</description>
    </item>
    <item>
      <title>The video should show the job before the brand</title>
      <link>https://growth.iangoh.com/blog/the-video-should-show-the-job-before-the-brand/</link>
      <guid>https://growth.iangoh.com/blog/the-video-should-show-the-job-before-the-brand/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on TikTok SaaS growth, useful demos, creator series, local market tests, and why short-form works when it shows the viewer&apos;s job fast.</description>
    </item>
    <item>
      <title>The podcast appearance should open a real door</title>
      <link>https://growth.iangoh.com/blog/the-podcast-appearance-should-open-a-real-door/</link>
      <guid>https://growth.iangoh.com/blog/the-podcast-appearance-should-open-a-real-door/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on podcast guesting, founder interviews, ABM guest lists, qualified pipeline, cross-promos, and why podcast growth needs a sharper job than downloads.</description>
    </item>
    <item>
      <title>The LinkedIn form should carry the campaign without multiplying</title>
      <link>https://growth.iangoh.com/blog/the-linkedin-form-should-carry-the-campaign-without-multiplying/</link>
      <guid>https://growth.iangoh.com/blog/the-linkedin-form-should-carry-the-campaign-without-multiplying/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why one good LinkedIn form often beats six cloned ones when hidden metadata keeps owner, asset, client, creative, and market context attached.</description>
    </item>
    <item>
      <title>The Teams rollout should survive the policy layer</title>
      <link>https://growth.iangoh.com/blog/the-teams-rollout-should-survive-the-policy-layer/</link>
      <guid>https://growth.iangoh.com/blog/the-teams-rollout-should-survive-the-policy-layer/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Teams adoption often depends on mobile pin counts, admin pin order, real pinnability, organizer-led meeting rollout, and room-device policy discipline.</description>
    </item>
    <item>
      <title>The newsletter sponsor slot should have a job</title>
      <link>https://growth.iangoh.com/blog/the-newsletter-sponsor-slot-should-have-a-job/</link>
      <guid>https://growth.iangoh.com/blog/the-newsletter-sponsor-slot-should-have-a-job/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on newsletter sponsorships, niche audience fit, simple offers, landing pages, break-even math, waitlist spikes, and sponsor demand.</description>
    </item>
    <item>
      <title>The Stripe app page should finish the install thought</title>
      <link>https://growth.iangoh.com/blog/the-stripe-app-page-should-finish-the-install-thought/</link>
      <guid>https://growth.iangoh.com/blog/the-stripe-app-page-should-finish-the-install-thought/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Stripe App growth gets better when install links, post-install routing, settings pages, external tests, shelf copy, and partner distribution work like one route.</description>
    </item>
    <item>
      <title>The answer should travel before the page ranks</title>
      <link>https://growth.iangoh.com/blog/the-answer-should-travel-before-the-page-ranks/</link>
      <guid>https://growth.iangoh.com/blog/the-answer-should-travel-before-the-page-ranks/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on native republishing, Reddit answer ops, canonical timing, AI citations, and why useful answers often move faster than a young domain.</description>
    </item>
    <item>
      <title>The page should speak the market, not just the language</title>
      <link>https://growth.iangoh.com/blog/the-page-should-speak-the-market-not-just-the-language/</link>
      <guid>https://growth.iangoh.com/blog/the-page-should-speak-the-market-not-just-the-language/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on international SEO, localization, hreflang, market-specific search intent, and why founders should translate context before scaling pages.</description>
    </item>
    <item>
      <title>The video should answer a search before it asks for attention</title>
      <link>https://growth.iangoh.com/blog/the-video-should-answer-a-search-before-it-asks-for-attention/</link>
      <guid>https://growth.iangoh.com/blog/the-video-should-answer-a-search-before-it-asks-for-attention/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on YouTube SEO, video-carousel queries, evergreen tutorials, thumbnails, comments, embedded video schema, and why search-led video can behave like a growth page.</description>
    </item>
    <item>
      <title>The Telegram Mini App should open where the habit already lives</title>
      <link>https://growth.iangoh.com/blog/the-telegram-mini-app-should-open-where-the-habit-already-lives/</link>
      <guid>https://growth.iangoh.com/blog/the-telegram-mini-app-should-open-where-the-habit-already-lives/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Telegram Mini App growth depends on Main Mini App setup, localized previews, smarter menu buttons, attachment-menu placement, admin-shaped group installs, and Stars affiliate loops.</description>
    </item>
    <item>
      <title>The comparison page should help the buyer decide</title>
      <link>https://growth.iangoh.com/blog/the-comparison-page-should-help-the-buyer-decide/</link>
      <guid>https://growth.iangoh.com/blog/the-comparison-page-should-help-the-buyer-decide/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on competitor pages, alternative pages, honest comparisons, pricing, FAQs, schema, and why bottom-of-funnel SEO should feel like a decision aid.</description>
    </item>
    <item>
      <title>The buyer page should name the industry, role, and job</title>
      <link>https://growth.iangoh.com/blog/the-buyer-page-should-name-the-industry-role-and-job/</link>
      <guid>https://growth.iangoh.com/blog/the-buyer-page-should-name-the-industry-role-and-job/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on use-case pages, industry pages, role pages, internal links, and why buyers should recognize themselves before the page asks them to convert.</description>
    </item>
    <item>
      <title>The definition page should teach the market and qualify the buyer</title>
      <link>https://growth.iangoh.com/blog/the-definition-page-should-teach-the-market-and-qualify-the-buyer/</link>
      <guid>https://growth.iangoh.com/blog/the-definition-page-should-teach-the-market-and-qualify-the-buyer/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on glossary pages, what-is pages, answer boxes, page-one definitions, and why glossary traffic still has to prove it can help the business.</description>
    </item>
    <item>
      <title>The lifecycle message should follow the last real signal</title>
      <link>https://growth.iangoh.com/blog/the-lifecycle-message-should-follow-the-last-real-signal/</link>
      <guid>https://growth.iangoh.com/blog/the-lifecycle-message-should-follow-the-last-real-signal/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why stronger onboarding and retention messaging usually comes from cleaner intent capture, better timing, and gentler unsubscribe controls rather than louder nurture copy.</description>
    </item>
    <item>
      <title>The Teams app should meet the work before the help doc</title>
      <link>https://growth.iangoh.com/blog/the-teams-app-should-meet-the-work-before-the-help-doc/</link>
      <guid>https://growth.iangoh.com/blog/the-teams-app-should-meet-the-work-before-the-help-doc/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Teams growth often comes from default scope choices, stronger first tabs, admin pinning, zero-install previews, and message-extension context that matches the user&apos;s real moment.</description>
    </item>
    <item>
      <title>The Slack app should start helping before the docs tab opens</title>
      <link>https://growth.iangoh.com/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/</link>
      <guid>https://growth.iangoh.com/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why trigger-aware onboarding, tighter welcome DMs, channel-level setup visibility, in-Slack help, and Direct Install usually matter more than another polished integration page.</description>
    </item>
    <item>
      <title>The archive is a growth channel if someone keeps it alive</title>
      <link>https://growth.iangoh.com/blog/the-archive-is-a-growth-channel-if-someone-keeps-it-alive/</link>
      <guid>https://growth.iangoh.com/blog/the-archive-is-a-growth-channel-if-someone-keeps-it-alive/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on historical optimization, content decay, pruning, Search Console queues, old posts, and why the archive is not dead weight.</description>
    </item>
    <item>
      <title>The App Store page should qualify the traffic it invites</title>
      <link>https://growth.iangoh.com/blog/the-app-store-page-should-qualify-the-traffic-it-invites/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-page-should-qualify-the-traffic-it-invites/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why custom-page keywords, value-aware analytics, better poster frames, accessibility labels, and category discipline usually beat another screenshot panic.</description>
    </item>
    <item>
      <title>The App Store campaign page should survive the tap</title>
      <link>https://growth.iangoh.com/blog/the-app-store-campaign-page-should-survive-the-tap/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-campaign-page-should-survive-the-tap/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why campaign-specific product pages, Apple Search Ads message match, deep links, event warm-up loops, and route-level App Store analytics make paid mobile traffic feel less wasteful.</description>
    </item>
    <item>
      <title>The extension page should survive the week after install</title>
      <link>https://growth.iangoh.com/blog/the-extension-page-should-survive-the-week-after-install/</link>
      <guid>https://growth.iangoh.com/blog/the-extension-page-should-survive-the-week-after-install/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why metric baselines, job-first copy, privacy answers, support hubs, and coherent store art make a browser-extension listing hold up after the first burst.</description>
    </item>
    <item>
      <title>The switch should look like current work before the cutover</title>
      <link>https://growth.iangoh.com/blog/the-switch-should-look-like-current-work-before-the-cutover/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-should-look-like-current-work-before-the-cutover/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why open-only pilot imports, top-level team staging, mapped Jira owners, filtered sync, and date-backed project graphs make a migration trial feel real.</description>
    </item>
    <item>
      <title>The docs page should show signs of life before support does</title>
      <link>https://growth.iangoh.com/blog/the-docs-page-should-show-signs-of-life-before-support-does/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-page-should-show-signs-of-life-before-support-does/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why one real article, a visible shipped trail, timed guidance, shared docs metrics, and nearby status proof beat a polished empty docs shell.</description>
    </item>
    <item>
      <title>The docs path should stay readable to bots and buyers</title>
      <link>https://growth.iangoh.com/blog/the-docs-path-should-stay-readable-to-bots-and-buyers/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-path-should-stay-readable-to-bots-and-buyers/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why API catalogs, clearer crawl policy, scoped search, live link checks, and smoother playground auth make docs easier to trust before the sales call.</description>
    </item>
    <item>
      <title>The Shopify app page should win the search result before the install</title>
      <link>https://growth.iangoh.com/blog/the-shopify-app-page-should-win-the-search-result-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-shopify-app-page-should-win-the-search-result-before-the-install/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why category fit, benefit-led subtitles, cleaner search terms, sharper snippets, and real support links do more for Shopify app growth than another vague traffic push.</description>
    </item>
    <item>
      <title>The docs page should let the buyer send the first request</title>
      <link>https://growth.iangoh.com/blog/the-docs-page-should-let-the-buyer-send-the-first-request/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-page-should-let-the-buyer-send-the-first-request/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on interactive API docs, synced collections, recipes, and why the first technical proof should happen before the meeting.</description>
    </item>
    <item>
      <title>The first useful click should open a live workspace</title>
      <link>https://growth.iangoh.com/blog/the-first-useful-click-should-open-a-live-workspace/</link>
      <guid>https://growth.iangoh.com/blog/the-first-useful-click-should-open-a-live-workspace/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why codespace badges, prebuilds, browser-run examples, generated sandboxes, and guided deploy buttons convert technical curiosity better than another setup document.</description>
    </item>
    <item>
      <title>The AI visibility report should point to a page that can win</title>
      <link>https://growth.iangoh.com/blog/the-ai-visibility-report-should-point-to-a-page-that-can-win/</link>
      <guid>https://growth.iangoh.com/blog/the-ai-visibility-report-should-point-to-a-page-that-can-win/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why the useful AI-visibility loop starts with real prompts, cited pages, source gaps, and landing-page evidence instead of one dramatic chatbot screenshot.</description>
    </item>
    <item>
      <title>The proof surface should answer before the call</title>
      <link>https://growth.iangoh.com/blog/the-proof-surface-should-answer-before-the-call/</link>
      <guid>https://growth.iangoh.com/blog/the-proof-surface-should-answer-before-the-call/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why graders, search reports, request dashboards, newsletter quality views, and live demos work best when they settle one skeptical question before anyone books the meeting.</description>
    </item>
    <item>
      <title>The docs route should let the developer verify before the call</title>
      <link>https://growth.iangoh.com/blog/the-docs-route-should-let-the-developer-verify-before-the-call/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-route-should-let-the-developer-verify-before-the-call/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why llms.txt, Markdown mirrors, code samples, status pages, changelogs, and previewed docs migrations make developer docs do more of the selling before support or sales steps in.</description>
    </item>
    <item>
      <title>The utility page should finish the job before the pitch</title>
      <link>https://growth.iangoh.com/blog/the-utility-page-should-finish-the-job-before-the-pitch/</link>
      <guid>https://growth.iangoh.com/blog/the-utility-page-should-finish-the-job-before-the-pitch/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why the best free tools teach, measure, or calculate something real before they ask for the signup, the demo, or the sales call.</description>
    </item>
    <item>
      <title>The customer-facing answer should keep the context attached</title>
      <link>https://growth.iangoh.com/blog/the-customer-facing-answer-should-keep-the-context-attached/</link>
      <guid>https://growth.iangoh.com/blog/the-customer-facing-answer-should-keep-the-context-attached/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why FAQ pages, support portals, trust centers, and status surfaces work better when they preserve the buyer&apos;s context instead of forcing another inbox loop.</description>
    </item>
    <item>
      <title>The free tool has to do the job before it asks for the lead</title>
      <link>https://growth.iangoh.com/blog/the-free-tool-has-to-do-the-job-before-it-asks-for-the-lead/</link>
      <guid>https://growth.iangoh.com/blog/the-free-tool-has-to-do-the-job-before-it-asks-for-the-lead/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on graders, calculators, micro tools, benchmark reports, and why a useful output beats a static lead form.</description>
    </item>
    <item>
      <title>The best SEO page lets the buyer touch the shape of the product</title>
      <link>https://growth.iangoh.com/blog/the-best-seo-page-lets-the-buyer-touch-the-shape-of-the-product/</link>
      <guid>https://growth.iangoh.com/blog/the-best-seo-page-lets-the-buyer-touch-the-shape-of-the-product/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on product-led SEO, template libraries, collection pages, creative use cases, and why useful pages beat keyword wrappers.</description>
    </item>
    <item>
      <title>The support report should write the next help page</title>
      <link>https://growth.iangoh.com/blog/the-support-report-should-write-the-next-help-page/</link>
      <guid>https://growth.iangoh.com/blog/the-support-report-should-write-the-next-help-page/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on no-result searches, ticket-to-search ratios, Messenger search, AI answer boxes, and why the best docs backlog starts in the search log.</description>
    </item>
    <item>
      <title>The help page is a sales page when the buyer is stuck</title>
      <link>https://growth.iangoh.com/blog/the-help-page-is-a-sales-page-when-the-buyer-is-stuck/</link>
      <guid>https://growth.iangoh.com/blog/the-help-page-is-a-sales-page-when-the-buyer-is-stuck/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on support docs, help-center SEO, onboarding clusters, FAQ blocks, changelog links, and why stuck buyers are still buyers.</description>
    </item>
    <item>
      <title>The page that earns links has to give something away</title>
      <link>https://growth.iangoh.com/blog/the-page-that-earns-links-has-to-give-something-away/</link>
      <guid>https://growth.iangoh.com/blog/the-page-that-earns-links-has-to-give-something-away/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on research assets, statistics hubs, custom graphics, relevant backlinks, and why good link earning starts before outreach.</description>
    </item>
    <item>
      <title>Programmatic SEO only works when the page has a reason</title>
      <link>https://growth.iangoh.com/blog/programmatic-seo-only-works-when-the-page-has-a-reason/</link>
      <guid>https://growth.iangoh.com/blog/programmatic-seo-only-works-when-the-page-has-a-reason/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on programmatic SEO, comparison pages, city pages, indexation, and why pages need real data before scale helps.</description>
    </item>
    <item>
      <title>Pricing is a growth channel when it explains the buyer</title>
      <link>https://growth.iangoh.com/blog/pricing-is-a-growth-channel-when-it-explains-the-buyer/</link>
      <guid>https://growth.iangoh.com/blog/pricing-is-a-growth-channel-when-it-explains-the-buyer/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on pricing and packaging as growth work, using SafeEx, Carta, Omnisend, Stompers, Toptal, and a Micro SaaS pricing test as case studies.</description>
    </item>
    <item>
      <title>Customer proof should have a page before it has a slogan</title>
      <link>https://growth.iangoh.com/blog/customer-proof-should-have-a-page-before-it-has-a-slogan/</link>
      <guid>https://growth.iangoh.com/blog/customer-proof-should-have-a-page-before-it-has-a-slogan/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on G2 customer-proof growth through Enablix, Appknox, Audiense, and Eventee: reviews as SEO, sales proof, case-study fuel, and category infrastructure.</description>
    </item>
    <item>
      <title>The marketplace app has to feel native before it can grow</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-app-has-to-feel-native-before-it-can-grow/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-app-has-to-feel-native-before-it-can-grow/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Canva Apps Marketplace growth: one-click utility, bulk workflows, mobile demand, free quotas, marketplace scale, and premium readiness.</description>
    </item>
    <item>
      <title>The integration launch should keep paying rent</title>
      <link>https://growth.iangoh.com/blog/the-integration-launch-should-keep-paying-rent/</link>
      <guid>https://growth.iangoh.com/blog/the-integration-launch-should-keep-paying-rent/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on what should happen after an integration announcement: internal enablement, workflow timing, template hygiene, community proof, and owned curation.</description>
    </item>
    <item>
      <title>The answer page is a sales call that does not end</title>
      <link>https://growth.iangoh.com/blog/the-answer-page-is-a-sales-call-that-does-not-end/</link>
      <guid>https://growth.iangoh.com/blog/the-answer-page-is-a-sales-call-that-does-not-end/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on answer-engine growth through Quora, SaaStr, Growth Hackers, and Stack Overflow: how useful answers, profiles, curation, and developer docs compound.</description>
    </item>
    <item>
      <title>The integration page should make the product feel connected</title>
      <link>https://growth.iangoh.com/blog/the-integration-page-should-make-the-product-feel-connected/</link>
      <guid>https://growth.iangoh.com/blog/the-integration-page-should-make-the-product-feel-connected/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A readable essay on Zapier partner growth, integration marketplaces, embedded workflow metrics, and the habit of proving that connected users become better customers.</description>
    </item>
    <item>
      <title>The academy is a distribution system</title>
      <link>https://growth.iangoh.com/blog/the-academy-is-a-distribution-system/</link>
      <guid>https://growth.iangoh.com/blog/the-academy-is-a-distribution-system/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on education-led growth through HubSpot Academy and Salesforce Trailhead: badges, startup onboarding, certification gates, company challenges, and hands-on learning.</description>
    </item>
    <item>
      <title>The AI product page should let the model be tried</title>
      <link>https://growth.iangoh.com/blog/the-ai-product-page-should-let-the-model-be-tried/</link>
      <guid>https://growth.iangoh.com/blog/the-ai-product-page-should-let-the-model-be-tried/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Hugging Face distribution: model cards, Spaces, dataset cards, Collections, community sprints, and leaderboards as AI-product growth surfaces.</description>
    </item>
    <item>
      <title>A referral program is not a miracle. It is plumbing.</title>
      <link>https://growth.iangoh.com/blog/a-referral-program-is-not-a-miracle-it-is-plumbing/</link>
      <guid>https://growth.iangoh.com/blog/a-referral-program-is-not-a-miracle-it-is-plumbing/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on referral loops through Dropbox, PayPal, Robinhood, Harry’s, and Wise, with the trap founders should avoid before copying the mechanics.</description>
    </item>
    <item>
      <title>The marketplace starts when the founder knocks</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-starts-when-the-founder-knocks/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-starts-when-the-founder-knocks/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Airbnb’s early growth: door-to-door host work, founder photography, Craigslist demand, shortage wedges, cereal as runway, and trust before scale.</description>
    </item>
    <item>
      <title>The extension page should survive the update, not just the install</title>
      <link>https://growth.iangoh.com/blog/the-extension-page-should-survive-the-update-not-just-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-extension-page-should-survive-the-update-not-just-the-install/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why partial rollouts, honest permission updates, signed package uploads, stable Firefox IDs, visible rejection fallbacks, and rollback-ready approved versions make extension growth less fragile after day one.</description>
    </item>
    <item>
      <title>The marketplace gets faster when the seller is live</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-gets-faster-when-the-seller-is-live/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-gets-faster-when-the-seller-is-live/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Whatnot: collectibles wedges, live auction urgency, seller approval, passionate host fit, AI listing speed, and category expansion after format proof.</description>
    </item>
    <item>
      <title>The marketplace grows when selling feels free</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-grows-when-selling-feels-free/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-grows-when-selling-feels-free/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Vinted: zero seller fees, buyer protection monetization, integrated shipping, market penetration, luxury verification, and second-hand-first positioning.</description>
    </item>
    <item>
      <title>The marketplace has to make selling feel social</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-has-to-make-selling-feel-social/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-has-to-make-selling-feel-social/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Poshmark: seller stylist identity, Posh Parties, sharing as distribution, community events, seller earnings proof, and trust infrastructure.</description>
    </item>
    <item>
      <title>The marketplace works when the seller wants to be seen</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-works-when-the-seller-wants-to-be-seen/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-works-when-the-seller-wants-to-be-seen/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Depop: social feed discovery, seller-led distribution, Gen Z resale positioning, creative supply for market entry, seller content tools, and repeat-buyer community retention.</description>
    </item>
    <item>
      <title>The story platform grows when readers help write the shelf</title>
      <link>https://growth.iangoh.com/blog/the-story-platform-grows-when-readers-help-write-the-shelf/</link>
      <guid>https://growth.iangoh.com/blog/the-story-platform-grows-when-readers-help-write-the-shelf/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Wattpad: mobile-first reading, reader feedback loops, free access, engagement signals, UGC-to-media pipelines, and niche collections for brand fit.</description>
    </item>
    <item>
      <title>The network starts where the room already wants to check</title>
      <link>https://growth.iangoh.com/blog/the-network-starts-where-the-room-already-wants-to-check/</link>
      <guid>https://growth.iangoh.com/blog/the-network-starts-where-the-room-already-wants-to-check/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Tinder: Greek-life atomic networks, sorority-first proof, party download gates, swiping as play, campus beachheads, and Tinder U reactivation.</description>
    </item>
    <item>
      <title>The platform wins when creators can build the next shelf</title>
      <link>https://growth.iangoh.com/blog/the-platform-wins-when-creators-can-build-the-next-shelf/</link>
      <guid>https://growth.iangoh.com/blog/the-platform-wins-when-creators-can-build-the-next-shelf/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Roblox: UGC positioning, seed users, creator cash-out thresholds, cross-device reach, market-entry readiness, and brand adoption through native creators.</description>
    </item>
    <item>
      <title>The launch thread should teach the product before the homepage does</title>
      <link>https://growth.iangoh.com/blog/the-launch-thread-should-teach-the-product-before-the-homepage-does/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-thread-should-teach-the-product-before-the-homepage-does/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Loom used Product Hunt as the real launch room: concentrated comments, a sharper first page, use-case-rich maker notes, personal video replies, repeat launches, and a tiny tagline people could retell.</description>
    </item>
    <item>
      <title>The unfinished game should give players something to show</title>
      <link>https://growth.iangoh.com/blog/the-unfinished-game-should-give-players-something-to-show/</link>
      <guid>https://growth.iangoh.com/blog/the-unfinished-game-should-give-players-something-to-show/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Minecraft: public alpha, paid early access, community-made proof, word of mouth before launch, beta sales milestones, and platform expansion after the PC loop worked.</description>
    </item>
    <item>
      <title>The boring product needs a story people want to repeat</title>
      <link>https://growth.iangoh.com/blog/the-boring-product-needs-a-story-people-want-to-repeat/</link>
      <guid>https://growth.iangoh.com/blog/the-boring-product-needs-a-story-people-want-to-repeat/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Liquid Death: pre-product brand validation, curiosity packaging, entertainment-first healthy marketing, retail launch stunts, category expansion, and lifecycle conversion.</description>
    </item>
    <item>
      <title>The platform should name the game before it names the category</title>
      <link>https://growth.iangoh.com/blog/the-platform-should-name-the-game-before-it-names-the-category/</link>
      <guid>https://growth.iangoh.com/blog/the-platform-should-name-the-game-before-it-names-the-category/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Twitch: spinning gaming out of Justin.tv, interviewing broadcasters, routing discovery by game, fixing bottom-viewer pain, monetizing streamers, and hiring practitioner onboarding help.</description>
    </item>
    <item>
      <title>The campaign is decided before the launch button</title>
      <link>https://growth.iangoh.com/blog/the-campaign-is-decided-before-the-launch-button/</link>
      <guid>https://growth.iangoh.com/blog/the-campaign-is-decided-before-the-launch-button/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Kickstarter and BackerKit: prelaunch list math, owned email plus platform followers, $1 update tiers, community stretch goals, video reviews, and relaunching from real audience proof.</description>
    </item>
    <item>
      <title>The marketplace should show up where the makers already are</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-should-show-up-where-the-makers-already-are/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-should-show-up-where-the-makers-already-are/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Etsy: craft-fair supply recruiting, forums, street teams, offline markets, Treasury curation, and handmade positioning against generic marketplaces.</description>
    </item>
    <item>
      <title>The first patron should prove the next creator</title>
      <link>https://growth.iangoh.com/blog/the-first-patron-should-prove-the-next-creator/</link>
      <guid>https://growth.iangoh.com/blog/the-first-patron-should-prove-the-next-creator/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Patreon: founder-led creator proof, safer per-creation pledges, monthly membership workarounds, friendly competitor acquisition, special offers, and earnings-first metrics.</description>
    </item>
    <item>
      <title>The sale should teach the next creator</title>
      <link>https://growth.iangoh.com/blog/the-sale-should-teach-the-next-creator/</link>
      <guid>https://growth.iangoh.com/blog/the-sale-should-teach-the-next-creator/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Gumroad: weekend validation, transaction-led acquisition, creator-shaped product abstractions, market-rate honesty, public financials, and customer ownership.</description>
    </item>
    <item>
      <title>The customer should not have to report the bug</title>
      <link>https://growth.iangoh.com/blog/the-customer-should-not-have-to-report-the-bug/</link>
      <guid>https://growth.iangoh.com/blog/the-customer-should-not-have-to-report-the-bug/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Retool: outbound as PMF research, Slack trial rooms, overnight feature gaps, language-market fit, wrong-ICP exits, and launching only after developer-grade proof.</description>
    </item>
    <item>
      <title>The category fight should clean up the whole site</title>
      <link>https://growth.iangoh.com/blog/the-category-fight-should-clean-up-the-whole-site/</link>
      <guid>https://growth.iangoh.com/blog/the-category-fight-should-clean-up-the-whole-site/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why build-in-public updates, sharper anti-incumbent pages, one clean archive, focus-area content clusters, relevant outreach, and live complaint listening usually do more than louder startup marketing.</description>
    </item>
    <item>
      <title>Word-of-mouth needs something to carry</title>
      <link>https://growth.iangoh.com/blog/word-of-mouth-needs-something-to-carry/</link>
      <guid>https://growth.iangoh.com/blog/word-of-mouth-needs-something-to-carry/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Baremetrics: paid-only early traction, painkiller messaging, one-click Stripe history, customer tweets, paid MVP validation, rebuilds from paying users, and public demos that convert.</description>
    </item>
    <item>
      <title>The first mile is part of the product</title>
      <link>https://growth.iangoh.com/blog/the-first-mile-is-part-of-the-product/</link>
      <guid>https://growth.iangoh.com/blog/the-first-mile-is-part-of-the-product/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Superhuman’s growth lessons: measure pull before scaling, narrow around loved users, turn onboarding into research, and productize the parts of the live session that actually change behavior.</description>
    </item>
    <item>
      <title>The first real market may arrive sideways</title>
      <link>https://growth.iangoh.com/blog/the-first-real-market-may-arrive-sideways/</link>
      <guid>https://growth.iangoh.com/blog/the-first-real-market-may-arrive-sideways/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Snapchat’s early growth: unexpected superfan segments, one-on-one demos, camera-first creation, co-present viewing, direct reply loops, and measuring word-of-mouth against press.</description>
    </item>
    <item>
      <title>The local marketplace should borrow the old workflow first</title>
      <link>https://growth.iangoh.com/blog/the-local-marketplace-should-borrow-the-old-workflow-first/</link>
      <guid>https://growth.iangoh.com/blog/the-local-marketplace-should-borrow-the-old-workflow-first/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Slice’s early pizzeria growth: loyalty-first positioning, founder field sales, physical credibility, fax-order bridges, reverse-franchise economics, and merchant-friendly pricing.</description>
    </item>
    <item>
      <title>The first newsletter subscribers are often in the room</title>
      <link>https://growth.iangoh.com/blog/the-first-newsletter-subscribers-are-often-in-the-room/</link>
      <guid>https://growth.iangoh.com/blog/the-first-newsletter-subscribers-are-often-in-the-room/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Morning Brew’s early growth: classroom signups, ambassador filtering, newsletter cross-promos, referral behavior design, owned growth tooling, and paid acquisition after the referral loop works.</description>
    </item>
    <item>
      <title>The link should sell the recipient before the sender explains</title>
      <link>https://growth.iangoh.com/blog/the-link-should-sell-the-recipient-before-the-sender-explains/</link>
      <guid>https://growth.iangoh.com/blog/the-link-should-sell-the-recipient-before-the-sender-explains/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Calendly’s early growth: competitor teardown, recipient-first design, partner-seeded first users, parent-teacher workflow spread, free launch timing, and feature-request sales calls.</description>
    </item>
    <item>
      <title>The library should survive the first wrong price</title>
      <link>https://growth.iangoh.com/blog/the-library-should-survive-the-first-wrong-price/</link>
      <guid>https://growth.iangoh.com/blog/the-library-should-survive-the-first-wrong-price/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on Page Flows: audience interviews, failed pricing, fake payment tests, quarterly pricing, long-tail SEO pages, and low-overhead content-library economics.</description>
    </item>
    <item>
      <title>The newsletter growth loop should have a memory</title>
      <link>https://growth.iangoh.com/blog/the-newsletter-growth-loop-should-have-a-memory/</link>
      <guid>https://growth.iangoh.com/blog/the-newsletter-growth-loop-should-have-a-memory/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on First 1000’s path from 2,000 to 10,000 subscribers: supporter CRMs, launch-day batching, monthly referral resets, rotating asks, and making the product easy to mention.</description>
    </item>
    <item>
      <title>The GitHub release page should finish the upgrade decision</title>
      <link>https://growth.iangoh.com/blog/the-github-release-page-should-finish-the-upgrade-decision/</link>
      <guid>https://growth.iangoh.com/blog/the-github-release-page-should-finish-the-upgrade-decision/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why grouped release notes, honest pre-release labels, stable latest pointers, durable latest links, and asset verification make GitHub releases easier to trust and easier to ship.</description>
    </item>
    <item>
      <title>The community thread should already contain the problem</title>
      <link>https://growth.iangoh.com/blog/the-community-thread-should-already-contain-the-problem/</link>
      <guid>https://growth.iangoh.com/blog/the-community-thread-should-already-contain-the-problem/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain essay on five Quo/OpenPhone early-growth moves: Reddit alerting, adjacent problem posts, requested-feature updates, review-worthy support moments, and persona data before horizontal scale.</description>
    </item>
    <item>
      <title>The price change is a research instrument</title>
      <link>https://growth.iangoh.com/blog/the-price-change-is-a-research-instrument/</link>
      <guid>https://growth.iangoh.com/blog/the-price-change-is-a-research-instrument/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A founder-readable essay on what Quo/OpenPhone and Baremetrics teach about charging the beta, segmenting outbound, surveying drop-offs, choosing media by buyer fit, and rebuilding from paying-customer feedback.</description>
    </item>
    <item>
      <title>The first customers should leave fingerprints on the product</title>
      <link>https://growth.iangoh.com/blog/the-first-customers-should-leave-fingerprints-on-the-product/</link>
      <guid>https://growth.iangoh.com/blog/the-first-customers-should-leave-fingerprints-on-the-product/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>A practical essay on five early-growth moves from OpenPhone and Baremetrics: comment-gated community demand, support through the product, disappointment surveys, instant imports, and admin-approved Q&amp;A sessions.</description>
    </item>
    <item>
      <title>The Chrome Web Store page should survive the release channel</title>
      <link>https://growth.iangoh.com/blog/the-chrome-web-store-page-should-survive-the-release-channel/</link>
      <guid>https://growth.iangoh.com/blog/the-chrome-web-store-page-should-survive-the-release-channel/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why reviewer instructions, deferred publishing, parallel beta channels, sticky update channels, locale-matched assets, and category discipline make a Chrome Web Store launch easier to trust and easier to control.</description>
    </item>
    <item>
      <title>The Safari extension page should finish the setup before the install</title>
      <link>https://growth.iangoh.com/blog/the-safari-extension-page-should-finish-the-setup-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-safari-extension-page-should-finish-the-setup-before-the-install/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why the Extensions shelf, cross-browser porting, TestFlight rehearsal, setup-first screenshots, honest in-use proof, and locale-aware metadata make Safari extensions easier to trust and easier to grow.</description>
    </item>
    <item>
      <title>The YouTube channel should route the next watch before the viewer leaves</title>
      <link>https://growth.iangoh.com/blog/the-youtube-channel-should-route-the-next-watch-before-the-viewer-leaves/</link>
      <guid>https://growth.iangoh.com/blog/the-youtube-channel-should-route-the-next-watch-before-the-viewer-leaves/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why YouTube growth gets stronger when the channel has real routing: the right ownership model, a split homepage for strangers and subscribers, official series paths, chapters, and clear handoffs from Shorts and outros.</description>
    </item>
    <item>
      <title>The Substack welcome path should not end at the subscribe box</title>
      <link>https://growth.iangoh.com/blog/the-substack-welcome-path-should-not-end-at-the-subscribe-box/</link>
      <guid>https://growth.iangoh.com/blog/the-substack-welcome-path-should-not-end-at-the-subscribe-box/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why the better Substack move is to keep the browse alive, match the first email to the entry path, learn intent early, open community with clear rules, and migrate audio audiences without dropping the feed.</description>
    </item>
    <item>
      <title>The Google Chat app should survive the first admin and the first space</title>
      <link>https://growth.iangoh.com/blog/the-google-chat-app-should-survive-the-first-admin-and-the-first-space/</link>
      <guid>https://growth.iangoh.com/blog/the-google-chat-app-should-survive-the-first-admin-and-the-first-space/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Google Chat growth depends on picking the right audience, clearing the admin gate, teaching the first workflow from the command menu, and making review access feel native instead of bolted on.</description>
    </item>
    <item>
      <title>The VS Code extension page should finish the trust check</title>
      <link>https://growth.iangoh.com/blog/the-vs-code-extension-page-should-finish-the-trust-check/</link>
      <guid>https://growth.iangoh.com/blog/the-vs-code-extension-page-should-finish-the-trust-check/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why sharper search metadata, shelf-fit categories, a real README, visible support, honest listing signals, and a verified publisher track make VS Code extensions easier to install without doubt.</description>
    </item>
    <item>
      <title>The Firefox Add-ons page should remove the surprise before install</title>
      <link>https://growth.iangoh.com/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/</link>
      <guid>https://growth.iangoh.com/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why naming, no-surprises copy, paid-feature disclosure, reviewable source packages, in-listing privacy text, and channel-tagged AMO links make Firefox add-ons easier to trust and easier to grow.</description>
    </item>
    <item>
      <title>The Microsoft Edge Add-ons page should finish the review before the install</title>
      <link>https://growth.iangoh.com/blog/the-microsoft-edge-add-ons-page-should-finish-the-review-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-microsoft-edge-add-ons-page-should-finish-the-review-before-the-install/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why manifest copy, hidden visibility, localized search metadata, shared assets, certification notes, and the trailing Featured badge matter more than another extension tagline tweak.</description>
    </item>
    <item>
      <title>The JetBrains plugin page should finish the IDE trust check</title>
      <link>https://growth.iangoh.com/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/</link>
      <guid>https://growth.iangoh.com/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why tighter names, preview-card copy, workflow screenshots, search-fit tags, verified vendor proof, and hidden releases make JetBrains Marketplace pages convert with less doubt.</description>
    </item>
    <item>
      <title>The docs route should fail in review, not in public</title>
      <link>https://growth.iangoh.com/blog/the-docs-route-should-fail-in-review-not-in-public/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-route-should-fail-in-review-not-in-public/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why preview mode, isolated branches, pre-save linting, recurring docs audits, zero-lint merge gates, and teammate approval make documentation behave more like product infrastructure than website copy.</description>
    </item>
    <item>
      <title>The trust center should finish the security review before the inbox starts</title>
      <link>https://growth.iangoh.com/blog/the-trust-center-should-finish-the-security-review-before-the-inbox-starts/</link>
      <guid>https://growth.iangoh.com/blog/the-trust-center-should-finish-the-security-review-before-the-inbox-starts/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why shared knowledge bases, visibility ladders, imported questionnaires, owner cadences, on-page intake, and routed answers make trust centers behave more like systems than showrooms.</description>
    </item>
    <item>
      <title>The Airtable base should survive the template copy</title>
      <link>https://growth.iangoh.com/blog/the-airtable-base-should-survive-the-template-copy/</link>
      <guid>https://growth.iangoh.com/blog/the-airtable-base-should-survive-the-template-copy/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why job-led template shelves, linked record templates, interface forms, sync sources, local automations, and multi-source proof tables turn a copied base into a working system.</description>
    </item>
    <item>
      <title>The Webflow Marketplace page should finish the install path</title>
      <link>https://growth.iangoh.com/blog/the-webflow-marketplace-page-should-finish-the-install-path/</link>
      <guid>https://growth.iangoh.com/blog/the-webflow-marketplace-page-should-finish-the-install-path/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why publisher identity, job-shaped copy, workflow screenshots, clean OAuth, review-ready demos, and honest policy pages make Webflow app listings convert with less friction.</description>
    </item>
    <item>
      <title>The newsletter should classify the reader before the second send</title>
      <link>https://growth.iangoh.com/blog/the-newsletter-should-classify-the-reader-before-the-second-send/</link>
      <guid>https://growth.iangoh.com/blog/the-newsletter-should-classify-the-reader-before-the-second-send/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why one welcome system, segmented automations, subscribe surveys, page-specific forms, signup flows, and custom domains make a beehiiv newsletter act more like a product.</description>
    </item>
    <item>
      <title>The Miro Marketplace page should teach the workflow before the install</title>
      <link>https://growth.iangoh.com/blog/the-miro-marketplace-page-should-teach-the-workflow-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-miro-marketplace-page-should-teach-the-workflow-before-the-install/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why board-job naming, workflow screenshots, 450-character setup copy, partner profiles, pricing sync, and disciplined review ops make Miro listings easier to trust.</description>
    </item>
    <item>
      <title>The template page should recruit the next site owner</title>
      <link>https://growth.iangoh.com/blog/the-template-page-should-recruit-the-next-site-owner/</link>
      <guid>https://growth.iangoh.com/blog/the-template-page-should-recruit-the-next-site-owner/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why proof images, search-shaped copy, pricing relaunches, remix-link commissions, trust cues, and edit-safe polish make creator marketplaces compound.</description>
    </item>
    <item>
      <title>The Atlassian Marketplace page should answer the admin before the demo</title>
      <link>https://growth.iangoh.com/blog/the-atlassian-marketplace-page-should-answer-the-admin-before-the-demo/</link>
      <guid>https://growth.iangoh.com/blog/the-atlassian-marketplace-page-should-answer-the-admin-before-the-demo/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why app naming, trust disclosures, pricing clarity, license-state testing, editions, and distinct partner branding make Atlassian Marketplace pages easier for real buyers to approve.</description>
    </item>
    <item>
      <title>The Shopify app page should qualify the install before it starts</title>
      <link>https://growth.iangoh.com/blog/the-shopify-app-page-should-qualify-the-install-before-it-starts/</link>
      <guid>https://growth.iangoh.com/blog/the-shopify-app-page-should-qualify-the-install-before-it-starts/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why brand-led naming, benefit-led media, guided demos, pricing discipline, translated listings, and install filters make Shopify App Store growth cleaner.</description>
    </item>
    <item>
      <title>The spike should teach the next system</title>
      <link>https://growth.iangoh.com/blog/the-spike-should-teach-the-next-system/</link>
      <guid>https://growth.iangoh.com/blog/the-spike-should-teach-the-next-system/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Buffer&apos;s launch and editorial lessons point to the same discipline: use early traffic, drop-off, and reader behavior to improve the next version instead of celebrating the first burst.</description>
    </item>
    <item>
      <title>The template should survive the duplicate</title>
      <link>https://growth.iangoh.com/blog/the-template-should-survive-the-duplicate/</link>
      <guid>https://growth.iangoh.com/blog/the-template-should-survive-the-duplicate/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why specific use cases, local-language editions, email restraint, demo-safe links, and webhook follow-up make Notion Marketplace pages hold up after the add.</description>
    </item>
    <item>
      <title>The repository should answer the trust question first</title>
      <link>https://growth.iangoh.com/blog/the-repository-should-answer-the-trust-question-first/</link>
      <guid>https://growth.iangoh.com/blog/the-repository-should-answer-the-trust-question-first/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why GitHub trust surfaces such as default health files, contribution rules, security policy, maintainer proof, and visible support paths often do more growth work than another launch thread.</description>
    </item>
    <item>
      <title>The issue intake should finish the sorting first</title>
      <link>https://growth.iangoh.com/blog/the-issue-intake-should-finish-the-sorting-first/</link>
      <guid>https://growth.iangoh.com/blog/the-issue-intake-should-finish-the-sorting-first/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why GitHub support and community growth get better when the chooser, the form, the discussion handoff, and the maintainer replies sort the work before anyone starts triaging by hand.</description>
    </item>
    <item>
      <title>The community archive should answer the next visitor</title>
      <link>https://growth.iangoh.com/blog/the-community-archive-should-answer-the-next-visitor/</link>
      <guid>https://growth.iangoh.com/blog/the-community-archive-should-answer-the-next-visitor/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why structured GitHub Discussions, answerable threads, pinned routes, category lanes, and weekly insight reviews turn a repo community into a better support and discovery surface.</description>
    </item>
    <item>
      <title>The newsletter should know which growth to keep</title>
      <link>https://growth.iangoh.com/blog/the-newsletter-should-know-which-growth-to-keep/</link>
      <guid>https://growth.iangoh.com/blog/the-newsletter-should-know-which-growth-to-keep/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why clean paid acquisition, visible referral ladders, branded routes, and open recommendation surfaces usually beat another batch of cheap subscribers.</description>
    </item>
    <item>
      <title>The newsletter should do the second subscribe</title>
      <link>https://growth.iangoh.com/blog/the-newsletter-should-do-the-second-subscribe/</link>
      <guid>https://growth.iangoh.com/blog/the-newsletter-should-do-the-second-subscribe/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why recommendation surfaces, welcome-page endorsements, gift referrals, and in-post sharing loops usually compound better than a lonely signup form.</description>
    </item>
    <item>
      <title>The monday marketplace page should survive the request-to-add click</title>
      <link>https://growth.iangoh.com/blog/the-monday-marketplace-page-should-survive-the-request-to-add-click/</link>
      <guid>https://growth.iangoh.com/blog/the-monday-marketplace-page-should-survive-the-request-to-add-click/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why monday marketplace growth gets better when search terms, demos, trust badges, partner proof, onboarding defaults, and pricing releases work like one route instead of six separate chores.</description>
    </item>
    <item>
      <title>The Teams Store page should survive the first admin review</title>
      <link>https://growth.iangoh.com/blog/the-teams-store-page-should-survive-the-first-admin-review/</link>
      <guid>https://growth.iangoh.com/blog/the-teams-store-page-should-survive-the-first-admin-review/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Teams store growth depends on tighter metadata, cleaner first-run proof, stronger icon discipline, and trust work finished before the promo plan starts.</description>
    </item>
    <item>
      <title>The Canva app page should survive the first open panel</title>
      <link>https://growth.iangoh.com/blog/the-canva-app-page-should-survive-the-first-open-panel/</link>
      <guid>https://growth.iangoh.com/blog/the-canva-app-page-should-survive-the-first-open-panel/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why the short description, hero image, trust links, review prep, mobile path, and one tight use case do more for Canva app growth than a pretty listing alone.</description>
    </item>
    <item>
      <title>The plugin directory page should survive the first update</title>
      <link>https://growth.iangoh.com/blog/the-plugin-directory-page-should-survive-the-first-update/</link>
      <guid>https://growth.iangoh.com/blog/the-plugin-directory-page-should-survive-the-first-update/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why WordPress plugin growth gets better when the readme line, release tag, setup notes, screenshots, and downloadable code all tell the same story to the admin.</description>
    </item>
    <item>
      <title>The founder should stay in the room</title>
      <link>https://growth.iangoh.com/blog/the-founder-should-stay-in-the-room/</link>
      <guid>https://growth.iangoh.com/blog/the-founder-should-stay-in-the-room/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>A practical note on why small community channels work better when the founder keeps answering, explaining, and leaving proof behind.</description>
    </item>
    <item>
      <title>The agent tool listing should survive the approval screen</title>
      <link>https://growth.iangoh.com/blog/the-agent-tool-listing-should-survive-the-approval-screen/</link>
      <guid>https://growth.iangoh.com/blog/the-agent-tool-listing-should-survive-the-approval-screen/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why HubSpot agent-tool growth gets better when scopes, use cases, config, naming, and proof video all describe one tool a buyer can actually trust.</description>
    </item>
    <item>
      <title>The Discord app page should finish the Add App click</title>
      <link>https://growth.iangoh.com/blog/the-discord-app-page-should-finish-the-add-app-click/</link>
      <guid>https://growth.iangoh.com/blog/the-discord-app-page-should-finish-the-add-app-click/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Discord growth gets better when discovery timing, install links, search copy, proof-first assets, and support fields work like one route instead of five disconnected profile settings.</description>
    </item>
    <item>
      <title>The AppExchange listing should survive the trial handoff</title>
      <link>https://growth.iangoh.com/blog/the-appexchange-listing-should-survive-the-trial-handoff/</link>
      <guid>https://growth.iangoh.com/blog/the-appexchange-listing-should-survive-the-trial-handoff/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why AppExchange growth gets better when package linkage, review timing, trial templates, install testing, scan reports, and reviewer access work like one route instead of six separate partner chores.</description>
    </item>
    <item>
      <title>The Zoom Marketplace page should survive the first admin click</title>
      <link>https://growth.iangoh.com/blog/the-zoom-marketplace-page-should-survive-the-first-admin-click/</link>
      <guid>https://growth.iangoh.com/blog/the-zoom-marketplace-page-should-survive-the-first-admin-click/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Zoom Marketplace growth improves when the search snippet, audience fit, docs, gallery, and access handoff work like one careful route instead of five separate fields.</description>
    </item>
    <item>
      <title>The marketplace page should answer the admin first</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-page-should-answer-the-admin-first/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-page-should-answer-the-admin-first/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why Google Workspace Marketplace growth gets better when screenshots, support links, regional targeting, draft updates, scope timing, and org-unit rollout all reduce install fear for the buyer with the keys.</description>
    </item>
    <item>
      <title>The Product Hunt launch should stay usable after the spike</title>
      <link>https://growth.iangoh.com/blog/the-product-hunt-launch-should-stay-usable-after-the-spike/</link>
      <guid>https://growth.iangoh.com/blog/the-product-hunt-launch-should-stay-usable-after-the-spike/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why live product access, tiny social proof assets, adjacent creator DMs, in-app review asks, and Product Hub review timing usually beat a prettier launch-day ceremony.</description>
    </item>
    <item>
      <title>The LinkedIn form should know where the lead goes</title>
      <link>https://growth.iangoh.com/blog/the-linkedin-form-should-know-where-the-lead-goes/</link>
      <guid>https://growth.iangoh.com/blog/the-linkedin-form-should-know-where-the-lead-goes/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why LinkedIn lead-gen forms work better when routing, field count, sync mapping, test submissions, and document previews are treated like one sales handoff.</description>
    </item>
    <item>
      <title>The Show HN thread should finish the first technical conversation</title>
      <link>https://growth.iangoh.com/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/</link>
      <guid>https://growth.iangoh.com/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why Hacker News launches work better when the post, first comment, and reply behavior feel like one honest technical conversation instead of a launch stunt.</description>
    </item>
    <item>
      <title>GitHub Marketplace pages should remove install fear</title>
      <link>https://growth.iangoh.com/blog/github-marketplace-pages-should-remove-install-fear/</link>
      <guid>https://growth.iangoh.com/blog/github-marketplace-pages-should-remove-install-fear/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why GitHub Marketplace growth improves when the listing, card, setup path, trial UI, and cancellation flow feel like one careful product instead of five separate chores.</description>
    </item>
    <item>
      <title>The marketplace page should finish the admin path</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-page-should-finish-the-admin-path/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-page-should-finish-the-admin-path/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why AppSource and Microsoft Marketplace pages win when they carry the buyer from search snippet to setup handoff instead of stopping at feature copy.</description>
    </item>
    <item>
      <title>The AppSumo page should answer the support queue before launch day</title>
      <link>https://growth.iangoh.com/blog/the-appsumo-page-should-answer-the-support-queue-before-launch-day/</link>
      <guid>https://growth.iangoh.com/blog/the-appsumo-page-should-answer-the-support-queue-before-launch-day/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Why tier cards, working test accounts, honest review timing, founder videos, and pre-written help content beat launch-week scramble.</description>
    </item>
    <item>
      <title>The Community page should teach the tool before the install</title>
      <link>https://growth.iangoh.com/blog/the-community-page-should-teach-the-tool-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-community-page-should-teach-the-tool-before-the-install/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why the team profile, proof links, search-fit copy, media demo, playground file, and public reply loop do more for Figma Community growth than another launch post.</description>
    </item>
    <item>
      <title>The help center should look like the company, not the tooling</title>
      <link>https://growth.iangoh.com/blog/the-help-center-should-look-like-the-company-not-the-tooling/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-should-look-like-the-company-not-the-tooling/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why the support domain, share image, footer links, typography, and crawl settings quietly decide whether a help center builds trust or leaks it.</description>
    </item>
    <item>
      <title>The Slack app directory page should answer the admin&apos;s next question</title>
      <link>https://growth.iangoh.com/blog/the-slack-app-directory-page-should-answer-the-admins-next-question/</link>
      <guid>https://growth.iangoh.com/blog/the-slack-app-directory-page-should-answer-the-admins-next-question/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why the short description, landing page proof, support path, link-triggered install suggestions, and non-dev review rehearsal do more for Slack app growth than another generic integration page.</description>
    </item>
    <item>
      <title>The feedback board should recruit the beta cohort before the roadmap meeting</title>
      <link>https://growth.iangoh.com/blog/the-feedback-board-should-recruit-the-beta-cohort-before-the-roadmap-meeting/</link>
      <guid>https://growth.iangoh.com/blog/the-feedback-board-should-recruit-the-beta-cohort-before-the-roadmap-meeting/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why better request entrypoints, Slack routing, MRR ranking, voter exports, and seeded boards turn a feedback portal into a faster product-growth loop.</description>
    </item>
    <item>
      <title>The extension listing should earn the install before the permission prompt</title>
      <link>https://growth.iangoh.com/blog/the-extension-listing-should-earn-the-install-before-the-permission-prompt/</link>
      <guid>https://growth.iangoh.com/blog/the-extension-listing-should-earn-the-install-before-the-permission-prompt/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why the summary, screenshots, promo assets, localization data, review loop, and login path do more for Chrome Web Store growth than another clever description rewrite.</description>
    </item>
    <item>
      <title>The waitlist should act like a working queue</title>
      <link>https://growth.iangoh.com/blog/the-waitlist-should-act-like-a-working-queue/</link>
      <guid>https://growth.iangoh.com/blog/the-waitlist-should-act-like-a-working-queue/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why helpful-comment ratios, community residency, reply bumps, conversation-first follow-up, and explicit pay signals beat vanity signups.</description>
    </item>
    <item>
      <title>Support starts paying off before the ticket exists</title>
      <link>https://growth.iangoh.com/blog/support-starts-paying-off-before-the-ticket-exists/</link>
      <guid>https://growth.iangoh.com/blog/support-starts-paying-off-before-the-ticket-exists/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why support QA, self-serve funnel gaps, message tagging, event-timed research, and goal-based lifecycle prompts do more for activation than another glossy help center rewrite.</description>
    </item>
    <item>
      <title>The Product Hunt page should keep working after launch day</title>
      <link>https://growth.iangoh.com/blog/the-product-hunt-page-should-keep-working-after-launch-day/</link>
      <guid>https://growth.iangoh.com/blog/the-product-hunt-page-should-keep-working-after-launch-day/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why community runway, teaser-page demand, a drafted first comment, category fit, and post-launch reviews make Product Hunt more useful than a one-day spike.</description>
    </item>
    <item>
      <title>The first customers usually come from the conversation already happening</title>
      <link>https://growth.iangoh.com/blog/the-first-customers-usually-come-from-the-conversation-already-happening/</link>
      <guid>https://growth.iangoh.com/blog/the-first-customers-usually-come-from-the-conversation-already-happening/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why problem-thread replies, founder-story context, visible product proof, manual walkthroughs, and a free-channel reachability test beat another launch-shaped fantasy.</description>
    </item>
    <item>
      <title>The answer should travel before the queue grows</title>
      <link>https://growth.iangoh.com/blog/the-answer-should-travel-before-the-queue-grows/</link>
      <guid>https://growth.iangoh.com/blog/the-answer-should-travel-before-the-queue-grows/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why AI-fed help content, Messenger search, Inbox article reuse, proactive sends, repair-triggering reactions, and article reporting beat another support hiring panic.</description>
    </item>
    <item>
      <title>The Shopify app page should reduce review drag before it chases visibility</title>
      <link>https://growth.iangoh.com/blog/the-shopify-app-page-should-reduce-review-drag-before-it-chases-visibility/</link>
      <guid>https://growth.iangoh.com/blog/the-shopify-app-page-should-reduce-review-drag-before-it-chases-visibility/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why staged visibility, AI self-review, one-clean-pass resubmission, compliance work, reviewer enablement, and better merchant reviews make Shopify App Store growth easier to trust.</description>
    </item>
    <item>
      <title>The agent only sells what the pages already know</title>
      <link>https://growth.iangoh.com/blog/the-agent-only-sells-what-the-pages-already-know/</link>
      <guid>https://growth.iangoh.com/blog/the-agent-only-sells-what-the-pages-already-know/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why buyer-journey previews, broad high-intent rollout, failed-conversation review, frontline objection logs, and day-zero launch updates make AI sales agents more believable.</description>
    </item>
    <item>
      <title>The marketplace listing should act like an operating document</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-listing-should-act-like-an-operating-document/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-listing-should-act-like-an-operating-document/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why buyer-job categories, real setup docs, honest integration pricing, visible support coverage, and domain-level analytics make marketplace pages easier to trust and easier to improve.</description>
    </item>
    <item>
      <title>The Google Play page should keep the promise after the tap</title>
      <link>https://growth.iangoh.com/blog/the-google-play-page-should-keep-the-promise-after-the-tap/</link>
      <guid>https://growth.iangoh.com/blog/the-google-play-page-should-keep-the-promise-after-the-tap/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why keyword-matched listings, custom URLs, listing groups, patchable deep links, and direct promo routes make Google Play growth feel less leaky.</description>
    </item>
    <item>
      <title>Complex onboarding should prove the value before the hard step</title>
      <link>https://growth.iangoh.com/blog/complex-onboarding-should-prove-the-value-before-the-hard-step/</link>
      <guid>https://growth.iangoh.com/blog/complex-onboarding-should-prove-the-value-before-the-hard-step/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why realistic previews, value-first step order, benefit-led copy, skippable anxiety points, and off-product guides make heavy onboarding easier to finish.</description>
    </item>
    <item>
      <title>Onboarding should change when the customer changed</title>
      <link>https://growth.iangoh.com/blog/onboarding-should-change-when-the-customer-changed/</link>
      <guid>https://growth.iangoh.com/blog/onboarding-should-change-when-the-customer-changed/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why audience shifts, team setup paths, shared ownership, activation milestones, and timed nudges matter more than polishing the same old first-run flow.</description>
    </item>
    <item>
      <title>The directory profile should do the shortlist work before the demo</title>
      <link>https://growth.iangoh.com/blog/the-directory-profile-should-do-the-shortlist-work-before-the-demo/</link>
      <guid>https://growth.iangoh.com/blog/the-directory-profile-should-do-the-shortlist-work-before-the-demo/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why category fit, profile completeness, detailed review asks, firmographic review mix, and comparison-ready pricing help software directory pages move a buyer closer to yes.</description>
    </item>
    <item>
      <title>The support queue should know what kind of thread it is</title>
      <link>https://growth.iangoh.com/blog/the-support-queue-should-know-what-kind-of-thread-it-is/</link>
      <guid>https://growth.iangoh.com/blog/the-support-queue-should-know-what-kind-of-thread-it-is/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why solved category defaults, solved tags, private-message resolutions, cohort-based approvals, and staged community rollouts make support archives easier to trust.</description>
    </item>
    <item>
      <title>The review request should show up after the proof</title>
      <link>https://growth.iangoh.com/blog/the-review-request-should-show-up-after-the-proof/</link>
      <guid>https://growth.iangoh.com/blog/the-review-request-should-show-up-after-the-proof/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why in-product asks, milestone timing, renewal moments, honest targeting, and customer-program refreshes make G2 reviews more believable and more useful.</description>
    </item>
    <item>
      <title>The community should teach the first contribution before it asks for loyalty</title>
      <link>https://growth.iangoh.com/blog/the-community-should-teach-the-first-contribution-before-it-asks-for-loyalty/</link>
      <guid>https://growth.iangoh.com/blog/the-community-should-teach-the-first-contribution-before-it-asks-for-loyalty/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why welcome messages, guided first posts, recurring events, and visible expert identity make a branded community easier to trust and easier to join.</description>
    </item>
    <item>
      <title>The admin listing should not hide the real setup</title>
      <link>https://growth.iangoh.com/blog/the-admin-listing-should-not-hide-the-real-setup/</link>
      <guid>https://growth.iangoh.com/blog/the-admin-listing-should-not-hide-the-real-setup/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why shared ownership, org-transfer planning, setup links, analytics access, and cleaner metadata make a Google Workspace Marketplace page do real buying work.</description>
    </item>
    <item>
      <title>The forum should route the newcomer before they post</title>
      <link>https://growth.iangoh.com/blog/the-forum-should-route-the-newcomer-before-they-post/</link>
      <guid>https://growth.iangoh.com/blog/the-forum-should-route-the-newcomer-before-they-post/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why category banners, sidebars, scoped idea voting, vote-follow prompts, and category-level moderation keep a community useful before the reply count explodes.</description>
    </item>
    <item>
      <title>A launch should teach before it interrupts</title>
      <link>https://growth.iangoh.com/blog/a-launch-should-teach-before-it-interrupts/</link>
      <guid>https://growth.iangoh.com/blog/a-launch-should-teach-before-it-interrupts/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why specialist launch support, prewritten help content, segmented feature messaging, contact suppression, and event-based measurement make releases easier to trust.</description>
    </item>
    <item>
      <title>The G2 Profile should help the buyer check the claim</title>
      <link>https://growth.iangoh.com/blog/the-g2-profile-should-help-the-buyer-check-the-claim/</link>
      <guid>https://growth.iangoh.com/blog/the-g2-profile-should-help-the-buyer-check-the-claim/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Why category placement, pricing, visual proof, interactive demos, downloadable evidence, and honest reviews make a G2 profile more useful than a badge wall.</description>
    </item>
    <item>
      <title>The support forum should stop acting like a chat room</title>
      <link>https://growth.iangoh.com/blog/the-support-forum-should-stop-acting-like-a-chat-room/</link>
      <guid>https://growth.iangoh.com/blog/the-support-forum-should-stop-acting-like-a-chat-room/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why structured intake, solved-state search, public ownership, docs indexes, and visible experts turn a community archive into a better growth surface.</description>
    </item>
    <item>
      <title>The help center should stay private until it can carry the work</title>
      <link>https://growth.iangoh.com/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why setup mode, promoted answers, manual order, timed publishing, and browseable collections make a help launch safer and more useful.</description>
    </item>
    <item>
      <title>The Atlassian Marketplace page should close the diligence gap</title>
      <link>https://growth.iangoh.com/blog/the-atlassian-marketplace-page-should-close-the-diligence-gap/</link>
      <guid>https://growth.iangoh.com/blog/the-atlassian-marketplace-page-should-close-the-diligence-gap/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why review buffers, licensing preflight, support detail, edition packaging, and pricing aftercare make an Atlassian Marketplace listing easier to trust and easier to buy from.</description>
    </item>
    <item>
      <title>The GitHub Marketplace page should survive the billing handoff</title>
      <link>https://growth.iangoh.com/blog/the-github-marketplace-page-should-survive-the-billing-handoff/</link>
      <guid>https://growth.iangoh.com/blog/the-github-marketplace-page-should-survive-the-billing-handoff/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why contact ownership, installability, staged pricing, plan replacement, and funnel metrics make GitHub Marketplace listings easier to trust and easier to buy from.</description>
    </item>
    <item>
      <title>The app directory page should answer the admin before the install</title>
      <link>https://growth.iangoh.com/blog/the-app-directory-page-should-answer-the-admin-before-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-app-directory-page-should-answer-the-admin-before-the-install/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why install-ready onboarding, fresh support links, permission discipline, verified publisher signals, and factual listing copy make app directories easier to trust.</description>
    </item>
    <item>
      <title>The answer should interrupt the ticket before it opens</title>
      <link>https://growth.iangoh.com/blog/the-answer-should-interrupt-the-ticket-before-it-opens/</link>
      <guid>https://growth.iangoh.com/blog/the-answer-should-interrupt-the-ticket-before-it-opens/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why subject-line suggestions, no-result triage, ticket-to-search ratios, clearer filters, and answer boxes make the help center easier to trust and cheaper to run.</description>
    </item>
    <item>
      <title>The marketplace listing should survive the admin handoff</title>
      <link>https://growth.iangoh.com/blog/the-marketplace-listing-should-survive-the-admin-handoff/</link>
      <guid>https://growth.iangoh.com/blog/the-marketplace-listing-should-survive-the-admin-handoff/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why combined integrations, region discipline, measured listing edits, draft testing, and scope-verification gates make admin-facing marketplace pages easier to trust.</description>
    </item>
    <item>
      <title>The feedback queue should show what it heard</title>
      <link>https://growth.iangoh.com/blog/the-feedback-queue-should-show-what-it-heard/</link>
      <guid>https://growth.iangoh.com/blog/the-feedback-queue-should-show-what-it-heard/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why support rotations, Slack capture, miss queues, smarter first replies, and synced statuses make the backlog easier to trust.</description>
    </item>
    <item>
      <title>The launch thread should look alive before it looks popular</title>
      <link>https://growth.iangoh.com/blog/the-launch-thread-should-look-alive-before-it-looks-popular/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-thread-should-look-alive-before-it-looks-popular/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why maker context, runnable product surfaces, native community posts, early replies, and a clear handoff usually beat launch-day vanity metrics.</description>
    </item>
    <item>
      <title>The docs route should feel boring even when the product is moving</title>
      <link>https://growth.iangoh.com/blog/the-docs-route-should-feel-boring-even-when-the-product-is-moving/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-route-should-feel-boring-even-when-the-product-is-moving/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why broken-link build failures, preview noindex rules, hidden unreleased docs, file-based links, and custom 404 recovery pages make documentation easier to trust.</description>
    </item>
    <item>
      <title>The help article should know what comes next</title>
      <link>https://growth.iangoh.com/blog/the-help-article-should-know-what-comes-next/</link>
      <guid>https://growth.iangoh.com/blog/the-help-article-should-know-what-comes-next/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why richer feedback capture, recurring review, friction dashboards, recommended resources, and measured support-to-blog links usually outperform another generic help-center redesign.</description>
    </item>
    <item>
      <title>The status page should answer who is affected before support opens</title>
      <link>https://growth.iangoh.com/blog/the-status-page-should-answer-who-is-affected-before-support-opens/</link>
      <guid>https://growth.iangoh.com/blog/the-status-page-should-answer-who-is-affected-before-support-opens/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why maintenance reminders, uptime history, segmented pages, regional sub-pages, and customer-only status views turn incident comms into a trust surface.</description>
    </item>
    <item>
      <title>The next step should already be there</title>
      <link>https://growth.iangoh.com/blog/the-next-step-should-already-be-there/</link>
      <guid>https://growth.iangoh.com/blog/the-next-step-should-already-be-there/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why milestone suggestions, project-native docs, event-based checklists, prewired workflows, and public intake channels usually activate users better than blank-slate onboarding.</description>
    </item>
    <item>
      <title>The listing should do the first minute of onboarding</title>
      <link>https://growth.iangoh.com/blog/the-listing-should-do-the-first-minute-of-onboarding/</link>
      <guid>https://growth.iangoh.com/blog/the-listing-should-do-the-first-minute-of-onboarding/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why marketplace trust checks, scope honesty, privacy detail, preview pages, and embedded integrations turn directory traffic into real evaluation.</description>
    </item>
    <item>
      <title>The template should do the first setup step</title>
      <link>https://growth.iangoh.com/blog/the-template-should-do-the-first-setup-step/</link>
      <guid>https://growth.iangoh.com/blog/the-template-should-do-the-first-setup-step/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why scoped project templates, in-project document defaults, structured intake templates, sample-data previews, and private draft copies usually beat empty workspaces.</description>
    </item>
    <item>
      <title>The site should have a page for the question the buyer typed</title>
      <link>https://growth.iangoh.com/blog/the-site-should-have-a-page-for-the-question-the-buyer-typed/</link>
      <guid>https://growth.iangoh.com/blog/the-site-should-have-a-page-for-the-question-the-buyer-typed/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why comparison pages, product-led guides, free tools, intent-split pages, and deliberate multiple rankings usually beat one heroic homepage.</description>
    </item>
    <item>
      <title>The forum should keep the answer after the chat scrolls away</title>
      <link>https://growth.iangoh.com/blog/the-forum-should-keep-the-answer-after-the-chat-scrolls-away/</link>
      <guid>https://growth.iangoh.com/blog/the-forum-should-keep-the-answer-after-the-chat-scrolls-away/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why solved answers, request voting, intake templates, duplicate warnings, and doc-style forum categories usually beat one noisy community inbox.</description>
    </item>
    <item>
      <title>The switch page should finish the move</title>
      <link>https://growth.iangoh.com/blog/the-switch-page-should-finish-the-move/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-page-should-finish-the-move/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why dual-run sync, reviewable importers, field-mapping previews, fallback routing, preserved help-center structure, and URL-first archive imports usually convert better than migration promises.</description>
    </item>
    <item>
      <title>The trust surface should show the work</title>
      <link>https://growth.iangoh.com/blog/the-trust-surface-should-show-the-work/</link>
      <guid>https://growth.iangoh.com/blog/the-trust-surface-should-show-the-work/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why live issues, public decisions, code-level proof, roadmap comments, and open docs contributions often beat one more polished trust page.</description>
    </item>
    <item>
      <title>The status page should answer before the ticket does</title>
      <link>https://growth.iangoh.com/blog/the-status-page-should-answer-before-the-ticket-does/</link>
      <guid>https://growth.iangoh.com/blog/the-status-page-should-answer-before-the-ticket-does/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why a real status domain, quieter component subscriptions, prepared incident copy, embedded status, and plain postmortems usually beat one apologetic outage email.</description>
    </item>
    <item>
      <title>The feedback queue should carry revenue before volume</title>
      <link>https://growth.iangoh.com/blog/the-feedback-queue-should-carry-revenue-before-volume/</link>
      <guid>https://growth.iangoh.com/blog/the-feedback-queue-should-carry-revenue-before-volume/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why frontline pilots, cleaner request buckets, weekly demand-plus-revenue reviews, prospect-linked votes, and company-aware reports usually beat one louder feature board.</description>
    </item>
    <item>
      <title>The docs site should answer like one product</title>
      <link>https://growth.iangoh.com/blog/the-docs-site-should-answer-like-one-product/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-site-should-answer-like-one-product/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why a branded docs domain, draft redirects, path-preserving migrations, unified search, and explicit answer pages usually beat one more docs redesign.</description>
    </item>
    <item>
      <title>The App Store route should be judged after the install</title>
      <link>https://growth.iangoh.com/blog/the-app-store-route-should-be-judged-after-the-install/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-route-should-be-judged-after-the-install/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why source mix, peer benchmarks, post-install retention, and stricter offer-code operations usually produce a cleaner App Store growth system than screenshot panic.</description>
    </item>
    <item>
      <title>The App Store surface should know who it is for</title>
      <link>https://growth.iangoh.com/blog/the-app-store-surface-should-know-who-it-is-for/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-surface-should-know-who-it-is-for/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description>Why promoted purchases, segmented offer codes, win-back links, event reminders, and eligibility reports usually beat treating every App Store visitor like the same buyer.</description>
    </item>
    <item>
      <title>The App Store route should stay intact after the tap</title>
      <link>https://growth.iangoh.com/blog/the-app-store-route-should-stay-intact-after-the-tap/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-route-should-stay-intact-after-the-tap/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why tags, pre-order tests, locale maps, screenshot gates, deep-linked custom pages, and route-level analytics usually beat one more generic launch push.</description>
    </item>
    <item>
      <title>The changelog should prove the product keeps moving</title>
      <link>https://growth.iangoh.com/blog/the-changelog-should-prove-the-product-keeps-moving/</link>
      <guid>https://growth.iangoh.com/blog/the-changelog-should-prove-the-product-keeps-moving/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why draft-first imports, reviewed history backfills, branded RSS, production-tied completion, and auto-generated drafts usually beat a prettier release page.</description>
    </item>
    <item>
      <title>The AI discovery surface should teach the crawler and the agent</title>
      <link>https://growth.iangoh.com/blog/the-ai-discovery-surface-should-teach-the-crawler-and-the-agent/</link>
      <guid>https://growth.iangoh.com/blog/the-ai-discovery-surface-should-teach-the-crawler-and-the-agent/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why schema, crawl files, experience-backed writing, skill frontmatter, and one-command installs usually beat publishing one more invisible docs section.</description>
    </item>
    <item>
      <title>Directories start working when the page fits the search</title>
      <link>https://growth.iangoh.com/blog/directories-start-working-when-the-page-fits-the-search/</link>
      <guid>https://growth.iangoh.com/blog/directories-start-working-when-the-page-fits-the-search/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why intent-matched blurbs, niche alternatives pages, public form surfaces, DR-ranked shortlists, and live user language make directory work less fake and more useful.</description>
    </item>
    <item>
      <title>The feedback board should keep getting sharper after the vote</title>
      <link>https://growth.iangoh.com/blog/the-feedback-board-should-keep-getting-sharper-after-the-vote/</link>
      <guid>https://growth.iangoh.com/blog/the-feedback-board-should-keep-getting-sharper-after-the-vote/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why source URLs, update comments, segment-aware voter lists, honest ETAs, and fresh roadmap ordering usually beat a louder request portal.</description>
    </item>
    <item>
      <title>The request system should keep the customer on the same thread</title>
      <link>https://growth.iangoh.com/blog/the-request-system-should-keep-the-customer-on-the-same-thread/</link>
      <guid>https://growth.iangoh.com/blog/the-request-system-should-keep-the-customer-on-the-same-thread/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why customer portals, customer-facing status labels, portal backfills, mirrored inboxes, and required tagging usually beat one more support cleanup sprint.</description>
    </item>
    <item>
      <title>The thread should earn the click before the landing page does</title>
      <link>https://growth.iangoh.com/blog/the-thread-should-earn-the-click-before-the-landing-page-does/</link>
      <guid>https://growth.iangoh.com/blog/the-thread-should-earn-the-click-before-the-landing-page-does/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why early low-noise replies, permission-based DMs, short personal demos, quiet trust-building, and angle-tracking usually beat the broad launch post when you need the first real users.</description>
    </item>
    <item>
      <title>The integration should feel like your product, not a detour</title>
      <link>https://growth.iangoh.com/blog/the-integration-should-feel-like-your-product-not-a-detour/</link>
      <guid>https://growth.iangoh.com/blog/the-integration-should-feel-like-your-product-not-a-detour/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why quick account bridges, embedded editors, use-case-first builders, real integration hubs, and non-technical workflow setup usually beat sending users to a separate automation surface.</description>
    </item>
    <item>
      <title>The support surface works better when each audience sees its own path</title>
      <link>https://growth.iangoh.com/blog/the-support-surface-works-better-when-each-audience-sees-its-own-path/</link>
      <guid>https://growth.iangoh.com/blog/the-support-surface-works-better-when-each-audience-sees-its-own-path/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why separate portals, segmented inbox views, SLA reviews, grounded support drafts, and auto-generated changelogs make support feel more like product and less like cleanup.</description>
    </item>
    <item>
      <title>The queue gets clearer when done means shipped</title>
      <link>https://growth.iangoh.com/blog/the-queue-gets-clearer-when-done-means-shipped/</link>
      <guid>https://growth.iangoh.com/blog/the-queue-gets-clearer-when-done-means-shipped/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why triage rotations, priority gates, honest snoozes, release-based completion, and path-filtered release lanes usually beat one more dashboard about throughput.</description>
    </item>
    <item>
      <title>The feedback loop breaks when the middle stays hidden</title>
      <link>https://growth.iangoh.com/blog/the-feedback-loop-breaks-when-the-middle-stays-hidden/</link>
      <guid>https://growth.iangoh.com/blog/the-feedback-loop-breaks-when-the-middle-stays-hidden/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why a visible request queue, signed-in feedback, stage emails, and an in-product beta switch usually do more than one louder launch page.</description>
    </item>
    <item>
      <title>The trust page should answer in the buyer&apos;s order</title>
      <link>https://growth.iangoh.com/blog/the-trust-page-should-answer-in-the-buyers-order/</link>
      <guid>https://growth.iangoh.com/blog/the-trust-page-should-answer-in-the-buyers-order/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why NDA-gated docs, questionnaire automation, and structured AI disclosures often do more for late-funnel momentum than another polished sales follow-up.</description>
    </item>
    <item>
      <title>The buyer trusts the proof they can open alone</title>
      <link>https://growth.iangoh.com/blog/the-buyer-trusts-the-proof-they-can-open-alone/</link>
      <guid>https://growth.iangoh.com/blog/the-buyer-trusts-the-proof-they-can-open-alone/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why switch pilots, trust-center upkeep, and AI disclosure pages often move a B2B deal faster than another polished sales meeting.</description>
    </item>
    <item>
      <title>The launch keeps working when the quiet surfaces stay alive</title>
      <link>https://growth.iangoh.com/blog/the-launch-keeps-working-when-the-quiet-surfaces-stay-alive/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-keeps-working-when-the-quiet-surfaces-stay-alive/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why customer-commented wireframes, roadmap notifications, release-note emails, iterative social updates, and support follow-ups keep a launch useful after the loud day ends.</description>
    </item>
    <item>
      <title>The support surface should separate audiences before the queue gets noisy</title>
      <link>https://growth.iangoh.com/blog/the-support-surface-should-separate-audiences-before-the-queue-gets-noisy/</link>
      <guid>https://growth.iangoh.com/blog/the-support-surface-should-separate-audiences-before-the-queue-gets-noisy/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why gated help centers, AI-readable internal docs, honest chat timing, visible AI handling, and weekly pattern digests usually beat one more support redesign.</description>
    </item>
    <item>
      <title>The money pages should earn before the thought leadership starts</title>
      <link>https://growth.iangoh.com/blog/the-money-pages-should-earn-before-the-thought-leadership-starts/</link>
      <guid>https://growth.iangoh.com/blog/the-money-pages-should-earn-before-the-thought-leadership-starts/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why pricing-alternative pages, comparison pages, careful syndication, dead-product outreach, and shutdown explainers usually pay back earlier than generic educational SEO.</description>
    </item>
    <item>
      <title>Developer docs keep earning when the route stays clean</title>
      <link>https://growth.iangoh.com/blog/developer-docs-keep-earning-when-the-route-stays-clean/</link>
      <guid>https://growth.iangoh.com/blog/developer-docs-keep-earning-when-the-route-stays-clean/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why legacy-host redirects, clean main-version URLs, migration redirect families, JWT logins, docs analytics, and changelog feeds usually beat another docs redesign.</description>
    </item>
    <item>
      <title>The docs page should know when to finish the job and when to hand off</title>
      <link>https://growth.iangoh.com/blog/the-docs-page-should-know-when-to-finish-the-job-and-when-to-hand-off/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-page-should-know-when-to-finish-the-job-and-when-to-hand-off/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why private Beacon docs, brand-owned support domains, in-article handoffs, honest chat availability, and internal runbooks usually beat one more polished help-center theme.</description>
    </item>
    <item>
      <title>The help center stops feeling generic when the brand context stays intact</title>
      <link>https://growth.iangoh.com/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why unlisted previews, audience-gated public articles, single-home routing, brand-linked Messenger suggestions, and real redirect maps usually beat one more docs redesign.</description>
    </item>
    <item>
      <title>The help center should know who it is for</title>
      <link>https://growth.iangoh.com/blog/the-help-center-should-know-who-it-is-for/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-should-know-who-it-is-for/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why login redirects, picked homepage answers, localized CTA cards, section order, and brand-scoped AI usually beat one more generic docs refresh.</description>
    </item>
    <item>
      <title>The help center homepage should route the first click</title>
      <link>https://growth.iangoh.com/blog/the-help-center-homepage-should-route-the-first-click/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-homepage-should-route-the-first-click/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why collection gates, scan-copy descriptions, top-question ordering, workflow sequencing, and customer card sorts usually matter more than one more docs redesign.</description>
    </item>
    <item>
      <title>The help center search page is a product surface</title>
      <link>https://growth.iangoh.com/blog/the-help-center-search-page-is-a-product-surface/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-search-page-is-a-product-surface/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why segmented search analytics, title-first instant-search copy, frontloaded answers, source-grouped results, and real 301s usually beat another vague docs cleanup sprint.</description>
    </item>
    <item>
      <title>The public roadmap only works if the team keeps answering</title>
      <link>https://growth.iangoh.com/blog/the-public-roadmap-only-works-if-the-team-keeps-answering/</link>
      <guid>https://growth.iangoh.com/blog/the-public-roadmap-only-works-if-the-team-keeps-answering/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why an intro lane, multi-source feedback, a real Next Up threshold, early support review, and internal launch training usually beat another performative roadmap page.</description>
    </item>
    <item>
      <title>The help-center search starts working when the archive stops guessing</title>
      <link>https://growth.iangoh.com/blog/the-help-center-search-starts-working-when-the-archive-stops-guessing/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-search-starts-working-when-the-archive-stops-guessing/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why one-job articles, blunt limitation pages, triggered education, related-answer loops, and task-led titles usually do more for support growth than another docs redesign.</description>
    </item>
    <item>
      <title>Programmatic SEO usually breaks in the boring parts</title>
      <link>https://growth.iangoh.com/blog/programmatic-seo-usually-breaks-in-the-boring-parts/</link>
      <guid>https://growth.iangoh.com/blog/programmatic-seo-usually-breaks-in-the-boring-parts/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why template quality, FAQ depth, CMS plumbing, indexing discipline, and snippet-ready tables matter more than the idea of scale.</description>
    </item>
    <item>
      <title>The launch should keep teaching you after launch day</title>
      <link>https://growth.iangoh.com/blog/the-launch-should-keep-teaching-you-after-launch-day/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-should-keep-teaching-you-after-launch-day/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>Why shared request triage, post-MVP roadmap clusters, missing-metric demand, launch-ready docs, and an internal release guide make a launch more useful after the applause fades.</description>
    </item>
    <item>
      <title>The help center should feel local before it feels complete</title>
      <link>https://growth.iangoh.com/blog/the-help-center-should-feel-local-before-it-feels-complete/</link>
      <guid>https://growth.iangoh.com/blog/the-help-center-should-feel-local-before-it-feels-complete/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why translation priority, visible collection gates, search-language copy, shared brand docs, and private-domain routing usually matter more than one more polished support theme.</description>
    </item>
    <item>
      <title>An agent needs a capability page, not just a crawl map</title>
      <link>https://growth.iangoh.com/blog/an-agent-needs-a-capability-page-not-just-a-crawl-map/</link>
      <guid>https://growth.iangoh.com/blog/an-agent-needs-a-capability-page-not-just-a-crawl-map/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why llms.txt is only the map, why skill.md is the operating note, and why manifests, bot access, and proxy hygiene decide whether the surface gets used.</description>
    </item>
    <item>
      <title>The changelog should meet the user where the work happens</title>
      <link>https://growth.iangoh.com/blog/the-changelog-should-meet-the-user-where-the-work-happens/</link>
      <guid>https://growth.iangoh.com/blog/the-changelog-should-meet-the-user-where-the-work-happens/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why imported release history, in-app changelog delivery, and a visible support portal usually build more trust than an empty updates page and another email blast.</description>
    </item>
    <item>
      <title>The launch page should explain itself before the room tries to help</title>
      <link>https://growth.iangoh.com/blog/the-launch-page-should-explain-itself-before-the-room-tries-to-help/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-page-should-explain-itself-before-the-room-tries-to-help/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why personal maker identity, usable access, clear launch pages, early supporter timing, and a little manual link-seeding usually beat vague launch theater.</description>
    </item>
    <item>
      <title>The launch thread only works if the product can finish the first job</title>
      <link>https://growth.iangoh.com/blog/the-launch-thread-only-works-if-the-product-can-finish-the-first-job/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-thread-only-works-if-the-product-can-finish-the-first-job/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why runnable HN launches, no-signup first use, fast usefulness, expert comments, and evergreen utility pages usually beat announcement-only launch theater.</description>
    </item>
    <item>
      <title>The launch usually gets judged in the inbox first</title>
      <link>https://growth.iangoh.com/blog/the-launch-usually-gets-judged-in-the-inbox-first/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-usually-gets-judged-in-the-inbox-first/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why support coverage, support-reviewed messaging, prototype passes, and measured proactive support usually do more for a launch than one more announcement asset.</description>
    </item>
    <item>
      <title>The support portal should know what to reveal</title>
      <link>https://growth.iangoh.com/blog/the-support-portal-should-know-what-to-reveal/</link>
      <guid>https://growth.iangoh.com/blog/the-support-portal-should-know-what-to-reveal/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why scoping, public-facing roadmap copy, published-only APIs, request context, and version history make a support portal feel trustworthy instead of leaky.</description>
    </item>
    <item>
      <title>A weak domain should borrow trust before it demands attention</title>
      <link>https://growth.iangoh.com/blog/a-weak-domain-should-borrow-trust-before-it-demands-attention/</link>
      <guid>https://growth.iangoh.com/blog/a-weak-domain-should-borrow-trust-before-it-demands-attention/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why native Reddit posts, review carryover, dead-link replacement, expert directories, and directory baselines often work better than waiting for a young site to become authoritative on its own.</description>
    </item>
    <item>
      <title>The support surface should answer and remember</title>
      <link>https://growth.iangoh.com/blog/the-support-surface-should-answer-and-remember/</link>
      <guid>https://growth.iangoh.com/blog/the-support-surface-should-answer-and-remember/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why the best support layer knows the docs, shows its proof, keeps the human lane visible, and preserves old evidence when you migrate.</description>
    </item>
    <item>
      <title>The launch page cannot carry the whole launch</title>
      <link>https://growth.iangoh.com/blog/the-launch-page-cannot-carry-the-whole-launch/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-page-cannot-carry-the-whole-launch/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why warmed supporters, a one-sentence value prop, a short live demo, and a fast case-study pivot usually matter more than another round of launch-page polishing.</description>
    </item>
    <item>
      <title>The agent-ready page should announce itself</title>
      <link>https://growth.iangoh.com/blog/the-agent-ready-page-should-announce-itself/</link>
      <guid>https://growth.iangoh.com/blog/the-agent-ready-page-should-announce-itself/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why well-known llms paths, discovery headers, full-context exports, and skill manifests make AI discovery easier to trust and easier to use.</description>
    </item>
    <item>
      <title>The support doc starts working when the product can point to it</title>
      <link>https://growth.iangoh.com/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/</link>
      <guid>https://growth.iangoh.com/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why one live article, shallow help-center navigation, widget-deep-linked docs, weekly AI question reports, and importer-first migrations make docs behave like product.</description>
    </item>
    <item>
      <title>The help page starts earning when it can finish the job</title>
      <link>https://growth.iangoh.com/blog/the-help-page-starts-earning-when-it-can-finish-the-job/</link>
      <guid>https://growth.iangoh.com/blog/the-help-page-starts-earning-when-it-can-finish-the-job/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why embedded templates, proof-sorted examples, guided previews, query-matched help search, and smart internal linking turn support pages into search and activation surfaces.</description>
    </item>
    <item>
      <title>The template marketplace starts working when the creator page feels real</title>
      <link>https://growth.iangoh.com/blog/the-template-marketplace-starts-working-when-the-creator-page-feels-real/</link>
      <guid>https://growth.iangoh.com/blog/the-template-marketplace-starts-working-when-the-creator-page-feels-real/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why creator profiles, easier submissions, ratings, metrics, reviewed listings, and editability standards turn a template gallery into a trustworthy growth surface.</description>
    </item>
    <item>
      <title>The support surface should stay attached to the work</title>
      <link>https://growth.iangoh.com/blog/the-support-surface-should-stay-attached-to-the-work/</link>
      <guid>https://growth.iangoh.com/blog/the-support-surface-should-stay-attached-to-the-work/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why shared analytics, docs APIs, live embeds, intent-preserving sign-in, and visible shipped work usually matter more than polishing the portal chrome.</description>
    </item>
    <item>
      <title>A template marketplace should help the buyer finish the choice</title>
      <link>https://growth.iangoh.com/blog/a-template-marketplace-should-help-the-buyer-finish-the-choice/</link>
      <guid>https://growth.iangoh.com/blog/a-template-marketplace-should-help-the-buyer-finish-the-choice/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why categories, bundles, trust signals, local language ranking, and example-filled templates usually matter more than adding another hundred files.</description>
    </item>
    <item>
      <title>The App Store page should branch before it broadens</title>
      <link>https://growth.iangoh.com/blog/the-app-store-page-should-branch-before-it-broadens/</link>
      <guid>https://growth.iangoh.com/blog/the-app-store-page-should-branch-before-it-broadens/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why page testing, value-weighted variants, keyword-matched search pages, country-specific Play listings, and translation gates usually beat one universal mobile store pitch.</description>
    </item>
    <item>
      <title>The alternative page should make the switch feel testable</title>
      <link>https://growth.iangoh.com/blog/the-alternative-page-should-make-the-switch-feel-testable/</link>
      <guid>https://growth.iangoh.com/blog/the-alternative-page-should-make-the-switch-feel-testable/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why competitor pain keywords, pricing-heavy alternative pages, reviewed facts, interactive demos, and source-specific import guides turn switcher SEO into real buying intent.</description>
    </item>
    <item>
      <title>The request should stay attached to the customer</title>
      <link>https://growth.iangoh.com/blog/the-request-should-stay-attached-to-the-customer/</link>
      <guid>https://growth.iangoh.com/blog/the-request-should-stay-attached-to-the-customer/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why original request evidence, account views, lifecycle alerts, and exportable proof make product feedback more useful than a cleaned-up backlog note.</description>
    </item>
    <item>
      <title>The community should know you before the launch asks</title>
      <link>https://growth.iangoh.com/blog/the-community-should-know-you-before-the-launch-asks/</link>
      <guid>https://growth.iangoh.com/blog/the-community-should-know-you-before-the-launch-asks/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why long community immersion, problem-first audience building, quiet subreddit help, power-user workshops, and competitor listening make attention warmer than a launch-day spike.</description>
    </item>
    <item>
      <title>The request system should sort pain before the roadmap sees it</title>
      <link>https://growth.iangoh.com/blog/the-request-system-should-sort-pain-before-the-roadmap-sees-it/</link>
      <guid>https://growth.iangoh.com/blog/the-request-system-should-sort-pain-before-the-roadmap-sees-it/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why on-call intake, source-specific queues, bug-versus-feature templates, lean forms, and customer-data hygiene make feedback usable before it turns into backlog theater.</description>
    </item>
    <item>
      <title>AI search usually cites the page that did the homework</title>
      <link>https://growth.iangoh.com/blog/ai-search-usually-cites-the-page-that-did-the-homework/</link>
      <guid>https://growth.iangoh.com/blog/ai-search-usually-cites-the-page-that-did-the-homework/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>Why buyer-question maps, painful comparison pages, competitor-intent SEO, and public strategy notes give SaaS sites a better shot at citations from both humans and answer engines.</description>
    </item>
    <item>
      <title>The fastest support answer starts before the reply</title>
      <link>https://growth.iangoh.com/blog/the-fastest-support-answer-starts-before-the-reply/</link>
      <guid>https://growth.iangoh.com/blog/the-fastest-support-answer-starts-before-the-reply/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why authenticated widgets, page-aware AI context, working-hours auto-replies, multilingual portals, and built-in debug evidence make support feel like product quality instead of ticket handling.</description>
    </item>
    <item>
      <title>Feedback only helps when the customer stays attached</title>
      <link>https://growth.iangoh.com/blog/feedback-only-helps-when-the-customer-stays-attached/</link>
      <guid>https://growth.iangoh.com/blog/feedback-only-helps-when-the-customer-stays-attached/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why familiar intake surfaces, customer identity mapping, strategic request views, churn alerts, and structured triage turn scattered feedback into roadmap proof.</description>
    </item>
    <item>
      <title>The request count is usually the wrong number</title>
      <link>https://growth.iangoh.com/blog/the-request-count-is-usually-the-wrong-number/</link>
      <guid>https://growth.iangoh.com/blog/the-request-count-is-usually-the-wrong-number/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why synced conversations, recurring-demand views, beta requests, and context-rich votes beat raw feature counts when you need product signal you can trust.</description>
    </item>
    <item>
      <title>The AI feature only feels smart after the first useful minute</title>
      <link>https://growth.iangoh.com/blog/the-ai-feature-only-feels-smart-after-the-first-useful-minute/</link>
      <guid>https://growth.iangoh.com/blog/the-ai-feature-only-feels-smart-after-the-first-useful-minute/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why setup wizards, starter prompts, model routing, async jobs, ratings loops, and segment benchmarks decide whether an AI feature earns activation or just curiosity.</description>
    </item>
    <item>
      <title>The first customers should leave tracks for the next ones</title>
      <link>https://growth.iangoh.com/blog/the-first-customers-should-leave-tracks-for-the-next-ones/</link>
      <guid>https://growth.iangoh.com/blog/the-first-customers-should-leave-tracks-for-the-next-ones/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why early sales calls, tester cohorts, founder posts, and post-win prompts work best when they create evidence the next buyer can reuse.</description>
    </item>
    <item>
      <title>The roadmap starts working when it answers back</title>
      <link>https://growth.iangoh.com/blog/the-roadmap-starts-working-when-it-answers-back/</link>
      <guid>https://growth.iangoh.com/blog/the-roadmap-starts-working-when-it-answers-back/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why account-wide request rollups, embedded portals, live context, and shipped-update broadcasts make roadmap pages feel like product, not theatre.</description>
    </item>
    <item>
      <title>The launch works better when the feature picks the room</title>
      <link>https://growth.iangoh.com/blog/the-launch-works-better-when-the-feature-picks-the-room/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-works-better-when-the-feature-picks-the-room/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why builder-written stories, channel-specific launches, angel amplification, run sheets, and ecosystem radar make a launch feel less like theater and more like distribution.</description>
    </item>
    <item>
      <title>The launch page should hand people somewhere to stay</title>
      <link>https://growth.iangoh.com/blog/the-launch-page-should-hand-people-somewhere-to-stay/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-page-should-hand-people-somewhere-to-stay/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why category placement, ready makers, beta gates, community handoffs, and personal video replies turn a launch page into something more durable than a traffic spike.</description>
    </item>
    <item>
      <title>The launch page should answer the second question</title>
      <link>https://growth.iangoh.com/blog/the-launch-page-should-answer-the-second-question/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-page-should-answer-the-second-question/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Most launches do not fail because nobody looked. They fail because the first interested stranger still has to guess too much.</description>
    </item>
    <item>
      <title>AI products stop feeling smart when they hide their context</title>
      <link>https://growth.iangoh.com/blog/ai-products-stop-feeling-smart-when-they-hide-their-context/</link>
      <guid>https://growth.iangoh.com/blog/ai-products-stop-feeling-smart-when-they-hide-their-context/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why MCP wedges, narrow workflows, richer product context, trace reviews, and visible uncertainty make AI products easier to trust.</description>
    </item>
    <item>
      <title>The first growth system usually looks manual</title>
      <link>https://growth.iangoh.com/blog/the-first-growth-system-usually-looks-manual/</link>
      <guid>https://growth.iangoh.com/blog/the-first-growth-system-usually-looks-manual/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why hand-setup onboarding, one-click deployment bridges, user-motive interviews, public handbooks, and support launch briefs often beat a polished early funnel.</description>
    </item>
    <item>
      <title>The evaluation path should keep teaching after the demo</title>
      <link>https://growth.iangoh.com/blog/the-evaluation-path-should-keep-teaching-after-the-demo/</link>
      <guid>https://growth.iangoh.com/blog/the-evaluation-path-should-keep-teaching-after-the-demo/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why live onboarding sessions, company-size setup guides, day-two learning libraries, and better preview review loops make a product switch easier to trust.</description>
    </item>
    <item>
      <title>The switch feels real when the old habits have nowhere to hide</title>
      <link>https://growth.iangoh.com/blog/the-switch-feels-real-when-the-old-habits-have-nowhere-to-hide/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-feels-real-when-the-old-habits-have-nowhere-to-hide/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why switch pilots, shared language guides, smaller team structures, integration checklists, and a real cutover note make product-tool migrations easier to trust.</description>
    </item>
    <item>
      <title>The page system has to deserve its index</title>
      <link>https://growth.iangoh.com/blog/the-page-system-has-to-deserve-its-index/</link>
      <guid>https://growth.iangoh.com/blog/the-page-system-has-to-deserve-its-index/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why unique data anchors, seeded templates, editorial support pages, and daily Search Console triage keep SEO page systems from collapsing into sameness.</description>
    </item>
    <item>
      <title>Support starts before the launch email</title>
      <link>https://growth.iangoh.com/blog/support-starts-before-the-launch-email/</link>
      <guid>https://growth.iangoh.com/blog/support-starts-before-the-launch-email/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why dedicated launch inboxes, early help docs, tour-linked answers, segmented channels, and well-timed support follow-ups make launches feel more trustworthy.</description>
    </item>
    <item>
      <title>The switch feels safer when the cutover has a script</title>
      <link>https://growth.iangoh.com/blog/the-switch-feels-safer-when-the-cutover-has-a-script/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-feels-safer-when-the-cutover-has-a-script/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why structure choices, contact preload, transcript imports, drain-and-fill cutovers, and visible rollback plans make a support migration easier to buy.</description>
    </item>
    <item>
      <title>The launch starts looking real before launch day</title>
      <link>https://growth.iangoh.com/blog/the-launch-starts-looking-real-before-launch-day/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-starts-looking-real-before-launch-day/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Why hard deadlines, short founder asks, self-hunts, fresh-prospect pricing tests, and visible pricing do more for a launch than another week of launch theater.</description>
    </item>
    <item>
      <title>The rollout usually breaks where ownership goes fuzzy</title>
      <link>https://growth.iangoh.com/blog/the-rollout-usually-breaks-where-ownership-goes-fuzzy/</link>
      <guid>https://growth.iangoh.com/blog/the-rollout-usually-breaks-where-ownership-goes-fuzzy/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why switch guides, renewal-timed go-lives, feedback intake teams, linked Slack channels, and account-aware request views make a migration feel safer before the contract is signed.</description>
    </item>
    <item>
      <title>The switcher usually needs a place to rehearse</title>
      <link>https://growth.iangoh.com/blog/the-switcher-usually-needs-a-place-to-rehearse/</link>
      <guid>https://growth.iangoh.com/blog/the-switcher-usually-needs-a-place-to-rehearse/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why demo workspaces, role-based quickstarts, customer portals, and synced changelogs make a product switch easier to trust before the contract is signed.</description>
    </item>
    <item>
      <title>The side page usually answers the real objection</title>
      <link>https://growth.iangoh.com/blog/the-side-page-usually-answers-the-real-objection/</link>
      <guid>https://growth.iangoh.com/blog/the-side-page-usually-answers-the-real-objection/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why trust centers, example galleries, searchable discussions, and migration prep often move a deal forward faster than a polished homepage rewrite.</description>
    </item>
    <item>
      <title>The docs move usually gets judged by the dull pages</title>
      <link>https://growth.iangoh.com/blog/the-docs-move-usually-gets-judged-by-the-dull-pages/</link>
      <guid>https://growth.iangoh.com/blog/the-docs-move-usually-gets-judged-by-the-dull-pages/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why redirects, collection pages, inbox routing, and trigger review often decide whether a support migration looks trustworthy.</description>
    </item>
    <item>
      <title>Demand usually leaks at the next surface</title>
      <link>https://growth.iangoh.com/blog/demand-usually-leaks-at-the-next-surface/</link>
      <guid>https://growth.iangoh.com/blog/demand-usually-leaks-at-the-next-surface/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why naming, SERP control, empty states, integration updates, and trigger-based follow-up matter more than another burst of attention.</description>
    </item>
    <item>
      <title>Old pages usually earn the next growth win</title>
      <link>https://growth.iangoh.com/blog/old-pages-usually-earn-the-next-growth-win/</link>
      <guid>https://growth.iangoh.com/blog/old-pages-usually-earn-the-next-growth-win/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why weak handoffs, buried winners, overlapping URLs, mistimed seasonal pages, and unfocused backlogs make teams publish too much and improve too little.</description>
    </item>
    <item>
      <title>Outbound usually works better when the buyer can recognize themselves</title>
      <link>https://growth.iangoh.com/blog/outbound-usually-works-better-when-the-buyer-can-recognize-themselves/</link>
      <guid>https://growth.iangoh.com/blog/outbound-usually-works-better-when-the-buyer-can-recognize-themselves/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why live reverse demos, real account signals, competitor customer evidence, and timing cues beat generic outbound playbooks.</description>
    </item>
    <item>
      <title>Search usually starts with the other tool</title>
      <link>https://growth.iangoh.com/blog/search-usually-starts-with-the-other-tool/</link>
      <guid>https://growth.iangoh.com/blog/search-usually-starts-with-the-other-tool/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why app-pair pages, real walkthroughs, template pages, category prioritization, and broad-to-use-case handoffs often beat another generic product page.</description>
    </item>
    <item>
      <title>Support surfaces often teach the workflow before the homepage does</title>
      <link>https://growth.iangoh.com/blog/support-surfaces-often-teach-the-workflow-before-the-homepage-does/</link>
      <guid>https://growth.iangoh.com/blog/support-surfaces-often-teach-the-workflow-before-the-homepage-does/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why onboarding stories, integration listings, help docs, footer links, and milestone-triggered nudges often move more real adoption than another top-level brand page.</description>
    </item>
    <item>
      <title>The buyer trusts what they can copy</title>
      <link>https://growth.iangoh.com/blog/the-buyer-trusts-what-they-can-copy/</link>
      <guid>https://growth.iangoh.com/blog/the-buyer-trusts-what-they-can-copy/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why starter repos, cloneables, template categories, and remixable community examples often teach the product better than another polished homepage claim.</description>
    </item>
    <item>
      <title>The feature usually deserves more than one launch</title>
      <link>https://growth.iangoh.com/blog/the-feature-usually-deserves-more-than-one-launch/</link>
      <guid>https://growth.iangoh.com/blog/the-feature-usually-deserves-more-than-one-launch/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why fixed dates, repeated launches, builder-written copy, trusted amplifiers, and post-launch interviews beat the one-day launch fantasy.</description>
    </item>
    <item>
      <title>The launch only works if the next surface keeps working</title>
      <link>https://growth.iangoh.com/blog/the-launch-only-works-if-the-next-surface-keeps-working/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-only-works-if-the-next-surface-keeps-working/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why first comments, promo codes, badges, directory relaunches, and buyer-community reposts usually matter more than the one noisy day itself.</description>
    </item>
    <item>
      <title>The support switch usually leaks in the routing layer</title>
      <link>https://growth.iangoh.com/blog/the-support-switch-usually-leaks-in-the-routing-layer/</link>
      <guid>https://growth.iangoh.com/blog/the-support-switch-usually-leaks-in-the-routing-layer/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why forwarding rules, shared-thread handoffs, duplicate control, trigger review, and docs cleanup make support migrations feel safe.</description>
    </item>
    <item>
      <title>The switch should feel boring before it feels done</title>
      <link>https://growth.iangoh.com/blog/the-switch-should-feel-boring-before-it-feels-done/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-should-feel-boring-before-it-feels-done/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why the best migration story is usually quiet: simpler history, sample runs, staged cutovers, guarded workflows, and visible office hours.</description>
    </item>
    <item>
      <title>The switch usually needs a map before a pitch</title>
      <link>https://growth.iangoh.com/blog/the-switch-usually-needs-a-map-before-a-pitch/</link>
      <guid>https://growth.iangoh.com/blog/the-switch-usually-needs-a-map-before-a-pitch/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why high-intent buyers and switchers often need directories, templates, pilot guides, and importer paths before they need another big brand story.</description>
    </item>
    <item>
      <title>The switcher usually buys the safer exit</title>
      <link>https://growth.iangoh.com/blog/the-switcher-usually-buys-the-safer-exit/</link>
      <guid>https://growth.iangoh.com/blog/the-switcher-usually-buys-the-safer-exit/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why migration proof, sync layers, support channels, redirects, and duplicate-content discipline often close more buyers than another feature pitch.</description>
    </item>
    <item>
      <title>The switcher usually trusts what they can check</title>
      <link>https://growth.iangoh.com/blog/the-switcher-usually-trusts-what-they-can-check/</link>
      <guid>https://growth.iangoh.com/blog/the-switcher-usually-trusts-what-they-can-check/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <description>Why redirects, importer docs, factual comparison pages, internal links, and objection-led alternative pages make a migration feel safe enough to start.</description>
    </item>
    <item>
      <title>A launch teaches more when the product is easy to touch</title>
      <link>https://growth.iangoh.com/blog/a-launch-teaches-more-when-the-product-is-easy-to-touch/</link>
      <guid>https://growth.iangoh.com/blog/a-launch-teaches-more-when-the-product-is-easy-to-touch/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A short essay on why early launches work better when the product is fast to try, narrow enough to learn from, and stripped of ceremony that blocks real usage.</description>
    </item>
    <item>
      <title>Borrowed attention only pays if the handoff is clean</title>
      <link>https://growth.iangoh.com/blog/borrowed-attention-only-pays-if-the-handoff-is-clean/</link>
      <guid>https://growth.iangoh.com/blog/borrowed-attention-only-pays-if-the-handoff-is-clean/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why launch spikes, bigger-account shares, and community attention only matter when the owned page, crawl path, and trust answers are ready to catch them.</description>
    </item>
    <item>
      <title>Buyers usually signal themselves before they buy</title>
      <link>https://growth.iangoh.com/blog/buyers-usually-signal-themselves-before-they-buy/</link>
      <guid>https://growth.iangoh.com/blog/buyers-usually-signal-themselves-before-they-buy/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A short essay on why better growth often starts by noticing visible intent in neighborhoods, search queries, listicles, and narrow account lists instead of shouting into broad channels.</description>
    </item>
    <item>
      <title>Compounding growth usually waits for density</title>
      <link>https://growth.iangoh.com/blog/compounding-growth-usually-waits-for-density/</link>
      <guid>https://growth.iangoh.com/blog/compounding-growth-usually-waits-for-density/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A lot of teams automate too early. The better pattern is to do the manual work first, learn where the real density is, then publish or automate only when the surface is ready to compound.</description>
    </item>
    <item>
      <title>Credibility is usually built before the big launch</title>
      <link>https://growth.iangoh.com/blog/credibility-is-usually-built-before-the-big-launch/</link>
      <guid>https://growth.iangoh.com/blog/credibility-is-usually-built-before-the-big-launch/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>The first real trust signals are usually manual: fast replies, founder-led onboarding, clearer feature pages, and a brand surface that says the same thing everywhere.</description>
    </item>
    <item>
      <title>Proof usually beats promotion in the early stage</title>
      <link>https://growth.iangoh.com/blog/proof-usually-beats-promotion-in-the-early-stage/</link>
      <guid>https://growth.iangoh.com/blog/proof-usually-beats-promotion-in-the-early-stage/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why young products often grow faster when they publish progress, show the team, close the customer loop, and let quality do the talking.</description>
    </item>
    <item>
      <title>Support often becomes the growth surface first</title>
      <link>https://growth.iangoh.com/blog/support-often-becomes-the-growth-surface-first/</link>
      <guid>https://growth.iangoh.com/blog/support-often-becomes-the-growth-surface-first/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why a lot of early growth happens inside support: faster answers, better in-product help, narrow education, and a few well-timed human touchpoints.</description>
    </item>
    <item>
      <title>The best growth surface is usually already yours</title>
      <link>https://growth.iangoh.com/blog/the-best-growth-surface-is-usually-already-yours/</link>
      <guid>https://growth.iangoh.com/blog/the-best-growth-surface-is-usually-already-yours/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why a lot of useful growth comes from owned surfaces you already have: onboarding emails, login pages, publishing systems, and old URLs with backlinks.</description>
    </item>
    <item>
      <title>The buyer is usually already on the right page</title>
      <link>https://growth.iangoh.com/blog/the-buyer-is-usually-already-on-the-right-page/</link>
      <guid>https://growth.iangoh.com/blog/the-buyer-is-usually-already-on-the-right-page/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why old landing pages, thank-you screens, tag hubs, and founder notes often deserve more growth attention than the homepage.</description>
    </item>
    <item>
      <title>The channel usually fails before the product does</title>
      <link>https://growth.iangoh.com/blog/the-channel-usually-fails-before-the-product-does/</link>
      <guid>https://growth.iangoh.com/blog/the-channel-usually-fails-before-the-product-does/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why a lot of growth problems are really product-readiness problems in disguise, from launches that leak to referral loops that start before anyone is ready to recommend you.</description>
    </item>
    <item>
      <title>The channel usually starts as a favor</title>
      <link>https://growth.iangoh.com/blog/the-channel-usually-starts-as-a-favor/</link>
      <guid>https://growth.iangoh.com/blog/the-channel-usually-starts-as-a-favor/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why early growth often begins with manual help, narrow lists, and one useful page before it turns into something repeatable.</description>
    </item>
    <item>
      <title>The evidence is usually sitting on a page you already have</title>
      <link>https://growth.iangoh.com/blog/the-evidence-is-usually-sitting-on-a-page-you-already-have/</link>
      <guid>https://growth.iangoh.com/blog/the-evidence-is-usually-sitting-on-a-page-you-already-have/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why the next growth move is often hiding in a traffic report, a high-intent page cluster, a loved feature, or a comparison list that already shapes buyer decisions.</description>
    </item>
    <item>
      <title>The first customers are supposed to feel a little unfair</title>
      <link>https://growth.iangoh.com/blog/first-customers-are-supposed-to-feel-a-little-unfair/</link>
      <guid>https://growth.iangoh.com/blog/first-customers-are-supposed-to-feel-a-little-unfair/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A short essay on why the best early growth often starts with warm customers, personal attention, and unfairly specific distribution before it becomes a scalable machine.</description>
    </item>
    <item>
      <title>The first growth machine is usually hand-built</title>
      <link>https://growth.iangoh.com/blog/the-first-growth-machine-is-usually-hand-built/</link>
      <guid>https://growth.iangoh.com/blog/the-first-growth-machine-is-usually-hand-built/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Early growth often starts with awkward manual work: filling blank states, writing the useful post, narrowing the list, and using real signals before you automate anything.</description>
    </item>
    <item>
      <title>The launch keeps going after launch day</title>
      <link>https://growth.iangoh.com/blog/the-launch-keeps-going-after-launch-day/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-keeps-going-after-launch-day/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why the real work of a launch often starts before the page is live and keeps compounding after the leaderboard stops moving.</description>
    </item>
    <item>
      <title>The launch often goes wrong the week before</title>
      <link>https://growth.iangoh.com/blog/the-launch-often-goes-wrong-the-week-before/</link>
      <guid>https://growth.iangoh.com/blog/the-launch-often-goes-wrong-the-week-before/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why strong launches usually look boring up close: channel fit, frozen scope, a written schedule, and a content runway that starts before anyone posts.</description>
    </item>
    <item>
      <title>The machine reader is part of the audience now</title>
      <link>https://growth.iangoh.com/blog/the-machine-reader-is-part-of-the-audience-now/</link>
      <guid>https://growth.iangoh.com/blog/the-machine-reader-is-part-of-the-audience-now/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why more growth surfaces need to be readable by agents as well as humans, and why clean markdown can be a trust move rather than a technical flourish.</description>
    </item>
    <item>
      <title>The narrow surface usually wins first</title>
      <link>https://growth.iangoh.com/blog/the-narrow-surface-usually-wins-first/</link>
      <guid>https://growth.iangoh.com/blog/the-narrow-surface-usually-wins-first/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why early growth often comes from the smallest page, cohort, or utility that is close to purchase, not from the broadest possible launch.</description>
    </item>
    <item>
      <title>The next useful answer usually wins</title>
      <link>https://growth.iangoh.com/blog/the-next-useful-answer-usually-wins/</link>
      <guid>https://growth.iangoh.com/blog/the-next-useful-answer-usually-wins/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why a lot of growth comes from answering the next obvious question faster, from the search result to the launch FAQ.</description>
    </item>
    <item>
      <title>The next useful surface usually beats the homepage</title>
      <link>https://growth.iangoh.com/blog/the-next-useful-surface-usually-beats-the-homepage/</link>
      <guid>https://growth.iangoh.com/blog/the-next-useful-surface-usually-beats-the-homepage/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A lot of growth is won on the pages and workflows right after interest: pricing, checkout, onboarding, and now the machine-readable content layer behind them.</description>
    </item>
    <item>
      <title>The page after the spike matters more than the spike</title>
      <link>https://growth.iangoh.com/blog/the-page-after-the-spike-matters-more-than-the-spike/</link>
      <guid>https://growth.iangoh.com/blog/the-page-after-the-spike-matters-more-than-the-spike/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>A launch bump helps, but the real growth asset is usually the page, demo, or review surface that keeps working after the crowd leaves.</description>
    </item>
    <item>
      <title>The page should fit the job before it tells the story</title>
      <link>https://growth.iangoh.com/blog/the-page-should-fit-the-job-before-it-tells-the-story/</link>
      <guid>https://growth.iangoh.com/blog/the-page-should-fit-the-job-before-it-tells-the-story/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why educational companion pages, exact-intent tools, compounding report URLs, localized utilities, and review hubs often beat the generic page a team wanted to publish.</description>
    </item>
    <item>
      <title>The signup ask works better after the first win</title>
      <link>https://growth.iangoh.com/blog/the-signup-ask-works-better-after-the-first-win/</link>
      <guid>https://growth.iangoh.com/blog/the-signup-ask-works-better-after-the-first-win/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why better early growth often comes from moving the signup ask one step later, after the user has done something real and wants the next layer of value.</description>
    </item>
    <item>
      <title>The small proof should travel before the pitch does</title>
      <link>https://growth.iangoh.com/blog/the-small-proof-should-travel-before-the-pitch-does/</link>
      <guid>https://growth.iangoh.com/blog/the-small-proof-should-travel-before-the-pitch-does/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why a live interview, a single-screen waitlist, a checklist in a reply, and a humble backlink ask often beat a louder launch.</description>
    </item>
    <item>
      <title>The useful page usually sells before the pitch does</title>
      <link>https://growth.iangoh.com/blog/the-useful-page-usually-sells-before-the-pitch-does/</link>
      <guid>https://growth.iangoh.com/blog/the-useful-page-usually-sells-before-the-pitch-does/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why some of the strongest growth comes from pages that quietly prove value: search answers, public metrics, powered-by loops, and first-use flows that do not over-explain.</description>
    </item>
    <item>
      <title>Trust often shows up before scale does</title>
      <link>https://growth.iangoh.com/blog/trust-often-shows-up-before-scale-does/</link>
      <guid>https://growth.iangoh.com/blog/trust-often-shows-up-before-scale-does/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <description>Why many early growth wins come from visible credibility, hand-made relevance, and launch timing that waits for repeat usage instead of applause.</description>
    </item>
  </channel>
</rss>
