The operating model behind the decision

See the work. Make the right move.

Connect customer commitments, the work they create, and the people who deliver it. OpX makes capacity and allocation decisions explainable.

Explore an example

Sales Professional Services Customer Success

OpX / Capacity & allocation Example data

Customer Success · 12-week planning window

The same account count.
A very different workload.

Team memberAccount countModeled workload
Evan Brooks390 / 300 hours
12 of 15 target
130%130%Over capacity
Leo Grant160 / 300 hours
12 of 15 target
53.3%53.3%Room to help

Account counts show both at 80%. Service and renewal effort reveal where the work is concentrated.

Renewal Recovery

One renewal touches the whole business.

See the opportunity, account team, customer relationship, delivery timing, capacity, and authority together before the team decides what to do.

Timing needs attention

Delivery lands after the renewal.

The forecast go-live is seven days late against the renewal date. The team has capacity to review a recovery plan.

Relationship
Sponsor quiet
Modeled workload
80% within capacity

Recommended next step

Prepare a delivery recovery review.

Bring the account owner and delivery lead together before the renewal to resolve the timing gap.

Account team
Maya Chen · Jordan Lee
Review owners
Account owner + delivery lead
Due before
Day 43 · Renewal
Approval requiredSenior approval before customer outreach.
Product and data boundaries
See the full Renewal Recovery example

How it works

A shared picture of the business. An explicit model for the decisions ahead.

OpX connects the facts behind a decision to the policies, thresholds, ratios, and authority that govern how your company operates.

CRM · Accounts

Ownership and renewals

Roster · People

Roles and availability

01 · Evidence

Connect the evidence.

Bring together a bounded, authorized source package with provenance intact.

Capacity modelv1
Service effort12 h / account
Effective supply120 h
Approved assumptions
02 · Operating model

Make the model explicit.

Encode the priorities, policies, thresholds, ratios, and authority you approve.

Capacity available

96 h demand / 120 h supply

Approval required

Before customer outreach

03 · Feasibility

Evaluate what is feasible.

Test the required response against team capacity, role fit, and decision authority.

Evidence changed01
Model re-evaluated02
Decision recorded03
04 · Operating memory

Keep the record.

Retain the evidence, decision, review, and outcome as a new operating state.

Why this doesn’t already exist

Your systems hold the records. Who holds the operating model?

Your CRM holds the account. Your PSA holds the project. Your HRIS holds the person. OpX connects them to answer: can the team cover next month’s work?

Read the operating philosophy
Capacity outlookNext month
Capacity gap0.7 FTE

Required work exceeds the team’s effective capacity.

Based on
CRMPSAHRISApproved model

Demand, availability, and ramp—traceable to the source.

Operating memory

Build on every decision.

Keep the evidence, the judgment, and the outcome. Give the next decision a place to start.

Explore operating memory
Patterns Decisions Outcomes
Context that accumulates.

The first engagement

One decision. A foundation to build on.

Start with a real question. Make the logic explicit. Review the next move together.

Beyond Renewal Recovery

One operating context. More decisions.

Begin with Renewal Recovery. Extend the same governed context into Sales, Professional Services, and Customer Success as the questions expand.

View application suites

Why OpX exists

Built from the work between systems.

I kept rebuilding the same operating context—in spreadsheets, capacity models, and meetings. That work needed a system of its own.

Start with one decision

Bring one renewal. Leave with a reviewable decision.

One renewal. One authorized source package. One reviewable decision.

What a first engagement includes