Constraint Migration
A Startup Reality Check Framework V1
Constraint Migration
A Startup Reality Check Framework V1
This is a living framework (updated as new cases emerge)
By Favour Akintoye
Most founders interpret a new crisis as evidence that something went wrong.
Constraint Migration proves the opposite.
A new crisis is evidence that something worked.
You solved the previous problem.
Now you are inside the next one.
And the next one is always harder than what you just survived.
1. The Core Principle
Every growth surface has one dominant constraint.
Not every problem. Not every challenge.
One bottleneck, the single pressure point determining how fast the system moves, how much it scales, and how long it survives.
When that constraint is solved, the system does not become unconstrained.
The dominant pressure shifts.
It migrates to a harder, less visible position, often hidden precisely because the previous solution looked like success.
This is the blind spot most analysis misses.
Not because it lacks intelligence.
But because winning creates the blind spot.
2. The Intellectual Lineage
Eliyahu Goldratt’s Theory of Constraints established the base: systems have one dominant bottleneck, and solving it reveals the next.
Constraint Migration builds on that foundation but changes the lens in two ways.
Goldratt is prescriptive.
A tool for operators managing systems they control, find the bottleneck, exploit it, subordinate everything else to it, repeat.
Constraint Migration is diagnostic.
A tool for reading systems from the outside, identifying where pressure concentrates, where it will migrate next, and what that shift means for strategy and capital allocation.
It's observes that solving a founding constraint doesn't eliminate constraint, it relocates it to a harder position. And that relocation is often invisible until the company is already inside it.
The second distinction matters more.
After a constraint is solved, organizations do not update cleanly.
The migration happens in the blind spot created by the solution itself.
Teams, budgets, and mental models remain anchored to the previous problem.
The system moves forward.
The organization stays behind.
That gap between where pressure actually lives and where the organization believes it lives is where most scaling failures originate.
Goldratt describes the mechanism.
Constraint Migration describes the wreckage it leaves when the mechanism runs unseen.
3. A Note on How to Read the Phases
These are not stages.
They are pressure types.
Companies do not move through them cleanly.
They accumulate them.
A company can be in Phase 1 in a new market, Phase 3 in a core market, and Phase 4 where regulation begins to react.
What matters is not sequence.
It is dominance.
Which pressure is controlling outcomes right now.
And whether the organization is responding to that pressure or the one it already solved.
4. The Four Pressure Types
Phase 1: The Adoption Constraint
Does anyone actually want this?
This is the founding pressure.
Everything early-stage organizes around it, product iteration, pricing, distribution, onboarding.
The adoption constraint is not about preference.
It is about substitution.
Can this product replace the existing behavior at scale.
In mobile money, it meant breaking telco lock-in.
In logistics, it meant proving physical delivery could be restructured.
In lending, it meant building trust where institutions had failed.
When adoption is solved, users arrive.
The constraint does not disappear.
It relocates.
Phase 2: The Infrastructure Constraint
Can the system carry what was unlocked?
Once adoption is solved, pressure shifts from demand to delivery.
The company is no longer fighting for users.
It is fighting to serve them reliably at scale.
This is where infrastructure becomes the constraint.
Agent networks.
Logistics systems.
Uptime reliability.
Fraud systems.
Compliance layers.
In physical systems, distribution dominates.
In digital systems, architecture dominates.
This phase is slow.
Capital-heavy.
Operationally rigid.
But solvable.
And once stabilized, pressure moves again.
Phase 3: The Unit Economics Constraint
Why does scale not produce margin?
This is where most companies break.
Not because they lack demand.
Because the cost structure stops cooperating with the model.
By this stage, adoption is solved.
Infrastructure exists.
Volume is real.
But margins collapse under their own weight.
Agent commissions.
Fraud management.
Expansion overhead.
Compliance costs.
Working capital requirements.
All scale with usage.
None compress fast enough.
The assumption that growth improves efficiency breaks here.
It often does not.
This is where founders misapply Phase 1 thinking.
More users.
Lower prices.
Faster expansion.
Each move deepens the constraint.
This is not a demand problem.
It is a margin structure problem.
And it does not respond to volume.
Phase 4: The Regulatory and Structural Constraint
What happens when the environment reacts?
At sufficient scale, systems become visible to power.
Governments see taxable flows.
Incumbents see displacement.
Regulators see systemic risk.
The company stops operating only inside a market.
It begins negotiating with the structure of the market.
This cannot be solved operationally.
It requires political positioning.
Regulatory relationships.
Institutional alignment.
Sometimes state-backed demand that partially insulates the system from commercial gravity.
Some companies have this.
Many do not.
And the difference is structural.
5. The False Signal Problem
The most dangerous moment is not when the constraint arrives.
It is when something that resembles it arrives first.
Friction is not the constraint.
It is the symptom.
Agent dissatisfaction is not the constraint.
It signals margin structure pressure.
Churn is not the constraint.
It signals pricing misalignment.
Regulatory pushback is not the constraint.
It signals lack of structural positioning.
Solving symptoms consumes resources.
Without moving the system.
The diagnostic question is simple.
What remains broken if this friction disappears?
That is the constraint.
6. Why Organizations Miss Migration
Organizations do not miss constraints.
They miss movement.
Teams do not dissolve after solving a problem.
They persist.
Marketing keeps optimizing acquisition after acquisition stops being the constraint.
Operations keep scaling infrastructure after infrastructure stops being the constraint.
Product keeps improving UX after UX stops being the constraint.
Each function is correct.
Each function is outdated.
The system moved.
The organization did not.
This is not a strategy failure.
It is an adaptation lag.
7. The Migration Diagnostic
Three questions.
Repeated constantly.
Where is friction actually appearing?
Not dashboards.
Field signals.
Agents.
Operators.
Customers.
Frontline systems always see migration first.
Where is the bottleneck actually located?
Symptoms are not constraints.
Low margins are not the constraint.
The constraint is the absence of a high-margin layer that subsidizes the system.
What are we still optimizing that no longer matters?
This is the hardest question.
It exposes inertia.
It reveals whether capital is aligned with the current constraint or the previous one.
If it is the previous one, the organization is already behind migration.
8. The Framework Across Sectors
Constraint Migration is not sector-specific.
It is structural.
Logistics systems:
Phase 1 is proving physical feasibility.
Phase 2 is utilization.
Phase 3 is unit economics under fixed infrastructure.
Phase 4 is regulatory exposure at scale.
Healthcare systems:
Phase 1 is adoption into clinical workflows.
Phase 2 is reliability under stress.
Phase 3 is integration cost with legacy systems.
Phase 4 is institutional regulation and funding alignment.
Consumer financial systems:
Phase 1 is trust.
Phase 2 is distribution.
Phase 3 is margin structure.
Phase 4 is regulatory positioning.
The sequence is consistent.
The environment changes.
The mechanism does not.
9. The SRC Archive as Evidence
Every company maps to this structure.
Not retrospectively.
But through observable signals of migration.
Carbon: adoption solved → default pressure emerges under macro stress → Phase 3 constraint.
Paga: infrastructure solved → super apps compress distribution advantage → Phase 3 + Phase 4 overlap.
Zipline: infrastructure solved → expansion into lower-urgency markets → unit economics pressure.
M-Pesa: full stack solved → internal flow resistance from dominance.
Wave: adoption solved → infrastructure solved → agent friction in Côte d’Ivoire → Uganda losses → regulatory pressure in Senegal.
The pattern holds.
The constraint always moves.
10. A Forward Prediction: Moniepoint
June 2026.
Moniepoint has processed ₦412 trillion.
Phase 1 solved.
Phase 2 solved.
Core Nigeria is dominant.
Credit Quality Constraint
Moniepoint sees real-time merchant cash flows.
This creates underwriting advantage.
But exposes macro vulnerability.
Inflation.
Currency shocks.
Income volatility.
As lending scales, default risk becomes the constraint.
Not visibility.
Stability.
Kenya Constraint
Moniepoint enters Kenya via Sumac.
But Kenya is structurally different.
Nigeria had fragmentation.
Kenya has M-Pesa.
Behavioral lock-in is not a gap.
It is infrastructure memory.
Phase 2 constraint reappears in a defended system.
Prediction
By 2028:
Nigeria remains profitable.
Credit faces macro-driven stress.
Kenya underperforms structurally.
Not because execution fails.
Because constraints migrated.
11. The Single Insight
Success is not constraint removal.
It is constraint elevation.
A Phase 3 company has already survived Phase 1 and Phase 2.
That is not a crisis.
It is progression.
12. Closing
Constraint Migration does not describe failure.
It describes motion.
Systems scale.
Pressure changes.
The mechanism stays constant.
And every company that survives long enough to see the next constraint has already proven something fundamental.
It worked.
Constraint Migration is an active framework in the Startup Reality Check OS.
First formally named in SRC #25: Wave — The Fintech That Broke Francophone Africa’s Money Dam… Now Carrying the Cost of Its Own Current.
Present across the SRC archive retroactively.
Framework origin: observed across 32+ published teardowns.
Framework Updates are triggered when new company outcomes contradict or refine existing phase mappings.
About Startup Reality Check
Startup Reality Check is an independent research publication studying African technology through systems thinking, market structure, execution, financial strength, and long-term durability. Each edition builds an evolving library of analytical frameworks for founders, operators, investors, and policymakers navigating emerging markets.
Including Wave, Zipline, Helium Health, Mpesa, and Carbon analyses.
Related SRC Systems
Fintech Systems
Wave:
Mpesa:
Paga:
Infrastructure Systems
Zipline:
Healthcare Systems
Rxall:
Startup Reality Check is written by Favour Akintoye.
favourt.substack.com
dave.400g@gmail.com