STAX: an AI workspace for your whole organisation
When the answer to a customer question sits across files, spreadsheets and a colleague's memory, the work slows down. STAX brings the knowledge and the next step into the same conversation.
Company knowledge.
A reviewed next step.
Start with the sources your team is allowed to use.
STAX is an alternative to per-seat AI workspaces such as Gemini Enterprise and Claude Team. Your staff ask questions of approved company knowledge, and the organisation pays one subscription based on queries, storage and model choice, not a licence for every person. STAX Data holds the knowledge; STAX GPT finds answers and prepares the next step.
Start with a workflow your team repeats
Choose work that depends on company information: preparing a proposal, finding an approved procedure, answering an internal policy question or reviewing an operational issue. Name the person who owns the source material and the person who approves the result.
The first implementation should establish whether people can find the right information, whether access rules hold and whether the output helps them complete the task. AI-generated answers and proposed actions still need the review appropriate to the work.
How will we know whether the pilot is useful?Use the first-workflow scoping worksheet to record sources, access and the output your team will review.
STAX Data and STAX GPT
STAX Data: organise the company knowledge
Start with the sources your team is allowed to use. Identify the current documents, their owners and any material that should stay outside the workspace. Agree how updates will be handled so old policies and superseded information do not become the answer.
STAX administration includes topic, user and file association controls, plus access categories. Discuss how these should support your departments and source material. Google Workspace connections and the actions they support are scoped for each client.
STAX GPT: turn a question into a reviewed next step
Use the knowledge layer to support a task: find the relevant procedure, prepare a response, summarise source material or outline an action for review. You decide which actions need a person's approval before anything is sent or changed.
Model choice belongs in that scope. Tell us your preferred provider, cost requirements and whether you would like to discuss using your own model API key. We will confirm the supported arrangement in your proposal.
Where to start by department
Find an approved onboarding procedure or policy.
What to validate
Separate general policy access from confidential personnel information.
The full team planning table follows. Swipe or scroll sideways on a small screen.
| Team | Example starting workflow | What to validate |
|---|---|---|
| HR | Find an approved onboarding procedure or policy. | Separate general policy access from confidential personnel information. |
| Sales and marketing | Prepare a customer response using current product and offer information. | Confirm the approved price source and review the response before sending. |
| Operations and finance | Find a procedure and prepare a summary of an exception. | Check the source date, access rules and who approves follow-up. |
| IT and support | Find a troubleshooting note and draft the next diagnostic step. | Check which systems and documents the user may access. |
These are starting examples. Start with one team and a defined source set before expanding.
Organisation-level pricing
STAX is one subscription for the organisation, not a licence per person. Your quote is built from three things:
| What | How it is measured |
|---|---|
| Queries | The questions your staff ask STAX. With the default model, your quote sets an agreed query limit. |
| Storage | Gigabytes of company knowledge held in STAX. |
| Model | Use the default model within the agreed query limit, request another model and pay as you go based on its API token usage, or bring your own API key and pay the model provider directly. |
Adding staff does not add a seat licence. More people asking more questions means more queries, so we size the query limit with you.
A staged rollout, with dates agreed after discovery
- 1Discovery and planning
- 2Knowledge and connection setup
- 3Department pilot and training
- 4Go-live and review
| Stage | Work to complete | Check before moving on |
|---|---|---|
| Discovery and planning | Choose the workflow, source owners, users and data boundaries. | Agree scope, success criteria and a delivery timetable. |
| Knowledge and connection setup | Prepare the approved source set and configure supported connections. | Test source updates, document access and the selected model arrangement. |
| Department pilot and training | Run representative tasks with the first team. | Review answer quality, permissions, approval steps and usability. |
| Go-live and review | Roll out the accepted scope and agree support responsibilities. | Review adoption, consumption and source maintenance before expanding. |
The timetable depends on source readiness, connection work and acceptance tests. We agree dates after discovery rather than promising a fixed implementation period on this page.
Choose a deployment approach for your organisation
Queries are answered by the model you choose. If you bring your own API key, that provider's terms apply to the queries it processes. Department access and Google Workspace connections are scoped with you, and retention and deletion terms are set in your agreement.
Compare STAX, Gemini Enterprise and Claude Team
Read across each decision. All product columns and source references are retained.
Checked on 29 October 2026. Product terms change. This comparison covers Claude Team and the per-user Gemini Enterprise Business, Standard and Plus subscriptions, alongside STAX. Google Cloud Agent Platform and model API consumption are outside this comparison. It does not imply identical features or a guaranteed cost saving.
| Decision | STAX | Gemini Enterprise | Claude Team |
|---|---|---|---|
| How it is priced | One organisation subscription, priced on queries, storage (GB) and model choice. No per-seat licence. Get a quote. | Per-user subscriptions for Gemini Enterprise Business, Standard and Plus. Confirm the selected edition, commitment and applicable terms. G1 G2 | Per-seat Team subscriptions with Standard and Premium seats. Usage limits and optional additional usage apply. C1 C2 |
| Model choice / BYOK | Default model within an agreed query limit; another model you request, billed on its API token usage; or your own API key, billed to you by the provider. | Gemini and administrator-enabled Claude models are documented. Third-party model usage is billed through Google. This does not establish arbitrary customer API-key BYOK. G2 | Access to Claude models. The reviewed Team sources do not establish customer-supplied third-party model API keys. C1 C2 |
| Department permissions | Topic/user/file association controls and access categories are present. Department access requirements and their implementation are scoped for each client. | Permission-aware search is documented. Standard and Plus describe identity controls and document-level access enforcement. G1 G3 | Team has role-based account permissions. Validate the selected connector and shared-content access for each department rather than assuming equivalent document controls. C2 C3 |
| Google Workspace integration | Request information about connecting your Workspace sources and the actions you need. Availability and connection scope are agreed in the client proposal. | Workspace connectors are documented. Confirm connector availability for the edition. G3 | Gmail, Calendar and Drive connectors. Team owners enable them, then users authenticate their accounts. C3 |
| Data location / ownership | Enterprise: the Data Store is built in your own GCP account and belongs to you; MatrixC hosts only the app. Hosted: run by MatrixC. Retention and deletion are set in the agreement. | Google says customers own their data and that it is not used to train its models. Standard/Plus residency controls are configuration-dependent. G3 | Organisation data is managed under the commercial agreement. Anthropic says commercial-product data is stored in the US, and traffic may be processed in select countries in the US, Europe, Asia and Australia unless agreed otherwise. C4 C5 |
| Who it suits (MatrixC assessment) | Organisations that want most staff using AI on company knowledge without paying per seat, with MatrixC setting up the sources and access. | Buyers evaluating Gemini Enterprise Business, Standard or Plus subscriptions for company search and agents, with edition-specific controls and per-user licensing. | Teams choosing Claude collaboration with per-seat administration and supported workplace connectors. |
BYOK here means supplying your own model-provider API key. It is different from customer-managed encryption keys.
MatrixC, a Google Cloud Premier Partner, also sells and implements Gemini Enterprise. We can discuss either option against your workflow, access requirements and expected use.
Review Gemini Enterprise pricing and quotation scope.
Official sources, each checked on 29 October 2026:
Try the advisor or take a free assessment
Try the STAX AI advisor to discuss a starting point. The advisor asks for your email and name, with company optional, before the conversation begins. Use a general business question rather than confidential company records in a public demo.
Choose an assessment for the decision you are making:
The demo and assessments are hosted on stax.matrixc.com. This page explains the product and quotation model.
Common questions
Choose a question, or read every answer.
Is STAX licensed per user?
No. Your quote is based on queries, storage and the model you choose. Your quotation defines the scope and applicable charges. User access must still be configured and managed.
What is the difference between STAX Data and STAX GPT?
STAX Data is the knowledge layer for organising the source material. STAX GPT is the conversational layer for finding information and preparing a next step. Confirm the supported sources and actions for your deployment.
Can each department have its own knowledge access?
STAX administration includes user/topic and topic/file association controls and access categories. Tell us which departments should access which sources. The access design and implementation are scoped for your organisation.
Can we use our own model or API key?
Yes. Use the default model within an agreed query limit, request another model and pay as you go based on its API token usage, or bring your own API key and pay the model provider directly. Model API keys are separate from encryption-key management.
Does STAX work with Google Workspace?
Tell us which Google Workspace sources and actions you need. We will discuss the connection approach and confirm availability, access requirements and scope in your proposal. The arrangement can differ between clients.
Where will our data be stored and processed?
For enterprise deployments, your Data Store is built in your own Google Cloud account and belongs to you; MatrixC hosts only the STAX app. For hosted deployments, MatrixC runs STAX for you. Queries go to the model you choose, under that provider's terms. Retention and deletion terms are set in your agreement.
How is STAX different from Gemini Enterprise or Claude Team?
Claude Team and Gemini Enterprise Business, Standard and Plus are licensed per user. STAX is one organisation subscription priced on queries, storage and model choice, set up with MatrixC around your knowledge sources and access needs. MatrixC also sells Gemini Enterprise if it suits you better.
How long will implementation take?
Agree the timetable after reviewing your source material, connections and access requirements. Discovery, setup, pilot and go-live have separate acceptance checks.
How should we judge whether it is worth continuing?
Agree a baseline for the chosen task before the pilot, then review answer quality, source accuracy, time required and actual use. Decide whether to expand from observed results.
Scope your first STAX workflow
A planning worksheet for your team and MatrixC
When staff need several files and a colleague's explanation to answer a routine question, choose one task to examine first. Record the information it needs, who may use it and who will review the result. This gives your team and MatrixC a starting point for the implementation discussion.
Open the first-workflow scoping worksheet
Use general descriptions and examples cleared for sharing. Leave confidential records, passwords and API keys out of the initial enquiry. Source access and any transfer of documents need to be agreed separately.
Organisation or team: ____________________
Person coordinating the discussion: ____________________
Date: ____________________
A. Choose the work
1. Describe one repeatable task
What starts the task, what does someone do today and what should the finished output help them do?
Complete this sentence: “When our team needs to __________, we use __________ to prepare __________.”
Your notes: ____________________________________________________________
2. Name the first team and workflow owner
Which team will try it first? Who owns the process and can decide whether the result is useful? Note how often the task occurs and any busy periods.
First team: ____________________
Workflow owner: ____________________
Frequency and busy periods: ____________________
B. Identify sources and access
3. List the approved source material
Start with the smallest source set that can answer the chosen question. Record a document description, its owner, the current version or date and who maintains it. Note where it lives and how changes will be approved. Source descriptions are enough for the first discussion.
| Source description | Owner | Current version or date | Update responsibility |
|---|---|---|---|
| ____________________ | ____________________ | ____________________ | ____________________ |
| ____________________ | ____________________ | ____________________ | ____________________ |
| ____________________ | ____________________ | ____________________ | ____________________ |
Sources that are outdated, unclear or still awaiting approval: ____________________
4. Define who may see what
List the roles or groups that may use each source. Identify material that must stay outside the pilot and who approves access. Include the access checks your team needs demonstrated before use.
Permitted roles or groups: ____________________
Restricted or excluded material: ____________________
Access approver and checks to agree: ____________________
5. Describe the output and any connections required
Choose the output you need, such as an answer, checklist, summary or draft response. Describe the source reference you need to check it. State what should happen when information is missing, outdated or contradictory.
If the task depends on Google Workspace or another system, name the source and the operation required. Separate finding information from creating or changing a record. MatrixC will confirm supported connections and actions for the proposed scope.
Expected output and source reference: ____________________
Missing or conflicting information should be handled by: ____________________
Systems, connections or requested actions: ____________________
C. Agree review and pilot checks
6. Keep a person responsible for the result
Who checks the answer or draft? Record the approval needed before a message is sent, a record is changed or another action is taken. Note where questions should go when the reviewer cannot resolve them.
Reviewer: ____________________
Approval required before sending or changing anything: ____________________
Escalation contact or role: ____________________
7. Define what a useful pilot must demonstrate
Record how the task works today, including manual steps, review effort or time required. Agree what you will compare during the pilot. Include a normal question, a missing or conflicting source and a request for restricted information in the checks you discuss with MatrixC.
Current process or baseline: ____________________
Checks and acceptance criteria: ____________________
Who decides whether to continue, revise or stop: ____________________
D. Prepare the quotation discussion
8. Estimate queries, storage and model needs
STAX uses an organisation-level subscription based on queries, storage and model choice. The number of people using the workflow helps estimate demand. It is not a per-seat licence count.
| Planning input | Your estimate or question |
|---|---|
| People expected to use this workflow | ____________________ |
| Expected questions in a typical month and at busy times | ____________________ |
| Source storage in GB, or an approximate file count if unknown | ____________________ |
| How often source material changes | ____________________ |
| Model preference | Default model / discuss another model / discuss our own model API key / advice needed |
| Deployment preference | Hosted arrangement / discuss our own GCP environment / advice needed |
With the default model, the quotation sets an agreed query limit. If you request another model, discuss its API-token usage charges. If you want to use your own model API key, ask MatrixC to confirm the supported arrangement and direct provider billing. Do not include the key in this worksheet.
These entries are planning estimates. MatrixC will confirm how usage is measured, applicable limits, supported options and charges in the proposal. Agree the implementation timetable after reviewing sources, access and connection requirements.
9. Agree responsibilities and the next decision
Identify who will maintain sources, approve access and support users. Mark responsibilities that still need agreement with MatrixC. Add your preferred pilot timing and any dependencies, such as source approval or administrator availability.
Source maintenance: ____________________
Access administration: ____________________
User support and escalation: ____________________
Preferred pilot timing and dependencies: ____________________
Next decision and its owner: ____________________
Example: finding an equipment handover procedure
This is a fictional planning example. It is not a customer result or a promise of a configured STAX deployment.
| Worksheet item | Example entry |
|---|---|
| Task | Help the operations team find the current equipment handover procedure and prepare a checklist for review. |
| Sources | One approved procedure and its current checklist. The operations lead owns both. |
| Access | The named pilot group may use the approved procedure. Personal records, account access details and individual equipment assignments stay outside this example. |
| Output | A draft checklist with a reference to the approved procedure. Missing or conflicting instructions are flagged for the operations lead. |
| Review and actions | The operations lead checks the draft. The example requests no automatic inventory update, email or other system change. |
| Pilot checks | Find the current instructions, handle a missing step, test the agreed access boundaries and compare review effort with the existing process. |
| Quotation inputs | Estimate questions and source storage for this workflow. Start by discussing the default model and confirm the deployment and support scope. |
Bring the scope to MatrixC
Share the task description, first team, source types, access boundaries and output you need. Leave unknown answers marked for discussion. Keep private documents and access material out of the initial message.
Discuss your first STAX workflow with MatrixC.
MatrixC will use the discussion to confirm fit, supported connections, access requirements and the proposed work. Your quotation should set out the organisation subscription, usage and storage basis, model arrangement, implementation work, responsibilities and applicable terms.
For product context, read how STAX works, the quotation inputs or model and API-key questions.
Use our enquiry form if you prefer to send a written summary.
Talk through your STAX scope
Bring one workflow, the sources it uses and the people who need access. Tell us whether you prefer a hosted arrangement or want to discuss your own GCP environment. We can use that to scope the deployment and an organisation-level usage and storage quotation.
