Vertical software isn’t dying, it’s focusing.
Focusing on the workflows and details that matter to companies, teams, and individuals.
Vertical software platforms sit at the equilibrium between the aggregate work to be done in an industry and the common workflows that can be productized at a sensible economic scale. They’re the common denominator. To a degree, they’re empowering but at some point, they become a limiter.
Where the inherent limitations of vertical software more or less forced everyone using the same tool to work in the same way, now every company, team, and contributor can now shape the tools around the way they want to work.
This opens up an opportunity to discover and embody competitive dynamics more than ever.
Vertical software isn’t dying, it’s focusing.
Focusing on the workflows and details that matter to companies, teams, and individuals.
Vertical software platforms sit at the equilibrium between the aggregate work to be done in an industry and the common workflows that can be productized at a sensible economic scale. They’re the common denominator. To a degree, they’re empowering but at some point, they become a limiter.
Where the inherent limitations of vertical software more or less forced everyone using the same tool to work in the same way, now every company, team, and contributor can now shape the tools around the way they want to work.
This opens up an opportunity to discover and embody competitive dynamics more than ever.
Subscribe to Occasional Observations
Subscribe to Occasional Observations
Occasional ObservationsWe don't need more founders
Building over founding
Occasional ObservationsThoughts on "How to Build a Car"
Reading through How to Build a Car, a few product-related themes flow through the entire book: • The constant search for advantages. Poring over the newly released rulebooks to find gaps & technicalities to creatively exploit. Examining other domains for cross-over insights. Every team isn’t just racing on the track, the design/engineering teams are racing each other to identify the smallest of levers before the next team. • The car is a system, not merely an object. The interconnectedness of...
Occasional ObservationsMercedes & Microsoft
"Let's put that in the parking lot"
Occasional ObservationsWe don't need more founders
Building over founding
Occasional ObservationsThoughts on "How to Build a Car"
Reading through How to Build a Car, a few product-related themes flow through the entire book: • The constant search for advantages. Poring over the newly released rulebooks to find gaps & technicalities to creatively exploit. Examining other domains for cross-over insights. Every team isn’t just racing on the track, the design/engineering teams are racing each other to identify the smallest of levers before the next team. • The car is a system, not merely an object. The interconnectedness of...
Occasional ObservationsMercedes & Microsoft
"Let's put that in the parking lot"
<100 subscribers
<100 subscribers
Support Occasional Observations
Occasional ObservationsOn the death of vertical software
Support Occasional Observations
Occasional ObservationsOn the death of vertical software
Share Dialog
Share Dialog
No comments yet