Standardizing Feature Flags Across a PE Portfolio's Portcos

When a platform company acquires a bolt-on, the fastest way to get visibility into the new company's release practices is to already have a standard the deal team recognizes: what a flag audit log looks like, how rollout approvals work, what the reporting up to the deal team should show. Picking one platform, LaunchDarkly or Split, at the platform-company level and requiring new acquisitions to migrate onto it within a set window turns a due-diligence unknown into a known integration task.

A deal team doesn't need visibility into individual flags; it needs confidence that engineering changes across the portfolio follow a consistent, auditable process. LaunchDarkly's audit log, rolled up across portcos on a shared account structure, gives an operating partner a simple way to confirm that standard is actually being followed, rather than taking each portco's word for it.

A portco that's genuinely SaaS-native, running experiments and staged rollouts constantly, may get real value from Split's metric-linked model that a portco running a smaller internal tool won't. Set the platform standard at the fund level, but let each portco's CTO decide how deeply to use its experimentation features based on their own product's needs, rather than mandating identical usage everywhere.

A bolt-on acquisition already running its own flag tooling, or none at all, shouldn't be forced onto the fund standard mid-release-cycle. Give the acquired team a defined migration window, typically one to two quarters, and treat the migration itself as a project with an owner, not an assumption that it'll happen organically once the deal closes.

A migration plan for a newly acquired company:

1. Don't force the acquired team onto the fund standard in the middle of a release cycle.
2. Give the team a defined migration window, typically one to two quarters.
3. Name an owner for the migration and treat it as a project rather than an assumption.
4. Standardize the platform and reporting structure, but let each portco keep its own targeting rules, flag naming and rollout cadence.

A roll-up combining two companies, one on LaunchDarkly and one on Split, faces a real migration decision that has nothing to do with which platform is better and everything to do with which team's existing flags and history are more valuable to preserve. Pick the platform with the larger active flag inventory or the more critical production dependencies as the target, and migrate the smaller team onto it rather than picking a fresh third option.

A buyer evaluating an acquisition during a future sale process will look at engineering process maturity as part of technical diligence, and a portfolio-wide flag platform standard with a clean audit trail is a concrete, demonstrable answer to a diligence question that otherwise gets a vague one. Treat this standardization as part of building toward a clean exit, not just an integration convenience for the current hold period.

Standardizing on one platform across several portfolio companies costs more in aggregate license fees than letting each portco pick independently, but it's usually a small line item against the integration time it saves, and integration time is what actually determines how quickly a bolt-on starts contributing to the platform company's numbers. Weigh the license cost against a realistic estimate of engineering hours saved during the next several integrations, not just the current one.

A useful early question for a newly acquired portco's CTO is simple: show me the last production change you rolled back, and how. The answer reveals more about actual engineering discipline than a description of tools used, since a team with a real rollback story to tell is usually further along than one that has to think hard to come up with an example. That conversation is worth having during the first week after close, not months in, since a CTO who hears about the standard secondhand from a peer at another portco tends to trust it less than one who heard it directly from the deal team.