The AgenticOS that runs your company live.
Your documents, processes, apps (the legacy ones too), goals, playbooks, KPIs and agents in one living system. It models how your company really works, stays true to your own systems, and keeps its own judgment: a referee on every action, and coaching that reads the game over time. Your people steer it while the game is on.
The main goal is the sun, each area a planet, and every role, record, action and goal a moon the company's people decided. Point at a shape to read it.
Beyond the tour
One living system for everything your company runs on
Today a company runs on documents nobody updates, processes in slides, apps that don't talk to each other, goals in a spreadsheet and a report at the end of the quarter. Kumi brings all of it into one AgenticOS, alive on the company's own data, where people and agents work under the same rules.
Change the play while the game is on
Management sees the company as it is today, and acts today, instead of reading about it when the quarter is over.
Informed when it's too late
The plan: 120 cars, none below the floor.
Counters slip below the floor. Nobody sees it in time.
The Q4 report, built by hand from three systems.
The post-mortem: nine cars were sold below the floor in November.
Act while it happens
The twin shows four counters below the floor this week.
Coaching flags the drift to Daniel, who owns the play.
Daniel tightens the play: used cars above 6% go to him. It runs on the twin first.
Back on track. The change and its reason are on the ledger.
An example from the demo club, Norte Autos, in its first season.
No more drift from the vision, no more outdated documentation, no more retyping between systems, no more post-mortems. The model stays true because it runs on the company's own data, and management changes the tactics while things happen.
Twenty-five years of the same four walls
We have spent twenty-five years building processes, applications and solutions for companies. The projects change. The walls they hit stay the same.
Friction with the teams
A new process or app arrives from above. The people who do the work were not asked, so they route around it, and adoption becomes a campaign.
Drift from reality
The process document is right the day it is written. Then a rule changes by message, a system adds a field, a workaround becomes the habit. Months later the documents describe a company that no longer exists.
Three truths
What the owners want, what the managers say happens and what really happens are three different stories. Every decision is made on the version one person happens to hold.
Too late
The numbers are gathered by hand into a report at the end of the quarter. By the time anyone reads it, all that is left is the post-mortem.
The first three walls are about alignment, and Kumi answers them with the company's DNA. The fourth is about time, and Kumi answers it with a live twin and a judgment layer that never sleeps.
Agents can now do the rule-following part of a company's work. What is missing is a safe place for them to do it: a live model of the company that its people trust, rules that hold whatever an agent is told, and a way to hand over work one action at a time as trust is earned. That is what we are building.
Where the ideas come from
Kumi borrows from playbooks that already work, and changes what doesn't fit a mid-size company.
The lighthouse
A copilot sells the tool. An autopilot sells the work.Julien Bek, Sequoia Capital, “Services: The New Software”, March 2026
- Intelligence work goes to AI. Judgment stays with people.
- Today's judgment becomes tomorrow's intelligence, as the data on it builds up.
- The outsourced task is the wedge.
Bek writes about companies that sell one kind of work to many customers. Kumi is the inside version: how a company turns its own services into software, under its own people, one season at a time.
Ontologies and forward deployment
- Borrowed
- An ontology of the business: a semantic layer of objects and links, and a kinetic layer of actions, built over the company's data by engineers who sit with the customer. Palantir does this for the largest organizations.
- Changed
- A judgment layer on top, the referee. Built in weeks by a pair, a person and an agent, decided piece by piece by the company's own people, with the data left where it lives.
Palantir, “Who wants to be a Delta?”; our reading of its public writing, October 2026.
The digital twin
- Borrowed
- Industry keeps a live model of a machine, synced to the real one, to see what is happening and to test before acting.
- Changed
- Kumi's twin is of a company's work: its records, actions and goals, read from its own systems and never retyped.
Operating systems
- Borrowed
- What an operating system gives every program: an identity and permissions, memory, a safe way to act, a schedule, a way to be installed and retired.
- Changed
- Kumi gives the same to agents: a position, a mandate per action, the huddle and the ledger, the toolbox behind the referee, seasons and a career.
The sports club
- Borrowed
- How a club brings in new players and learns to trust them: scouts, a bootcamp, a pre-season, a season, a referee, a scoreboard, a career from rookie to veteran. Words a CEO, a seller and an engineer already share.
- Changed
- The players are agents and the club is a company. Each word is also a part of the system.
Agile and OKRs
- Borrowed
- Short sprints, retros, and goals with key results, each scored on its own.
- Changed
- Key results are computed on the twin, never typed in. When a play misses, the play changes that week and the goal stays.
Discovery and culture research
- Borrowed
- The engagement draws on EOS, GOV.UK's discovery phase, the Design Sprint and Lean Inception. The three truths come from Schein's levels of culture and Argyris's espoused theory against theory-in-use.
- Changed
- An agent does the reading and people do the deciding. Every principle and contradiction becomes a record with its evidence.
EOS · GOV.UK · Design Sprint · Lean Inception · Schein · Argyris
Your company's ontology, running as a digital twin
Kumi models a company in three layers. The semantic layer is what the company is. The kinetic layer is what it does. The judgment layer is what makes sense: the referee rules on every action in the moment, and Coaching reads the game over time. Connected to the company's own systems, the model runs live. Kumi calls this ontology the blueprint.
Judgment: each orange mark is a finding, from the referee or from Coaching. Point at a shape or a finding.
What the judgment layer found
In the demo club: the Scout during the bootcamp, Coaching over the season, the referee in the moment.
What the company is
Areas, roles and people, records, systems (the legacy ones too), documents and goals, with the links between them. Every shape cites its evidence and the person who decided it.
What the company does
Actions with their limits, plays and set pieces, decisions. People and agents act through the same actions, so every move lands in the twin.
What makes sense
Rules, principles and common sense, held in two places, as in a match. The referee rules on every action in the moment: applied, asked or refused. Coaching reads the game over time and sends each gap, misalignment or drift to its owner. Neither decides alone.
The referee on one action
One night lead, from the website to the ledger.
A lead arrives
A family asks about a 2019 Aveo on the website, after the stores close.
The rookies propose
The Lead responder drafts a reply. The Counter assistant drafts an offer: 7% below market, free freight.
The referee checks
Paola decides
The ledger records it
Waiting for Paola. Try her two buttons.
A digital twin, not a diagram
The blueprint reads the CRM, the dealer system, spreadsheets and documents through connectors, and nobody retypes it. Key results are computed on it every night. When reality moves, the twin moves, and the referee notices.
An ontology, sized for mid-size companies
Ontology platforms built this for the largest organizations, with teams of engineers over months. Kumi builds it in weeks, with the company's own people deciding each piece, and adds the judgment layer on top.
The DNA: everything and everyone, aligned
The DNA is how a company decides: the owner's vision, its principles, the unwritten rules, and the tensions between them. Kumi draws it as strands, from the vision down to the people and agents who act. Anyone can see whether everything pulls the same way, and who settles it when it doesn't.
Four strands, five tensions. Select a strand to read its three truths, then see it after the DNA sessions.
It holds because the strands are live. A new document, a rule changed by message, a practice that drifts: each shows up on its strand and goes to the person who settles it. The overruled version is retired, and the ledger keeps why.
A framework, a process and a platform
Three layers that only work together. The framework is the same for every company. The process is how one company lives it, season after season. The platform is the AgenticOS, delivered as a service, that runs it every day.
The framework
the same for every company- Principles
- People decide what agents may never decide. Autonomy is earned per action, on evidence. The three truths meet on one screen. Every change is a version someone approves. Nothing crosses clubs.
- Roles
- The coach · the directors · the key users · the scouting pair (a forward-deployed engineer and the Scout, an agent) · the squad
- The career
- Recruit → rookie → starter → veteran, promoted on evidence and demoted any day
- Mandate
- Per action: watch, ask or act
The process
one company's journey, with loops- Bootcamp
- Kickoff, discover, model, the key users accept, version 1, recruit
- Pre-season
- Four sprints in shadow, the first one blind; a weekly review per action; the close
- Season
- A quarter of goals in weekly sprints; one brief a day per person; plays changed when they miss
- Retro
- The season graded; plays rewritten; promotions; the next version
The AgenticOS
the platform, delivered as a serviceWhat it is not
A copilot makes one person faster and leaves the work with them. In Kumi agents do the work, and people decide.
The company owns its agents, its data and its rules. A forward-deployed pair helps at the start, until the company runs Kumi alone.
Dashboards tell you what happened. The AgenticOS shows it as it happens, and lets you change the play.
From the first meeting to a season at work
Eight steps, in the order a club lives them. Step through them and watch the blueprint grow. The dates are the demo club's: about six weeks from the kickoff to the first actions agents take on their own.
Point at a shape to read it.
Walk it yourself. The bootcamp prototype plays the whole journey with the demo club, from the kickoff to the retro, one screen at a time.
Open the bootcamp prototypeThe AgenticOS, live: a day at work
Once the season starts, Kumi runs with the company's day. Each person meets it where they already work, and every number on the screen comes from the company's own systems.
Where people meet Kumi
The team app proposed
Everyone, on their phone
Two modes. The Huddle: talk or type with Kumi, your team and its agents, in channels and threads, and decide in one tap. Blueprint: your scorecard, your playbook and every call the referee made for you. It opens from Teams or Slack, or in a browser tab; installing it is optional.
Mission Control
The coach and the directors
The day as it happens: every case, what waits for people, the goals with their forecast, what the watch found. The scoreboard, the referee's calls, the reports, the tasks, the replay, and the Huddle, with the same channels and threads as the team app.
The back office proposed
Each club's admins
Setting up the club: its companies, sites, areas and people, who may see what, and the systems Kumi connects to.
The team's channels proposed
Everyone, where they already talk
Microsoft Teams and Slack first: the brief, a decision or a nudge arrives in the channel, and a tap opens the card in the team app. People sign in with the company's own account. WhatsApp and email later.
08:30 · your brief
2 decisions wait for you. 6 leads were answered overnight, within your limits.
A decision
Counter · 2021 Hilux
The buyer asks 9% off. The counter assistant proposes 7%, within your floor of 8%.
What you can do
Watch the day live
Every case as it happens, from the company's own systems: where it happened, how fast Kumi heard of it, and a link to the record. Goals show their forecast and their chance, and the watch raises what drifts.
Replay any moment, review any call
Play back a day or a week on the blueprint and watch each case travel. Open any referee call: what happened, why it was decided check by check, and whether it was right. A wrong call becomes a change to a rule, a play or a mandate.
Ask the Scorekeeper
A specialist agent keeps the score. Ask in plain words and get the story, a chart and the numbers, with the cases they count. The daily and weekly reports arrive on their own; save an answer, or pin it to a live dashboard.
Give a task in plain words
“Lower the 2021 Hilux by 5% and write to the leads who asked about it.” The squad drafts a plan of the actions it may take, and the referee checks it before it starts. What no agent may do waits for a person, or for a grant for that task alone. It closes only with evidence.
See the value of the work
Hours given back, margin protected and what the squad costs, computed from the cases and marked as estimates. The return is something management watches, not a promise in a deck.
Keep the connections healthy
The kit manager watches every system Kumi hears from: how late it is, which writes wait to be confirmed, which credentials expire. When a bridge goes down, the twin knows, and so does the system's owner.
- The Scout models the company with the human scout.
- The assistant coach finds what drifts and drafts the findings.
- The Scorekeeper keeps the score: reports, dashboards, answers.
- The kit manager keeps the connections healthy.
Who does what, and when. Every role in the company, from the owner to the front desk, with what Kumi does for them in each phase.
Open Kumi at Work Open the team appWhy it will work
Kumi starts small, inside work a company already pays for, and grows only as fast as people trust it.
Who it is for
Companies with real systems and real people
Mid-size first: a CRM, an ERP or a dealer system, spreadsheets, a chat tool, and teams who know the work. The large data-platform projects are out of their reach.
The first clubs
Kumi's own development crew comes first: the platform is built by its own squad. Then a company in automotive remarketing.
It starts where work is already bought
The first positions take tasks companies already pay someone outside to do: lead response, follow-ups, collections. That is a vendor swap, not a reorganization.
Management acts in real time
Goals are computed every night and Coaching flags drift the day it starts, so the owner changes the play that week, not after the quarter.
Judgment stays human by rule
People-only decisions are rules the referee enforces on every action. Agents never hold credentials; a short-lived token is minted for each call.
Autonomy is earned per action
An agent moves from ask to act on one action at a time, when its agreement with people and its golden set clear the bar. Nobody's job changes on day one.
Legacy stays where it is
Kumi reads the systems of record through connectors and acts through agent users. No migration, and no new database to feed by hand.
It compounds
Each club's decisions, golden sets and ledger are its own data. As Bek writes, when you sell the work, every better model makes it faster and cheaper.
- How Kumi charges: the business model and pricing
- The product's final name; Kumi is the working name
- Who employs the forward-deployed engineer
- The standard length of a bootcamp
Design phase, by choice
We are designing the method and the system before writing code. Every spec, decision and screen is reviewed before it is accepted. Code starts when the design is settled.
Specs, decisions and prototypes, reviewed one by one.
Kumi's development squad is the first club, building the platform.
A club in automotive remarketing, from kickoff to season.
Position templates per industry, more channels, and apps that join through one contract.