Skip to content

Worksuite World Models

Org World Model + Customer World Model Version 1.0 | April 2026 | Internal — Confidential

Unfamiliar term? See the AWE Glossary. Source theory: From Hierarchy to Intelligence — Block (Jack Dorsey).

1. Why World Models Exist

In a traditional company, middle management is a compression layer. Managers route information, precompute decisions, and maintain alignment. They exist because humans were the only available coordination mechanism — not because hierarchy is optimal.

AWE removes most of that layer. Something has to replace the context managers used to carry, or the organization seizes up. At Worksuite, two models do that work:

  • Org World Model — how Worksuite understands itself: our operations, performance, priorities, people, and commitments.
  • Customer World Model — how Worksuite understands every customer: their workforce, their data, their contracts, their outcomes.

Jack Dorsey's framing, which we've adopted: "The world model provides the context that a manager used to provide, so ICs can make decisions about their layer without waiting to be told what to do."

The models are the reason a 50-person Worksuite can out-execute a 500-person competitor. Without them, AWE is just layoffs.

2. The Org World Model

2.1 Definition

The continuously updated, agent-accessible representation of how Worksuite runs. It is not a document. It is not a dashboard. It is the composite of every recorded artifact the company generates, indexed and queryable by every IC and every agent.

Owner (STO): CEO (Joey Boothe). The CEO's job is to ensure the Org World Model is correct, current, and leveraged to full capacity. Every other WLT member contributes the slice they own.

2.2 What's In It

Layer Examples Contributed By
Strategy Mission, Big 3 Metrics, FY26 Objectives, Initiatives, Org World Model + Org Operating Model CEO
Operations P&L, cash position, ARR, burn, forecast, pipeline COO + Finance
People Roster, roles, Player/Coach assignments, T-SEMS signals VP of People Success
Services PayOps / CompOps / Help Desk health, customer operational load Head of Services and PayOps
Delivery Active CAPs, CSBs, TSBs, BCs, PSBs; STO assignments; time-cap adherence BSAs + TSAs
Platform Architecture, capability inventory, tech debt, reliability signals TSAs
Decisions D3 records, escalations, ICE Specs, meeting decisions Every IC

If it's a recorded artifact — a Slack thread, a Granola transcript, a commit, a CAP note, a CSB doc, a Zuora export — it's raw material for the Org World Model.

2.3 What It Replaces

Old mechanism Replaced by Org World Model
Weekly status meetings Agent query: "what shipped this week, what's at risk"
Manager rollups Agent-composed view across any slice
PRDs and backlogs ICE Specs indexed against the Big 3 and Objectives
Executive briefings Real-time composed answers to any strategic question
"Who owns X?" via email STO lookup across any work product

2.4 How ICs Use It

  • BSAs pull customer-adjacent context (other customers' patterns, platform capabilities, pricing precedents) when designing a CSB.
  • TSAs pull architecture, tech debt, and in-flight TSB/PSB context before starting a new build.
  • Player/Coaches pull T-SEMS signals and delivery data for their directs.
  • WLT pulls strategic slices for decisions without asking anyone to assemble a deck.

Rule of thumb: if you're about to ask a person a question an agent could answer from the Org World Model, check the Org World Model first. If it can't answer, that's a signal — file the gap.

3. The Customer World Model

3.1 Definition

The per-customer representation of everything Worksuite knows about a single customer relationship and the workforce it runs. One model per customer.

Each customer has its own GitHub repository — that repo is the Customer World Model's home. It's where the slice lives, where it evolves, and where agents read from and write to.

Owner (STO): The BSA on the account owns the completeness and accuracy of their customer's slice. The CEO owns the Customer World Model as an org capability.

3.2 What's In It

Every Customer World Model covers the same dimensions, at whatever depth the customer's engagement supports:

  • Commercial — contract, subscription, ARR, margin, renewal state
  • Workforce — the contingent workforce the customer manages through Worksuite: headcount, tenure, classification, compliance state, payment flows
  • Operations — the operational load running the program: PayOps, CompOps, and Help Desk activity
  • Solution footprint — active CAPs, CSBs, TSBs delivered, Platform capabilities enabled
  • Relationship — stakeholders, meeting history, open threads, sentiment
  • Product signal — usage, feature adoption, engagement depth
  • Health — risk signals, renewal posture, NPS

The point is not where each signal lives today — it's that all of it resolves to a single, agent-queryable view of the customer.

3.3 The Maturity Ladder

A Customer World Model is only as valuable as its depth. There are four rungs; each unlocks something the rung below cannot do:

Rung What it answers What it enables
1. Descriptive What is true about this customer right now? Replace manual account-prep. A BSA gets the slice instead of assembling it.
2. Diagnostic Why is this happening? Root-cause conversations grounded in data, not hunches.
3. Predictive What is likely to happen next? Renewal risk, expansion signals, ops load forecasts — acted on before they fire.
4. Causal What happens if Worksuite does X? The intelligence layer composes CSBs at the moment the customer needs them.

Most Customer World Models start at Rung 1. The job — as a company, across BSAs, TSAs, and Services — is to push every model up the ladder. Rung 4 is the bar; Rung 1 is the floor.

3.4 The Compounding Loop

The Customer World Model is a compounding asset, not a static snapshot:

The better the model, the more outcomes Worksuite can deliver that others can't. The more outcomes we deliver, the deeper the customer's engagement. The deeper the engagement, the richer the signal. The richer the signal, the better the model.

That loop is the structural advantage. It's also why shortcuts hurt: every customer slice that doesn't climb the ladder is a competitor's opening later.

Tied directly to the Big 3: - ARR — causal models catch renewal risk before it fires; GDR moves. - Operating Cash Burn — patterns across models surface PSBs with evidence, not guesses. - eNPS — BSAs and TSAs stop re-assembling customer context every engagement; the model carries it.

3.5 How ICs Use It

  • BSAs live in their customers' Customer World Models. The CAP is the strategic narrative; the Customer World Model is the live state.
  • TSAs query across Customer World Models to find patterns that justify a PSB. ("Five customers have hit this same limit in the last quarter.")
  • Worksuite Services ICs use it to anticipate operational load.
  • Sales & Marketing use aggregate patterns to sharpen positioning.

4. How the Models Relate

                ┌─────────────────────────────┐
                │     Org World Model         │
                │   (how Worksuite runs)      │
                │      STO: CEO               │
                └──────────┬──────────────────┘
                           │
                   informs priorities,
                   surfaces patterns
                           │
                ┌──────────▼──────────────────┐
                │   Customer World Models     │
                │  (one per customer)         │
                │   STO per slice: BSA        │
                └─────────────────────────────┘
                           │
                   customer reality
                   feeds back up
                           │
                ┌──────────▼──────────────────┐
                │  ICE Specs · CSBs · TSBs    │
                │   (how we act on both)      │
                └─────────────────────────────┘
  • The Org World Model tells you what Worksuite can do, what it's already doing, and what it has committed to.
  • The Customer World Model tells you what a specific customer needs and how they're performing against it.
  • The ICE Framework is how a BSA or TSA composes the two into a decision: given what Worksuite is (Org) and what this customer is (Customer), what should we build?

5. The Intelligence Layer

The world models are the substrate. The intelligence layer is the set of agents that compose the models into answers, drafts, and recommendations at the point of decision — for BSAs designing CSBs, for TSAs initiating PSBs, for Player/Coaches running 1:1s, for the WLT making strategic calls.

For the Customer World Model, the intelligence layer operates inside the customer's GitHub repository. Agents read the slice, write back to it, and compose capabilities against it. That repo is the unit of leverage — not a central app, not a dashboard.

If an agent can't answer a question well, the gap is usually in the model, not the agent. Fix the model first.

6. Governance

Question Answer
Who owns the Org World Model? CEO (Joey Boothe).
Who owns a Customer World Model slice? The BSA on the account.
Who owns the Customer World Model as a capability? CEO, supported by TSAs (data/platform surfaces) and Head of Services and PayOps (operational data).
Who owns the intelligence layer (agents)? TSAs, with COO-owned People Experience providing access.
Where does a Customer World Model live? In the customer's dedicated GitHub repository. One repo per customer.
What if the model is wrong? File it the same way you'd file a bug. The Org World Model fixes itself through corrections, the same way the Platform does.

7. Relationship to AWE Design Tenets

AWE Tenet World Model Role
People First Models free humans to do the judgment work only humans can do.
Small = Speed = Competitive Advantage Models are how a small team carries the context a big team used to carry.
Lean Into What Humans Excel At Empathy, judgment, creativity stay human; context-carrying goes to the model.
No information bottlenecks The model is the anti-bottleneck. Every IC gets the same view.
Fail fast, learn fast, pivot fast Models make signal-to-insight latency approach zero.
STO everywhere STOs use models to make decisions without waiting for permission.

8. What This Is Not

  • Not a data warehouse. A warehouse is one surface among many. The model is the composite.
  • Not a single product or dashboard. The Customer World Model lives in a per-customer GitHub repository. The intelligence layer operates on that repo.
  • Not "AI will manage people." Player/Coaches manage people. The models provide the context Player/Coaches and ICs need to operate without traditional managers.
  • Not finished. The model will never be "done." It improves the same way the Platform does — continuously, in response to real use, climbing the maturity ladder over time.

9. Further Reading

Document maintained by Red. Joey owns the Org World Model; BSAs own their Customer World Model slices.