Glossary/Foundational Concepts

Company Domain Expertise

May 27, 2026·By Jeff Moss

The first branch off Customer Domain Expertise. The expertise to design how a company has to operate to deliver its customers' outcomes, across the six customer-facing departments (Marketing, Sales, Onboarding, Customer Success, Support, Product) and the responsibilities, processes, metrics, and roles that flow through them. Captured in the Operating Model Matrix: six departments by six operating rows (customer outcomes, company metrics, responsibilities, processes, role archetypes, context methodology). Built on the 10 Foundational Libraries consumed across columns.

"How would our company have to operate to actually make those customer outcomes real? It is the question almost no team can answer cleanly."

What it is

Company Domain Expertise is the first branch off Customer Domain Expertise. The expertise to design how a company has to operate to deliver its customers' outcomes.

You cannot do Company Domain Expertise without Customer Domain Expertise as a prerequisite. The operating model is the answer to a question only the customer model can ask: given what we know about the customer, how does our company have to operate to deliver their outcomes? Almost no one publishes operating-model thinking at this depth, by design, because most companies skip the Customer Domain Expertise that makes it possible.

The Operating Model Matrix is the canonical artifact. Six customer-facing departments form the customer flywheel: Marketing leads to Sales leads to Onboarding leads to Customer Success leads to Support, with Product as the substrate that makes all of it possible. Each department gets six operating rows: customer outcomes (per use case, in the customer's KPIs), company metrics (lagging and leading), responsibilities (scale-invariant), processes (named by purpose), role archetypes, and context methodology (customer intel, company intel, cross-customer intel).

The matrix sits on top of ten Foundational Libraries consumed across columns: Outcome to Use Case, Success Patterns, Product to Outcome Map, Solution Packaging, Proof Points, Risk Patterns, ICP and Segment, Knowledge Base, Failure Mode Classification, and the 5-Component Sales-to-CS Handoff Template. Each library has a primary owner and a list of consuming departments. Defined once, consumed many times.

Three locked principles shape the matrix. Responsibilities not tasks: roles are defined by the responsibilities they own, which are scale-invariant. A 4-person company has the same responsibilities as a 400-person company, just distributed differently. The Filter Rule: every cell must trace a direct line from customer performance improvement to company performance improvement. Internal-only metrics like rep ramp, story points, or promotion rate are excluded. Responsibility-anchored process naming: processes are named by purpose, like "Surface, Measure and Prove Value," not by delivery mechanism, like "QBR Process." Names that describe purpose survive channel shifts from human to digital to AI-agent delivery.

The orchestration runs across three delivery channels: human-led, digital, and AI-agent. Every modern customer-facing motion is hybrid. The matrix is the substrate that lets a company decide which combinations of channels deliver which responsibilities to which customers.

Source: methodology-canon/methodology-reference.md > Company Domain Expertise

Key Takeaways

•Company Domain Expertise builds on Customer Domain Expertise: you cannot design how the company operates until you can articulate what the customer is trying to achieve.
•Captured in the Operating Model Matrix: 6 customer-facing departments by 6 operating rows. The 10 Foundational Libraries are the shared substrate consumed across columns.
•Three locked principles shape it: responsibilities not tasks (scale-invariant), the Filter Rule (every cell traces customer outcome to company outcome), responsibility-anchored process naming (purpose, not delivery mechanism).
•Orchestrated across three delivery channels: human-led, digital, AI-agent. Every modern customer-facing motion is hybrid.
•Almost no one publishes operating-model thinking at this depth, because most companies skip the Customer Domain Expertise that makes it possible.

The Mistake Everybody Makes

Most companies design each department's operating model in isolation. Marketing optimizes for MQLs without knowing whether those MQLs retain. Sales optimizes for bookings without knowing whether those customers can win. CS optimizes for renewal forecasts without knowing whether the customer is positioned for next-value expansion. Each function is internally coherent and externally disconnected from customer outcomes.

How to Apply

1.Start with the customer flywheel: Marketing leads to Sales leads to Onboarding leads to CS leads to Support, with Product as the substrate.
2.For each department, define the customer outcomes that department drives, per use case (not aggregate).
3.Define the company metrics that ladder up from those customer outcomes. Separate leading from lagging. Apply the Filter Rule (no internal-only metrics like rep ramp or story points).
4.Define the scale-invariant responsibilities the department owns. Name processes by purpose, not delivery mechanism.
5.Map role archetypes (generalist, specialist, leadership) that staff the processes.
6.Identify which Foundational Libraries the department contributes to and consumes from.
7.Connect the departments through the compound customer-outcome chain so signals route across the flywheel.

Examples

Two customers at a rural-physicians staffing group

I worked with a rural-physicians staffing group, not even a software company. They had been treating doctors as a resource and hospitals as the customer. We realized they actually had two customers: hospitals AND doctors. We restructured their operating model to make doctors successful (the customer they had been ignoring), and their facilities went from 70 percent staffed to 95-plus percent staffed in a year. The mechanism was Company Domain Expertise applied: redesigning how the company operated to deliver outcomes for both customer types simultaneously.

Where Used in Product

Future product surface:Layer 2 role playbook designer (post-GA): each playbook renders from the Operating Model Matrix.
Coaching:The AI coach uses the matrix to recommend cross-functional design decisions.

Jeff Moss

Founder, Expansion Playbooks. A decade studying customer retention and expansion data from 75+ recurring revenue businesses.

Back to glossary