Thought Leadership: “Connect, Don’t Consolidate: IT for Founder-Brand Portfolios”
A practical note on IT transformation in founder-brand portfolios
Your organization just acquired their third founder-led brand in 24 months. Each one has a different e-commerce stack, a different 3PL, a spreadsheet where the ERP should be, and a founding team that built something genuinely good, in part because no one slowed them down with IT governance. Your job now is to bring these brands real capability with shared infrastructure, data visibility, cost leverage and without turning them into a mini-enterprise. Move fast, because the synergy thesis depends on it. Stay light, because the moment you show up with a technical roadmap and a change management framework, you’ve lost the stakeholders
The biggest mistake in year one is treating this like an enterprise merger. Integration thinking says: standardize everything, move everyone to the same stack, eliminate redundancy. Connection thinking says: make the brands visible to each other, give them shared services where they want them, and leave them alone where they don’t. These are fundamentally different approaches, and confusing the two is where most portfolio IT efforts stall.
Before any IT planning conversation with a newly acquired brand, understand what the founding team is protecting. It’s almost always one of four things: speed to market, customer experience, brand identity, or founder autonomy. If your IT strategy fails to account for all four, the resistance you encounter will look like stubbornness. It isn’t. It’s a legitimate concern that your plan hasn’t been addressed.
The mental model that works best is a simple three-zone architecture. The shared foundation which includes cloud hosting, identity and access, security monitoring, SaaS contract leverage is non-negotiable and should feel invisible to brand teams. Shared services like a common ERP, a data warehouse, or shared 3PL relationships are opt-in: offer them, prove they’re better than what the brand already has, and let adoption follow. The brand-owned solutions such as ecommerce platform, CRM, customer data, marketing stack stays untouched unless you’re invited in. The hardest discipline isn’t designing this model — it’s resisting the urge to put things in the shared zone just because it’s tidier. If it creates friction for the brand team, the consolidation costs more than it saves.
Founders respond to quick wins, not big-bang transformations. The sequencing that works across 12 to 18 months follows a crawl-walk-run logic. Start by listening and audit what each brand actually has, not what the due diligence deck claimed. Map the real stack, the real pain points. Then pick one shared problem everyone has, usually financial or operations reporting, and get onto a common reporting layer fast; that’s your first visible win. From there, establish the shared foundation quietly identity management, security baseline, SaaS cost governance. Next, introduce opt-in shared services one at a time, led by whichever saves the most money or solves the sharpest pain, and let the first brand’s success sell it to the next. Finally, start building the data layer. A unified data warehouse across brands is the highest-value IT investment a portfolio can make and it enables cross-brand insight and AI use cases that no individual brand could justify alone.
If you sit inside or alongside a larger parent company, use it to unlock the value strategically. Someone there has already gone through the painful version of the problem you’re facing. Stand solutions that are pre-configured, lightly customized implementations of proven platforms and can cut a 24-month ERP rollout to under 12 months. That’s the difference between a synergy thesis that works and one that exists only in the deal model. The rule of thumb: take the outputs of the parent’s learning with the configured tools, the contract leverage, the integration patterns and more importantly leave behind the process overhead designed for a much larger, much slower organization. Every time you consider importing a parent-company practice, ask: who owns the functional capability enhancements after we implement it? If the answer is nobody closer to the brands, you’ve imported a dependency, not a capability.
The brands you’ve acquired were built by teams who solved problems with whatever was available. That scrappiness is an advantage, not a liability. IT portfolio with the goal of standardization shouldn’t replace it with process, it should equip associates with better tools so their resourcefulness scales instead of hitting a ceiling. Keep security, finance and operations enterprise-grade; keep everything else as lightweight as possible while still reliable. Know the difference before you start.
If you’re building IT across a founder-brand portfolio and have a lesson worth sharing, “good or ugly” let’s start the conversation.
Anand Radhakrishnan
Chief Information Officer, KIND
