How do you handle SOC 2 / HIPAA / similar compliance requirements?

The architecture is built on Cloudflare with explicit access gating and audit logging — that’s the foundation. For SOC 2 work, we add specific log retention configurations and document the data flows for your auditor. For HIPAA-touching installs, we scope the BAA with your compliance team and partition the brain so PHI lives only where it’s explicitly governed. Real compliance work adds 2-4 weeks to the timeline and 10-20% to the setup cost — flagged during discovery.

What if some departments don't want to enroll?

Don’t force them. The Mid tier works just as well rolled out to 3 departments as to 6. The unenrolled ones still access the Company Brain through SSO; they just don’t get the Personal Brain layer. Bringing them in later is a follow-on engagement, sized to the additional brains.

How does this integrate with Microsoft Copilot or Google Gemini Enterprise?

The brains expose MCP endpoints that both Copilot (via custom plugins) and Gemini (via extensions) can query. Employees keep using their familiar AI tools; the brain just shows up as another piece of context the tool can reach. Most Mid installs run alongside an existing Copilot or Gemini Enterprise deployment.

What does the quarterly governance review look like?

90 minutes per quarter with the leadership group that owns AI governance. We walk through the audit log dashboards: query patterns, brain-utilization heatmaps, gaps in the corpus where employees ask questions the brain can’t answer. We update the governance contract if departments’ needs have shifted, and scope any new role-skill installs for the next quarter.

What if we need to add more departments mid-engagement?

The architecture supports it. Adding a department mid-build adds approximately 2-3 weeks to the timeline and proportional cost to the setup fee, depending on scope. Adding a department post-launch is a follow-on engagement, scoped at the time.

What happens if I switch from M365 to Google Workspace (or vice versa)?

The brain layer doesn’t care. SSO swaps to the new identity provider; ingestion swaps to the new file system. Switching costs are real but contained — typically 2-4 weeks of follow-on work, not a full rebuild. The portability is a feature.

Company Install · Mid Tier

Cross-functional teams. Governance that actually scales.

Price$25,000 – $45,000 setup + $2,500 – $3,500/moBook →

Duration

3–4 month engagement. 60-day post-launch support included.

Who it fits

Companies that have outgrown one-team-one-brain. Multiple functions. Real compliance footprint. Cross-departmental coordination needs.

15–50 employees. The tier where the AI rollout coordinates across departments, and the line between "this is institutional" and "this is mine" gets written down before it’s tested.

How it works

Diagnose. Build. Hand you the keys.

One method, three moves: we map your actual work, build your private brain from it, and hand you the keys — owned, portable, queryable from anywhere.

We map your actual work — the tools, the gaps, the shape your role needs.

We build your private brain from it — your corpus, indexed and queryable.

It's yours. Reach it from any LLM, at your own subdomain. You own it.

A brain per person. One that ties them together.

Every employee gets a portable brain — and a shared Company Brain holds what the org knows.

Each person gets their own private, searchable brain built from their real work — theirs to keep, portable when they move on.
Institutional knowledge — process, decisions, history — in one brain every tool can query, always current, nobody maintaining it.
READ, WRITE, ACT gates and access rules on who can query what. You own the deployment — it doesn’t walk out the door with anyone.

The architecture changes between 15 and 50.

Past 15 enrolled employees, the social fabric that made the Small tier work starts to fray. Nobody knows everyone. Teams form sub-cultures with their own vocabulary and workflows. The single-tier governance that held when the founder could pop into any conversation stops being enough.

Mid takes what was implicit and makes it structural. Departmental governance. Audit logs. Onboarding curriculum. Integration with the M365 / Google Workspace / Slack stack.
The Small-tier architecture stays the foundation — Personal Brains owned by employees, Company Brain owned by the company. Mid adds the scaffolding that holds it up under cross-functional weight.

“Past fifteen, the social fabric that held the small tier together starts to fray. The governance work is taking what was implicit and making it structural.”

What Mid adds over Small

The scaffolding layer.

Multi-department governance
Company Brain partitions by function. Sales-shape, engineering-shape, operations slices with different visibility rules. Governance contract grows from 5 pages to 15.
Onboarding curriculum
Real onboarding flow walks new hires through the brain in week one. Role-specific. New hire's Personal Brain starts forming day one.
Audit logs
Every cross-brain query logged. Quarterly governance review dashboards. Satisfies most compliance audit requirements for regulated industries.
M365 / Google / Slack
Real integration. Brains ingest from shared Drives + Teams folders. Conversational surface extends into Slack and Teams.
Department skill libraries
Each function gets custom skills. Engineering gets PR review + scoping. Sales gets proposal generation + follow-up. Compounds within function.

At Mid scale, the install IS the change-management project

Scope the right tier in 30 minutes.

Diagnostic Call (free) maps your headcount, compliance footprint, and integration stack to a tier and rough estimate. No commitment.

Book the Diagnostic Call→Or read Large tier↗

How a Mid-tier engagement runs

Four months to launch.

M1
Discovery + architecture
Department interviews. Governance contract drafted with department heads. Compliance scoping. M365/Google/Slack integration plan locked. Enrollment list confirmed.
M2
Build
Company Brain build with departmental partitions. Personal Brain installs in parallel (4–6/week). SSO + Slack/Teams integration. Department-tier skill libraries.
M3
Integration + training
Full integration testing. Department-specific training (2hrs each function). Onboarding curriculum finalized. Audit log dashboards stand up.
M4
Phased launch
Department-by-department over 2–3 weeks. Slower rollout catches edge cases per-department. By end of M4 the 60-day support window starts.

Pricing variance — why $25K–$45K.

The wide setup range reflects three factors:

Headcount enrolled — closer to 20 vs closer to 50.
Integration depth — basic SSO+Slack vs full M365 + audit + Drive ingestion.
Compliance scope — general business vs regulated industry with audit requirements.

A typical $25K install: 20 employees, basic Slack integration, no compliance requirements, 3 departments.
A typical $45K install: 45 employees, deep M365 integration, SOC 2-adjacent compliance work, 6+ departments.
Most Mid installs land in the $30K–$38K range.

Monthly retainer ($2.5K–$3.5K) scales similarly — roughly 1–2% of enrolled team compensation against the value of time saved. Payback runs 3–6 months.

Who this is for

Named by role.

The COO of a growing companyYou have 20-40 employees across 3-5 functions. The patchwork is breaking. You want governance written down before it gets tested.
The Head of OperationsYou own the operating stack. AI is the next layer. You want it installed properly the first time, with audit logs that satisfy your governance committee.
The department GM inside a larger orgYou have 30 people, real budget, and corporate IT isn't going to solve AI for you in any reasonable timeframe. You can run a real install at the department level.
The Head of PeopleYou're responsible for onboarding. Today it takes a quarter to ramp a new hire. The brain + onboarding curriculum compresses that to weeks while improving consistency.

What’s included

In the price.

Everything in Small tier, plus:
Multi-department governance with departmental partitions on the Company Brain
Onboarding curriculum, role-specific and built into the brain experience
Audit logs for cross-brain queries, with quarterly governance review dashboards
Deep M365, Google Workspace, and Slack integration (ingestion + conversational surface)
Department-tier skill libraries — function-specific, compounding within the team
Compliance scoping during discovery (HIPAA-adjacent / SOC 2-adjacent / etc. as needed)
Phased department-by-department launch over 2-3 weeks
60-day post-launch support window with structured weekly check-ins

Common questions

Asked, answered.

How do you handle SOC 2 / HIPAA / similar compliance requirements?
The architecture is built on Cloudflare with explicit access gating and audit logging — that’s the foundation. For SOC 2 work, we add specific log retention configurations and document the data flows for your auditor. For HIPAA-touching installs, we scope the BAA with your compliance team and partition the brain so PHI lives only where it’s explicitly governed. Real compliance work adds 2-4 weeks to the timeline and 10-20% to the setup cost — flagged during discovery.
What if some departments don't want to enroll?
Don’t force them. The Mid tier works just as well rolled out to 3 departments as to 6. The unenrolled ones still access the Company Brain through SSO; they just don’t get the Personal Brain layer. Bringing them in later is a follow-on engagement, sized to the additional brains.
How does this integrate with Microsoft Copilot or Google Gemini Enterprise?
The brains expose MCP endpoints that both Copilot (via custom plugins) and Gemini (via extensions) can query. Employees keep using their familiar AI tools; the brain just shows up as another piece of context the tool can reach. Most Mid installs run alongside an existing Copilot or Gemini Enterprise deployment.
What does the quarterly governance review look like?
90 minutes per quarter with the leadership group that owns AI governance. We walk through the audit log dashboards: query patterns, brain-utilization heatmaps, gaps in the corpus where employees ask questions the brain can’t answer. We update the governance contract if departments’ needs have shifted, and scope any new role-skill installs for the next quarter.
What if we need to add more departments mid-engagement?
The architecture supports it. Adding a department mid-build adds approximately 2-3 weeks to the timeline and proportional cost to the setup fee, depending on scope. Adding a department post-launch is a follow-on engagement, scoped at the time.
What happens if I switch from M365 to Google Workspace (or vice versa)?
The brain layer doesn’t care. SSO swaps to the new identity provider; ingestion swaps to the new file system. Switching costs are real but contained — typically 2-4 weeks of follow-on work, not a full rebuild. The portability is a feature.