The company that doesn't want a network effect — until it does

Most identity companies today are racing to lock in a directional network effect: lots of users, lots of relying parties, mutual lock-in. We deliberately chose not to chase that — yet. Here is the patient sequence we are betting on.

What network-effect-first looks like

Sign up users. Onboard relying parties. Hope each side sees the other and stays. This is the LinkedIn / Worldcoin / classic-marketplace pattern. It works when the protocol on top is mature enough that every new user adds value to every other user. For a category in active formation — which agent identity emphatically is today — it produces fragility: a fast-growing user base before the protocol is durable, and the lock-in becomes a tax on iteration.

What protocol-first looks like

Get the cryptography right. Get the developer experience right. Get the audit trail right. Get the regulatory compliance story right. Win a small number of relying parties whose pain is acute. Then open to network effects, because the protocol can absorb the new users without breaking. Wait, refine, then accelerate.

The cost we pay for patience

Real. Numbers grow more slowly. Marketing campaigns underperform. Investor decks need to argue something other than "look at the user count." We accept those costs because the alternative — premature network growth on top of an immature protocol — has killed every category we have studied.

What unlocks the network

Three signals we wait for. (1) The protocol is auditable: third parties can verify our claims without us. (2) The relying-party set is diverse: at least one bank, one healthcare provider, one large retailer, one open-source agent framework. (3) The reference implementations are hardened: 100,000 RPS verified by independent benchmarks; performance and security audits public. When all three hold, we open the network and let it run.

What this means for users today

If you are an early-adopter human, you are joining a small protocol that will get bigger. The number of relying parties accepting Manav is small relative to where it will be in 18 months. We tell you so explicitly because this is not the company that grows by surprise, only by deliberate sequence.

What it means for relying parties

If you integrate now, you are joining the protocol's design surface. We listen. The protocol shape today is being shaped by the relying parties who joined before the network unlocked. Later joiners get a more polished protocol; earlier joiners get a hand in shaping it.

Common objections

Two objections worth answering. Stated values do not survive growth pressure — true historically, which is why we put structural mechanisms (open-source, governance, protocol-enforced custody) behind the words rather than just the words. This sounds like marketing — the test will be the audit hashes, the protocol design, and the operating agreements, not the prose.

Frequently asked questions

What does this commitment cost us if we honor it? Real money in the years where the temptation would have been highest. We are pricing it in upfront because the commitment is structural, not aspirational.

Where do we publish this commitment? Here, on the protocol governance page, and in the operating agreements with our investors. Anyone can audit whether the commitment is being kept by reading the audit hashes we publish quarterly.

What if leadership changes? The commitment is structural enough that a new leadership cannot quietly reverse it. The protocol mechanics make the breach detectable; the legal commitments add a second layer; the cultural commitments add a third.

Where to start

For the wider posture, read manav manifesto and why open source. The values, the protocol, and the operating model only fit together when read in that order.

Adjacent reading

For the wider posture, see the manifesto, why open-source, and the values. The three together describe the company we are trying to build; the protocol is downstream of that posture.

What we trade for portability

A network-effect product gets better the more users it has. A portable product gets better the more places it works. The two are not the same, and the second is what identity needs. The user does not benefit from being on the largest identity network; the user benefits from a credential that travels. This is the choice we made, and it costs us a marketing story that other startups get to tell. We do not get to say "join the network." We get to say "carry the credential." The slow flywheel of that choice is real but undramatic — every relying party that adds verification, every wallet that adds support, every regulator that names a standard. The compounding is in the integrations, not the user count. Most identity startups optimized for the user count and failed at the integrations. We are betting on the inverse.

The network effect we want is the one that works. We will wait until the protocol earns it.