Technical Debt & ArchitectureFebruary 2, 20263 min read
Single Points of Failure: How Buyers Find Them in 48 Hours
Concentration risk is easy to detect and hard to hide. Two days of the right questions is usually enough.
Reviewers do not need to understand your product to find its dependencies. They need commit history, an access list, and thirty minutes with each engineer.
The detection method
- Map commits per file to identify sole authorship
- Compare production access lists against on-call rosters
- Ask each engineer what they would need if a specific colleague were unavailable
- Trace which vendors have no alternative and no exit plan
The same exercise run internally, a quarter earlier, produces a list you can act on rather than defend.
Working an active deal?
We respond within one business day with fit and a flat-fee scope.
Tell us about the deal