GrowthPilot AI
Transparent MVP launch status

Public enough to test. Not pretending to be finished.

GrowthPilot AI is a working AI SEO, AEO/GEO, and ad-growth planning MVP. This page summarizes what is live, what has been verified, which exposure surfaces are active, and which production blockers still need durable credentials or account authorization.

Request a free AI growth audit Use the launch kit View launch evidence View directory JSON
Verified

Platform surface

  • Landing page, press kit, AI crawler context, RSS, sitemap, and robots files.
  • AI SEO/AEO/GEO pages, industry pages, tools, templates, reports, badges, and directory assets.
  • Lead capture, event attribution, ops dashboard, CSV export, webhook retry, and CRM handoff workflow.
Verified

Deployment paths

  • Full Node release archive and VPS release archive.
  • Provider configs for Render, Railway, Fly.io, Docker/VPS, Procfile hosts, Netlify, Vercel, and GitHub Pages.
  • Static launch package for exposure when backend credentials are not yet available.
Evidence

Checks to rerun

  • npm test
  • npm run check:authorized-exposure -- --require-one
  • npm run check:release-ready
  • npm run check:production-launch -- https://your-domain.example --ops-token "$OPS_TOKEN"
  • npm run check:external-exposure -- https://your-domain.example
Preview only

What temporary URLs are for

Temporary tunnels are useful for demos, public preview health checks, Telegra.ph refreshes, QA, and feedback. They are not appropriate for final directory submissions that expect a stable URL.

Blocked

What still needs credentials

  • Stable production host or custom domain.
  • Durable LEAD_WEBHOOK_URL before serious traffic.
  • Founder-controlled accounts for Product Hunt, LinkedIn, Reddit, Indie Hackers, Hacker News, X, email, DMs, and Chinese channels.
  • Budget approval before paid directories or ads.
Evidence boundary

No-account exposure is not account-authorized launch evidence

GrowthPilot AI currently separates public technical exposure from founder-account execution. Telegra.ph pages, IndexNow submissions, public preview health checks, and deployment candidate checks help discovery and QA, but they do not prove a real social post, directory submission, direct message, email, comment, vote, review, lead, sale, ranking, or CRM write happened.

Account-authorized exposure is counted only after a real post, submission, DM, or outreach action is executed through an authorized account and recorded with npm run launch:record-exposure. This protects the launch metrics from inflated proof while the product is still moving toward stable hosting and durable CRM storage.

Boundaries

What is not claimed

GrowthPilot AI does not guarantee rankings, AI answer inclusion, indexing, ad ROI, leads, sales, revenue, or platform approval. Real outreach, social posting, paid spend, and regulated claims require human authorization and review.

Next execution queue

Account-authorized exposure sequence

1. Stable URL Deploy to a durable host, run production launch gate, configure discovery files, and refresh external exposure pages for the final domain.
2. Community proof Use UTM links from the exposure board for Hacker News Show HN, Indie Hackers, LinkedIn, X, Reddit, Zhihu/WeChat, and Xiaohongshu. Record only real posts from authorized accounts.
3. Directory submissions Submit Product Hunt, BetaList, Futurepedia, TAAFT, Microlaunch, and free tool directories only after the stable URL and screenshot gallery are ready. Keep paid directories on hold until budget approval.
4. Lead durability Connect CRM webhook, verify retry behavior, monitor the ops daily report, and keep outreach small until lead routing is durable.