diff --git a/apps/web/content/getting-started/installation.mdx b/apps/web/content/getting-started/installation.mdx
index 11ca98a..04bc9f3 100644
--- a/apps/web/content/getting-started/installation.mdx
+++ b/apps/web/content/getting-started/installation.mdx
@@ -18,10 +18,15 @@ helpbase ships as a scaffolder that creates a standalone Next.js project. No run
 
 <Steps>
   <Step title="Run the scaffolder">
+    For new docs sites:
     ```bash
     npx create-helpbase my-docs
     ```
-    This creates a new directory with a complete help center project.
+    For adding helpbase to an existing app:
+    ```bash
+    pnpm dlx helpbase init
+    ```
+    This drops the full helpbase primitive into your current directory.
   </Step>
   <Step title="Pick a content source">
     The scaffolder asks where to seed content from. Three options:
diff --git a/apps/web/content/getting-started/introduction.mdx b/apps/web/content/getting-started/introduction.mdx
index 7e77cb1..0ccf43e 100644
--- a/apps/web/content/getting-started/introduction.mdx
+++ b/apps/web/content/getting-started/introduction.mdx
@@ -26,11 +26,14 @@ Most help center tools are either closed-source hosted SaaS or generic wikis tha
 ## Quick start
 
 <Steps>
-  <Step title="Scaffold a new project">
-    Run the scaffolder to create a new help center project with sample content:
+  <Step title="Install helpbase">
+    Run the one-command install in your existing Next.js app:
+    ```bash
+    pnpm dlx helpbase init
+    ```
+    Or scaffold a fresh project:
     ```bash
     npx create-helpbase my-docs
-    cd my-docs
     ```
   </Step>
   <Step title="Start the dev server">