# The first useful click should open a live workspace > Why codespace badges, prebuilds, browser-run examples, generated sandboxes, and guided deploy buttons convert technical curiosity better than another setup document. - Canonical HTML: https://growth.iangoh.com/blog/the-first-useful-click-should-open-a-live-workspace/ - Published: 2026-06-08 - Updated: 2026-06-08T08:20:41.000Z - Categories: runnable demos, documentation, product-led growth - Niches: Developer tools, API products, AI products, SaaS, Open-source software ## On this page - The README should open the environment, not apologize for setup time - Runnable docs beat dead snippets when the buyer is technical - Fresh examples matter more than a big library of stale ones - Template growth depends on what happens before and after deploy - Ian's operator take ## Start with these related tactics - [GitHub Codespaces quickstart badge before local setup doc maze](/growth-ideas/github-codespaces-quickstart-badge-before-local-setup-doc-maze/): Put an Open in GitHub Codespaces badge with the quickstart resume route in the README before sending a new developer through a long local setup page. - [GitHub Codespaces prebuild before workshop or launch-day push](/growth-ideas/github-codespaces-prebuild-before-workshop-or-launch-day-push/): Prebuild the codespace before a launch, tutorial, or workshop push when the repository takes more than two minutes to boot. - [StackBlitz Open in button before clone-and-install detour](/growth-ideas/stackblitz-open-in-button-before-clone-and-install-detour/): Add an Open in StackBlitz button to docs and READMEs before asking a curious developer to clone the repo just to see one example work. A lot of technical products still make the same bad trade. They explain first and let the proof arrive later. That sounds reasonable until you watch how people actually evaluate developer tools. The reader opens the README, the docs page, or the template link because they want one useful click. If that click turns into setup homework, the page starts losing before the product gets a fair test. ## The README should open the environment, not apologize for setup time [GitHub Codespaces quickstart badge before local setup doc maze](/growth-ideas/github-codespaces-quickstart-badge-before-local-setup-doc-maze/) is the cleanest example in this batch. A badge in the README is not a gimmick. It is a way to move the visitor from curiosity to a running environment without asking them to trust an installation guide they have not benefited from yet. That works even better when it sits beside [GitHub Codespaces prebuild before workshop or launch-day push](/growth-ideas/github-codespaces-prebuild-before-workshop-or-launch-day-push/). The badge earns the click. The prebuild keeps the click from turning into a wait screen. ## Runnable docs beat dead snippets when the buyer is technical [StackBlitz Open in button before clone-and-install detour](/growth-ideas/stackblitz-open-in-button-before-clone-and-install-detour/) solves the first handoff. [StackBlitz embed open file and initial path before static snippet](/growth-ideas/stackblitz-embed-open-file-and-initial-path-before-static-snippet/) solves the second. One gets the reader into a live environment. The other makes sure they land on the right screen once they are there. I would read those beside [Hugging Face Space demo as live product page](/growth-ideas/huggingface-space-demo-as-live-product-page/). Different product category, same rule. A technical buyer trusts the page faster when the page can be tried. ## Fresh examples matter more than a big library of stale ones [StackBlitz SDK generated project before stale sample repo](/growth-ideas/stackblitz-sdk-generated-project-before-stale-sample-repo/) is really about honesty. If the docs promise a live example, the example should match the docs you just wrote. Generating a project from the current snippet is often cleaner than letting a sample repository drift until nobody is sure whether the breakage is in the product or in the tutorial. That point gets missed because teams count examples instead of counting examples that still tell the truth. ## Template growth depends on what happens before and after deploy [Vercel deploy button doc link and demo card before template dropoff](/growth-ideas/vercel-deploy-button-doc-link-and-demo-card-before-template-dropoff/) matters because template funnels usually fall apart in two places. First, the user cannot tell what to do with the env vars. Then, after success, they still do not know what they are supposed to inspect next. That is why it pairs well with [Baremetrics public dashboard demo as trust page](/growth-ideas/baremetrics-public-dashboard-demo-as-trust-page/). The deploy step is not the finish line. The user still needs a proof surface that shows why the deployment was worth the effort. ## Ian's operator take I keep coming back to the same question: what is the first useful click. On a technical product, that click should usually run something, resume something, or show a live system that explains itself. If it only opens another page of instructions, the content route is doing the slow work in the wrong order. This is strongest in developer tools, API products, open-source software, AI products, and any SaaS product where a technical evaluator wants to test the shape of the product before they talk to a human. The first click should lower doubt, not create more chores. If you want help deciding which README badge, live example, deploy flow, or proof surface should exist first, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [GitHub Codespaces quickstart badge before local setup doc maze](/growth-ideas/github-codespaces-quickstart-badge-before-local-setup-doc-maze/) - Developer Tools, Documentation, Activation - [GitHub Codespaces prebuild before workshop or launch-day push](/growth-ideas/github-codespaces-prebuild-before-workshop-or-launch-day-push/) - Developer Tools, Launches, Documentation - [StackBlitz Open in button before clone-and-install detour](/growth-ideas/stackblitz-open-in-button-before-clone-and-install-detour/) - Developer Tools, Documentation, Product-Led Growth - [StackBlitz embed open file and initial path before static snippet](/growth-ideas/stackblitz-embed-open-file-and-initial-path-before-static-snippet/) - Documentation, SEO, Developer Tools - [StackBlitz SDK generated project before stale sample repo](/growth-ideas/stackblitz-sdk-generated-project-before-stale-sample-repo/) - Documentation, Developer Tools, Product Ops - [Vercel deploy button doc link and demo card before template dropoff](/growth-ideas/vercel-deploy-button-doc-link-and-demo-card-before-template-dropoff/) - Developer Tools, Activation, Templates ## Essay chronology - [Newer essay: The docs page should let the buyer send the first request](/blog/the-docs-page-should-let-the-buyer-send-the-first-request/) - documentation, API docs, developer tools - [Older essay: The AI visibility report should point to a page that can win](/blog/the-ai-visibility-report-should-point-to-a-page-that-can-win/) - AI visibility, SEO, brand trust ## Keep reading - [The docs route should let the developer verify before the call](/blog/the-docs-route-should-let-the-developer-verify-before-the-call/) - documentation, brand trust, SEO - [The community archive should answer the next visitor](/blog/the-community-archive-should-answer-the-next-visitor/) - community-led growth, SEO, documentation - [The Notion connection should earn the first workspace](/blog/the-notion-connection-should-earn-the-first-workspace/) - product-led growth, marketplaces, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [GitHub Docs: Facilitating quick creation and resumption of codespaces](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces) · [GrowthDex source hub](/sources/github-docs-facilitating-quick-creation-and-resumption-of-codespaces-doc/) - [GitHub Docs: About GitHub Codespaces prebuilds](https://docs.github.com/en/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds) · [GrowthDex source hub](/sources/github-docs-about-github-codespaces-prebuilds-docs-github-com/) - [StackBlitz Docs: Getting started](https://developer.stackblitz.com/guides/user-guide/getting-started) · [GrowthDex source hub](/sources/stackblitz-docs-getting-started-developer-stackblitz-com/) - [StackBlitz Docs: Embedding projects](https://developer.stackblitz.com/guides/integration/embedding) · [GrowthDex source hub](/sources/stackblitz-docs-embedding-projects-developer-stackblitz-com/) - [StackBlitz Docs: Creating projects with the SDK](https://developer.stackblitz.com/guides/integration/create-with-sdk) · [GrowthDex source hub](/sources/stackblitz-docs-creating-projects-with-the-sdk-developer-stackblitz-com/) - [Vercel Docs: Working with the Deploy Button](https://vercel.com/docs/deployments/deploy-button) · [GrowthDex source hub](/sources/vercel-docs-working-with-the-deploy-button-vercel-com/) ## Editing notes - Kept the essay on one narrow claim: the first useful click on a technical page should open a live workspace or proof surface. - Used plain objects like badges, prebuilds, env vars, snippets, and demo cards instead of inflated language about transformation or innovation. - Cut vague developer-community language and tied each section to a concrete mechanic documented by GitHub, StackBlitz, or Vercel. - Closed with an operator judgment and advisory CTA instead of a generic summary about the future of developer experience. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.