Key Takeaways
- Hg deploys dedicated in-house technical squads directly into portfolio companies, cutting software build timelines from 12 to 18 months down to 3 months.
- Value creation now requires portfolio companies to rebuild operations around automated models across engineering, customer support, sales, and marketing.
- Narrow vertical concentration in B2B software enables direct transfer of code patterns, architecture decisions, and commercial playbooks across portfolio assets.
- Private equity governance has shifted from tracking financial reporting to rewriting product roadmaps, defensive pricing structures, and internal tooling in boardrooms.
Shrinking Development Cycles from 18 Months to 90 Days
Traditional enterprise software product roadmaps run on long horizons. Engineering teams spec features, run QA cycles, and release updates across 12 to 18 months. In B2B software, that timeline leaves incumbents open to faster competitors.
Hg associate Katie Yuan outlines how the firm bypassed this structural bottleneck by building an internal tech incubator. Rather than issuing high-level strategic mandates from London, the firm embeds specialized software engineers directly into portfolio company engineering departments.
“Usually products might take 12 to 18 months to be launched,” Yuan explains. “With the help of those AI talent, they can ship the products out in about 3 months.”
This approach replaces the traditional external consulting model. Dropping technical operators directly into the code base allows portfolio companies to test, iterate, and release production-grade tools in one quarter instead of four.
Turning Vertical Focus into Shared Code and Strategy
Most diversified buyout funds struggle to transfer operational insights between assets. A playbook designed for a manufacturing supplier offers zero utility to a healthcare clinic network. Hg avoids this trap by maintaining a concentrated footprint within specific B2B software verticals.
As Yuan points out, domain specialization creates a compounding data and execution advantage across the portfolio:
When one portfolio asset figures out how to automate customer support workflows or restructure pricing tiers for automated features, that blueprint moves immediately to peer companies. The sponsor acts as a distribution hub for technical execution, reducing the cost of experimentation for every asset under management.
Boardrooms Move from Monitoring to Product Architecture
Private equity boards traditionally spent their hours reviewing quarterly EBITDA performance, tracking debt covenants, and approving bolt-on acquisitions. Today, the conversation in software boardrooms looks radically different.
Deal leads and operating partners now spend board sessions debating product roadmaps, gross margin implications of API compute costs, and competitive moats against new entrants. Host Liz Shu noted this shift during the conversation, pointing out the distinct seat junior and senior investors now occupy in these discussions:
Software sponsors can no longer rely purely on financial engineering or multiple arbitrage. If an enterprise software asset cannot build defenses around its data and workflow integration, its terminal multiple compresses.
Why It Matters
This operating model signals a split in how private equity firms extract value from software assets. Generalist buyout funds relying on quarterly board reviews will face severe multiple compression against specialized sponsors that deploy technical talent directly into portfolio codebases. Firms capable of cutting software delivery timelines to 90 days will protect their margins, maintain pricing power, and command premium exits.