Enterprise Services · Organizational Capacity Intelligence License
Performance infrastructure. Not another program.
The License is what comes after the Pilot. It begins by reproducing what worked through the next connected work group, then keeps the changes that improved execution from sliding back once no one is watching.
You keep tracing where important work gets stuck, change the conditions causing it, and see whether execution actually gets better. When the same conditions are also wearing down judgment, focus, or communication, that stays visible too.
Executive Summary Sustain the changes that improved execution. +
A Pilot tells you whether the approach works in your environment, and its 30-day durability check shows what begins to hold as active Pilot support decreases. The License starts with the next connected work group, tests whether the proven change travels, and then sustains what worked across the licensed scope.
What it can include:
- The Emergent Skills app and ten Professional Skills Pillars across the licensed population
- The Zones Framework as private individual language and shared work-routing logic
- Manager cohorts focused on declared capacity, observable load, and task consequence
- Privacy-protected aggregate operating-demand patterns and operating-outcome reporting
- Intervention playbooks, ongoing support, and quarterly executive reviews
The private side stays private. Managers do not see individual app use or Zone history. They act on what an employee chooses to declare, what is observable in the calendar and workload, and how complex, reversible, or consequential the work is.
Renewal has to be earned. Did approval wait fall? Did decisions move faster? Did rework come down? App engagement and employee sentiment can help explain what happened, but they are not the proof.
Current commercial structure: Foundation begins at $480 per licensed employee per year, with a 200-person and $96,000 annual minimum. Scale begins at $600 per licensed employee per year, with a 500-person and $300,000 annual minimum. Enterprise scope and pricing are customized. Final scope, inclusions, implementation timing, and commercial terms are confirmed during scoping.
Three Design Partner slots are available for 2026 for organizations prepared to test the production-scale operating model without treating projected outcomes as established results.
What The License Sustains
Fix the path. Protect the capacity. Improve execution.
Execution drag has two interacting sources: friction in the work path and reduced access to skill in the people carrying it. A queue, a broken handoff, or excess work in progress can slow execution even when capacity is intact. The same conditions can also reduce access to judgment, focus, communication, and creativity.
We do not assume every stalled priority is a capacity problem. Trace the work first. If the evidence also points to a capacity effect, the Four Tests have to support that conclusion.
The operating sequence: Find the drag. Test the capacity effect. Change the conditions. Measure the result.
The Economics Are Earned From Your Operating Results
We do not take an industry percentage, multiply it by your payroll, and call the result ROI. Your business case comes from what actually changed in your operation.
The commercial case begins with the baseline established in the Pilot. Renewal asks whether the connected intervention continues to improve or protect agreed operating outcomes after the initial test period.
The Five Capacity Taxes help us look for where the cost is landing. They overlap, so we do not add five estimates together to manufacture a bigger number. Recovery Debt is estimated only when longitudinal and turnover evidence supports it. Forfeited Upside remains separate and uses client-supplied opportunities and valuations.
The strongest business case is specific: which work-path condition changed, which operating metric moved, what value the organization assigns to that movement, and whether the change held long enough to justify continuing.
What the License Includes
Five connected components, one recurring operating discipline.
Private app and professional development
Employees get private access to the app, the Reset → Build → Thrive development arc, and ten Professional Skills Pillars. The app starts with a simple question: what capacity do I actually have right now, and what kind of work does that support?
Tools are built for the floor and scaled to the ceiling. Green uses the full version, Yellow a smaller version, Red a tiny version, and Can't-Even a five-second floor.
When capacity is low, the app supports a reset or helps route around the state. The goal is not to force Green. When usable access does not return, consequential work waits, pairs, simplifies, or moves.
When capacity is available, the app shifts to five Green deployment paths: Think Better, Communicate Better, Fix the Pattern, Create Better, and Prepare Better.
Individual app activity and Zone history remain private. No manager or employer receives a record of which intervention a person used or when it was used.
Zones as private language and shared routing logic
Green, Yellow, Red, and Can't-Even help individuals describe their own operating state. The organization can use the framework as shared routing logic without turning Zones into an employee rating system or a manager dashboard.
Managers do not assign a Zone or infer one from behavior. They use capacity an employee chooses to declare, observable load, and task consequence to decide whether work should proceed, wait, pair, simplify, or move.
Manager demand-and-consequence cohorts
Managers learn how to stop recreating the conditions the Pilot just fixed. That means fewer unnecessary escalations, clearer decision rights, more protection around consequential work, and routing the next task by its consequence and reversibility.
Managers manage demand and consequence. They do not monitor private state.
Aggregate operating-demand and outcome reporting
Reporting focuses on privacy-protected aggregate operating-demand patterns and agreed operating outcomes. Demand patterns can include queue age, work in progress, and meeting load. Operating outcomes can include approval wait, decision cycle time, reversals, rework, manager after-hours load, milestone completion, and strategic work completed.
There is no employee surveillance layer hiding behind the aggregate reporting. No individual drill-down. No individual inference. No live Zone dashboard. No use in performance evaluation. Cohort thresholds, sponsor access, source systems, and reporting rules are agreed before deployment.
Current capabilities and any planned integrations are reviewed explicitly during scoping. A feature is not represented as live until it is available in the contracted deployment.
Quarterly executive reviews and intervention support
Quarterly reviews examine what changed in the work path, what operating outcomes moved, what did not move, where the old route reappeared, which connected group should be considered next, and which condition now deserves attention. The Five Capacity Taxes help organize economic exposure, but the review begins with the primary work-path pattern rather than naming a Tax as the cause.
Intervention playbooks and ongoing support help the organization sequence, test, and sustain the next change. The License is software-enabled operating infrastructure, not a software subscription standing alone.
How Deployment Works
The License normally follows a successful Pilot and its 30-day durability check because those establish the operating baseline, test reversibility, and show what begins to hold as active Pilot support decreases.
Deployment does not begin by asking an entire licensed population to change at once. It begins with the proven Pilot route and the next connected group that shares a decision, approval, handoff, manager, or dependency with it. That group receives a local owner, the relevant intervention, and an operating metric tied to its part of the route. Broader expansion follows when the result holds.
The supporting deployment work covers the practical requirements: privacy and legal review, app access, manager cohorts, reporting rules, and what we will measure first. How much work that takes depends on your population size and security requirements.
The first reporting cycle compares the connected group's agreed operating outcome with the Pilot baseline and records whether the proven change traveled, was adapted, was bypassed, or reverted. The organization should not wait for a single blended capacity score, because the License does not claim to produce one. It tracks operating-demand patterns, measured outcomes, and supporting aggregate program signals while keeping individual app use private.
We have not yet proved the License works at production scale: sustained use, measured operating improvement, renewal, and trusted privacy over time. That is what the Design Partner deployments are for. We will measure what happens and report the result whichever way it lands.
Who The License Is For
Organizations ready to sustain proven changes across demanding knowledge work.
The broad market is any mid-to-large organization with departments whose output depends on judgment and decisions under pressure, not routine execution.
The practical starting unit is usually one department, function, or business unit where a successful Pilot has already moved an agreed operating metric and the 30-day durability check supports continuing. Inside that scope, expansion starts with the next connected work group rather than treating the whole population as one rollout. The industry matters less than the work: this fits environments where judgment, coordination, and consequential decisions drive the result, which is why it shows up across pharma, financial services, private equity, professional services, law, technology, engineering, healthcare, and clinical operations.
License Tiers
Current commercial structure is differentiated by licensed population, manager-cohort depth, reporting scope, and support. Final inclusions are confirmed during scoping and contracting.
Foundation
$480 per employee per year
Minimum population: 200 employees
Minimum annual contract: $96,000
App and ten-pillar curriculum, internal use of the Zones routing language, one manager cohort per year for up to 30 managers, standard privacy-protected aggregate reporting, quarterly executive reviews, and standard support.
Best fit: a defined knowledge-worker population expanding from a successful Pilot.
Scale
$600 per employee per year
Minimum population: 500 employees
Minimum annual contract: $300,000
Everything in Foundation, plus two manager cohorts per year for up to 60 managers, expanded reporting and intervention support, priority service, and an annual measurement refresh. A full Capacity Audit, if needed, is scoped separately.
Best fit: multiple teams or functions sustaining a shared operating discipline.
Enterprise
Custom pricing
Scope and minimum are determined during scoping
Customized population, manager cohorts, reporting architecture, intervention support, executive review cadence, implementation services, and account support, all subject to privacy and evidence guardrails.
Best fit: large organizations expanding a proven model across multiple functions or business units.
Commercial credits, multi-year pricing, implementation services, and Design Partner terms are confirmed in the written proposal. No public pricing statement overrides the executed agreement.
Who Delivers the License
A senior practitioner leads deployment and owns the operating plan, manager-cohort delivery, quarterly reviews, intervention support, and coordination of any annual measurement refresh. The named delivery model is confirmed during scoping.
During the Design Partner phase, the founder is directly involved in kickoff, methodology review, findings interpretation, and executive readouts. As the License matures, those responsibilities move into the standard delivery model.
Background. Jim Wilde brings more than four decades of enterprise systems experience, including nine years as a consultant and lead developer on mta.info, the public-facing platform for the Metropolitan Transportation Authority. The methodology is documented in CAPACITY: The Variable No One Measures.
2026 Design Partner Cohort · Three Slots
Help test the production-scale model.
The License has not yet earned production-scale outcome claims. Design Partners help test sustained use, manager adoption, privacy trust, operating results, and renewal logic in real demanding work.
- Founder involvement at named moments such as kickoff, methodology review, and executive readouts.
- Methodology adaptation within clear guardrails while the production operating model is refined.
- Case-study consideration only when measured results, client permission, and confidentiality requirements support publication.
Current Design Partner terms include 15% off the first engagement. Final commercial terms are stated in the written proposal.
Questions We Get
Do we need a successful Pilot before licensing?
Normally, yes. The Pilot establishes the baseline, changes one or two work-path conditions, introduces the manager and individual layers, and tests whether an agreed operating metric improves. Its 30-day durability check tests what begins to hold as active Pilot support decreases. The License then starts with the next connected work group before expanding the operating discipline across the licensed scope.
What is the privacy architecture?
Individual app activity and Zone history are private. Managers and sponsors do not receive live individual-state monitoring, individual intervention history, or manager drill-down. Reporting is limited to privacy-protected aggregate operating-demand patterns, agreed operating outcomes, and supporting program measures under cohort and access rules set before deployment.
Can managers see or assign employee Zones?
No. A Zone is the state already present and is identified privately by the individual. Managers use capacity the employee chooses to declare, observable workload, and task consequence. They do not infer a Zone from behavior or use Zones as employee ratings.
Can we license only part of the organization?
Yes. That is usually the safer starting shape. The licensed population can be one department, function, or business unit where the Pilot has produced credible evidence and an executive owns the operating result.
Is this primarily a software subscription?
No. The app is one component. The License connects five things: work-path redesign, manager practice, private individual support, aggregate reporting, and quarterly executive review.
What outcomes justify renewal?
Renewal should be based primarily on operating outcomes agreed before deployment, such as approval wait, decision cycle time, or rework. App use and sentiment can help explain implementation, but they are not the primary proof.
What happens if we do not renew?
Licensed app access and ongoing services end according to the agreement. The client retains its own operating data and the deliverables specified in the contract. Managers and employees retain what they learned. Continued use of branded materials, reporting components, and licensed content is governed by the executed agreement.
Sustain what the Pilot proved.
If the Pilot moved something that matters and the durability check supports continuing, bring us the result. We will identify the next connected work group, the operating metric it should carry, what population the License should cover, and what the broader system still has to prove.