Own Iroh.

What you'd own.

Every artifact below transfers to your accounts on day one. The whole engine.

• ●Complete Python/JavaScript codebase and P2P WebRTC architecture.
• ●Brand identity, domain, landing page, and brand guidelines.
• ●Founder persona, segment research, and TAM analysis documentation.
• ●Three-tier pricing model and year-one financial projections.
• ●Customer outreach playbook and GTM strategy for developer communities.
• ●Production deployment guide and infrastructure setup documentation.

What Roll Digital builds for you.

Custom scope to take Iroh from MVP shell to operating business.

• ▸Production FastAPI backend with Postgres for persistence and multi-tenancy.
• ▸Stripe billing integration for free tier and team subscriptions.
• ▸Multi-tenant authentication with email and OAuth sign-in support.
• ▸Persistent room storage, scheduling, and team access controls.
• ▸TURN relay servers and NAT traversal optimization for reliability.
• ▸Admin dashboard with metrics, churn analysis, and user management.
• ▸Automated onboarding email sequence and in-app product tour.
• ▸Monitoring, alerting, and incident response playbook for production uptime.

Why this could work.

P2P video is a real wedge for privacy-conscious dev teams; Hacker News and GitHub communities are proven channels for exactly this buyer. The $15-25/mo team tier hits the price-insensitive floor for teams already spending on dev tools. The 140k-person TAM and 9% success rate suggest this works only for a disciplined operator who can stay narrow. $52k median year-one ARR is achievable but requires strong GTM execution against free alternatives.

What you'd risk.

Three structural risks are acute. First: you're selling technical differentiation (P2P, no servers) that most buyers can't evaluate and don't care about against permanently free alternatives. Second: P2P fails silently on enterprise firewalls, VPNs, and CGNAT networks, meaning every call failure is a churn event. Third: network effects run both ways; every new customer requires both sides to adopt, doubling acquisition friction. The 9% success probability reflects these headwinds.

Who this fits.

This fits a founder with existing distribution into developer or privacy communities, comfort shipping production infrastructure, and willingness to operate a niche, hardware-constrained business. Ideal: a solo SaaS founder or technical agency principal who's seen community-driven growth work and has the patience to win a low-TAM market through focused execution rather than broad marketing spend.

Timeline.

From contract signing to operating business.

1. Day 1
   Receive codebase, brand, GTM playbook, and financial model.
2. Week 1
   Deploy staging environment and validate infrastructure and dependencies.
3. Week 3
   Complete Stripe billing and multi-tenant authentication system.
4. Week 6
   Launch production and begin Hacker News community outreach.
5. Day 90
   Achieve 10-20 paying team accounts and validate CAC model.

Pricing.

Three ways in, depending on how much you want to build yourself.