Home/Proprietary Frameworks
Capability Compounding Curve™
Capability Compounding
Curve™.
The financial model that shows why ownership beats vendor engagement — not just in year one, but permanently. The curve that crosses at month nine and widens every quarter after.
What the Curve Shows
Ownership crosses the line
at month nine.
In the first six months, the GCC model costs roughly the same as a vendor engagement of the same size — when you include setup, management fee, and salaries. By month nine, the owned model’s value-per-dollar begins to exceed the vendor model. By month 24, the gap is permanent and widening.
The Capability Compounding Curve™ is the financial model that makes this visible. It is not a theoretical argument for ownership — it is a quantified illustration of three compounding mechanisms that vendor engagements structurally cannot replicate.
Mechanism 1 — Knowledge compounds
Every sprint adds to the team’s institutional knowledge of your domain, your codebase, and your priorities. Sprint velocity at month 12 is materially higher than month 1 — with the same team, the same cost, and increasing output. A vendor team resets every time the engagement renews.
Mechanism 2 — IP accumulates
Every model, dataset, evaluation framework, and documented architecture adds to your IP library. At month 24, that library has two years of proprietary capability your competitors cannot access. The vendor model produces the same IP — but it belongs to the vendor.
Mechanism 3 — Attrition cost falls
The longer your GCC team is together, the lower your attrition. Lower attrition means fewer replacement hires, less onboarding cost, and less knowledge loss. The cost per unit of output falls every quarter as the team matures.
Why the vendor model cannot compound
In a vendor engagement, the knowledge, IP, and team stability belong to the vendor. When the contract renews, you are paying for access — not accumulation. The vendor’s margin grows with your dependency. Your compounding value grows with your ownership.
The Curve in Practice
What the compounding curve
looks like for your GCC.
M1–6
Setup Phase — Costs comparable to vendor
Management fee + setup + salaries. Similar to a vendor engagement of the same size. The institution is forming. Knowledge is thin. IP library is starting.
M9
Crossover — GCC value exceeds vendor value
The team knows your domain deeply. Sprint velocity is 40–60% higher than month 1. The IP library has real value. A vendor team of the same age has turned over 15–20%.
M18
Compounding — Gap widens permanently
Two years of IP. Team that knows your codebase and priorities better than any vendor team could. Attrition stabilised. The Capability Compounding Curve has separated permanently from the vendor model line.
M36
Institutional Advantage — Irreversible
Three years of compounding. The gap between your owned GCC and a vendor engagement of the same investment is permanent. The vendor model cannot catch up because it does not accumulate.
Capability Compounding Curve™
See the compounding curve
for your specific GCC.
The Digital Twin models your compounding curve before you commit. See where the crossover happens for your mandate.