Bolt.new for Agencies: Teams Seats, Client Handoff and Limits

Bolt.new (Bolt) can carry an agency's client work, and the plan built for a studio is Teams, priced per member: from $30 per member per month billed monthly, or $27 per member per month billed yearly ($324 a year per member), at the entry level of 10M tokens a month per seat; higher token levels cost more per member ^[1]. That buys one workspace and bill, team templates, your own design systems and admin control over publishing, but no shared token pool. Pick it if your studio ships pitch prototypes, landing pages and client portals and hands code over through GitHub. Skip it if you need SSO, guaranteed response times or the right to resell access, since those sit on Enterprise or are barred outright.

Seats, roles and who pays for each prompt

Every paid member receives the monthly allotment of the team's token level, and those tokens stay with the person who accrued them. Nothing is pooled. The pricing card talks about shared capacity, yet the same page and the help center say tokens are not shared between members; admins can only see how much each person has spent. A member without a paid seat shows N/A, can open team projects and cannot prompt. That shapes staffing: an account manager who only reviews work can sit unpaid, while every designer or developer who prompts needs a seat.

By our arithmetic, a three-person studio at the 10M level pays $90 per month billed monthly ($1,080 a year) or $81 per month billed yearly ($972 a year), and by our arithmetic five people pay $150 per month billed monthly ($1,800 a year) or $135 per month billed yearly ($1,620 a year). Against an individual Pro account at the same 10M level, a Teams seat costs $5 more per month billed monthly and $9 more per month billed yearly. Splitting one Pro login among staff is not the cheap route. The Terms of Service and the acceptable use policy tie each account to one named individual and forbid shared credentials or concurrent logins, which can lead to termination.

Teams has three team roles: Admin, Billing Admin and Member, and whoever creates the team becomes Admin. Inside projects, people get Viewer, Editor or Co-owner rights, and the default project role for team members is Viewer. Inviting a client is off by default; an admin must switch on external collaboration first, and outsiders can only be Viewers or Editors. Any client who prompts as an Editor spends tokens from their own account, not yours. When someone leaves mid-cycle, their tokens vanish at once, while the seat stays occupied until the period ends on a monthly plan, or until the next monthly billing anniversary on an annual one. A member added with no seat to reuse is charged the full seat amount.

From the pitch call to a working prototype

Bolt's agency pages sell a specific moment: describing a deliverable during the client call and showing something clickable before it ends. Ryplix, an agency Bolt profiles, builds client prototypes live, shares the running link and lets clients prompt small edits; it also replaced its own CRM, project management and invoicing with apps built in Bolt. Bolt's own advice for pitches is sensible. Keep the prototype in your workspace and share the running URL, not the code, until the statement of work is signed.

Repeat work is where Teams earns its premium. Team templates turn a finished project, with its files, configuration and structure, into a locked starting point that individual plans never see. Editing a template changes only future projects, so live client builds stay untouched, and admins can edit or delete every template in the organization. Client branding goes further through your own design system, which needs paid Teams: Bolt ingests files, public sites, a GitHub repo, a Storybook or NPM packages, with repos and packages working best. Each team gets 10 adds or syncs a week.

Bolt's numbers on agency work deserve a careful read. Bolt says that in September 2026 self-identified agency users had built 501,479 projects, that 81% were built and finished inside a single day, and that 1.5% cleared its production-grade bar: published, connected to a database and still running seven days later ^[2]. Bolt adds that portals, internal tools and CRMs reach production more often than client websites. Plan your offer around durable software, not throwaway mockups. Remember that token use climbs as a project grows, as our pricing breakdown explains.

Publishing client sites without surprises

Every plan publishes to a free bolt.host address, but custom domains, badge removal and private sites, which most client work expects, need a paid plan. Paid plans remove the Made in Bolt badge on the next site update, connect or buy custom domains, and share sites privately with invited emails. Teams adds a whitelisted email domain, and admins can force every team site to private only or public only. A site on a custom domain must stay public. Admins also choose the deploy provider for the whole team: user-specified, Netlify or Bolt Cloud. Netlify hosts browser-only sites with no database or backend.

Hosting limits apply to the whole account, not to each project ^[3]. Paid hosting includes 30 GB of bandwidth and 1 million requests a month, with optional pay-as-you-go up to a spending cap you set; at that cap the site pauses until usage resets. Free accounts get 10 GB and 333,333 requests, a hard limit that takes sites offline. For a studio running dozens of client sites from one place, one viral campaign can drain the allowance every other client relies on. Set the cap deliberately.

Domains bought through Bolt are final and non-refundable, and Bolt does not publish their prices. Renewals are charged to your card one month and five days before the renewal date, and auto-renew must stay on at least six days before expiry. A domain the client already owns, connected through DNS records, keeps that billing relationship off your books. It also travels more easily later. Decide domain ownership before launch.

Handing the finished project to the client

GitHub is the cleanest exit. Sync is two-way: Bolt commits each change that does not break the project and checks the repository every 30 seconds for outside edits. Branches can be created inside Bolt, while merges happen in GitHub. A GitHub organization admin can install the Bolt app once and approve repositories, so members never connect personal accounts. Disconnecting a project is permanent. Exports carry code, not secrets, so Bolt suggests writing environment variables and service keys into the statement of work. Our GitHub and export guide covers the zip route.

Project transfers are trickier. A transfer moves the project out of your account and always takes its Bolt database along, but custom domains must be removed first, the GitHub integration is dropped, and a Supabase account never moves ^[4]. A Bolt-bought domain cannot be reconnected after a transfer until it expires, which is why Bolt advises against transferring such projects. There is another catch for client databases. Connecting a client's own Supabase project needs Pro or Teams, and one Bolt account links to only one Supabase organization, for good.

Before handover, the project security audit in the Publish menu reviews code and database, fixes most issues itself and uses no tokens; it runs on paid plans, up to 30 times a day, and its report can go into the handoff pack. Bolt calls it a first pass, not a replacement for enterprise tooling. On ownership, the Terms let users keep their content and assign StackBlitz's rights in AI output to the extent the law permits, while warning that such output may not be copyrightable. Put that sentence in your contract.

Fine print that touches client work

The acceptable use policy bars reselling or sublicensing access to the service except as the Terms permit, and bars using AI output to build a competing product. Selling clients the apps you build is a different matter. Bolt says client portals can carry the client's brand with no third-party logo, which depends on a paid plan removing the badge. Reselling Bolt seats or logins to clients, by contrast, is exactly what the policy rules out.

Confidentiality favors the team workspace. Unless they opt out, individual accounts outside the EEA, UK and Switzerland may have content created from October 2026 used for AI training and licensed to third parties as de-identified datasets; opting out is free but does not undo training already done. Teams and Enterprise workspaces are excluded. A freelancer doing client work on a personal Pro account should switch the setting off. Support is thinner than many agencies expect: paid plans get email, Monday to Friday in business hours, with no response-time commitment. SSO, audit logs and 24/7 priority support belong to Enterprise. Subscriptions are non-refundable except where the law requires, as our full review details.

The bottom line

Bolt fits agencies that sell prototypes, campaign pages and client portals and want working code they can hand over through GitHub. Teams is the plan that makes it a studio tool, for templates, client design systems, publishing controls and exclusion from the training default, but budget it seat by seat because tokens never pool. Plan domains, hosting caps and transfers before the first client goes live. Teams that need SSO, contracted support times or resale rights should talk to Enterprise or look elsewhere.