For Anthropic's Claude Code, I was asked to design a feature that would increase virality within Fortune 2000 organizations. The challenge: propose a feature that was compelling, competitive, and achievable by a small engineering team in 3 months.
Hero Visual
Multiple Persona Tool Concept
Grow adoption of Claude Code inside large enterprises through a 'land and expand' strategy, starting with developers and pulling in adjacent personas.
Specs, designs, and tools scattered across multiple platforms, creating inefficiencies
PMs and designers brought in late, causing rework and missed requirements
Limited visibility for stakeholders into development progress and decisions
No central record of architectural and product decisions made during development
Non-developers face steep learning curves with existing developer tools
A collaborative online interface connected to GitHub that lets non-developers explore repositories, make lightweight contributions, and collaborate with developers directly in Claude Code.
Visual repository exploration for non-technical users
Context-aware AI assistance alongside files
Tailored contribution paths for each persona
Developers → Designers → PMs viral loop
Each developer invitation pulls in new personas, creating exponential seat growth within organizations
Viral Loop Diagram
Developer → PM → Designer → Stakeholder
Cross-team adoption drives organizational transformation
Each invite pulls in a new persona, creating growth loops
Natural alignment with Fortune 2000 procurement models
Unique multi-persona collaboration differentiator
Developer-only focus, no cross-functional tools
IDE-centric, limited collaboration features
Education focus, not enterprise-ready
Unique position: Enterprise collaboration across all roles
Key performance indicators to measure viral growth and adoption success
New org members per dev invite
Invites create new active users
Invited users become active
Reduced cross-team friction
| Risk | Mitigation |
|---|---|
Security concerns with online IDE Enterprise skepticism of cloud tools | SOC2 compliance, on-prem deployment options |
Model outputs buggy for non-devs Quality issues with fuzzy prompts | Role-specific permissions, specialized model training |
High inference cost Multi-persona usage increases costs | Distilled/specialized models for different roles |
Vendor lock-in (GitHub) Dependency on single platform | Diversified integrations roadmap (GitLab, Bitbucket) |
Achievable roadmap for a small engineering team to deliver MVP
Timeline Visualization
Month 1: Core Infrastructure | Month 2: Persona Features | Month 3: Launch & Iterate
Though my proposal wasn't selected, I'm proud of how I approached the challenge: identifying pain points, expanding virality loops beyond developers, and proposing a feasible feature for a small team.
Deep customer interviews and pain point analysis informed the solution
Focused on enterprise virality mechanics and seat expansion dynamics
Designed for small team feasibility within 3-month timeline
From fragmented tools to unified collaboration platform
Successful enterprise products need built-in expansion mechanics that align with organizational structures
Expanding beyond single user types creates broader organizational value and stickiness
Small team constraints force creative solutions that can become competitive advantages
Building platforms that enable collaboration creates more value than point solutions
Starting with one persona and expanding creates natural growth paths in enterprises
Unique positioning in unexplored spaces creates defensible advantages
From enterprise virality to platform design, I help companies build products that grow themselves.