By Cristian Anastasiu, Excendio Advisors
What if the smartest person in the room for your next acquisition wasn’t your CFO or your investment banker – but your customer?
That’s exactly what happened at Cisco, and it set the template for one of the most celebrated M&A track records in tech history. What began as a single, almost reluctant deal in 1993 grew into a repeatable playbook that Cisco has now run more than 220 times. But the origin story is the part most people skip past, and it’s the part with the real lesson in it.
A Nine-Year-Old Company That Had Never Bought Anything
Cisco was founded in 1984 by a small group of Stanford computer scientists who built one of the first commercially viable multi-protocol routers. By the early 1990s, the company had ridden that single product category to a dominant position in enterprise networking. Routers were the connective tissue of the internet’s early buildout – they were how a bank’s Chicago office talked to its New York office, how a university connected its labs, how a growing intranet became something bigger than a room full of cables.
For its first seven years in business, Cisco hadn’t acquired a single company. It didn’t need to. Routers alone were still generating explosive growth, and the “build it ourselves” instinct was deeply embedded in Cisco’s engineering-first culture.
But by the early 1990s, a new class of hardware was creeping into the conversation: LAN switches. Where routers were general-purpose devices that could handle almost any networking task, switches were narrower and cheaper – built specifically to move data quickly within a local network, without the overhead routers carried. For companies with large, fast-growing local networks, switches were starting to look like the more efficient tool for a big piece of the job.
Inside Cisco, this was not a popular idea. Many engineers and executives believed switches were a passing trend – that a sufficiently capable router could do everything a switch could do, and that building or buying switching technology would just dilute focus. It’s a familiar pattern in tech, “not invented here!”: the incumbent, having won with one architecture, is often the last to admit a cheaper, narrower architecture might be eating its lunch from below.
Boeing Forces the Issue
The debate might have continued running in circles inside Cisco’s offices indefinitely. Instead, it was settled by a customer.
In 1993, Cisco was negotiating a multi-million router deal with Boeing. Boeing was in the middle of a major network expansion, and its networking needs weren’t limited to routers – it also needed LAN switches, and a lot of them. But Boeing wasn’t interested in juggling two vendors, two support contracts, and two sets of integration headaches. It wanted one relationship to manage, one vendor accountable for the whole network.
Boeing made its position unambiguous: there would be no purchase order unless Cisco will offer switches in addition to routers. In other words, Boeing wasn’t just expressing a preference – it was holding a real, sizable order hostage to Cisco’s willingness to fill the gap in its product line.
This is worth sitting with for a moment. Cisco’s own internal experts were still debating whether switches even mattered. Its biggest customer had already answered the question with its checkbook.
Cisco Didn’t Argue With the Market
To Cisco’s credit, it didn’t try to win the argument. It didn’t send an engineering team to convince Boeing that routers alone could do the job. It didn’t propose a phased in-house development effort that would “eventually” close the gap. Both of those responses are the default instinct for organizations that have built their identity around a single technology – and both would likely have cost Cisco the account, and possibly the market transition altogether.
Instead, Cisco moved. It approached Crescendo Communications, whose switches were Boeing’s favorites, offering to acquire the company. And the two companies moved quickly toward a deal. Cisco and Crescendo signed a definitive agreement on September 20, 1993.
It was the first acquisition in Cisco’s history. The company that had spent its first seven years building everything in-house had just decided, in a matter of weeks, that the fastest way to solve a customer’s problem was to buy the solution rather than build it.
John Chambers would later summarize the philosophy that guided the decision: “At Cisco, when it comes to technology, we have no religion.” It’s a deceptively simple line, but it captures something most technology companies struggle with – the willingness to treat your own product roadmap as a means to an end, not an end in itself.
Why the Deal Actually Worked
Plenty of acquisitions are made for defensible strategic reasons and still fail in execution. Crescendo didn’t. Several factors lined up in Cisco’s favor.
The products fit together cleanly. Routers and switches weren’t competing technologies so much as complementary layers of the same network – Crescendo’s switching gear filled a real technical gap rather than duplicating something Cisco already had. That made the “why” of the deal easy to explain internally and externally.
The cultures matched. Crescendo, like Cisco, was a fast-moving, engineering-driven Silicon Valley company obsessed with customer needs. Integrating two organizations with similar instincts about speed, ownership, and customer focus is a fundamentally easier problem than integrating two organizations with different values – and it’s a mismatch that kills far more acquisitions than any spreadsheet ever will.
Cisco protected what it bought. Rather than absorbing Crescendo into an existing division and diluting its identity, Cisco ran it as a standalone business unit and kept its leadership team in place, with real authority. That decision mattered enormously. Several of the people who came over from Crescendo – including founder Mario Mazzola – went on to become central figures in Cisco’s growth over the following two decades, helping engineer a string of subsequent acquisitions and product lines rather than leaving once their earnout vested, which is the more common outcome in tech M&A.
The results were hard to argue with. Crescendo’s revenue scaled from $10 million to $500 million in just eighteen months under Cisco’s ownership – a fiftyfold increase that turned a niche switching vendor into a core pillar of Cisco’s enterprise business. The deal helped cement Cisco’s dominance just as the switch-versus-router debate was being settled definitively in the market’s favor, and it became, quite literally, deal number one in what is now a portfolio of more than 220 acquisitions.
A Pattern, Not a One-Off
What makes the Crescendo deal worth studying isn’t just that it worked – it’s that it became a repeatable formula. Cisco’s subsequent acquisition strategy, refined over three decades, has consistently leaned on the same underlying logic: identify a market transition (often flagged by customers before it shows up in competitive analysis), move quickly to acquire the team that already has the technology, and preserve that team’s autonomy rather than forcing an awkward merger into an existing org chart. Cisco later formalized this into its “build, buy, partner” framework, sorting acquisitions into categories like market acceleration and new market entry – but the underlying instinct traces directly back to the lesson Boeing taught the company in 1993.
A small footnote adds a nice bit of symmetry to the story: years after leaving Cisco, John Chambers and several Crescendo alumni went on to co-found Pensando Systems, a networking startup later acquired by AMD. Strong teams, once they’ve found a rhythm together, tend to keep finding each other – a reminder that the value Cisco captured in 1993 wasn’t just a product line, it was a group of people who kept compounding that value for decades afterward.
The Lesson for Your Next Deal
M&A strategy is, understandably, driven by financial models, competitive analysis, and boardroom conviction. All of that matters, and none of it should be skipped. But Cisco’s first acquisition is a reminder that customers often have a clearer view of market gaps than anyone sitting inside the building – because they’re the ones living with those gaps every single day, in ways that don’t always show up cleanly in a market-sizing deck.
Boeing didn’t care about Cisco’s internal debate over whether switches were “really” necessary. It cared about running its network efficiently, and it told Cisco exactly what that required. Cisco’s real skill wasn’t predicting the market transition on its own – it was listening when a customer told it the transition had already happened, and then acting on that information in weeks rather than quarters.
For anyone on the buy side or the sell side of a transaction, that’s a cheap and underused diagnostic tool: before you finalize your thesis, ask your best customers what they actually need – not what they say they like, but what would make them consolidate their spend with you. The answer might be more valuable than anything your advisors produce, and unlike most market research, it comes with a purchase order attached.