Bolt Client Workspace Setup (Onboarding)
A sequence with 8 steps: Subscribe to the Teams plan at $30 per member per month and assign each delivery lead a seat.
By InnovaAI ResearchPublished
What are the steps?
Bolt Client Workspace Setup (Onboarding)
- 01
Subscribe to the Teams plan at $30 per member per month and assign each delivery lead a seat
Teams adds centralized billing and team-level access controls, so client work is not billed to a personal Pro account at $25/month. Keep one Free ($0) seat for evaluation builds only, since Free projects carry Bolt branding and a 1M token monthly cap.
- 02
Create one project folder per client and name it with the client slug plus engagement type
Separate folders prevent prompt history and generated code from bleeding between accounts. This matters once the agency passes roughly 10 concurrent clients, where Bolt's lack of multi-tenant client reporting makes folder discipline the only audit trail.
- 03
Set the intake brief as a natural language spec before the first prompt
Bolt builds from conversation, so the opening prompt defines the data model. Include page list, auth requirements, and database entities in the brief so the generated schema does not need rework after the client sees a demo.
- 04
Import existing assets through Figma or GitHub rather than rebuilding from scratch
Design imports and repo imports skip the blank-page phase on retainer clients who already have brand systems. File uploads cap at 100MB on Pro and Teams versus 10MB on Free, which decides whether a client's asset pack fits.
- 05
Configure built-in authentication and database tables inside the project before any UI polish
Bolt provisions hosting, databases, and auth natively, so there is no separate infrastructure vendor to wire up. Lock the auth roles first; retrofitting permissions after pages are generated costs more tokens than doing it up front.
- 06
Connect the client's custom domain and verify SEO metadata, sitemap, and page titles
Custom domain support is a Pro-and-above feature, so confirm the seat tier before promising a branded URL. Bolt branding appears on Free-tier sites and must be removed before any client-facing launch.
- 07
Record token consumption at handoff and set the monthly ceiling for the account
Pro starts at 10M tokens per month with unused tokens rolling over; Teams seats share centralized billing. Log the burn rate per client so the retainer price reflects actual usage rather than a guess.
- 08
Deliver the handoff guide and train the client team on editing within Bolt
Walk the client through prompt-based edits and the project folder structure. Agencies that skip this step absorb every copy change as unbilled delivery work.
More on Bolt
- StrategyWhy Bolt's Token Economics Decide Agency Margin Before the Build Does
- ConceptBolt Token Burn Rate
- Evaluation RuleBolt Rule: Adopt Bolt Only When the Build Fits Inside One Token Budget and One Client Domain
- Decision FrameworkBolt: Buy vs Skip (Agency Full-Stack Delivery)
- Failure PatternThe Bolt Token Burn Trap: Why Agencies Fail With Bolt on Fixed-Fee Client Builds
- Implementation BlueprintBolt Client Site Launch Sprint (6-8 days)