Ask Skip: What Happens When Your Streaming Vendor Gets Bought?

We rely on several companies for delivery, monetization, and day-to-day operations. When one gets acquired, what should we reevaluate before signing the next contract?

— VP, Audience Experience

An acquisition is a good time to revisit a vendor relationship that’s probably become more important, and more expensive to change, since the original contract was signed.

Berkshire Hathaway just agreed to invest another $330 million in Bending Spoons, bringing its total commitment to $930 million. Bending Spoons owns Vimeo and Brightcove, two established video technology businesses serving customers across enterprise video, publishing, and streaming.

The company has built an acquisition strategy around buying established software businesses, improving their operations, investing in product development, and expanding profitability.

That can be a very good outcome for customers. An owner with access to capital, engineering resources, and experience improving software products can address problems that an independent company might struggle to solve.

But acquisitions also create a natural point to revisit priorities, operating models, and commercial relationships.

And when a vendor is deeply embedded in your business, those conversations deserve considerably more attention than the average software renewal.

The Cost of Switching Is Usually Higher Than Anyone Remembers

Video infrastructure gets complicated once it’s embedded in a business that’s already operating.

A company might start by selecting a video management system based on features, reliability, integrations, and price. Then the engineering team connects it to the CMS, analytics, advertising systems, and internal workflows.

Depending on the operation, there may also be integrations involving DRM, entitlements, encoding profiles, metadata, player configurations, and device applications.

Over time, the tech becomes part of how the company operates.

Replacing it means more than finding another vendor with a competitive proposal. Someone has to migrate the content, rebuild integrations, validate workflows, test playback, train users, and make sure nothing important breaks.

That’s why established B2B technology relationships tend to be durable.

The customer benefits from continuity, institutional knowledge, and a product already integrated into its operation. The supplier benefits from recurring revenue and a deeper understanding of what its customer needs.

Both sides have an incentive to keep the relationship working.

But that dependency needs to be understood when the commercial agreement comes up for renewal.

A vendor that looks 10% cheaper on paper can become considerably more expensive once engineering, migration, retraining, and operational risk enter the calculation.

Nobody wants to discover halfway through a migration that the metadata export works beautifully except for the fields that run the business.

A New Owner Can Bring Real Product Improvements

The Bending Spoons example is interesting because there’s already evidence of continued product investment following its acquisitions.

In its second-quarter results, Bending Spoons said Vimeo delivered more than 30 product improvements, reduced system stability incidents by approximately 90% compared with pre-acquisition levels, and improved upload and search performance by at least 30%.

The company also reported faster customer-support resolution times.

Brightcove introduced Gen 2 in September, bringing together improvements across video workflows, monetization, live streaming, accessibility, and AI-powered tools. The launch followed additional engineering and product development investment under Bending Spoons’ ownership.

If a new owner can improve the product, accelerate engineering work, and reduce operational complexity, customers have good reasons to welcome the investment.

There’s also a legitimate economic advantage to scale.

Software businesses carry substantial development costs. Engineering, infrastructure, security, support systems, and product management all require ongoing investment.

A larger technology owner may be able to spread certain capabilities across several businesses rather than requiring each product to fund them independently.

That can make improvements more economical and accelerate development.

Of course, the value still has to show up in the product.

An improvement to upload performance may be extremely useful for one customer, while another cares more about live reliability, advertising integrations, or content management.

The acquisition announcement starts the conversation. Product performance determines whether the investment is delivering.

The Roadmap Becomes Part of the Relationship

One of the more important things to revisit after an acquisition is the product roadmap.

Every vendor has to make choices about where to invest its engineering resources. New ownership can bring fresh priorities, additional capabilities, and a different approach to deciding which features deserve attention.

A company serving several customer segments can’t develop every feature requested by every account. Some capabilities have broad commercial value. Others solve problems for a relatively small group of customers.

Those tradeoffs are part of running a healthy software business.

The customer’s responsibility is understanding where its own requirements fit.

If a streaming service depends on a specific API, workflow, or integration, it should understand how the vendor intends to support that capability. If the vendor is introducing a new architecture or consolidating functionality, the customer needs to know how that affects its operation.

That conversation is easier when both sides are specific.

A customer saying it needs better analytics doesn’t give the product team much to work with. Explaining that a missing data field prevents accurate advertising reconciliation across three distribution partners is a different conversation.

Now there’s a business problem, an operational consequence, and something the supplier can actually prioritize.

Vendors also deserve clarity about what the customer is willing to pay for.

Advanced support, custom integrations, accelerated development, and unusual service requirements cost money. A customer expecting those capabilities should be prepared to explain their value and negotiate accordingly.

The strongest partnerships tend to work because the vendor understands the customer’s economics, and the customer understands what it takes to support the product.

An acquisition is a perfectly reasonable occasion to revisit those assumptions.

The Contract Should Reflect How Important the Technology Has Become

Here’s where I think many companies could do a better job, regardless of who owns the vendor.

Technology relationships often become more operationally important without the commercial agreement receiving the same attention.

A system that started as a relatively small component may now support subscription revenue, advertising delivery, live events, and daily publishing operations.

Yet the contract may still reflect the requirements established when the original deal was signed.

I’d want the next renewal discussion to address service levels, support responsibilities, product changes, data access, and how the parties handle future transitions.

The specific terms depend on the service being provided.

A customer running occasional corporate webinars has different needs from a streaming service delivering live sports with paid subscribers and advertising commitments.

Those differences should appear in the agreement.

A service-level commitment is useful, but the operating team needs to understand what it guarantees. Does the clock measure the initial support response or the time required to restore service? Who gets involved when a critical issue requires engineering support? How are incidents escalated?

For a live operation, those details can be considerably more important than a small difference in the annual software fee.

The vendor also needs realistic commitments around usage, volume, support requirements, and contract duration. Predictable demand helps suppliers plan capacity, invest in the product, and price the relationship appropriately.

And while acquisition agreements may change who owns the supplier, they don’t automatically change every customer contract. Change-of-control provisions, termination rights, and transition obligations depend on the agreement.

That’s worth knowing before somebody walks into the renewal meeting assuming the acquisition gives them a negotiating right they never had.

Know What It Would Take to Leave Before You Decide to Stay

I’d approach an acquisition-driven vendor review with two objectives.

First, understand how the product and service are performing today. Look at reliability, support, capabilities, pricing, and the roadmap. Give the new owner credit for improvements that are helping the business.

Second, understand the company’s alternatives.

That means documenting the integrations, identifying the operational dependencies, confirming what data can be exported, and estimating what a realistic migration would require.

For critical services, that work might include testing an alternative supplier or establishing a transition plan that could be activated if circumstances required it.

The exercise has value even when the company has every intention of staying with its existing partner.

Knowing the cost of changing providers makes it easier to evaluate pricing, service commitments, and future investment. It also prevents procurement from mistaking a lower quoted fee for a lower total operating cost.

And it gives the vendor a better understanding of what the customer values.

A supplier that knows a customer depends heavily on live reliability can prioritize support and engineering discussions around that requirement. A customer that understands the vendor’s roadmap can make better decisions about when to adopt new capabilities and when to fund something more specialized.

Those are productive conversations to have before a renewal becomes contentious.

Bending Spoons’ continued investment in Vimeo and Brightcove provides a timely reason to examine how acquisitions can affect established technology relationships. The reported improvements at Vimeo and Brightcove’s Gen 2 launch are concrete developments worth evaluating on their merits.

I’d judge the relationship by the product, the support, the roadmap, and the economics.

If those are improving, the case for continuing with the supplier gets stronger. If requirements have changed or important gaps remain, the renewal is an opportunity to address them while both sides still have time to make sensible decisions.

The best vendor negotiations usually happen when both companies understand the cost of the relationship, the value they’re getting, and what they need from each other next.

That’s a much better basis for a long-term partnership than discovering how expensive it would be to change vendors after somebody has already decided the contract isn’t working.

Ask Me Anything

Whether you’re fed up, fired up, or just want the truth behind the trends, send me your questions using this form. Anonymity guaranteed. Bullshit not included.