T420 Ecosystem: Master Architecture

Version: 1.0 Date: December 18, 2025 Status: Living Document Purpose: Single source of truth for how FleetOS, Robo-Hub, and Robo-Dapp work together


Executive Summary

T420 is ONE SYSTEM with THREE PRODUCTS serving different market segments.

The ecosystem started as three separate builds but evolved as we discovered shared patterns. As development progresses (particularly Robo-Hub β†’ Robo-Dapp), we're identifying opportunities to leverage shared components and shared databases to create a more manageable, elegant codebase.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    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 Upward

Table of Contents


1. Market Segmentation

The 100-20-2 Rule

Product
Market Size
Target Users
Complexity
Revenue

FleetOS

100% US Market

Independent mobile service providers + Regular fleets

LOW (Free coordination tool)

Freemium ($0-49/mo)

Robo-Hub

20% US Market

Professional suppliers + Shepherds (entrepreneurs)

MEDIUM (B2B marketplace)

B2B (NFT sales, contracts)

Robo-Dapp

2% US Market

Shepherds operating T420 robotaxi fleets

HIGH (On/off-chain ops)

Protocol fees, staking

Total Addressable Market (TAM)

US Fleet Maintenance & Repair Market: ~$80B annually

  • FleetOS TAM: $80B (100%) - All mobile service providers

    • Mobile tire shops: 15,000+ businesses

    • Mobile mechanics: 25,000+ operators

    • EV charging: 5,000+ providers

    • Tow/roadside: 30,000+ operators

    • Glass repair: 8,000+ mobile units

  • Robo-Hub TAM: $16B (20%) - Professional suppliers + entrepreneurs

    • Multi-location suppliers

    • Contract-seeking businesses

    • Zone license buyers (Shepherds)

  • Robo-Dapp TAM: $1.6B (2%) - T420 robotaxi operators

    • Shepherd-operated fleets

    • Protocol participants

    • DePIN stakeholders


2. Product Positioning

FleetOS: The Volume Play

Tagline: "From Chaos to Compliance"

Target: 100% of mobile service market

  • Independent operators (1-10 employees)

  • Underserved providers

  • No tech infrastructure

  • Currently using WhatsApp/phone calls

Value Proposition:

  • Free forever coordination

  • "Easier than WhatsApp"

  • 10-20x faster request handling

  • No contracts, no complexity

  • Viral growth (invite existing customers)

Brand Identity:

  • Clean, simple, approachable

  • NO crypto/blockchain talk

  • NO T420 branding (except subtle footer)

  • Focus: Relationships, not automation

Positioning Statement:

FleetOS prevents silence when silence is expensive. Get organized, respond faster, never lose a request.


Robo-Hub: The Monetization Layer

Tagline: "Strategic Sourcing & Governance Platform"

Target: 20% of market (entrepreneurs + professional suppliers)

  • Shepherds buying zone licenses (NFTs)

  • Suppliers seeking large contracts

  • Fleets wanting vetted, contracted suppliers

Value Proposition:

  • For Shepherds: Buy zone license β†’ Source suppliers β†’ Launch fleet ops

  • For Suppliers: Get matched with high-volume customers

  • AI-assisted procurement: RFQ negotiation, market pricing, contract terms

Brand Identity:

  • Professional, B2B-focused

  • T420 branded (explicit protocol connection)

  • Blockchain-native (NFTs, staking)

  • Focus: Contracts, economics, governance

Positioning Statement:

Robo-Hub connects entrepreneurs with suppliers to establish infrastructure contracts. Own your zone. Build your network. Launch your fleet.


Robo-Dapp: The Protocol Lock-In

Tagline: "On-Chain Fleet Operations"

Target: 2% of market (T420 robotaxi operators - Shepherds only)

  • Shepherd-operated fleets

  • T420 protocol participants

  • DePIN stakeholders

Value Proposition:

  • Daily dispatch (book parts & services from contracted suppliers)

  • Smart contract payments (instant settlement, 24-48hr)

  • Real-time fleet KPIs (DePIN dashboard)

  • Token staking + governance rewards

Brand Identity:

  • Technical, protocol-first

  • Full T420 branding

  • On-chain identity matters

  • Focus: Automation, efficiency, decentralization

Positioning Statement:

Robo-Dapp is the operational layer for T420 protocol. Manage your fleet, coordinate services, settle payments on-chain. Built for Shepherds.


3. User Journeys

Journey 1: Joe's Mobile Tire Service (FleetOS β†’ Robo-Hub β†’ Robo-Dapp)

Month 1: FleetOS Entry (Free)

  1. Discovery: Joe hears about FleetOS from another tire shop owner

  2. Signup: 5-minute onboarding (email, business name, WhatsApp)

  3. Viral Activation: Invites 3 existing fleet customers:

    • Miami Fleet Co. (15 vehicles)

    • Sunshine Transport (24 vehicles)

    • Express Delivery (8 vehicles)

  4. Daily Usage:

    • Receives requests via WhatsApp magic links

    • One-tap responses (Acknowledge β†’ Accept β†’ Complete)

    • Organized dashboard vs WhatsApp chaos

  5. Result: 10-20x faster coordination, saves 12 hours/week

Month 3: Robo-Hub Upgrade (Contracts)

  1. Discovery: A Shepherd (Sarah) buys Miami South Beach zone license

  2. Inbound Lead: Sarah finds Joe on Robo-Hub supplier directory

  3. RFQ: Sarah sends RFQ: "Need mobile tire provider for 50-vehicle fleet, 24/7 coverage"

  4. AI-Assisted Negotiation:

    • AI analyzes Joe's quote ($95/rotation) vs market avg ($85)

    • AI suggests counter-offer to Sarah

    • Joe adjusts pricing, adds after-hours SLA

  5. Contract Signed: Joe gets guaranteed volume (200 tire rotations/month)

  6. Result: Predictable revenue, higher rates, long-term contract

Month 6: Robo-Dapp Integration (Operations)

  1. Fleet Launch: Sarah launches T420 robotaxi fleet operations

  2. API Integration: Joe's tire service integrated via T420 Connect

  3. Work Orders: Flow automatically from Robo-Dapp to Joe's CRM

  4. Smart Contract Payments: Instant settlement (24-48hr, no chasing invoices)

  5. Staking: Joe stakes T420 tokens for priority dispatch

  6. Result: Predictable cash flow, instant payments, protocol participation


Journey 2: Sarah the Shepherd (Robo-Hub β†’ Robo-Dapp β†’ FleetOS Growth)

Month 0: Zone License Purchase

  1. Discovery: Sarah researches robotaxi market opportunity

  2. Zone Selection: Chooses Miami South Beach (10 license capacity)

  3. NFT Purchase: Mints zone license NFT ($5,000 stake)

  4. Onboarding: Completes Shepherd profile (business plan, capital proof)

Month 1-2: Supplier Sourcing (Robo-Hub)

  1. Supplier Search: Uses Robo-Hub marketplace to find local suppliers:

    • Mobile tire providers (Joe's shop + 2 competitors)

    • EV charging operators (3 options)

    • Mobile mechanics (5 options)

  2. RFQ Dispatch: AI Agent sends standardized RFQs to 11 suppliers

  3. Negotiation: Reviews quotes, AI provides market comparisons

  4. Contracts Signed: 6 suppliers contracted with agreed rates/SLAs

  5. Relationship Building: Invites all 6 suppliers to use FleetOS for coordination

Month 3: Fleet Launch (Robo-Dapp)

  1. Fleet Setup: Imports 50 Tesla Model Y vehicles into Robo-Dapp

  2. Supplier Integration: 6 contracted suppliers connected via T420 Connect API

  3. Daily Operations:

    • Vehicle #A7832 needs tire rotation β†’ Robo-Dapp auto-creates request

    • Request sent to Joe (contracted tire supplier) via FleetOS

    • Joe responds in 30 seconds via WhatsApp magic link

    • Payment settles via smart contract (24-48hr)

  4. Governance: Sarah participates in T420 DAO (token holder)

Month 6: Network Effects

  1. FleetOS Adoption: Sarah's 6 suppliers now use FleetOS for ALL their fleet customers

  2. Viral Growth: Each supplier invites 10+ more fleets to FleetOS

  3. Sarah's Benefit: More suppliers on FleetOS = easier to find backup/overflow providers

  4. Protocol Growth: FleetOS β†’ Robo-Hub funnel generates more Shepherds


Journey 3: Miami Fleet Co. (FleetOS Only - Never Upgrades)

Month 1: Invited by Joe

  1. Invite: Joe (tire supplier) sends FleetOS invite link via WhatsApp

  2. Signup: 3-minute onboarding (fleet name, email, 15 vehicles)

  3. Relationship Created: Joe auto-added as trusted supplier

Month 2-12: Ongoing Usage

  1. Service Requests: Creates 2-3 requests per month (tire issues, maintenance)

  2. Coordination: Sends requests to Joe + 2 other suppliers already on FleetOS

  3. Tracking: Views service history, response times, completion status

  4. Never Upgrades: Stays on free tier forever (doesn't need intelligence features)

Why This Matters:

  • Miami Fleet Co. still provides value to ecosystem (creates requests for suppliers)

  • Generates data for intelligence layer (response time baselines)

  • Potential future upsell (Pro tier for larger fleets)

  • Contributes to network effects (may invite other suppliers)


4. Shared Architecture

Evolution: Separate β†’ Shared

Phase 1 (Current): Three Separate Codebases

Phase 2 (Near Future): Shared Foundation

Phase 3 (Future): Unified Platform


Shared Core Objects

These objects exist across all three products:

1. User

Shared by:

  • FleetOS: Basic email-based users

  • Robo-Hub: Email + wallet address (Web3 auth)

  • Robo-Dapp: Wallet-first identity


2. Relationship

Shared by:

  • FleetOS: Basic relationships (fleet ↔ supplier)

  • Robo-Hub: Contracted relationships (Shepherd ↔ supplier)

  • Robo-Dapp: Operational relationships (execution layer)

Why This Works:

  • Same graph structure across all products

  • FleetOS relationships can upgrade to Robo-Hub contracts

  • Robo-Hub contracts can activate in Robo-Dapp

  • Intelligence (health_score, avg_response_time) benefits all products


3. Service Request

Shared by:

  • FleetOS: Basic service coordination

  • Robo-Hub: Contract execution tracking

  • Robo-Dapp: On-chain work orders + payments

Why This Works:

  • Same request structure across products

  • FleetOS requests can be referenced in Robo-Hub contracts

  • Robo-Dapp requests can be created from FleetOS relationships

  • Payment layer (Robo-Dapp) sits on top of coordination layer (FleetOS)


4. Notification

Shared by:

  • FleetOS: WhatsApp magic links, status updates

  • Robo-Hub: RFQ notifications, contract updates

  • Robo-Dapp: Payment confirmations, dispatch alerts

Why This Works:

  • Single notification infrastructure

  • Cross-product message history

  • Unified deliverability tracking

  • Cost efficiency (shared Twilio/SendGrid accounts)


Shared Services

NotificationService

Current Usage:

  • FleetOS: New request notifications, status updates

  • Robo-Hub: RFQ invitations, contract updates (future)

  • Robo-Dapp: Payment confirmations, dispatch alerts (future)


InviteService

Current Usage:

  • FleetOS: Viral loop (supplier invites fleets, fleets invite suppliers)

  • Robo-Hub: Shepherd invites suppliers to bid on contracts (future)


IntelligenceService

Future Usage:

  • FleetOS: Relationship health, exception detection (Phase 0-3)

  • Robo-Hub: RFQ analysis, market pricing, negotiation prep (Phase 3-5)

  • Robo-Dapp: Operational insights, dispatch optimization (Phase 5-7)


5. Technical Evolution

How We Got Here

Initial State (Separate Builds):

  • FleetOS: Built as standalone coordination tool

  • Robo-Hub: Built as Shepherd marketplace (Zone Licenses, NFTs)

  • Robo-Dapp: Built as on-chain fleet operations platform

Commonality Discovery:

  1. User Identity: All three need suppliers + fleets

  2. Relationships: Same graph structure (fleet ↔ supplier)

  3. Service Requests: Same coordination primitives

  4. Notifications: Same WhatsApp/email infrastructure

  5. Intelligence: Same pattern detection logic

Decision Point (Now):

  • Continue separate codebases = 3x maintenance overhead

  • Merge into shared foundation = elegant, maintainable, scalable


Migration Path

Stage 1: Shared Services (Current - Week 3)

Action Items:

  • βœ… NotificationService already works across products

  • βœ… InviteService already works across products

  • 🟑 Create IntelligenceService for Phase 0 features

  • 🟑 Document shared service contracts


Stage 2: Shared Database Schema (Month 1-2)

Action Items:

  • 🟑 Design unified schema

  • 🟑 Migrate FleetOS to Supabase (planned Week 3)

  • 🟑 Ensure Robo-Hub/Robo-Dapp can use same database

  • 🟑 Add foreign key constraints to enforce relationships


Stage 3: Shared UI Components (Month 2-3)

Reusable Components:

  • RelationshipCard

  • ServiceRequestCard

  • NotificationBadge

  • HealthIndicator (πŸŸ’πŸŸ‘πŸ”΄)

  • MagicLinkAuth

  • InviteFlow

Action Items:

  • 🟑 Extract common components into shared library

  • 🟑 Add product-specific theming

  • 🟑 Document component API contracts


Stage 4: Monorepo Architecture (Month 3-6)

Option A: Turborepo

Option B: Nx Monorepo

Benefits:

  • Single npm install for entire platform

  • Shared dependencies (React, Next.js, Supabase)

  • Cross-product imports: import { NotificationService } from '@t420/shared'

  • Unified build pipeline

  • Reduced maintenance overhead


6. Database Schema

Unified Schema Design


7. Component Reusability

Shared UI Components

Design System

Theme Configuration:


Reusable Components

1. RelationshipCard

Usage:


2. ServiceRequestCard


3. HealthIndicator


4. MagicLinkAuth


Code Sharing Benefits

Before (Separate Codebases):

After (Shared Components):


8. Revenue Model

Product-Level Revenue

Product
Free Tier
Paid Tiers
Revenue Streams

FleetOS

Coordination (unlimited)

Pro ($49/mo)

Subscriptions

Robo-Hub

None (B2B only)

Zone Licenses ($5K+ stake)

NFT sales, Contract fees

Robo-Dapp

None (Shepherds only)

Transaction fees (2.5%)

Protocol fees, Staking


FleetOS Revenue

Free Tier (100% of users):

  • Unlimited service requests

  • Unlimited relationships

  • WhatsApp notifications

  • Email notifications

  • Basic status tracking

  • Service history

Pro Tier ($49/month per company):

  • Response-time visibility

  • Missed-request alerts

  • Relationship health indicators (πŸŸ’πŸŸ‘πŸ”΄)

  • Multi-supplier requests

  • Exports & audit logs

  • Priority support

Projected Revenue (Year 1):

  • 10,000 suppliers sign up (100% market focus)

  • 5% convert to Pro = 500 paying customers

  • 500 Γ— $49 = $24,500/month = $294,000/year

Projected Revenue (Year 3):

  • 50,000 suppliers (market penetration)

  • 10% Pro conversion = 5,000 paying customers

  • 5,000 Γ— $49 = $245,000/month = $2.94M/year


Robo-Hub Revenue

Zone License Sales:

  • 100 US cities Γ— 10 zones per city = 1,000 zone licenses

  • Average license: $5,000 base stake + $500/vehicle

  • Example: 50-vehicle Shepherd = $5K + ($500 Γ— 50) = $30K total stake

  • Potential TAM: 1,000 licenses Γ— $30K avg = $30M in NFT sales

Contract Facilitation Fees:

  • 2.5% fee on annual contract value (AMC)

  • Example: Shepherd signs $200K/year contract with tire supplier

  • T420 takes: $200K Γ— 2.5% = $5K facilitation fee

  • Projected: 500 Shepherds Γ— 5 suppliers Γ— $150K avg contract Γ— 2.5% = $9.375M/year

Projected Revenue (Robo-Hub - Year 3):

  • Zone license sales: $10M (333 licenses sold)

  • Contract facilitation: $5M (annual recurring)

  • Total: $15M/year


Robo-Dapp Revenue

Transaction Fees:

  • 2.5% protocol fee on every service payment

  • Example: $100 tire rotation β†’ $2.50 to protocol

  • Revenue split: 42% Shepherd / 42% Supplier / 16% Protocol

  • Projected: 500 Shepherds Γ— 50 vehicles Γ— 2.4 requests/year Γ— $150 avg = $9M volume

  • Protocol share: $9M Γ— 16% = $1.44M/year

Staking Rewards:

  • Suppliers stake T420 tokens for priority dispatch

  • Shepherds stake for zone exclusivity

  • Staking pool generates yield (reinvested into protocol)

Projected Revenue (Robo-Dapp - Year 3):

  • Transaction fees: $1.44M

  • Staking revenue: $500K

  • Total: $1.94M/year


Total T420 Ecosystem Revenue (Year 3 Projection)

Product
Revenue
% of Total

FleetOS

$2.94M

14.5%

Robo-Hub

$15M

74%

Robo-Dapp

$1.94M

9.5%

TOTAL

$19.88M

100%

Key Insight:

  • Robo-Hub (20% market) generates 74% of revenue

  • FleetOS (100% market) generates only 14.5% BUT is the funnel

  • Without FleetOS's viral growth, Robo-Hub has no suppliers to contract


9. Growth Strategy

The Funnel


Growth Metrics by Product

FleetOS:

  • North Star Metric: Relationships created

  • Leading Indicators:

    • Supplier signups per week

    • Invites sent per supplier

    • Invite acceptance rate

  • Lagging Indicators:

    • Total service requests

    • Pro conversion rate

Target (Year 1):

  • 10,000 suppliers

  • 25,000 relationships

  • 100,000 service requests

  • 500 Pro subscribers


Robo-Hub:

  • North Star Metric: Contracts signed (Shepherd ↔ Supplier)

  • Leading Indicators:

    • Zone licenses minted

    • RFQs dispatched

    • Suppliers bidding on RFQs

  • Lagging Indicators:

    • Annual contract value (ACV)

    • Contract renewal rate

Target (Year 1):

  • 100 Shepherds

  • 300 contracts signed

  • $15M total contract value


Robo-Dapp:

  • North Star Metric: On-chain transaction volume

  • Leading Indicators:

    • Shepherds launching fleets

    • Suppliers integrated via API

    • Daily work orders

  • Lagging Indicators:

    • Payment settlement speed

    • Dispute rate

Target (Year 1):

  • 20 active Shepherd fleets

  • 100 integrated suppliers

  • $2M transaction volume


Viral Mechanics

FleetOS Viral Loop:

  1. Supplier signs up (5 min)

  2. Invites 3-5 existing fleet customers

  3. Each fleet invites 2-3 existing suppliers

  4. Network effects compound

K-Factor Calculation:

  • Average supplier invites 4 fleets

  • 50% acceptance rate = 2 new fleets

  • Each fleet invites 3 suppliers

  • 40% acceptance rate = 1.2 new suppliers

  • K-Factor: 1.2 (viral growth!)

Robo-Hub Sourcing Loop:

  1. Shepherd buys zone license

  2. Needs to source 5-10 suppliers

  3. Finds them on FleetOS (already vetted by fleets)

  4. Invites suppliers to bid on contracts

  5. Suppliers already have FleetOS dashboard (zero friction)

Cross-Product Synergy:

  • FleetOS generates supplier pool for Robo-Hub

  • Robo-Hub generates high-value customers for FleetOS suppliers

  • Robo-Dapp generates guaranteed volume for Robo-Hub suppliers


10. Roadmap

Phase 1: FleetOS Foundation (Current - Month 3)

Weeks 1-2 (βœ… COMPLETE):

Week 3 (IN PROGRESS):

Month 2:

Month 3:


Phase 2: Robo-Hub MVP (Months 4-6)

Month 4:

Month 5:

Month 6:


Phase 3: Robo-Dapp MVP (Months 7-12)

Month 7-8:

Month 9-10:

Month 11-12:


Phase 4: Shared Infrastructure (Months 13-18)

Month 13-15:

Month 16-18:


Phase 5: Scale (Months 19-24)

Goals:

  • FleetOS: 50,000 suppliers, 100,000 relationships

  • Robo-Hub: 500 Shepherds, $50M contract value

  • Robo-Dapp: 50 active fleets, $10M transaction volume

  • Shared platform: 70%+ code reuse across products


Appendix A: Terminology

Universal Terms (All Products)

Term
Definition

User

Any person using T420 ecosystem (supplier, fleet, Shepherd)

Relationship

Connection between fleet and supplier (repeatable service relationship)

Service Request

Work order for specific service (tire rotation, charging, etc.)

Notification

Message sent via WhatsApp, email, or SMS

Intelligence

Derived insights from historical behavior (response times, patterns)

FleetOS-Specific Terms

Term
Definition

Service Provider

Mobile operator offering fleet services (marketing term)

Supplier

Same as Service Provider (internal term)

Fleet

Company with vehicles needing maintenance

Magic Link

One-click authentication URL (no password)

TodayView

Supplier dashboard showing today's service requests

Health Score

Relationship quality indicator (πŸŸ’πŸŸ‘πŸ”΄)

Robo-Hub-Specific Terms

Term
Definition

Shepherd

Entrepreneur who buys zone license and operates robotaxi fleet

Zone License

NFT granting exclusive right to operate in geographic zone

RFQ

Request for Quote (Shepherd solicits bids from suppliers)

Contract

Formal service agreement between Shepherd and supplier

T420 Connect

API integration allowing suppliers to receive work orders

Robo-Dapp-Specific Terms

Term
Definition

Work Order

On-chain service request (similar to Service Request)

Smart Contract Payment

Automated payment settlement on blockchain

42/42/16 Split

Revenue distribution (42% Shepherd, 42% Supplier, 16% Protocol)

Staking

Locking T420 tokens for benefits (priority dispatch, governance)

DePIN

Decentralized Physical Infrastructure Network


Appendix B: Success Criteria

FleetOS Success (Month 12)

  • βœ… 10,000+ suppliers signed up

  • βœ… 25,000+ relationships created

  • βœ… 100,000+ service requests completed

  • βœ… 500+ Pro subscribers ($294K ARR)

  • βœ… 10-20x faster coordination validated

  • βœ… "Easier than WhatsApp" claim confirmed by users

  • βœ… 80%+ invite acceptance rate (viral loop working)

  • βœ… Zero supplier backlash (relationship-first approach validated)

Robo-Hub Success (Month 12)

  • βœ… 100+ Shepherds onboarded

  • βœ… 300+ contracts signed

  • βœ… $15M+ total contract value

  • βœ… AI-assisted procurement reduces negotiation time by 50%

  • βœ… FleetOS β†’ Robo-Hub funnel conversion: 2%

  • βœ… Contract renewal rate: 80%+

Robo-Dapp Success (Month 12)

  • βœ… 20+ Shepherds operating fleets on-chain

  • βœ… 100+ suppliers integrated via API

  • βœ… $2M+ transaction volume

  • βœ… 24-48hr payment settlement (faster than traditional invoicing)

  • βœ… <1% dispute rate

  • βœ… Robo-Hub β†’ Robo-Dapp activation: 20%

Ecosystem Success (Month 24)

  • βœ… 50,000 suppliers on FleetOS

  • βœ… 500 Shepherds on Robo-Hub

  • βœ… 50 active fleets on Robo-Dapp

  • βœ… $20M+ annual revenue across all products

  • βœ… 70%+ code reuse (shared components, database, services)

  • βœ… T420 recognized as category leader in fleet service coordination


Appendix C: Key Documents

Strategy Documents

  1. T420_ECOSYSTEM_MASTER_ARCHITECTURE.md (this document)

    • Overview of entire ecosystem

    • How products work together

    • Shared architecture

    • Roadmap

  2. fleet_os_ai_reveal_24_month_prd_strategy_build_brief.md

    • FleetOS-specific strategy

    • 24-month AI reveal roadmap

    • Phase-by-phase product evolution

    • Engineering guardrails

  3. 2️⃣ Public Manifesto_ "Intelligence, Not Automation".md

    • External-facing philosophy

    • "Intelligence, Not Automation" positioning

    • Website-ready content

  4. FLEETOS_STRATEGY_CONFLICT_ANALYSIS.md

    • Cross-reference of current implementation vs strategy

    • Conflict resolution

    • Alignment validation

Implementation Documents

  1. FLEETOS_DEMO_READY.md

    • FleetOS demo status (Weeks 1-2)

    • What's working

    • How to test

  2. FLEETOS_WEEK2_COMPLETE.md

    • Week 2 detailed documentation

    • Service request workflow

    • Notification system

    • Magic link authentication

  3. FLEETOS_INTEGRATION_GUIDE.md

    • Quick reference for developers

    • Routing setup

    • Service integration

    • Environment variables

  4. ARCHITECTURE.md (legacy - needs update)

    • Original architecture (pre-FleetOS)

    • Robo-Hub + Robo-Dapp focus

    • To be superseded by this document


Appendix D: Contact & Contributions

Document Maintained By: T420 Product Team Last Updated: December 18, 2025 Version: 1.0 Status: Living Document (expect frequent updates as we build)

Contributing:

  • All three products should reference this document when making architectural decisions

  • Propose changes via pull request with clear rationale

  • Major changes require product team consensus

  • Keep this doc updated as implementation evolves

Questions?

  • Technical architecture: See database schema + shared services sections

  • Product strategy: See product positioning + roadmap sections

  • Growth/metrics: See growth strategy + success criteria sections


Closing Thoughts

Why This Matters

We started with three separate builds. We're converging toward one elegant system.

The Vision:

  • FleetOS brings volume (100% market, viral growth)

  • Robo-Hub brings value (20% market, 74% revenue)

  • Robo-Dapp brings protocol (2% market, on-chain lock-in)

The Architecture:

  • Shared database (one graph, three views)

  • Shared components (write once, use everywhere)

  • Shared intelligence (patterns learned across products)

The Opportunity:

  • $80B market (fleet maintenance & repair)

  • Zero direct competitors (relationship-first positioning)

  • Network effects (each user adds value to all users)

  • Protocol lock-in (on-chain payments, governance, staking)

The Path:

  1. Build FleetOS (Months 0-3) β†’ Prove "easier than WhatsApp"

  2. Build Robo-Hub (Months 4-6) β†’ Monetize via contracts

  3. Build Robo-Dapp (Months 7-12) β†’ Lock in via protocol

  4. Unify platform (Months 13-18) β†’ Share everything

  5. Scale ecosystem (Months 19-24) β†’ Dominate category

We're not building three products. We're building one system that serves three markets.

Let's ship it. πŸš€


END OF DOCUMENT

Last updated

Was this helpful?