T420 Ecosystem: Master Architecture
Executive Summary
┌─────────────────────────────────────────────────────────────────┐
│ T420 PROTOCOL (One System) │
│ │
│ Shared Infrastructure: │
│ • Relationship Graph (Fleet ↔ Supplier connections) │
│ • User Authentication (Magic links, JWT, Web3) │
│ • Notification Engine (WhatsApp, Email, SMS) │
│ • Intelligence Layer (Pattern detection, baselines, AI) │
│ • Database (PostgreSQL/Supabase - shared schema) │
│ │
└─────────────────────────────────────────────────────────────────┘
│
┌────────────┼────────────┐
│ │ │
┌───────▼──────┐ ┌──▼──────┐ ┌──▼──────────┐
│ FleetOS │ │Robo-Hub │ │ Robo-Dapp │
│ │ │ │ │ │
│ 100% US │ │ 20% US │ │ 2% US │
│ Market │ │ Market │ │ Market │
│ │ │ │ │ │
│ FREE │ │ PAID │ │ PREMIUM │
│ Entry Point │ │ B2B │ │ On-Chain │
└──────────────┘ └─────────┘ └─────────────┘
│ │ │
└────────────────┴──────────────┘
Users Flow UpwardTable of Contents
1. Market Segmentation
The 100-20-2 Rule
Product
Market Size
Target Users
Complexity
Revenue
Total Addressable Market (TAM)
2. Product Positioning
FleetOS: The Volume Play
Robo-Hub: The Monetization Layer
Robo-Dapp: The Protocol Lock-In
3. User Journeys
Journey 1: Joe's Mobile Tire Service (FleetOS → Robo-Hub → Robo-Dapp)
Journey 2: Sarah the Shepherd (Robo-Hub → Robo-Dapp → FleetOS Growth)
Journey 3: Miami Fleet Co. (FleetOS Only - Never Upgrades)
4. Shared Architecture
Evolution: Separate → Shared
Shared Core Objects
1. User
2. Relationship
3. Service Request
4. Notification
Shared Services
NotificationService
InviteService
IntelligenceService
5. Technical Evolution
How We Got Here
Migration Path
Stage 1: Shared Services (Current - Week 3)
Stage 2: Shared Database Schema (Month 1-2)
Stage 3: Shared UI Components (Month 2-3)
Stage 4: Monorepo Architecture (Month 3-6)
6. Database Schema
Unified Schema Design
7. Component Reusability
Shared UI Components
Design System
Reusable Components
Code Sharing Benefits
8. Revenue Model
Product-Level Revenue
Product
Free Tier
Paid Tiers
Revenue Streams
FleetOS Revenue
Robo-Hub Revenue
Robo-Dapp Revenue
Total T420 Ecosystem Revenue (Year 3 Projection)
Product
Revenue
% of Total
9. Growth Strategy
The Funnel
Growth Metrics by Product
Viral Mechanics
10. Roadmap
Phase 1: FleetOS Foundation (Current - Month 3)
Phase 2: Robo-Hub MVP (Months 4-6)
Phase 3: Robo-Dapp MVP (Months 7-12)
Phase 4: Shared Infrastructure (Months 13-18)
Phase 5: Scale (Months 19-24)
Appendix A: Terminology
Universal Terms (All Products)
Term
Definition
FleetOS-Specific Terms
Term
Definition
Robo-Hub-Specific Terms
Term
Definition
Robo-Dapp-Specific Terms
Term
Definition
Appendix B: Success Criteria
FleetOS Success (Month 12)
Robo-Hub Success (Month 12)
Robo-Dapp Success (Month 12)
Ecosystem Success (Month 24)
Appendix C: Key Documents
Strategy Documents
Implementation Documents
Appendix D: Contact & Contributions
Closing Thoughts
Why This Matters
Last updated
Was this helpful?