One standard, across everyone’s engagements
The problem at team scale is not writing speed. It is that eight analysts produce eight house styles, nobody can find last quarter's SOW, and the first sign of an AI bill is the invoice.
Generation is refused once the ceiling is reached.
- Delivery$104.1062%
- Presales$61.2031%
- Internal$17.107%
The house style lives in the platform, not in a folder of templates
Document structure comes from the document-type registry; page furniture and branding come from the workspace. Neither is a file anyone can start from the wrong copy of.
Prompts, centrally administered
Each document type's system prompt and format are set once, versioned whenever they change.
Branding per workspace
Logos, fonts, margins, footers and confidentiality notes belong to the workspace, not the exporter.
The same pack every time
Every engagement produces the same documents, in the same order, whoever ran it.
A workspace is a real boundary
Projects, documents, chats, runs and costs each belong to exactly one workspace. Teams working on separate accounts — or a practice keeping a sensitive client apart — get separation that holds in the queries, not just in the navigation.
A resource in another workspace answers 404 rather than 403, because a 403 confirms that it exists.
Access is membership, never row ownership: a colleague in the same workspace reaches its projects, and a resource in another workspace answers 404 rather than 403 — a 403 would confirm it exists.
Roles that match how a firm is actually organised
Five organisation roles and four workspace roles, resolved from one capability matrix — plus roles you define yourself when those do not fit.
- Owner
- Everything, including billing and ownership changes.
- Admin
- Runs the organisation day to day. No billing, no ownership.
- Billing
- Invoices and plan only — deliberately no access to client deliverables.
- Member
- Belongs to the organisation; reaches a workspace by being a member of it.
- Guest
- External collaborator, granted individual workspaces.
- Admin
- The workspace, its members and its settings.
- Manager
- All the work, including deleting a project.
- Contributor
- Creates and edits, generates and exports. Cannot delete.
- Viewer
- Read and export only.
- Custom
- Your own role, layered on top of a built-in one — never instead of it.
A ceiling that refuses work, not a warning email
Every generation is costed from the rates configured for its model, and the organisation’s month-to-date total is checked before a run starts, before each document in a pack, and before a chat turn. Once the ceiling is reached, generation is refused across every workspace until the month rolls over or the limit is raised.
- Spend broken down by workspace, provider and model.
- Runs, tokens, duration and cost per engagement.
- Unpriced models are called out rather than counted as free.
Generation is refused once the ceiling is reached.
- Delivery$104.1062%
- Presales$61.2031%
- Internal$17.107%
The engagement survives the person
Requirements, sources, deliverables, versions and decisions belong to the workspace. Somebody joining an account mid-flight reads the same material the original analyst did, and the assistant answers from it.
Nothing is authorised by who created a row, so a colleague picking up a project is not locked out of it.
| Source | Type | Chunks | State |
|---|---|---|---|
| Client brief.docx | DOCX | 38 | Indexed |
| Existing platform audit.pdf | 126 | Indexed | |
| API limits — vendor note.md | Markdown | 12 | Indexed |
| Kick-off transcript.txt | Text | — | Processing |
What a delivery lead can see without asking
Three surfaces, all derived from what actually happened rather than from anyone keeping a list up to date.
Attention
Every deliverable now behind the document it was written from, ranked by consequence.
Activity
Who did what, to which object, when — filterable by workspace and action.
Analytics
Runs, tokens, cost and duration by provider, model and workspace.
Bring one team and one account
Run a live engagement through it with the people who would actually use it, and judge the standardisation on real output.