We map your actual work — the tools, the gaps, the shape your role needs.
Company Install · Enterprise Tier
Full institutional embed. AI rollout as operating-model change.
Duration
12+ month engagement. Quarterly governance + outcome reviews. Multi-year retainer typical.
Who it fits
Companies of 250+ where AI rollout is a real strategic priority. Companies where the existing operating model and the AI infrastructure have to evolve together.
250+ employees. The tier where the install isn’t separable from how the company changes how it works. Twelve months minimum. Custom-priced because the work at this scale isn’t productizable in the normal sense.
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 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.
Why Enterprise is custom.
At 250+ employees, the install stops running alongside operations. It becomes part of how the company changes its operating model.
- The real work is structural, not technical. The architecture is necessary infrastructure, but the real work is in the slower changes: how decisions get made, how knowledge moves between functions, how leadership transitions happen without losing institutional memory.
- No two operating models match.The architecture decisions are the same across engagements; the deployment, change management, and integration with the company’s broader strategy can’t be packaged into a SKU.
- Pricing is phased to delivery. It ranges from low six figures to mid seven figures. Most Enterprise engagements run as multi-year partnerships with phased payment tied to phased delivery and outcome milestones.
“Every Enterprise install is custom because the work at this scale is custom. No two five-hundred-person companies have the same operating model.”
What an Enterprise engagement covers
Six layers of partnership.
Architecture at scale
Multi-tenant platform, cross-department rights, 200–1500+ enrolled brains deployed in waves across 12–18 months. Function-tier skill libraries.
Operating-model integration
AI rollout connects to broader change initiatives. Reorgs, new departments, M&A absorption — the install becomes part of the operating model.
Executive partnership
Direct C-suite working relationship. Monthly executive briefings. Standing seat at the operations committee.
Custom skill development
Not generic role-tuned skills. Custom skills tuned to your specific operating practices — your sales stages, your artifacts, your way.
Internal capability transfer
1–4 person internal team trained and embedded. By engagement end, the company has both the system AND the capability to evolve it.
Strategic advisory layer
Quarterly reviews of where AI infrastructure should evolve next. Macro-trend reads. Separate from operational care; sits at the strategy table.
Enterprise starts with a discovery quarter, not a contract
Q1 is bounded. The full commitment lands after.
First quarter (discovery + architecture + executive alignment) produces a detailed scope before any multi-year contract is signed. You see the work product first.
How a 12+ month engagement runs
Four quarters to operating-model integration.
- Q1
Discovery + alignment
Executive interviews. Operating-model mapping. Compliance scoping. Multi-tenant architecture designed. Pilot dept selected. Executive sponsorship locked.
- Q2–3
Pilot + wave one
Pilot depts deployed first. Wave-one (3–6 depts, 60–200 brains) rolled out in parallel. Internal capability team begins embedding.
- Q4
Wave two + steady
Remaining departments. Cross-department rights fully activated. Governance contract finalized at executive level. First annual outcome review.
- Y2+
Strategic partnership
Ongoing evolution. New capabilities quarterly. M&A absorption. Internal team takes full ownership; our role evolves to strategic advisory.
Who runs Enterprise engagements.
We do, personally, as the primary partner.
- A small, named senior team.The deployment work is supported by a small team brought in for the engagement — typically 2–4 senior practitioners across architecture, compliance, change management, and skill development. We don’t run two Enterprise engagements at once. The team is named before contract.
- Cloudflare for architecture at scale.The platform underneath the brains is Cloudflare’s enterprise infrastructure, with direct support relationships for novel deployment patterns.
- Specialists for heavy compliance.For SOC 2, HITRUST, or FedRAMP-adjacent work, we bring in specialists who’ve done the specific work before. The team is calibrated to the engagement; you don’t pay for capability you don’t need.
Who this is for
Named by role.
- The CEO of a 300-1500 person companyAI is on your board agenda. You want a real partner, not a vendor selling tools. You want the rollout to land as an operating-model upgrade, not a feature deployment.
- The COO of an enterpriseYou own the operational execution. You've been through enough large rollouts to know that the architecture is the easy part — the change management is what determines success.
- The CIO / CTO of a mid-market companyYou're responsible for the technical stack at scale. You want the AI architecture to be yours, multi-tenant, portable across vendor changes, and built to evolve with the company over 5+ years.
- The Head of Strategy / TransformationYou lead the strategic change office. The AI rollout intersects with three other initiatives you're running. You need a partner who can hold the operating-model view, not just deploy a system.
What’s included
In the price.
- Custom-scoped engagement, sized to your institutional reality
- Full Large-tier architecture + scaled deployment (up to 1500+ enrolled brains)
- Multi-year strategic partnership, with phased delivery and outcome milestones
- Direct executive partnership: monthly briefings, quarterly governance + outcome reviews
- Custom skill development tuned to your specific operating practices
- Internal capability transfer — embedded team trained to own the platform post-engagement
- Strategic advisory layer beyond operational deployment
- Compliance work scoped to your regulatory environment (HIPAA, SOC 2, FedRAMP-adjacent, etc.)
- Operating-model integration with other change initiatives
- Named senior team disclosed before contract
Common questions
Asked, answered.
How much does this cost?
Low six figures to mid seven figures depending on scope. Most Enterprise engagements run as multi-year partnerships with phased payment tied to phased delivery. The first phase (typically Q1 discovery + architecture) is bounded and produces a detailed scope before you sign for the full engagement.
How is this different from hiring a Big Four consulting firm?
Specialization and ownership. Big Four engagements at this scale are run by generalist project managers who staff specialists below them; the work scales by adding bodies. This engagement is run by us directly with a small senior team, all of whom have built brain installs before. The output is also different — Big Four produces a strategy and architecture deck; this produces deployed infrastructure plus internal capability. The work product is the system, not the strategy doc.
What about Microsoft, Google, or other enterprise AI partnerships we already have?
The Install layers on top. Microsoft Copilot, Google Gemini Enterprise, OpenAI Enterprise — all consume MCP endpoints, all get more useful with the Personal and Company Brain layers underneath. The Enterprise tier integrates with whatever vendor relationships you have rather than replacing them. Most Enterprise installs run alongside one or two existing enterprise AI deployments.
What's the risk if the engagement doesn't work?
If Q1 discovery reveals the institutional readiness isn’t there, we say so and you exit cleanly. Past that, phased delivery against milestones lets you see whether the engagement is producing value at any point and decide whether to continue. The off-ramps are explicit, not buried.
Can you support our M&A activity?
Yes. The multi-tenant architecture is built for absorbing acquired entities. Acquired companies can be onboarded onto the institutional umbrella with their own Company Brain and Personal Brain installs, integrating with the parent at whatever pace makes sense (not necessarily Day 1). For active M&A pipelines, the engagement can include playbook development for AI-rollout-during-acquisition.
What happens at the end of the engagement?
By design, the company owns the deployed infrastructure and has an internal team trained to evolve it. The strategic advisory relationship typically continues at a lighter cadence (quarterly rather than monthly) for years after — but the company is no longer dependent on us for day-to-day operation.
Adjacent paths
Where this connects.
Large tier — 50–250 employees
The tier below. Right scale if you're under 250 enrolled employees.
Company Install overview
The parent page with full architecture explanation across all four tiers.
AI Strategy Advisory
For ongoing strategic-level advisory without the full Enterprise install commitment.
Back to The Install
The full offer ladder.
Start with the Diagnostic Call.
Enterprise engagements start with a 30-minute Diagnostic Call to determine whether the engagement is the right shape, followed by a longer institutional discovery phase. You don’t commit on the first call — you see what discovery produces first.
As featured in
