Studio
One delivery team taking on client work
TBCper month
- Up to 5 people in one workroom
- Unlimited documents and revisions
- Word and PDF export with traceability matrix
- Your GitHub organisation and your CI
- Approval gates on merge and deploy
Indicative
One subscription covers the workroom and everyone in it. Agent work is metered separately against a limit you set, so a run cannot quietly become an invoice.
These figures are not final. Teqys is in a closed beta and pricing is being settled with the first teams using it — ask for access and we will tell you where it is landing.
One delivery team taking on client work
TBCper month
Several clients, each needing their own separate workroom
TBCper month
Delivery inside a company with its own compliance rules
Let's talkannual
The gates are not an upgrade. A plan nobody approved cannot be built from on any tier.
One client and one codebase. Documents, approvals, the repository and the deployment for that project all live inside it, and people outside it cannot see any of them.
Roles are per organisation: owners and admins drive delivery, members do the work, and client reviewers see only the project they were invited to. A reviewer cannot reach your other clients.
The run stops and waits rather than half-finishing. You raise the limit or approve a smaller scope, and it picks up from the last completed step.
It is pushed to your GitHub organisation under your branch protection from the first commit. There is no export step because it was never anywhere else.
Every document downloads as Word, and the version you upload back is the one the builders read. Prose you rewrite by hand is marked so the agents use your text rather than their own typed fields.
We are taking on a small number of teams during the beta and setting up their workrooms by hand.