/new-client
The Orchestrator (any industry, any service combination)
The orchestrator for onboarding a new business client end-to-end, any industry, any combination of website/walkthrough/flyover services — imported verbatim from the business-studio repo (Phase 2) and adapted for the monorepo.
verified (imported 8396511dd50446c2324c8c5b2a2d90e1e996fb97)v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #98 — Import business-studio agents · verbatim import from the staged copy; no client data
Shares that number with /build-website, /build-walkthrough, /build-flyover.
Example requests
- “new client”
- “onboard”
- “set up this client”
- “run the full pipeline for”
- “build me a website and a walkthrough”
What it needs, and what it hands back
Needs connected
- github
- vercel
Better with: openart.
Uses mcp__github__*, Vercel MCP (create_git_project, list_deployments, get_deployment), which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/status.md summary
- a live site + delivered videos, per services purchased
Stops and asks
- client's first OpenArt credit batch (Step 0.5)
Steps it cannot do through an API, and hands you instead: Vercel dashboard Import fallback if create_git_project is unavailable/denied.
How it runs
These are the headings of its own written instructions — 425 lines you can read and change.
- Step 0 — Environment, intake, services, client folder, OpenArt project
- Step 1 — Website first (when purchased)
- Step 2 — Videos, deploying as they complete
- Step 2b — Edited video(s), after the website and the generated videos
- Step 3 — Final summary