Note /
Can this scale past the first team
The first team is the easy one. The question underneath the enquiry is whether the second team means starting again, and the answer was settled by how a Team Install is put together.
One organisation, scoped workspaces
A Team Install is a multiplayer-class deployment, currently QM or Buzz, and it arrives as an organisation rather than as a single agent with more users. The fixed price covers organisation setup, a Slack or Teams surface, scoped workspaces and admin training. The scoped workspaces are the part that answers this note. A Team Install is set up in workspaces from the first day, so a second team is a second workspace inside a deployment that already exists, not a second deployment.
Growth is a line on the menu
Extra agent workspaces / seat expansion is a published item at $400 one-off. It sits on the standard connector line of the add-on menu, at the same price as connecting a CRM or a helpdesk, and it is bought once rather than rented. The price line says something about the work: the menu describes the $400 line as connection and expansion modules, against bespoke-engineering modules on the $700 line. What an add-on is, and why most of them can carry a fixed price, is its own note.
So the second team can be totalled from the menu before anyone speaks to us. A Team Install is priced once, and each add-on after it is priced per item.
What stays the same as the deployment grows
The new workspace lands on the same infrastructure as the first one, which is yours, with credentials that never leave your environment. It sits under the same hardened default as the rest of the deployment: agents get access to the tools their job needs and nothing else, and actions with consequences wait for human sign-off. The posture you chose is the one recorded in your handover document. New integrations and new features are sold as add-ons rather than as support, which is why expansion is a menu line and not a retainer ticket.
When the first team is one person
The one case that is not a fixed-price line is a Solo Install whose existing work later has to move into a team deployment. A Solo Install is a personal-class agent, currently OpenClaw or Hermes, and it is the answer to one person’s workflow. A Team Install is still priced once. Carrying an existing agent’s configuration across frameworks is a framework migration, a named item on the menu that carries no fixed price: it is quoted on application once scoped and anchored on $850 a day. The test that decides between the two installs is whose workflows the agents will serve, which is covered in choosing between Solo and Team. If a second team is already in view, say so at enquiry, because that is the detail the recommendation is made on.
Ask it before the install
The enquiry form has a free-text field for what you want agents doing. If growth is part of the picture, put it there. The written response arrives within 24 hours with the recommendation and the fixed price, and the shape of the deployment is settled with the second team in mind rather than discovered when it arrives.