Inside MOS

Eight modules. One operating system.

What each part of MOS does — and why it's there.

My Hub

Start the day knowing what matters.

Without a front door, every employee invents their own — five tabs and a guess. My Hub is one page: what's due, what's on track, what needs attention. And it's where the operating rhythm lives. The weekly check-in takes about five minutes; multiplied across the company, it's the heartbeat that keeps everything else true.

Day at a glance: Your check-in, goals, and action items on one page. No morning tool tour.
Weekly check-in: Five minutes a week. That small rhythm is what keeps the source of truth current.
Manager dashboard: Every report's GOATs and check-in status, so status meetings stop being detective work.
Where I fit: Each person sees their place in the org and how their work ladders up.

People

Because past 150 people, nobody holds the org in their head.

When the org lives in memory, every reorg, hire, and acquisition makes the picture blurrier. People is the org, defined: every person, team, circle, and reporting line in one place. Change it once and everyone — including your AI — sees the same structure.

People and teams directories: Find anyone by name, role, team, or location — without asking around.
Org charts, two ways: How teams are structured and who reports to whom. They're not the same thing, so MOS draws both.
Circles: The cross-team groups real work actually runs through, made visible.
One directory across entities: Employees, contractors, and acquired teams in one list — not five.

Goals

A goal tracker holds goals. This holds the reasoning.

Most companies can list their goals. Few can show how Monday's work serves them. The GOAT cascade makes the connection structural: Goals break into Objectives, Objectives into Approaches, Approaches into Tactics — each level laddering up, each tactic owned by one person. Work that can't draw the line up stands out. That's the point.

The GOAT cascade: Four levels, cleanly linked. Read the strategy top-down or trace any task back up.
Status at a glance: On track, at risk, blocked, off track — visible in week three, not week twelve.
Any slice in one click: Filter the whole cascade by group, business unit, team, or person.
Roadmap and strategy views: The plan and the goals stay connected instead of drifting apart in separate decks.

Finance

Every unit should know the numbers it owns.

P&Ls usually live in finance tools most leaders never open, forwarded as spreadsheets that age in inboxes. The Finance module gives each unit its own picture — sourced from the financial system, labeled with its owner, and read-only by design. MOS doesn't replace your ERP. It makes the numbers legible to the people accountable for them.

P&L per business unit: Each leader sees the picture they own, not a forwarded spreadsheet.
Budget requests: One path to ask for money, one place to see where the ask stands.
Vendor directory: Who you pay, for what, and who owns the relationship.
Source-of-truth labels: Every page names the system the data comes from and the person who stands behind it.

Resources

The library everything else stands on.

This is the definitional core: every artifact that describes how the company runs, typed and owned. The applicability matrix turns “write it down” from a hope into a checklist — it declares which artifacts each group, unit, and team owes, so a missing charter is a visible gap, not a silent one.

Typed artifacts: Strategies, charters, GOATs, roadmaps, SOPs, budgets — each with a shape, an owner, and a verified date.
Mapped to your taxonomy: Artifacts hang off the org itself, from group level down to a single team.
Applicability matrix: Declares which artifacts each entity owes — so gaps are visible, not silent.
Shared language: Brand standards, tools, and the glossary live in the same library everything else cites.

MOS AI

Answers with receipts.

Ask about a policy, a goal, or a process and get the current answer with the source attached. The assistant can be trusted because of what it stands on: the curated library, not the whole drive. That's also why it's everywhere — trust plus reach is what makes an assistant useful.

On every page: Ask where you are. The assistant comes to the work, not the other way around.
Grounded answers: Built on artifacts with owners and verified dates — not on whatever the drive coughs up.
Pages and actions by command: One shortcut finds any page or action. Type what you want to do, not where it's buried.

Integrations

MOS doesn't want your stack's job.

The fastest way to ruin a source of truth is to make it compete with the tools that hold live state. So MOS links instead: tasks stay in your project tool, connected to the goals they serve; quick links jump from the Hub to where the work happens; MCP exposes the same truth to every agent you run.

Linked, not duplicated: Tasks and projects connect to the goals they serve. The work stays where it happens.
Quick links from the Hub: Jump straight to the tools that hold live state.
MCP-native: Any agent in your stack can ground on the same curated truth.

Admin & governance

A source of truth needs a spine.

Trust is a governance outcome. Admin is where it's enforced: roles and permissions decide who sees what; usage analytics show what's actually read; rollout brings teams on in stages; the changelog writes the system's own history down. Boring on purpose — this is the part that keeps everything else true.

Roles and permissions: People and agents see exactly what they're entitled to — no more, no less.
Usage analytics: Know what's read, what's ignored, and where adoption needs help.
Staged rollout: Bring the company on team by team, not big-bang.
Changelog: The system's own history, written down — it practices what it preaches.

See the modules on your own company.

Book a demo