The Business Brain · for the enterprise
Enterprise
Business Brain.
Operating Intelligence for organizations — accumulated, governed, accountable. One intelligence above the tools your team already uses, where the memory, judgment, and work of the business live together.
We share what we have today, what's on the roadmap, and where we won't sign — before you ever see a quote.
Q3 Strategy · brief
Context
What did we decide about Q3 pricing?
Enterprise · audit
Every action logged
The premise
The cost of fragmented work
is mostly invisible — until it isn't.
Every modern organization runs its work across four to six tools that don't really know about each other. The work gets done. But three costs compound silently — and at scale, they become quietly enormous.
Knowledge evaporates.
Decisions made in chat are lost within weeks. Context shared in DMs walks out the door when people leave. New hires take 90 days to learn what the organization already knew.
AI lives outside the work.
Generic AI assistants don't know your business, your clients, your decisions, or your patterns. Every prompt starts from zero. Every output is generic best-practice — never your specific context.
Governance fragments by tool.
Each surface has its own permissions, its own audit log, its own data-residency stance, its own AI provider. Compliance evidence scatters. Risk consolidates upward; control disperses downward.
The market response has been to add more tools. The structural answer is not another tool — it's an operating intelligence layer above the tools.
Six foundation surfaces · one intelligence
This is what Colix looks like,
surface by surface.
Six surfaces where the work of the organization lives. The Context layer (next section) sits on top of all six.
Surface · 01 of 06
Documentation
every page knows its place.
Block-based pages for proposals, briefs, strategy memos, meeting notes, decision records, runbooks. Every page lives in a permissioned tree, threaded with conversation, attached to the projects and clients it belongs to.
- Rich blocks: text, headings, tables, embeds, code, callouts
- Comments and threaded conversation on every block
- Page-level + block-level permissions
- Decision records as first-class block types — searchable, citable
Q3 Strategy · brief
Decision · open
Proceed with EMEA 6% list increase, effective July 1
Surface · 02 of 06
Messaging
conversations stay where the work is.
Team channels, threaded discussions, direct messages — organized around the projects, processes, and clients they belong to. No firehose. No scrolling-to-find. Conversation is tied to context.
- Channels per project, process, client, or team
- Threads keep the conversation about one thing in one place
- Decisions made in chat become part of the project's permanent record
- Mentions, presence, read receipts — and DM AI is opt-in per conversation
# strategy
6 in channelMaya
10:02
Pricing Committee approved the EMEA increase yesterday. Decision record attached.
Sam
10:07
Three accounts flagged for exec-touch communication — Aiden is drafting.
AI · summary proposed
3 decisions, 1 open action — would you like a daily digest?
Surface · 03 of 06
Work pages
projects, processes, and clients as first-class entities.
Three structured work surfaces. Projects for time-boxed initiatives. Processes for repeating workflows that need governance and approvals. Clients for engagements, accounts, and relationships. All three accumulate context the same way.
- Project pages: scope, deliverables, milestones, tasks, owners, status
- Process pages: defined stages, owners, SLAs, audit trail per run
- Client pages: engagement history, decisions, conversations, deliverables
- Same primitives across all three — pages, tasks, conversations, decisions
Projects
12 active
Processes
8 defined
Clients
37 engaged
Active engagements
Project · Q3 GTM launch
Process · New-vendor onboarding · run 247
Client · Acme · Strategic review
Process · Quarterly close · run 14
Surface · 04 of 06
Inner-circle mail
internal email, structured.
A native mail surface for internal correspondence — with the rich-block content of a Colix page, threaded by topic, attached to the projects and clients the conversation belongs to. External mail integrates through Google Workspace and Microsoft 365.
- Internal mail with full Colix block content (not plain text)
- Auto-attached to the project, process, or client at hand
- External mail integrated — send and receive through your existing accounts
- Every sent message logged on the relevant Colix page
Inner-circle mail · # strategy
Today · 4 messagesEMEA Q3 — final decision and rollout
Approved by the committee on May 14. Effective July 1. Rollout plan attached as block, with grandfathering clauses…
Three accounts for executive-touch
Account list below with current ARR, renewal date, and recommended call-script…
Surface · 05 of 06
Calendar
your week, where the work is.
Calendar events from Google and Microsoft alongside Colix-native events — project milestones, process deadlines, client commitments. Open an event; the relevant project page, conversation thread, and decisions are one tap away.
- Two-way sync with Google Workspace and Microsoft 365
- Colix-native events tied to projects, processes, and client commitments
- Meeting notes auto-attached to the event and the project page
- AI-drafted briefing before each meeting, sourced from the work itself
Week of May 25
5 days · 12 eventsMon
25
10:00
Pricing Committee
Tue
26
14:00
Acme · QBR prep
Wed
27
09:30
EMEA team sync
Thu
28
11:00
Process review
Fri
29
13:00
Q3 Strategy review
AI · brief proposed
Pre-meeting brief for Acme QBR — sourced from the engagement page
Surface · 06 of 06
Inbox
what needs you, today.
One surface that surfaces the decisions, tasks, and approvals that need a human response right now — across every project, process, client, mail thread, and conversation. The Inbox is what senior leaders open first thing in the morning.
- Decisions, tasks, approvals — prioritized by context
- Each item carries its full context: which engagement, which thread, what AI proposed
- One-tap approve, reject-with-reason, or defer-back-to-queue
- AI-suggested actions are visible until you tap — never autonomous
Inbox · Tuesday morning
4 items · 2 urgentDecision · pricing approval
Pricing · Q3
Approval · vendor onboarding · run 247
Process · finance
Review draft · Acme QBR brief
Client · Acme
Reply needed · CISO data-residency q.
Inner-circle mail
On top of the six surfaces · Context
Ask Nora what your business knows.
Get a grounded answer.
Context is the layer that turns six surfaces of accumulated work into a single intelligence you can interrogate. Multi-turn. Multi-layer. Grounded in the documents, decisions, conversations, and deliverables your team has already produced — with permissions respected at every step.
The questions Context is built for
- Decision questions — "What did we decide about [vendor / strategy / customer] last quarter? Why?"
- Status questions — "Where does [program] stand across the four teams running pieces of it?"
- Relationship questions — "What did [client] tell us in the last three meetings? What did they ask for?"
- Expertise questions — "Who is closest to [topic] — and what have they said about it?"
- Pattern questions — "Have we seen this objection / risk / situation before? What worked?"
Every answer cites its sources. Every source respects the asker's permissions. When the source is a document the asker can't read, the answer is honest about not having access — never silently includes or excludes.
Context · Ask Nora
You · 9:41 AM
What did we decide about the Q3 pricing change for the EMEA accounts?
Nora · grounded answer
On May 14, the Pricing Committee approved a 6% list increase for EMEA enterprise accounts, effective July 1, with a 90-day grandfathering window for renewals already in flight. The driver was the EUR/USD shift and the Q1 margin compression. Three accounts are flagged for executive-touch communication — see the decision record on Pricing Committee · May 14.
Three commitments · architectural, not advisory
Built so AI runs as your team
— not around them.
The first major liability event caused by an unsupervised AI action will reshape every enterprise procurement conversation. The architecture below is what your CISO and General Counsel will want to see.
Commitment · 01
AI runs as the user.
Where you have permission, AI has permission. Where you don't, neither does AI. There is no elevated AI service account. There never will be.
Commitment · 02
AI proposes; teams approve.
Every shared-state action AI takes is a proposal — visible until a human taps approve. Every approval is logged with user, timestamp, evidence, and reasoning. One-tap revert. Complete audit by default.
Commitment · 03
Training is permanently off.
AI training on your content is disabled by architecture. Changing this would require explicit, opt-in consent per customer plus executive sign-off. There are no plans to.
Model choice · per workspace, per task
Pick the model
your security team approved.
AI workloads route across multiple providers — by task, by jurisdiction, by your security team's policy. When the model market shifts — pricing, capabilities, regulation — you toggle. You don't migrate.
- Risk-diversify across providers. No single AI vendor holds your roadmap.
- Match the jurisdiction. Data-handling and provenance per region.
- Cost control. Pin low-cost models for bulk; reserve top-tier for the hard ones.
- Bring your own keys. Colix as pure infrastructure; you pay providers directly.
- Local or on-premise models supported for regulated workloads.
Workspace default · per-user override allowed
Anthropic Claude
Workspace default
OpenAI GPT
Available
Google Gemini
Available
DeepSeek
Available
Your local / private model
BYOK · self-hosted
Switch providers per workspace, per region, per task — policy controls determine which workload routes to which provider. Failed first-try doesn't cost credits, on any provider.
Security · governance · sovereignty
Enterprise controls,
honestly stated.
What is live today. What is on the roadmap with a date. What is negotiable under your Enterprise contract. We don't market capabilities we don't have.
Single sign-on (SAML 2.0)
Day 1
SCIM provisioning
GA Q3 2026
Role-based access control (page, channel, AI-action)
Day 1
Audit-log streaming to SIEM (Splunk, Datadog)
Enterprise · Q4 2026
Data residency by region (US / EU / APAC)
Enterprise · per MSA
Customer-managed encryption keys (CMEK)
Enterprise · Q4 2026
Zero-retention AI provider configurations
Enterprise · per DPA
Bring-your-own AI provider keys (BYOK)
Business + Enterprise
On-premise / air-gapped deployment
Enterprise · regulated workloads
SOC 2 Type II certification
In active progress · we do not claim it yet
We will share our current security posture document, in-progress audit evidence, and contractual delivery commitments before you sign anything. Read the public security page.
The pilot path
Ninety days to live.
Twelve months to compounding returns.
Three structured phases. One business unit at a time. Every phase has a clear outcome the executive sponsor signs off on before the next phase begins.
Phase 1 · Foundation
Days 1–30
Tenant provisioning, SSO integration, pilot business unit selected. Initial workspace structured for the unit's actual workflows. Mail and calendar integrations live. First processes and client pages populated.
Phase outcome
The pilot unit's daily work is genuinely happening on Colix — not 'we set it up,' daily work.
Phase 2 · Expansion
Days 31–60
Additional business units onboarded — one per week, structured by the pilot unit's lessons. Audit-log streaming configured. Custom integrations begin. Process library expands. Initial measurement baseline established for time-to-decision metrics.
Phase outcome
Cross-unit Context Q&A becomes useful. The Inbox becomes the default daily surface for senior leadership.
Phase 3 · Compounding
Days 61–90 and onward
All in-scope business units running on Colix. Cross-organizational Context Q&A is routine. Pipeline visibility informs quarterly business reviews. First measurable gains in decision velocity reported.
Phase outcome
Year 1's investment becomes Year 2's competitive asset. The brain remembers what your organization did, decided, and learned — across every quarter.
The most useful next step
A structured working session.
Ninety minutes. Four to six people.
We walk through Colix's live product against your actual workflows. We discuss architectural fit, integrations, and compliance in concrete terms. We identify the right pilot business unit and agree the success criteria. If the working session confirms strategic fit, we propose a 30-day paid pilot.
Frequently asked
Common questions
at the enterprise stage.
Is Enterprise a self-serve tier?
No. Enterprise is sales-led. We want a real conversation about your security posture, compliance requirements, integration targets, and deployment timeline before anything goes in writing.
How does Colix's AI access work for content my team has restricted access to?
AI runs as the user, not as a service account. Where the user has permission to a document, channel, or page, AI has permission. Where the user doesn't, AI doesn't either. There is no elevated AI index that 'summarizes safely across permission boundaries.' We treat permission boundaries as architectural, not advisory.
Can we keep our own AI provider relationships?
Yes. On Business and Enterprise, you can route AI work to providers you've already negotiated with — Anthropic, OpenAI, Google, DeepSeek, or a self-hosted local model. Bring your keys; Colix becomes pure infrastructure. Where pricing changes, jurisdiction shifts, or a model's capabilities evolve, you switch the routing — not the workspace.
What about SOC 2, HIPAA, and the EU AI Act?
SOC 2 Type II is in active progress. We do not claim certifications we don't currently hold. For HIPAA, the architecture supports BAA-eligible deployments under Enterprise contract with PHI tagging. The EU AI Act readiness program runs in parallel with SOC 2 — accountable-AI primitives, audit-log retention, and per-user permission boundaries are already structural.
Can we get audit-log streaming to our SIEM?
Yes — Splunk and Datadog under Enterprise contract, GA Q4 2026. Other destinations are negotiable under MSA.
What's the SLA?
We don't publish a uniform SLA. Availability targets, response windows, and remediation paths are negotiated per Enterprise contract — your auditor's bar is the bar we sign to. We'd rather meet a real number than print a marketing one.
How is pricing structured at organizational scale?
Enterprise contracts are negotiated under MSA — typically per-seat with volume bands, plus negotiated terms for data residency, SIEM streaming, CMEK, custom integrations, and dedicated technical relationship. AI usage at Enterprise scale is structured per-organization, not per-seat metering.
What does the pilot cost?
Phase 1 (the first 30 days) runs under a paid pilot agreement scoped to one business unit. The pilot terminates cleanly if you decide not to proceed; if you do proceed, the pilot deployment converts directly into Phase 2 without re-provisioning.