top of page
Search

Every Great Platform Has Had to Cut the Cord

Sep 9
5 min read

What Apple, Tesla, and Netflix can teach us about turning a vendor breakup into a stronger business — and what it means for INNOVA's own hardware changeover.


If you've read our recent client notices, you know the short version: the cloud layer connecting your INNOVA controller to the app went down because our business relationship with the outside developer who built and hosted it came to an end. What we haven't spent much time on is this: INNOVA is far from the first company this has happened to. Some of the biggest names in tech have gone through the exact same moment — and came out of it stronger, not weaker.


This isn't a new story

Depending on an outside vendor for a core piece of your product is one of the most common decisions a growing company makes. It's faster, it's cheaper up front, and it lets you focus on what you do best while someone else handles the plumbing. It works right up until the relationship ends — and then the company that was renting a critical piece of its own product has to decide what comes next.


The companies that come out ahead don't just patch the gap and move on. They use the disruption as the reason to finally own that layer outright. Three of the clearest examples of this playbook are Apple, Tesla, and Netflix — three companies operating at a completely different scale than INNOVA, but going through a structurally identical decision.


Case Study 1

Apple & Intel: Ending a 15-Year Chip Partnership

For 15 years, every Mac ran on Intel processors — a relationship that began in 2005 when Apple abandoned PowerPC chips for Intel's x86 architecture. Over time, Intel's chip roadmap increasingly became the ceiling on what a Mac could do: performance gains slowed, thermal and battery-life compromises piled up, and Apple's own chip designers — who had spent a decade building industry-leading processors for the iPhone and iPad — had already proven they could do better.


At its 2020 developer conference, Apple announced it was walking away from Intel entirely, committing to a full transition to its own custom silicon within roughly two years. The first Apple Silicon Macs, powered by the new M1 chip, shipped that November. The full lineup — including the last holdout, the Mac Pro — didn't finish the switch until 2023, about three years after the announcement.


The payoff was immediate and dramatic: reviewers and customers alike found the new chips delivered a leap in performance-per-watt that Intel's roadmap had no answer for, and Apple gained something it never had with a supplier — total control over how its hardware and software worked together.


Sources: Apple (WWDC 2020, businesswire.com); The Register; MacRumors; 9to5Mac


Case Study 2

Tesla & Mobileye: A Breakup Forced Into the Open

Tesla's early Autopilot system depended on Mobileye, an Israeli supplier whose EyeQ chip and camera software handled the computer vision behind the feature. The relationship became strained after a fatal 2016 crash involving a Model S using Autopilot. Mobileye's leadership grew concerned that Tesla was pushing the technology faster than Mobileye was comfortable with, and during a July 2016 earnings call, Mobileye's chairman confirmed the two companies would part ways once Tesla's current chip generation reached end of life.


The split played out publicly and bitterly, with each company giving a different account of who ended it and why. Whatever the full story, the outcome was the same: Tesla needed a new path forward for the technology behind its signature feature, and fast.


Tesla bridged the gap within months, shipping cars with Nvidia hardware later in 2016. But the real rebuild came three years later, in 2019, when Tesla introduced its own custom-designed "FSD Chip" — full ownership of the silicon behind its self-driving ambitions, with no outside supplier's caution or roadmap setting the pace.


Sources: Electrek; The Motley Fool; Forbes; Wikipedia (Tesla Autopilot hardware)


Case Study 3

Netflix & Third-Party CDNs: Getting Ahead of the Problem

Before it built its own infrastructure, Netflix streamed video to its customers by renting capacity from third-party content delivery networks — companies like Akamai, Limelight, and Level 3. As Netflix's streaming business exploded, that dependency became a serious liability: delivery costs climbed, Netflix had limited control over quality, and its sheer traffic volume was straining relationships between those CDNs and internet providers. A public dispute between Level 3 and Comcast over exactly this issue made the risk impossible to ignore.


Rather than wait for a forced breakup, Netflix made the call in 2011 to build its own purpose-built content delivery network. It launched publicly in 2012 under the name Open Connect — at the time carrying only around 5% of Netflix's total traffic.


That share didn't stay small for long. By 2016, Open Connect was carrying 100% of Netflix's video traffic worldwide. Today, the network embeds servers directly inside internet providers' own facilities in thousands of locations across more than 100 countries, and Netflix's traffic alone accounts for a significant share of global internet traffic during peak evening hours.


The same pattern, at INNOVA's scale

INNOVA now manages nearly a thousand connected properties, representing millions of dollars in installed lighting systems that run every night on schedules, synced to an app, dependent on a cloud layer to stay online. Until recently, that cloud layer — the piece connecting your controller to the INNOVA app — was built, owned, and hosted by an outside developer. When that business relationship ended, the connection went down.


It's the same structural moment Apple hit with Intel, Tesla hit with Mobileye, and Netflix saw coming with its CDN providers: a core piece of the product was in someone else's hands, and that arrangement had an expiration date whether anyone had planned for it or not.


Sources: TechCrunch; Netflix (about.netflix.com); Netflix Open Connect Briefing Paper


Building back better and stronger

Just like the companies above, we're not treating this as a problem to patch — we're treating it as the reason to finally own this layer outright. Here's what that looks like in practice:

  • Right now: every connected system is moving onto standardized, open-platform hardware — the same foundation across the entire network, restoring cloud access today while removing dependency on any single outside vendor.

  • Next: INNOVA's own firmware, running on hardware built to our specification — no longer someone else's roadmap deciding what our systems can do.

  • Long term: a cloud layer and app INNOVA owns end to end, the same position Apple, Tesla, and Netflix are in today — meaning faster feature rollouts, no renewed dependency risk, and a founda

  • tion that can scale to the next thousand properties instead of being capped by the last one.


The System Evolution Plan exists to fund and accelerate exactly this build. Every one of the companies in this article spent between three and five years turning a vendor breakup into full ownership of a core piece of their product. We're already underway on ours — and when it's done, INNOVA will be in a stronger, more independent position than it has ever been.





 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page