hermes-brain/ideas/social-growth-strategy.org

Alternative Growth — Social-First Scenario

• Why This Path Exists
• Phase 0: Unified Digital Existence Layer (0 → 10K users, 3-12 months)
• Phase 1: Network Effects — The Social Graph (10K → 1M users, 1-3 years)
• Phase 2: The Institution Crossover (1M → 10M users, 2-5 years)
• Phase 3: Default Infrastructure (10M → 1B+, 5-15 years)
• Comparison: Two Paths Side By Side
• Assessment: Which Is More Likely?
• References

The existing growth-strategy assumes institution-first growth: compliance → developer → consumer → regulatory. This page documents an alternative path: grow as a general-purpose social identity network, let institutions catch up later. Passepartout's three subsystems (the verification subsystem, the social protocol) are the same; the order of operations and the primary growth levers differ fundamentally.

Why This Path Exists

The institution-first scenario (growth strategy) takes the product's core technical capability — verification — and finds the customer with the clearest pain. That is the safe bet. But Passepartout ships with a second product that has nothing to do with verification: the social protocol, a unified publishing network, contract platform, payment network, and decentralized identity layer rolled into one. No product on the market offers this combination — ENS is names, Bluesky is social, Stripe is payments, DocuSign is contracts. The social protocol replaces all four with one provable layer.

The social-first scenario leans into what the social protocol is as a product, not what Passepartout is as a technology. Publishing, payments, contracts, and identity are all mass-market primitives. They can grow without ever mentioning ACL2, gate rules, or compliance. Verification is the infrastructure underneath, invisible to users until they need it.

Historical precedent: Instagram was a check-in app with filters. The camera and social graph came first; the advertising platform came later. Twitter was SMS broadcast; the real-time news network was emergent. In each case the product that users wanted had a different shape than the product that ultimately captured value.

Phase 0: Unified Digital Existence Layer (0 → 10K users, 3-12 months)

The key premise: the social protocol is not an identity product. It is four layers in one — a publishing network, a contract platform, a payment network, and decentralized infrastructure — all unified under a single identity. No product on the market offers this combination. ENS is names only. Bluesky is social only. Stripe is payments only. The social protocol replaces all of them with one provable layer.

Customer: Anyone who touches more than one of these layers today and feels the friction of managing separate accounts, separate reputations, and separate data silos. The most likely first adopters:

• Creators who publish across platforms and want verified ownership of their content
• Freelancers and contractors who send invoices, sign agreements, and manage multiple identities
• Crypto-natives who understand self-sovereignty but are tired of blockchain UX
• Developers building agents that need a persistent identity, payment channel, and data store

The minimum viable social protocol must ship all four layers at Phase 0. Not fully featured, but functional — enough that a user can register, publish a signed post, send a payment, and sign a simple contract using one identity. The value is in the unification: one account replaces four.

Growth lever: Multi-vector network effects. The social protocol grows not on a single curve but on four simultaneous curves:

1. Publishing: each new creator attracts readers, who may become creators
2. Payments: each new payment user creates liquidity that makes the network more useful for everyone
3. Contracts: each new contract written on the social protocol creates a template and a precedent
4. PDS: each new PDS increases the federation surface and the compute marketplace supply

Any of these can be the primary growth vector in a given market. If publishing stalls in one region, payments might take off. This redundancy dramatically increases the probability that some vector finds PMF.

Tactics:

1. Entry point optimization. Ship all four layers but actively measure which one drives signups in each channel. If a blog post about "verified publishing" drives 10× more signups than a post about "decentralized identity," double down on publishing. The platform is unified enough that users who join for one reason discover the other three.
2. Creator tools. Offer a one-click "publish with provenance" widget. A creator writes on Substack, Medium, or their own blog, pastes the social protocol embed, and every post is automatically signed and timestamped. Readers see a blue checkmark that links to the social protocol attestation. This is a better blue checkmark than Twitter's because it's cryptographically verifiable — and it works across platforms.
3. Freelancer onboarding. Ship an invoice-and-contract template: "Send a verified invoice. Get a signed contract. Get paid on the social protocol." The freelancer registers once, and their invoices, contracts, and payment history are provably theirs. This is a productivity tool first and a social network second — users join to get paid, stay because their professional reputation is on it.
4. PDS hosting as infrastructure. The PDS is the backbone, not the headline. Freemium model: first 1GB free, $5-15/mo for unlimited. The PDS stores your identity, content, contracts, and payment history in one place. The value prop: one account, one data store, one reputation, everywhere.
5. Fee-based revenue. The social protocol takes 0.5-2% on payment transactions and 5-10% on marketplace contracts (data licensing, compute). These fees are invisible to users (built into the platform layer) and scale with usage. Unlike subscription revenue, they require zero active selling — the platform grows, fees follow.

Revenue:

Stream	Year 1 target	Mature
Payment processing fees (0.5-2%)	$100K-1M	$10-50M/yr
PDS hosting subscriptions	$50K-200K	$1-3M/yr
Marketplace contract commissions	$20K-100K	$5-20M/yr
Premium username auctions	$50K-300K	$2-5M/yr
Creator tools (Pro tier)	$50K-200K	$2-10M/yr
Total	$270K-1.8M	$20-88M/yr

The fees are the key difference from my earlier estimate. The social protocol's payment and contract layers generate revenue per transaction without requiring subscription growth. A user who never pays for PDS hosting still generates fees if they send a payment or sign a contract on the network.

Key metric: Platform usage across any of the four layers. Fee volume (total value processed through payments + contracts). Not DAU — a user who joins for payments and never publishes is still generating revenue.

Failure mode: The unified platform is harder to explain than a single-purpose product. "One account for identity, publishing, payments, and contracts" sounds like a pitch deck, not a product. The risk is that the scope of the social protocol makes it incomprehensible — users don't know what problem it solves because it solves too many. The mitigations: optimize for a single entry vector per channel, let users discover the others naturally.

Phase 1: Network Effects — The Social Graph (10K → 1M users, 1-3 years)

Customer: The early adopter base expands to include privacy-conscious mainstream users. The trigger is a platform failure event: a major platform bans a creator, de-platforms a community, or suffers a data breach. When that happens, the social protocol is ready — it offers the same social primitives (messaging, identity, publishing) but with ownership.

Growth lever: Metcalfe's law + switching cost. Each new user makes the network more valuable. But the real lock-in is the reputation graph: attestations, signatures, and data provenance are cumulative. A user with 3 years of verified activity on the social protocol cannot replicate that on any other platform. The switching cost grows with time.

Tactics:

1. Ship verified messaging. Every message between social protocol users is signed and timestamped. No third party can modify or delete it. The product pitch: Twitter, but your tweets are yours, and nobody can rewrite history.
2. Publish an attestation API. Third-party services (news outlets, marketplaces, social platforms) can query the social protocol to verify a user's reputation. News comments show "verified human, 2yr history, no abuse flags." This creates outbound value — the network becomes useful to people who aren't even on it.
3. Offer PDS-to-PDS federation. Social protocol instances communicate directly. No central server. This differentiates from every centralized platform and gives a structural privacy advantage that no amount of VC funding can replicate.
4. Introduce data licensing. Users can license their verified data to AI training companies, researchers, advertisers — on their own terms, with their own price. The social protocol takes a 10-15% commission. This creates a revenue share that users understand viscerally. Compare: X/Twitter makes billions selling user data and gives nothing back. Social protocol users get paid.
5. Verification becomes visible. Each user's profile shows a "verification score" based on the length and depth of their attested history. Long-time users get a visible badge. This creates status competition around the one thing nobody else can offer: provable history.

Revenue:

Stream	Year 3 target	Mature
PDS hosting subscriptions	$500K-2M	$10-50M/yr
Data licensing commissions	$200K-1M	$20-100M/yr
Premium username renewals	$100K-500K	$5-10M/yr
Verified badge program	$100K-300K	$2-5M/yr
Attestation API (per-query)	$50K-200K	$5-20M/yr
Total	$1-4M	$42-185M/yr

Key metric: Daily active PDS users. Inter-instance messages per day. Attestation API queries.

Failure mode: Network effects fail to trigger because the user experience is not better than existing platforms — it's different. Different is not enough. The product must match or exceed the UX of mainstream social platforms while offering the ownership advantage. If the UX gap is too large, users stay on Twitter/Bluesky/Threads despite the privacy cost.

Phase 2: The Institution Crossover (1M → 10M users, 2-5 years)

Customer: At 1M+ active identities, the network has critical mass. Institutions (universities, media companies, government agencies, enterprises) can no longer ignore it because their users are on it. The crossover happens organically: a university registrar wants to issue verified credentials. A newsroom wants to publish with verified provenance. A regulator wants to use the social protocol's attestation infrastructure because it already has users.

Growth lever: Institutional network effects. Every institution that joins brings 10K-100K users with it (employees, students, customers). Each new institutional user increases the value of verification for everyone else. The growth curve becomes logistic with institutional jumps, not smooth organic growth.

Tactics:

1. Ship the environment subsystem enterprise bundle (SSO, compliance reports, fleet management, audit logging). This was the entire Phase 0-1 of the institution-first scenario. Here it is a Phase 2 feature — built to serve institutions that are already inside the network, not sold to cold prospects.
2. Offer verified credentialing: degrees, certifications, professional licenses, issued on the social protocol, verifiable by anyone. The institution pays for the issuance. The graduate gets a portable, provable credential.
3. Offer provenance publishing: news organizations publish articles signed by their social protocol identity. Readers verify provenance in one click.
4. Verification appliances are now a fulfillment order, not a sales pitch. Institutions already inside the network ask: "Can we run our own instance?" The answer is yes — here is an environment subsystem appliance. The gate rule SDK is a value-up, not a product.
5. The compute marketplace activates naturally. With 10M+ users and thousands of institutions, compute supply and demand are both present without bootstrapping.

Revenue:

Stream	Year 5 target	Mature
Enterprise environment subsystem seats	$5-20M	$50-200M/yr
Verified credential issuance	$2-10M	$20-100M/yr
Compute marketplace fees	$1-5M	$50-200M/yr
PDS hosting (scaled)	$2-10M	$20-50M/yr
Data licensing (scaled)	$1-5M	$20-100M/yr
Verification appliances	$2-10M	$50-100M/yr
Total	$13-60M	$210-750M/yr

Key metric: Institutional join events. Environment subsystem subscriptions. Credentials issued.

Failure mode: The institution crossover never comes because the social graph stalls at 1M users — enough for a niche, not enough for critical mass. The network becomes a high-quality-but-small community like early App.net or Mastodon. Verification is real but irrelevant because the rest of the world is on different platforms. The institution-first scenario is still possible from here (direct enterprise sales), but the supposed advantage of "users first" has not materialized.

Phase 3: Default Infrastructure (10M → 1B+, 5-15 years)

Customer: At this scale, the social protocol is the default identity and communication layer for a significant fraction of internet users. New users join because everyone is there. Institutions join because everyone is there. The regulatory capture that the institution-first scenario required as a growth lever happens here as a consequence — regulators adopt social protocol attestation because it is the standard.

Growth lever: Default status. The network is the path of least resistance. A new social platform would need to replicate not just the user base but the entire attestation history, compute marketplace, and institutional infrastructure. The moat is not legal (regulation) but practical (installed base + cumulative value).

Tactics: Similar end state to the institution-first scenario — verification monopoly, certified appliance sales, insurance marketplace, nation-state deployments. The difference is the path and the character of the moat:

• Institution-first moat: regulatory lock-in. You comply because the law requires it.
• Social-first moat: installed-base lock-in. You join because everyone is there.

The regulatory moat is faster to deploy but brittle (a change in government can undo it). The installed-base moat is slower to build but self-reinforcing.

Revenue: Same end state as growth-strategy.org Phase 3 — $1B+ across certification, infrastructure rent, marketplace fees, and insurance underwriting.

Comparison: Two Paths Side By Side

Dimension	Institution-first	Social-first
First customer	CISO, compliance buyer	Creators, devs, payment users
First revenue	$2-12M (year 1)	$500K-3M (year 1)
Time to $10M ARR	12-24 months	2-4 years
Time to $50M ARR	2-4 years	4-7 years
Time to $1B+	5-15 years	8-20 years
Capital requirement	Low (revenue-funded)	Low-Moderate (fees fund growth)
Marketing cost	Sales team + compliance mktg	Community + product-led growth
Key execution skill	Enterprise sales	Consumer product + platform design
Network effect trigger	Developer SDK (Phase 1)	Multi-vector: any of 4 layers
Phase 0 offer	Compliance report	Unified identity + pub + pay + contract
Moat type	Regulatory + insurance	Installed base + attestation
Moat durability	Good (legal)	Strong (practical)
Entry vectors	One: compliance pain	Four: publishing, payments, contracts, ownership
Failure mode	Wrong pricing, too early	Any vector stalls — but all 4 must

Assessment: Which Is More Likely?

I initially assessed institution-first as significantly more likely. The unified-layer correction narrows the gap considerably. Here is the revised assessment:

The social-first path's strongest argument — which I dismissed too quickly — is that the social protocol is not competing with any single product. A competitor who beats it on publishing (Substack, Medium) cannot also beat it on payments (Stripe, PayPal) and contracts (DocuSign, LexisNexis) and identity management — simultaneously. The unification is not a feature; it is the structural advantage. Each layer reinforces the others, and competing against the whole stack requires matching all four, which no existing product does.

The multi-vector growth also matters. The institution-first path has one entry vector (compliance pain) and one failure mode (wrong pricing or too early). The social-first path has four entry vectors, and any one of them reaching PMF carries the other three. The probability that publishing or payments or contracts or identity ownership finds product-market fit is higher than the probability that any single one does.

The fee-based revenue model further improves Phase 0 economics. Payment processing fees scale with transaction volume, not user count. A small number of high-value users (freelancers sending invoices, creators selling subscriptions) can generate meaningful revenue before the network reaches critical mass.

However: the core tension remains. The team building Passepartout is a deep-tech verification team — their competence is ACL2, gate rules, provably correct systems. The social-first path requires the team to also be a consumer product team — UX design, growth loops, community management, creator partnerships, payment infrastructure, fraud detection. That is not impossible (the team can hire) but it is a different company than the one building Passepartout.

The institution-first path monetizes the team's existing competence from day one. The social-first path requires building a second competence (consumer platform) that does not exist yet. This is the real distinction, not the product's inherent potential.

My updated assessment: the institution-first path is still higher probability, but not by the wide margin I initially claimed. The gap is narrower because the social protocol as a unified layer is genuinely unprecedented.

The hybrid path may be the strongest: ship the four-layer social protocol as a public platform alongside the enterprise compliance sales.

References

• Primary growth strategy — institution-first
• Revenue streams by component
• Social protocol contract platform details
• Effects and growth as interleaved curves
• Development timeline — Phase Zero and End State

The social-first path is attractive because the end state is stronger. But the path to it requires building a consumer product alongside the deep-tech verification infrastructure — essentially running two startups in parallel. The Social protocol Social Space requirements describe the community interaction model that makes the social-first path viable..