Company Install · Enterprise Tier
Full institutional embed. AI rollout as operating-model change.
12+ month engagement. Quarterly governance + outcome reviews. Multi-year retainer typical.
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.
Why Enterprise is custom.
At 250+ employees, the AI install stops being a project that runs alongside the company’s normal operations. It becomes part of how the company changes its operating model. The technical architecture is necessary infrastructure, but the real work is in the slower, structural changes: how decisions get made, how knowledge moves between functions, how leadership transitions happen without losing institutional memory.
Every Enterprise install is custom because the work at this scale is custom. No two 500-person companies have the same operating model. The architecture decisions are the same; the deployment, change management, and integration with the company’s broader strategy can’t be packaged into a SKU.
Pricing 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.
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.
“Every Enterprise install is custom because the work at this scale is custom. No two five-hundred-person companies have the same operating model.”
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; my role evolves to strategic advisory.
Who runs Enterprise engagements.
I do, personally, as the primary partner. The deployment work is supported by a small team I bring in for the specific engagement — typically 2–4 senior practitioners across architecture, compliance, change management, and skill development. I don’t run two Enterprise engagements simultaneously. The team is named before contract.
For technical architecture at this scale, I partner with Cloudflare directly — the platform underneath the brains is Cloudflare’s enterprise infrastructure, with direct support relationships for novel deployment patterns.
For heavy compliance (SOC 2, HITRUST, FedRAMP-adjacent), I 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 the larger commitment lands. You don’t sign for the full multi-year engagement until you’ve seen what the first quarter produces.
How is this different from hiring a Big Four consulting firm?
Specialization and ownership. Big Four engagements at this scale are typically run by generalist project managers who staff specialists below them; the work scales by adding bodies. The Enterprise engagement is run by me directly with a small senior team, all of whom have built brain installs before. The output is also different — Big Four typically produces a strategy and architecture deck; this engagement 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 of them consume MCP endpoints, all of them get more useful with the Personal and Company Brain layers underneath. The Enterprise tier explicitly 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?
The first quarter is bounded and produces concrete output before the longer commitment lands. If discovery reveals that the institutional readiness isn’t there, we say so and you can exit cleanly. Past that, phased delivery against milestones means at any point you can see whether the engagement is producing value and decide whether to continue. The structure is designed to make off-ramps explicit rather than 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 organization at whatever pace makes sense (not necessarily Day 1). For active M&A pipelines, the Enterprise 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 as long as it’s useful. Most Enterprise engagements I’ve seen evolve into a strategic advisory relationship that continues for years after the operational work is complete — but the company is no longer dependent on me for day-to-day operation.
Adjacent paths
Where this connects.
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 before any commitment. You don’t commit to the engagement on the first call. You see what discovery produces before deciding.
As featured in
