To encourage adoption of tech benefiting multiple business units, Oshkosh's CVC arm uses a central budget to fund initial proofs of concept. This removes the "who pays?" friction, as no single department has to bear the initial cost for a company-wide benefit, with the successful unit paying later.

Related Insights

Instead of a large upfront equity investment, strategic partners can use warrants. This gives the corporation the option to earn equity later if the startup achieves specific milestones, often through their joint partnership. This approach de-risks the initial investment and directly rewards successful collaboration.

Rather than relying on formal knowledge sharing, Alphabet's X embeds central teams (like legal, finance, prototyping) that float between projects. These individuals become natural vectors, carrying insights, best practices, and innovative ideas from one project to another, fostering organic knowledge transfer.

To ensure genuine collaboration across funds, Centerbridge structures compensation so a "substantial minority" of an individual's pay comes from other areas of the firm. This economic incentive forces a firm-wide perspective and makes being "part of one team" a financial reality, not just a cultural slogan.

AI agent platforms are typically priced by usage, not seats, making initial costs low. Instead of a top-down mandate for one tool, leaders should encourage teams to expense and experiment with several options. The best solution for the team will emerge organically through use.

Oshkosh's CVC team is a hybrid, not siloed in one department. It includes members from corporate development, a venture lead in a tech hub (Bay Area), and a counterpart in an engineering business unit. This structure ensures that strategic goals, technological feasibility, and market deal flow are constantly aligned.

To avoid distracting from its core business, Bolt tests new ventures like scooters and food delivery using a standardized playbook. A small team of 5-10 people is given a modest budget and a six-month timeline to build an MVP and show traction. If successful, they get more funding; if not, the project is shut down.

Instead of large, multi-year software rollouts, organizations should break down business objectives (e.g., shifting revenue to digital) into functional needs. This enables a modular, agile approach where technology solves specific problems for individual teams, delivering benefits in weeks, not years.

To secure budget for conference attendance, frame it as a critical component of a larger, pre-approved strategic initiative. By anchoring the trip to a specific project, like evaluating conversation intelligence tools, the cost becomes a tangible research expense for de-risking a major investment, rather than a vague professional development trip.

Oshkosh's corporate development team presents venture opportunities in monthly meetings with the entire executive leadership. This process provides immediate feedback, allowing the team to quickly kill deals that lack support or identify which ones require a more robust investment thesis, saving significant diligence time.

Oshkosh evolved its corporate venture capital from focusing on financial returns to prioritizing strategic innovation. This "CVC 2.0" approach emphasizes direct partnerships and technology integration to supplement in-house R&D, making innovation the primary goal, though financial returns are still a factor.