The Opportunity

ENS is at an inflection point. After years of maturing the protocol, tooling, and ecosystem, the next phase of growth depends on distribution — ensuring ENS identity becomes a default standard across wallets, chains, WaaS/RaaS providers, social apps, defi and payments, AI agents, and every user-facing app of Web3.

We need a way to leverage the power of individual teams — ENS Labs, Service Providers, and Ecosystem projects — to create coordinated and unified BD and integration efforts. By aligning incentives, standardizing integration pathways, and coordinating outreach, we can unlock exponential growth of ENS resolution, registrations, subnames, users, and revenue.

The Challenge: BD coordination

Despite its protocol maturity and widespread ecosystem support, ENS outreach and growth remain fragmented. Different teams — ENS Labs, Service Providers, and independent ecosystem projects — pursue integrations in isolation, often duplicating efforts or sometimes missing high-value opportunities. Multiple teams may approach the same partners with different messages and offering, creating confusion, risking looking unprofessional, and reducing success rates.

There is no unified and shared business development system to coordinate outreach, track prospects and integrations, or strategically prioritize partners across wallets, L2s, payment apps, AI ecosystems, etc.

ENS Labs has limited bandwidth and cannot pursue every integration or partnership opportunity. At the same time, Service Providers like Namespace generate more leads and opportunities than they can manage on their own. This creates a clear need for a shared business development framework — one that enables opportunities to be distributed, tracked, and acted on collaboratively, ensuring no valuable lead goes without proper attention.

The Solution: ENS Alliance

The ENS Alliance serves as a dedicated business development coordination layer and advocacy group — extending ENS Labs’ reach while aligning the efforts of Service Providers and Ecosystem projects around shared growth objectives. It bridges the gap between protocol development and ENS support/integration, ensuring widespread outreach strategy and ensuring every opportunity receives focused attention from the right partners.

In practice, this creates the dedicated BD arm for ENS that everyone needs but one team individually doesn’t have the bandwidth to build and run. Service Providers gain coordinated market access, Labs expands its impact without additional overhead, and the entire ecosystem works toward universal ENS adoption instead of competing for the same conversations.

The goal is a shared BD framework that reduces outreach overlap, increases transparency, and maximizes collective outcomes. By synchronizing outreach, tracking opportunities, and clarifying ownership across all contributors — ENS Labs, Service Providers, and ecosystem teams — the Alliance makes growth more efficient, structured, and scalable.

This allows everyone to be on the same page at all times, and the DAO to benefit from cohesive, measurable growth in ENS integrations, subname adoption, and resolution support.

Why now?

The timing is ideal

The protocol has matured technically, the ENS brand is recognized globally, and demand for human-readable, verifiable, onchain identity is accelerating across many Web3 verticals.