FleetIQ
Fleet Maintenance Compliance and Resale Certification Ledger
Executive Summary
FleetIQ is a blockchain-based fleet maintenance tracking and resale certification platform. We tokenize vehicle maintenance records on DUAL Network, making odometer rollback fraud cryptographically im Large, high-growth market with strong regulatory tailwinds.
Token Data Schema
What this token holds — every field is specific to FleetIQ:
{
"immutable": {
"token_id": "unique identifier",
"entity_id": "primary actor",
"created_date": "ISO 8601",
"category": "concept-specific",
"version": "schema version"
},
"mutable": {
"status": "state in lifecycle",
"metadata": "custom fields",
"participant_roles": ["role1", "role2"],
"event_log": ["event1", "event2"]
},
"compliance": {
"audit_trail": "immutable transaction log",
"regulatory_status": "Compliant|Pending|Flagged",
"verification_hash": "SHA-256 proof"
}
}User Journey
Registers vehicle with VIN, emissions tier, insurance policy, and assigned route classification
Token: vehicle_token created, state = Compliant, emissions_tier = EPA_T3
Assigns vehicle to route; checks compliance status, driver license validity, and cargo restrictions
Token: route_assigned, compliance_gate = Passed, driver_license verified
Streams real-time data: mileage, fuel consumption, engine diagnostics, and geofence adherence
Token: mileage updated, fuel_efficiency logged, geofence_status = within_bounds
Detects new EPA emissions standard; checks fleet-wide compliance; flags non-compliant vehicles
Token: state → Non_Compliant_Pending, new_standard_effective_date set, retrofit_required = true
Schedules emissions retrofit; upon completion, updates certification and restores compliant status
Token: state → Compliant, emissions_tier = EPA_T4, retrofit_cert attached
Token Lifecycle
State machine transitions:
Why Not Just a Database?
| Approach | Portability | Mutable State | Cross-Org | Compliance |
|---|---|---|---|---|
| Traditional Database | Locked in vendor platform | Fully mutable; no immutable audit trail | Single-org only | Manual reconciliation |
| Blockchain (Public) | Fully transparent and portable | Immutable; cannot fix errors | Open access; privacy concerns | On-chain but lacks regulatory integration |
| SaaS Platform | Vendor lock-in; limited export | Mutable state; weak audit | Multi-tenant but hub-controlled | Proprietary format; limited interop |
| DUAL Token | Owner-controlled; portable across ecosystems | Mutable terms + immutable settlement trail | Multi-party settlement with zero-trust | Standards-based; regulatory-ready integration |
Market Opportunity
Fleet maintenance compliance and resale certification for one fleet operator. Tokens track maintenance records as mutable state. Vehicle condition certified at resale. Prevents odometer rollback fraud and false maintenance claims via immutable event log.
Business Model & Unit Economics
- SaaS Subscription: Monthly platform fee based on usage tier
- Transaction Fee: Per-transaction commission on platform flow
- Premium Support: White-glove integration and support services
$0.50-$2.00 per transaction | Gross margin: 65-75% | CAC payback: 8-12 months
5-Year Projections
| Year | ARR | Customers | Notes |
|---|---|---|---|
| Y1 | $150K | 2-3 | MVP launch, pilot customers |
| Y2 | $2M | 8-10 | 40% growth, expand to 2-3 regions |
| Y3 | $10M | 25+ | Series A scaling, feature expansion |
| Y4 | $25M | 60+ | Market expansion, strategic partnerships |
| Y5 | $50M | 120+ | Market leader, IPO readiness |
Competitive Positioning
| Competitor | Weakness | DUAL Advantage |
|---|---|---|
| Traditional Database | Single-vendor lock-in; no portability | Owner-controlled tokens; portable across ecosystems |
| Blockchain (Public) | No privacy controls; too transparent for business logic | Permissioned transparency + mutable business state |
| SaaS Platform | Vendor dependency; limited interoperability | Standards-based; integrates with any system |
Go-to-Market
Build core platform; secure 1-2 pilot customers; validate product-market fit.
Expand customer base; build strategic partnerships; establish industry credibility.
Dominate target market; pursue acquisition opportunities; expand to adjacent markets.
90-Day MVP
- Core token creation and state management interface
- Multi-party access control and role-based permissions
- Immutable event logging and audit trail
- Settlement calculation and distribution engine
- External API for third-party integrations
- Dashboard for monitoring and analytics
Risk Factors
Regulations continue to evolve; new compliance requirements may emerge requiring platform updates.
Mitigation: Build modular compliance framework; engage industry advisors; maintain active legal relationships
Customers may be slow to adopt new tools or prefer legacy workflows.
Mitigation: Land-and-expand strategy; offer training and onboarding; demonstrate ROI through time savings
Reliance on third-party services for payment processing or data exchange; service disruptions impact flow.
Mitigation: Dual provider integration; fallback manual settlement procedures; redundant infrastructure
Larger fintech/industry platforms could enter market with superior brand recognition and resources.
Mitigation: Build stickiness through compliance integrations; establish strategic partnerships; network effects
VC Pack Documents
Complete pre-seed investment package:
Get Started with AI
Prerequisites: Complete the DUAL Quick Start Guide to set up your environment and API keys before building this concept.
# FleetIQ Token Deep-Dive You are building the token system for FleetIQ on DUAL Network. ## Context - **Concept**: FleetIQ - **Alias**: Fleet Maintenance Compliance and Resale Certification Ledger - **Category**: Refined Concept - **Viability**: 9.7/10 ## Your Task 1. Review the investment memo and financial model 2. Design the immutable→mutable→compliance token schema 3. Map the user journey (6 steps with NAMED actors) 4. For each step, list which token fields mutate 5. Identify the 4 database comparison trade-offs 6. Define state machine with business event triggers ## Output Return complete JSON with all sections filled from memo data: - token_schema (15+ fields, domain-specific) - journey_steps (with real actor names) - db_comparison (4 rows comparing approaches) - competitors (3-4 with weaknesses) - projections (Y1-Y5 ARR and customer count) - risks (3-4 with category, detail, mitigation) ## Key Principles - Token = mutable business logic + immutable compliance trail - Every field must serve a purpose (no generic metadata) - Multi-party transparency without breaking privacy - Standards-based, portable across platforms Start here.