The adoption program leaves you trained teams and a governed library of skills. The Company OS is what they become — one layer any employee can ask anything, grounded in your institutional knowledge, acting across every system where work happens.
White light, recombined
The Layer
Think Ramp’s Glass, or the internal OS Slack runs on — built around your company instead of theirs.
What it is
What it isn’t
Architecture
An employee asks in plain language; the stack decides what to call and what it’s allowed to touch.
Wherever people already work — chat, desktop, voice on mobile.
A frontier model that decides which skills to call, in what order.
The 20–50 governed workflows the adoption program shipped — versioned, owned, evaluated.
Your data and tools, behind your permission boundaries — nothing more.
A Day With the OS
Real queries from a running Company OS — every answer cites where it looked.
How did EMEA pipeline move against commit this week?
EMEA sits at 92% of commit, down four points week-over-week. Two deals slipped the quarter — Nordika ($410K) and Bellmont ($275K) — pushed, not lost.
Which suppliers have price-rise clauses triggering next quarter?
Three indexation clauses trigger in Q3: Halvorsen (Aug 1, CPI + 2%), Trellix (Sep 15, capped 4%), Ardent (Sep 30, fuel-linked). Renegotiation windows open 60 days prior.
Draft the board update on the program.
Drafted and sitting in your drafts. Adoption at 84% weekly active, 52 skills live — every number linked to its dashboard.
The Query Library
What people actually ask a running Company OS, function by function.
“Where are we against the forecast, and what changed since Tuesday?”
“Which entities are holding up the close right now?”
“How did EMEA pipeline move against commit this week?”
“Which renewals in the next quarter look at-risk, and why?”
“Which supplier contracts have price-rise clauses triggering next quarter?”
“Summarize our obligations under the three agreements signed this month.”
“What broke last night and what did it cost us?”
“Who still has access they shouldn’t after the reorg?”
“Draft the onboarding plan for the engineer starting Monday in the Lisbon office.”
“What did the engagement survey say about the support team, really?”
“Assemble the quarterly board update on the AI program.”
“Show me every override on the invoice classifier this month.”
Earned, Not Installed
You can’t buy them, and you can’t skip to the end without them.
People who already trust and use skills daily — no adoption cliff to climb.
200–400 workflows mapped and prioritized, so the OS knows what to do first.
Eval harnesses, audit trails, and confidence gates it inherits instead of inventing.
The hard rule
The Build Plan
Connect the systems, teach it the company, open the doors.
ERP, HR, ticketing, and CRM become its tools — permissions mapped first, orchestrator live over the top twenty skills.
The knowledge layer lands; cross-function queries open to a fifty-person pilot, every answer citing its sources.
Company-wide rollout on the existing enablement machinery — telemetry from day one, handoff to your internal AI engineer.
What Compounds
Each workshop adds skills linearly — the OS makes them work together.
What took three teams a week now takes one question.
What the twenty-year controller knows, every new hire inherits.
Every add-on plugs into skills, governance, and interface at close.
What the OS Inherits
Everything months one to three built keeps working — the OS just becomes the biggest thing it protects, measures, and feeds.
The point
Proof
Four operating companies ran the adoption program in parallel; then the HoldCo connected the whole estate under one Company OS.
How OS builds are priced
Company OS builds run $1.2–2.8M, sized to system count and governance depth. The scope is written at week 12 of the adoption program, when the process inventory proves what the OS should do first.
Scoping Factors
Five factors set where a build lands in the $1.2–2.8M range — all known by the time we quote.
Read-only lookups cost less than write-back actions.
How strictly data is walled off — entity, geography, fund.
Regulated industries need more evals, gates, and evidence.
How much institutional memory gets structured in.
Every language asked in, the eval harness must cover.
Scoped at week 12, priced fixed, milestone-billed — the full number before the build starts.
The Arc
The spectrum splits: trained teams, a scored inventory, a governed skill library — a number the CFO can defend.
The spectrum recombines: one brain over every system, value that multiplies instead of adds.
Restated
The Rest of the Spectrum
Ready to move
The Company OS is scoped at week 12, after the adoption program proves what it should do first. Pick the function that hurts most.
Talk to LightCI