Grok BotSoftwareInfra & DevOpsAI score · 73/100AI-assisted edit · no obvious prompt-injection riskX

MeetETA: From Password-Protected Prototype to Launched Product with Grok Bot

Input: existing Next.js password-protected prototype + Grok Bot (AI agent with its own computer); Process: phased audit, multi-round PR iteration, infrastructure migration; Output: public time-zone conversion site, Chrome extension, launch assets

Some experienceStepsWorkflowTip
Who
Solo creators, PMs, or operators with an existing prototype but limited engineering resources
You get
Iterate a password-gated prototype into a publicly launched product including site, Chrome extension, SEO pages, launch video, and analytics tracking
You need
Vercel · GitHub · Cloudflare · Google Analytics · Pabbly

Constraints

Requires Cursor account with Grok Bot access; existing code repo (GitHub) and deployment account (Vercel). Optional: Claude Code token, Cloudflare, Pabbly, Google Analytics/GTM. Cost reference (author-reported, not tested by us): Grok Bot Super $100/mo, Claude Max $100/mo, Vercel Pro $20/mo, Chrome Web Store developer fee $5 one-time, ElevenLabs Starter ~$6/mo, Higgsfield ~$23/mo.

What they did

Author Akbar Lalani (not a developer) spent 11–13 October 2026 using Cursor's Grok Bot to iterate a Next.js time-zone app prototype, MeetETA, that had been dormant since August 2025. Grok Bot ran on its own Linux machine: reading code, writing specs, having Claude Code implement features via a provided token, running builds and tests, opening the site in a real browser, and taking screenshots. It opened pull requests with Vercel preview links. The author reviewed previews, merged code, executed DNS changes, submitted the extension, and posted launch content. Over three days they completed 24 PRs (23 merged), upgraded to Next.js 15.5 + React 19, grew the test suite to 466 tests, launched meeteta.com, and shipped a Chrome extension, launch video, SEO page system, and event tracking.

How it went

Author-reported: a client found it easier than her previous workflow; Google Trends showed 'EST to IST' vastly outranked generic converter queries; after Claude provided keyword data, Grok Bot built 66 SEO pages; npm audit showed zero production vulnerabilities after upgrade. One production build failed on the 'Share this time' release and was fixed in ~10 minutes. Vercel auto-deploy broke and returned 404s before settling. Cloudflare Turnstile failed in automated browsers and on preview URLs, later restricted to registered hosts. The Chrome extension was submitted and remained under review. (Author report; not verified by us.)

Worth knowing

No Grok Bot system prompt or startup command text is available. Grok Bot requires a Cursor account and Super plan ($100/mo) for full use. The Claude Code coding step needs an additional token and cost. Critical actions—DNS changes, store submission, LinkedIn/YouTube posting, signup emails—remained manual, not fully automated. The author explicitly retained merge authority and product decisions. Absolute search volume data came from paid SEO tools Grok Bot could not access directly. Chrome Web Store review status is unknown.

Steps

  1. Connect Grok Bot and configure project environment

    Enable Grok Bot in Cursor, connect GitHub, Vercel, Gmail and other accounts. Authorize the existing Next.js repo so the bot can read code, create branches, and open pull requests.

  2. Audit existing code and verify issue list

    Have Grok Bot audit the current prototype without trusting earlier audit results. Ask it to confirm or refute known issues and find new ones (e.g., password bypass, EOL dependencies, hydration failures).

  3. Research demand with available data

    Have Grok Bot research keyword demand using public tools like Google Trends. If absolute search volume is unavailable, require it to label it 'unknown' instead of guessing.

  4. Iterate in small build rounds

    Drive changes in small PR batches. Each round targets specific goals (e.g., time sliders, mobile menu, natural-language input, EST/EDT warning). Require every PR to include a Vercel preview link and desktop/mobile screenshots.

  5. Upgrade dependencies and harden security

    Perform major Next.js/React upgrades in a dedicated round, run npm audit to confirm zero production vulnerabilities. Add server-side spam protection (Cloudflare Turnstile, honeypot, rate limiting).

  6. Migrate domain and go live

    Remove the password gate, deploy a welcome page and signup route. Move the domain from Replit to Vercel; have Grok Bot draft exact DNS changes, then apply them manually in Cloudflare.

  7. Build Chrome extension and submit for review

    Develop an extension using the same parsing code as the site, supporting time selection on any page (including Gmail). Have Grok Bot test in a headless browser, generate store assets and listing copy. Submit manually to the Chrome Web Store.

  8. Produce launch video and marketing assets

    Collaborate with Grok Bot on a 30-second demo script, record the real site with Playwright, generate voiceover with ElevenLabs, extract subtitle timings with Whisper, and render multi-size versions in Remotion.

  9. Deploy SEO pages and sitemap

    Generate city clock pages and zone-pair pages in bulk from keyword data, set daylight-saving aliases to redirect, and submit the sitemap to Google Search Console.

  10. Set up trustworthy analytics tracking

    Configure event tracking in GTM/GA4 (city add/remove, time conversion, share link copy, etc.), ensuring user-typed text is not collected. Validate in GTM Preview before publishing.

Prompt you can copy

Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.

This block is the prompt. Ads are never placed here.

No prompt needed — just follow the steps.

How to talk to Grok Bot: brief it like a developer, ask it to show results (preview links, screenshots) rather than just describe them.

Source

MeetETA:用 Grok Bot 把密码墙原型推到可演示产品 · AkbarLalani · X · 2026-10-26T13:58:40.000Z

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related