The OpX platform

The work. The people. The model that connects them.

Your systems hold the records. OpX connects them to the service requirements, capacity assumptions, and approval rules behind each decision.

Explore the platform View applications
OpX / One operating foundationArchitecture overview
01 / Connected evidence
Customer commitments

Accounts · renewals · projects

People & roles

Ownership · availability · skills

Source records

Approved inputs · provenance

02 / Approved model
Operating modelVersioned
Demand
Service requirements
Supply
Capacity & ramp
Allocation
Fit & priorities
Authority
Named approvers
03 / Reviewable response
Evaluate the situation

Findings, responses, or an explicit hold

Review & authorize

Approval remains with your team

Operating memoryEvidence · model versions · decisions · observationsA record for the next decision
Source evidence + an approved operating model. A finding, a reviewable response, or an explicit hold. Each decision adds to the operating record.

01 · Operating graph

Different systems. Shared operating meaning.

Authenticated file transfer brings evidence into OpX. Approved source records connect customers, stakeholders, and accountable team members. Execution remains with authorized people and configured systems.

  • IdentityThe same customer and person across systems
  • Account teamCommercial, delivery, and success ownership
  • RelationshipsWho owns, supports, sponsors, and operates the account
OpX / Operating graph Architectural explanation
Account team
Maya Chen

Account executive

Jordan Lee

Customer success

Priya Shah

Delivery lead

Customer stakeholders
Avery Brooks

Executive sponsor

Sam Ortiz

Operational owner

Resolved across source systemsOne customer. Five current relationships.

Commercial, delivery, and success ownership stay attached to the same Acme account and customer stakeholders.

Relationship data

Identities and ownership are resolved from approved customer and people records.

Current operating stateOperating model

02 · Operating model

Make the operating assumptions explicit.

The active model makes policy, authority, thresholds, and ratios explicit before any situation is evaluated.

OpX / Operating modelArchitectural explanation
Current evidence

Operating reality

RenewalDay 43
7-day gap
Go-liveDay 50
Modeled workload80% of capacity

Updates as eligible source facts change.

Approved model

Operating intent

Policy
Go-live before renewal
Authority
Senior approval before outreach
Threshold
Overload above 100% capacity
Ratio
12 hours per account ÷ 120 effective hours

Versioned and approved by accountable operators.

What the comparison revealsDelivery lands 7 days after renewal.

Capacity is available. The timing conflict needs review.

Approval required

You do not implement a digital operating model as a transformation project. You accumulate it one governed decision at a time.

Current state + approved intentDecision runtime

03 · Decision runtime

Evaluate the situation. Keep the boundary intact.

The runtime applies approved operating intent to the current evidence and reassesses whenever the situation changes.

An assessment can support action. It does not grant authority.

OpX / Decision runtimeImplemented behavior
Evaluate together
7-day delivery gap

Go-live follows renewal

80% workload

Capacity available for review

Policy not met

Go-live should precede renewal

Assessment
Intervention warranted

Prepare a recovery review

Approval still required

Before customer outreach

Evaluation

Current evidence is evaluated under the active model. The authority boundary remains separate.

Runtime / Configurable patterns

Define what needs attention.

Choose the scope, conditions, and severity. Test a draft against your data before activation.

Account riskExample configuration
Accounts

High-value account, low health

Where
Account ARRis above$100,000
And
Health scoreis below40
When both conditions matchFlag churn risk for review
Critical
Available fields follow your data policies.
Bounded assessmentGoverned work

04 · Governed work

One situation. The right response.

From a shared situation to the right person, AI assistant, or workflow.

01 Connected data

Renewal
Day 43 CRM
Project delayed
Day 50 PSA · Go-live

02 Operating model

Renewal readiness
Go-liveRenewalDelivery before renewal
Approved model

03 Configurable runtime

Renewal delivery risk
Renewal within45 days
ProjectDelayed
7-day delivery gap

04 Routed response

Person
Alert the PS leader
AI assistant
Draft renewal prep
Workflow
Schedule recovery meeting
Senior approval required

Before customer outreach. Execution stays with your team.

Example routing

AI and workflow routing depend on configured integrations and permissions.

Decision + response + resultOperating memory

05 · Operating memory

The next decision should not start over.

Patterns, decisions, and observations become a connected record. Each new situation begins with the context of what came before.

PatternDelivery risk recognizedRenewal timing + project readiness
DecisionOwner reassignedWho decided, and why
DecisionReview closedRationale retained with the evidence
ObservationStable coverage observedLater outcomes kept distinct
Individual decisions. Accumulating context.

Evidence stays attached. Decisions stay reviewable. Outcomes stay distinct.

Product & evidence boundaries

The complete system

Evidence enters. A governed decision remains.

Each stage adds one necessary part of the operating record without collapsing evidence, judgment, authority, action, and outcomes into the same claim.

  1. InputsConnected evidence

    Current source facts become a shared operating state.

  2. EvaluationApproved intent

    Policies, ratios, and thresholds make judgment explicit.

  3. AuthorityBoundary retained

    An assessment can recommend action without granting permission.

  4. OutputGoverned work

    What, why, who, and when travel with the evidence.

  5. MemoryDecision retained

    Changes, choices, and measured outcomes remain reviewable.

Start with one decision

Prove one operating loop.

Choose one consequential operating question. Connect the relevant evidence, define the approved model, and evaluate the first governed response.

01Choose the decision02Bind the evidence03Approve the model04Evaluate the loop