Coordinate a web app build from a phone through Grok Bot and Cursor
At a glance
Ian Nuttall used Grok Bot to coordinate planning, design, implementation, and deployment of undercut.lol while supervising mainly from his phone. This workflow is listed under app-development, agent-orchestration, mobile-workflows.
Grok Bot proposed the idea and name, launched Cursor background agents for planning, design, and auditing, and assigned backend implementation to other agents. Nuttall checked progress through the Grok Bot and Cursor apps. The project was hosted on Cloudflare Workers.
How it went
Nuttall reports a build of about eight hours, with roughly 75% of his participation happening on his phone.
Worth knowing
He explicitly expresses uncertainty about whether the project will work commercially or earn money.
Save ideas in this browser. Upvotes count across the board.
A builder pattern for selling Grok Bot work: give each client a studio+client@mail.grokbot.com tag and a routine that only accepts requests from approved contacts.
An indie hacker packaged an agency's eight repeated workflows (briefs, client approval with revision counters, quotes with margin checks, content calendars, post-mortems) as free MIT Claude skills.
A thread claims a whole online business runs on 16 Grok Bots plus Opus for ~$165/mo with Whop, Vercel, Notion, Sheets, and Cursor wired in—founder's job is approving each consequential step.
A developer routed Grok Bot through their ChatGPT Pro subscription after hitting cloud-agent limits, calling remote Codex environments clunkier than Cursor but workable.
