Three of the companies I have been part of exist because the previous one exposed a constraint it could not solve. That sequence was not planned and it was not accidental.
Build something. Discover that its value is limited by a constraint upstream or downstream of it. Build that.
Portfolios first, because software cannot fix an improvised investment layer. Risk analytics second, because a strategy a client abandons has delivered nothing. Delivery third, because most firms do not want to assemble the pieces.
A platform with nothing to deliver is a shell. Analytics with no portfolio to inform is a report. Each layer needs the one beneath it to exist before it has a job.
Every one of them was obvious only after the previous one was working. That is not vision. It is paying attention.
It is not a master plan executed over twenty years. Told afterwards it sounds like one, and that is a distortion worth resisting.
Each step was a response to a constraint that had become impossible to ignore. The coherence is real and it is retrospective.
It can become a justification for building anything adjacent. Every business has constraints in every direction, and "we discovered a problem upstream" can rationalise almost any expansion.
The discipline is asking whether the constraint is genuinely binding, or just visible.
Civly is not part of the sequence. Different customer, different domain, no shared infrastructure.
Retrofitting it into the thesis would be storytelling. It exists because the problem was worth solving, which is a sufficient reason and a different one.
When something is not working as well as it should, look at what is immediately above and below it before improving the thing itself.
The constraint is usually not where the symptom is.
Read next
The four companies →