Platform Fragility Post-Organic

Before the term sheet, a CTO asked for a modularity audit. The feared rewrite turned out to be 6 seams.

Organic growth builds platforms the same way everywhere: each sprint adds the shortest path, and after 2 years the shortest paths form a knot. Nothing is wrong enough to stop for, and everything is connected enough that nobody dares touch the core.

The fragility pattern has a signature: one shared database everyone writes to, transformation logic spread across 3 layers, and a handful of tables that 40 things silently depend on.

The audit that helps is small:

1. Map what actually depends on what. Query logs and import graphs, not the architecture diagram from 2024.
2. Count the crossings. Modules that reach into each other’s internals are the seams.
3. Rank by blast radius. Usually 5 or 6 seams carry most of the fragility.

Then fix seams, one per sprint, behind interfaces. The platform keeps shipping the whole time.

Rewrites get proposed because the knot looks uniform from above. Up close it mostly isn’t.

If an investor’s tech DD started Monday, which part of your platform would you least want them to pull on?