Capital is often described as fuel.
Useful metaphor.
But fuel suggests uniform acceleration.
Companies are not uniform systems.
They are differentiated architectures made of branches: product decisions, operating assumptions, authority, people, customer commitments, distribution logic, infrastructure, capital structure.
And capital does not touch all of them equally.
It enters through specific uses:
A hiring plan.
A GTM motion.
A product expansion.
A new market.
A customer commitment.
An operating model that now has enough runway to continue.
Some branches receive almost no additional force.
Others suddenly become faster, stronger and harder to reverse.
That distinction matters.
Earlier, we used a simple relation:
Trajectory Cost = Wrong Path × Force × Time
Capital belongs inside Force.
Not because capital is good or bad.
Because capital amplifies.
It can turn a validated branch into leverage.
It can also give a provisional branch enough momentum to become structure.
The same capital can strengthen capability, increase optionality and open entirely new trajectories.
Or it can make an assumption more expensive to question later.
This is why looking at “the company” as one object is not enough.
The relevant object is the architecture capital is about to act on:
Which branches will receive force?
Which assumptions will gain resources?
Which commitments will become durable?
Which parts of the current architecture will become easier to scale — and which will become harder to unwind?
In our lab, this is the more useful question:
What becomes faster, stronger or harder to reverse once this capital enters?
Because capital does not enter a neutral system.
It enters an architecture already producing a trajectory.
And once amplification is branch-specific,
the present-state snapshot stops being the whole object.
The next question is no longer only:
What is this company today?
It is also:
What is this capital about to make more true?