a16z’s Brutal Lesson to Crypto Founders: Why Enterprises Don’t Buy the Best Technology?

Original Title: The best technology doesn't always win (in the enterprise)

Original Authors: Pyrs Carvolth, Christian Crowley, a16z crypto

Original Translation: Chopper, Foresight News

During the current blockchain application cycle, founders are learning an unsettling yet profound lesson: Enterprises don't buy the "best" technology; they buy the least disruptive upgrade path.

For decades, new enterprise technologies have promised an order-of-magnitude improvement over traditional infrastructure: faster settlement, lower costs, cleaner architecture. However, the reality on the ground has rarely aligned perfectly with technological advantages.

This means: if your product, though "objectively better," can't win, the gap lies not in performance but in product-market fit.

This article is written for a group of crypto-native founders who started in the public chain scene and are now painfully pivoting toward enterprise business. For many, this is a massive blind spot. Below, combining our own experiences, successful founder case studies of selling to enterprises, and real feedback from enterprise buyers, we share several key takeaways to help everyone better market to enterprises and secure deals.

What Does "Best" Really Mean

Within large enterprises, the "best technology" is the one that seamlessly integrates with existing systems, approval processes, risk models, and incentive structures.

SWIFT, slow and expensive, yet still standing. Why? Because it provides a sense of shared governance and regulatory security. COBOL is still in use because rewriting stable systems poses survival risks. Batch file transfers persist because they can create clear checkpoints and audit trails.

One potentially uncomfortable conclusion is: Enterprise blockchain adoption hurdles are not due to lack of education or vision but rather a product-design misalignment. Founders who insist on pitching the most perfect technological form will continue to face obstacles. Founders who treat enterprise constraints as design inputs rather than concessions are most likely to succeed.

So, rather than diluting the value of blockchain, the key is to help the tech team package an enterprise-friendly version, and this requires the following approaches.

Enterprise Fear of Loss Is Far Greater Than Love of Gain

Founders often make a mistake when pitching to enterprises: assuming that decision-makers are primarily driven by gains, such as better technology, faster systems, lower costs, cleaner architecture, and so on.

The reality is, the core motivation for enterprise buyers is to minimize downside risk.

Why? In large organizations, the cost of failure is asymmetric. This is completely opposite to small startup companies. Founders who haven't worked in big corporations can easily overlook this point. Missed opportunities are rarely penalized, but clear mistakes (especially those related to unfamiliar new technologies) can severely impact one's career progression, trigger audits, or even invite regulatory scrutiny.

Decision-makers almost never directly benefit from the technologies they advocate for. Even if there is strategic alignment and company-wide investment, the benefits are diffuse and indirect. On the other hand, losses are immediate and often at a personal level.

As a result, enterprise decisions are rarely driven by "what could be achieved," but more by "most likely won't fail." This is why many "better" technologies struggle to gain adoption. The barrier to implementation is usually not technological superiority, but rather: will implementing this technology make the decision-maker's job safer or riskier.

Therefore, you must rethink: who is your customer. One of the most common mistakes founders make in enterprise sales is assuming that the "most tech-savvy person" is the buyer. In reality, enterprise implementation is seldom driven by technological beliefs but more by organizational dynamics.

In large organizations, decisions are less about gains and more about risk management, cost coordination, and accountability. At an enterprise scale, most organizations will outsource part of their decision-making process to consulting firms. This is not because they lack intelligence or professional capabilities but because critical decisions need continuous validation and to stand up to scrutiny. Bringing in a well-known third party can provide external endorsement, distribute responsibility, and offer credible justification when decisions are later questioned. Most Fortune 500 companies operate this way, which is why there are huge consulting fees in their budgets every year.

In other words: the bigger the institution, the more important it is for decisions to withstand internal scrutiny afterward. As the saying goes, "No one ever got fired for hiring McKinsey."

How Enterprises Actually Make Decisions

Enterprise decision-making is similar to how many people use ChatGPT nowadays: we're not letting it make decisions for us; we're using it to test ideas, weigh pros and cons, reduce uncertainty, and always hold ourselves accountable.

The behavior of enterprises is broadly similar; it's just that their decision-making layer is human, not a large model.

New decisions must pass through various checkpoints such as legal, compliance, risk, procurement, security, executive oversight, and more. Each layer is concerned with different issues, such as:

· What could go wrong?

· Who is accountable if something goes wrong?

· How does this fit into the existing system?

· How do I explain this decision to executives, regulators, or the board?

Therefore, for truly meaningful innovation projects, the "customer" is almost never a single buyer. The so-called "buyer" is actually a coalition of stakeholders, many of whom are more concerned about not making a mistake rather than innovation.

Many technically superior products often lose out here: It's not that they are unusable, but rather that there are no suitable people in the organization who can safely use them.

Take an online gambling platform, for example. As prediction markets become popular, a crypto "liquidity provider" (such as a fiat on-ramp service) may see the online sports betting platform as a natural enterprise customer. However, to do so, you must first understand: the regulatory framework for online sports betting is different from prediction markets, including separate licenses for each state. Knowing that each state has a different attitude towards crypto regulation, the on-ramp service will understand: its customer is not looking to access crypto liquidity products, engineering, or business teams, but rather the legal, compliance, financial teams who are concerned about the risks to existing gambling licenses and core fiat business.

The simplest solution is to clearly identify decision-makers early on. Do not hesitate to ask your product champions (people who love your product) how you can help them sell internally. Behind the scenes are often legal, compliance, risk, finance, security... they all have undisclosed veto power and very different concerns. Winning teams will package the product as a risk-controlled decision, providing stakeholders with ready-made answers and a clear benefit/risk framework. Just by asking, you can find out who to tailor your pitch to and then find a seemingly safe but reassuring path to "consensus."

Consulting Firms

Many times, new technology reaches the enterprise buyer through an intermediary. Consulting firms, system integrators, auditors, and other third parties often play a key role in the transformation and legitimization of new technology. Whether you like it or not, they have become the gatekeepers of new technology. They use mature, familiar frameworks and collaboration models to translate new solutions into familiar concepts and turn uncertainty into practical recommendations.

Founders often feel frustrated or skeptical about this, believing that consulting firms slow down progress, add unnecessary processes, and become additional stakeholders influencing final decisions. And they do! But founders must be realistic: In the U.S. alone, the management consulting services market is expected to exceed $130 billion by 2026, with much of it coming from large enterprises seeking help in strategy, risk, and transformation. Although blockchain-related business accounts for only a small portion, don't think that just adding "blockchain" to a project will allow you to bypass this decision-making system.

Whether you like it or not, this paradigm has been influencing corporate decision-making for decades. Even if you are selling a blockchain solution, this logic will not disappear. Our experience interacting with Fortune 500 companies, large banks, and asset management institutions has repeatedly shown that ignoring this layer could lead to a strategic mistake.

The collaboration between Deloitte and Digital Asset is a prime example: by partnering with consulting firms like Deloitte, Digital Asset's blockchain infrastructure is repackaged into a language more familiar to enterprises, such as governance, risk, and compliance. For institutional buyers, the participation of trusted parties like Deloitte validates the technology, making the implementation path clearer and more robust.

Avoid Using the Same Script

Because corporate decision-makers are highly sensitive to their own needs (especially downside risk), you must tailor your presentations: Do not use the same corporate sales pitch, the same PowerPoint deck, or the same framework for every potential customer.

Details matter. Two large banks may seem similar on the surface, but their systems, constraints, and internal priorities could be vastly different. Something that resonates with one may be entirely ineffective with another.

A one-size-fits-all script signals to the other party that you have not taken the time to understand that organization's specific definition of the project. If your pitch is not personalized, it's hard for the institution to believe that your solution can seamlessly fit in.

There is an even more serious mistake: the "start over" narrative. In the crypto space, founders often tend to paint a whole new future: completely replacing old systems and ushering in a new era with updated, superior decentralized technology. However, enterprises rarely do this; traditional infrastructure is deeply ingrained in workflows, compliance processes, existing vendor contracts, reporting systems, and countless touchpoints and stakeholders. Starting over not only disrupts daily operations but also introduces various risks.

The broader the scope of the transformation, the fewer people within the organization dare to sign off: the bigger the decision, the larger the decision coalition.

The successful cases we have seen start with founders adapting to the current state of enterprise clients, rather than demanding clients to adapt to their ideals. When designing entry points, you should be able to integrate with existing systems and workflows, minimize disruptions, and establish reliable touchpoints.

A recent example is the collaboration between Uniswap and BlackRock on tokenized funds. Uniswap did not position DeFi as a replacement for traditional asset management but rather provided permissionless secondary market liquidity for products issued by BlackRock under existing regulatory and fund structures. This integration did not require BlackRock to abandon its operating model but simply extended it to the blockchain.

Waiting for you to go through the procurement process, after the solution is officially launched, there will still be plenty of time to pursue bigger goals.

Enterprises Hedge Their Bets, You Need to Be the "Right Hedge Play"

This risk aversion manifests as a predictable behavior: institutions hedge their bets, often on a large scale.

Larger enterprises do not put all their eggs in one basket by betting on emerging infrastructure. Instead, they conduct multiple experiments simultaneously. They allocate small budgets to multiple vendors, test various solutions in innovation departments, or conduct pilots without affecting core systems. To institutions, this preserves their options while limiting risk exposure.

But for founders, there lies a subtle trap here:

Being selected ≠ Being adopted. Many crypto companies are just one of the options enterprises use to dip their toes in the water; trying out a pilot is fine, but there is no real need to scale up.

The real goal is not to win a pilot but to become the top choice for hedging. This requires not only technological superiority but also professionalism.

Why Professionalism Trumps Purity

In such markets, clarity, predictability, and trustworthiness often outweigh pure innovation: winning based solely on technology is challenging. Therefore, professionalism is crucial as it reduces uncertainty.

When we talk about professionalism, we mean: when designing and presenting a product, one must fully consider institutional realities (such as legal constraints, governance processes, and existing systems) and commit to operating within these real-world frameworks. Adhering to conventions is like telling the other party: this product is governable, auditable, and controllable. Regardless of whether this aligns with the blockchain or crypto ethos, this is how enterprises view technology implementation.

It may seem like enterprises are resistant to change, but they are not. This is a rational response to corporate incentive structures.

Being fixated on the ideological purity behind the technology, whether it's "decentralization" or "minimal trust," is challenging to convince institutions bound by legal, regulatory, and reputational constraints. Demanding that a company accept a product that embodies the "full vision" in one go is asking for too much, too soon.

Of course, there are examples of a win-win scenario with groundbreaking technology + ideological purity. LayerZero recently launched a new public chain called Zero, aiming to address scalability and interoperability challenges in enterprise adoption while adhering to the core principles of decentralization and permissionless innovation.

However, Zero's true difference is not just its architecture, but its institutional design philosophy. It did not create a one-size-fits-all network and expect enterprises to adapt. Instead, it collaborated with core partners to jointly design dedicated "Zones" for specific use cases such as payments, settlement, and capital markets.

Zero's architecture, team's willingness to truly collaborate around these use cases, and the LayerZero brand have all significantly reduced some concerns of large traditional financial institutions. These factors, combined, led institutions like Citadel, DTCC, ICE to announce partnerships with Zero.

Founders often easily interpret enterprise resistance as conservatism, bureaucracy, lack of vision. Sometimes it is indeed the case, but there is usually another reason: most institutions are not irrational; their goal is to maintain operations. Their design goals are capital preservation, reputation protection, and withstand scrutiny.

In this environment, the winning technology is not necessarily the most elegant, the most ideologically pure, but the technology that strives to adapt to the enterprise's current state.

These realities can help us see the long-term potential of blockchain infrastructure in the enterprise space.

Enterprise transformation is rarely an overnight success. Look at the "digital transformation" of the 2010s: despite the relevant technology existing for many years, most large enterprises are still modernizing their core systems, often requiring significant investments to hire consulting firms. Large-scale digital transformation is an incremental process that needs to be achieved through controlled integration and use-case-driven expansion, rather than a sudden complete overhaul overnight. That is the reality of enterprise transformation.

Successful founders are not those who demand a complete vision from the outset but those who understand how to stepwise execute.

Original Article Link