Standalone Platform Strategy for Homepage.dev
Why Homepage.dev operates as an independent platform, not a satellite of do.dev
🎯 Executive Summary
Homepage.dev will operate as a completely standalone platform with independent authentication, billing, user management, and infrastructure. This strategic decision positions homepage.dev for maximum growth potential, enterprise credibility, and platform autonomy.
Key Insight: The "Notion moment" requires platform-level thinking, not feature-level execution.
📖 Supporting Documentation:
- Product Requirements - Complete platform vision
- Architecture Overview - Technical implementation
- Implementation Plan - Development roadmap
🔄 Satellite vs Standalone Comparison
Satellite Architecture (Typical do.dev Pattern)
interface SatelliteApproach {
authentication: "shared-multi-tenant-system"
userBase: "subset-of-do.dev-users"
billing: "unified-across-all-properties"
infrastructure: "shared-convex-deployments"
constraints: {
growthCeiling: "limited-by-parent-platform"
pricing: "constrained-by-do.dev-tiers"
features: "must-align-with-overall-strategy"
positioning: "secondary-product"
}
benefits: {
development: "faster-initial-setup"
maintenance: "shared-infrastructure-costs"
crossSelling: "user-overlap-opportunities"
}
}Standalone Architecture (Homepage.dev Strategy)
interface StandaloneApproach {
authentication: "dedicated-clerk-instance"
userBase: "independent-user-acquisition"
billing: "separate-revenue-streams"
infrastructure: "purpose-built-convex-projects"
advantages: {
growthPotential: "unlimited-scaling"
pricing: "optimized-for-productivity-market"
features: "homepage-specific-innovation"
positioning: "primary-platform"
}
investments: {
development: "higher-initial-setup-cost"
maintenance: "independent-infrastructure"
team: "dedicated-product-focus"
}
}🚀 Strategic Advantages of Independence
1. Unlimited Growth Trajectory
Satellite Limitation: Growth constrained by do.dev's user base and market positioning
// Satellite growth model
const maxUsers = doDevUsers.filter(user => needsHomepage) // Limited subset
const pricing = doDevPricing.filter(tier => fits) // Constrained optionsStandalone Opportunity: Tap into entire productivity tools market
// Standalone growth model
const maxUsers = globalProductivityUsers // $5.2B market
const pricing = optimizedForHomepageUsers // Custom tiers
const enterprise = dedicatedEnterpriseFeatures // No constraints2. Enterprise Market Credibility
Enterprise Purchasing Reality:
- Large organizations prefer dedicated platforms over satellite products
- Compliance teams scrutinize primary platform relationships
- IT procurement favors specialized solutions with clear ownership
- Security reviews are easier with standalone infrastructure
Standalone Positioning:
Enterprise Credibility:
- "Best-in-class homepage platform" vs "do.dev feature"
- Dedicated security compliance (SOC2, GDPR)
- Specialized customer success team
- Platform-specific SLAs and support
- Independent roadmap and development focus3. Pricing and Monetization Flexibility
Satellite Constraints:
- Must fit within do.dev's pricing structure
- Cannot cannibalize existing tiers
- Cross-product complexity in billing
- Limited enterprise pricing power
Standalone Freedom:
Optimized Pricing Strategy:
Free Tier: 3 homepages, 10 modules, 1GB storage
Pro Tier: $4.99/month - individual power users
Team Tier: $9.99/user/month - small teams (sweet spot)
Enterprise: Custom pricing - large organizations
Revenue Streams:
- Subscription tiers (70% of revenue)
- Module marketplace (20% of revenue)
- Enterprise services (10% of revenue)4. Technical Architecture Optimization
Purpose-Built Infrastructure:
// Standalone technical advantages
interface StandaloneTechStack {
// Optimized for real-time collaboration
database: "convex-real-time-subscriptions"
sync: "sub-100ms-global-latency"
modules: "sandboxed-execution-environment"
// Homepage-specific optimizations
caching: "module-aware-cdn-strategy"
scaling: "collaborative-workload-patterns"
security: "module-marketplace-isolation"
// No legacy constraints
architecture: "greenfield-modern-stack"
decisions: "homepage-first-optimization"
}5. Developer Ecosystem Focus
Platform-Level Developer Relations:
- Dedicated SDK team focused solely on homepage modules
- Module marketplace as primary platform differentiator
- Developer success program with homepage-specific expertise
- API design optimized for real-time collaborative modules
- Revenue sharing competitive with mobile app stores
Satellite Limitation: Developer tools would be secondary to do.dev's primary focus
🎯 Market Positioning Strategy
Competitive Landscape
Individual Tools:
- Start.me: Limited customization, no real-time
- Momentum: Beautiful but basic, no collaboration
- Bookmark Ninja: Bookmarks only, no platform
Team Platforms:
- Notion: General-purpose, not browser-native
- Obsidian: Knowledge management focus
- Slack: Communication-centric
Homepage.dev Position:
- Browser-native productivity platform
- Real-time collaboration built-in
- Module marketplace for extensibility
- Team workspaces with enterprise features"Notion Moment" Positioning
Just as Notion created a new category by combining docs, databases, and collaboration, homepage.dev creates the "browser productivity platform" category by combining:
- Customizable Homepages (Start.me functionality)
- Real-time Collaboration (Figma-level sync)
- Module Marketplace (Platform extensibility)
- Team Workspaces (Enterprise collaboration)
- Developer Ecosystem (Third-party innovation)
💰 Business Model Advantages
Revenue Stream Optimization
interface StandaloneRevenue {
// Primary revenue (80%)
subscriptions: {
individualPro: "$4.99/month × 25K users = $1.5M ARR"
teamTier: "$9.99/user/month × 5K users = $600K ARR"
enterprise: "Custom pricing × 50 orgs = $2M ARR"
}
// Platform revenue (20%)
marketplace: {
moduleRevenue: "30% of $1M developer revenue = $300K"
premiumModules: "Featured placement and tools"
enterpriseModules: "Higher revenue share deals"
}
// Total Year 2: $4.4M ARR vs $1M as satellite
}Investment and Valuation Impact
- Standalone Platform: Valued as productivity platform ($100M+ potential)
- Satellite Product: Valued as feature addition to do.dev ($10M ceiling)
- Enterprise Sales: Dedicated sales team vs shared resources
- Platform Multiplier: Module ecosystem creates compounding value
🏗️ Implementation Strategy
Phase 1: Independence Setup
Week 1-2: Authentication Independence
- Create dedicated Clerk instance
- Set up homepage-specific user models
- Independent organization management
Week 3-4: Infrastructure Setup
- Three-project Convex architecture
- Purpose-built real-time schemas
- Module marketplace foundationPhase 2: Platform Differentiation
Week 5-12: Platform Features
- Real-time collaboration engine
- Module SDK and marketplace
- Team workspace functionality
Week 13-16: Enterprise Readiness
- SSO and compliance features
- Advanced security and audit logs
- Dedicated customer successPhase 3: Market Independence
Week 17-20: Go-to-Market
- Separate marketing and positioning
- Independent customer acquisition
- Enterprise sales program
- Developer relations program🔄 Migration from Current State
Current State Analysis
- Simple Next.js landing page
- No authentication system
- Static content only
- Shared UI components with do.dev ecosystem
Migration Path
interface MigrationStrategy {
// Keep valuable assets
preserve: {
uiComponents: "@workspace/ui package"
designSystem: "tailwind + shadcn patterns"
buildTools: "turborepo + turbopack setup"
domain: "homepage.dev branding"
}
// Replace with standalone
replace: {
auth: "multi-tenant → standalone Clerk"
database: "none → dedicated Convex projects"
infrastructure: "simple hosting → platform deployment"
positioning: "landing page → full platform"
}
}🎯 Success Metrics for Standalone Strategy
Independence Validation Metrics
Month 3:
- 1K+ independent user registrations
- 0% user overlap with do.dev (proving separate market)
- 50+ team workspace creations
Month 6:
- 10K+ platform users
- $50K+ MRR from homepage-specific tiers
- 25+ enterprise prospects in pipeline
Month 12:
- 100K+ users (10x larger than potential do.dev subset)
- $500K+ MRR with platform-optimized pricing
- 100+ modules in marketplace
- 5+ enterprise customers paying $50K+/yearPlatform Success Indicators
- Developer Adoption: 50+ active module developers
- Enterprise Penetration: 25+ teams with 100+ users each
- Market Validation: Clear category leadership in "browser productivity"
- Acquisition Interest: Platform-level valuation discussions
🚨 Risk Mitigation
Standalone Risks and Mitigations
Risk: Higher Development Cost
Mitigation:
- Phase development to validate market demand
- Focus on team tier for faster revenue
- Leverage existing UI components and patterns
Risk: Marketing Isolation
Mitigation:
- Clear positioning as "brother platform" to do.dev
- Cross-promotion where beneficial
- Independent brand building in productivity space
Risk: Infrastructure Complexity
Mitigation:
- Use proven technologies (Clerk, Convex)
- Gradual scaling with monitoring
- Shared learnings from do.dev operations🎬 Conclusion
The standalone strategy positions homepage.dev to capture the full market opportunity rather than being constrained as a satellite product. This approach requires higher initial investment but offers:
- 10x larger addressable market
- Platform-level valuations
- Enterprise credibility
- Developer ecosystem potential
- Unlimited growth trajectory
The "Notion moment" requires platform-level ambition with platform-level independence.
By operating as a standalone platform, homepage.dev can become the definitive solution for browser productivity rather than an interesting feature of a larger ecosystem.
📖 Implementation Resources:
- Implementation Checklist - Detailed development tasks
- Module SDK - Developer ecosystem foundation
- Development Tenets - Core development principles
This strategy document guides all architecture, development, and go-to-market decisions for homepage.dev.
Last Updated: January 2025