SubFlow
Enterprise SaaS License Optimization and Reallocation
Executive Summary
CONFIDENTIAL SUBFLOW PRE-SEED FUNDING MEMO SaaS License Optimization & Reallocation To: Investors From: SubFlow Team Date: April 1, 2026 Funding: $500K Pre-Seed Executive Summary Enterprises waste $45 billion annually on SaaS licenses. Up to 30% of software licenses remain underutilized, unused, or needlessly expire. SubFlow automates license lif
Token Data Schema
What this token holds — every field is specific to SubFlow:
{
"immutable": {"license_id": "uuid", "vendor": "string", "employee_id": "string", "issue_date": "timestamp", "seats": "int"},
"mutable": {"status": "Assigned|In_Use|Reallocation_Triggered|Available|Reallocated", "owner": "string", "usage_hours": "int", "last_activity": "timestamp"},
"compliance": {"vendor_toS": "string", "audit_log": ["string"], "sso_required": "bool"}
}
User Journey
Provisions SaaS license seat
Token: license_token.status = Assigned
Uses license in SaaS app
Token: status → In_Use, usage_hours++
Employee departs, triggers offboarding
Token: status → Reallocation_Triggered
Reclaims and reassigns license
Token: status → Reallocated, new_owner_id set
Validates vendor ToS compliance
Token: audit_log appended, certified
Token Lifecycle
State machine transitions:
Why Not Just a Database?
| Approach | Portability | Mutable State | Cross-Org | Compliance |
|---|---|---|---|---|
| Traditional DB | Locked to vendor | Any field mutable | Manual reconciliation | Single audit trail |
| Public Blockchain | Portable but slow | Immutable-only | Transparent but expensive | Full transparency |
| SaaS Platform | Vendor lock-in | Centralized control | Complex APIs | Vendor-dependent |
| DUAL Token | Portable across systems | Selective mutability | Native settlement | Embedded rules |
Market Opportunity
SubFlow addresses growing need for tokenized asset management. DUAL enables native token solutions without blockchain overhead.
Business Model & Unit Economics
- Platform License: SubFlow subscription: $25K-$100K/year
- Transaction Fees: 2-5% of tokenized volume
- Compliance Services: Audits and reports: $10K-$50K/audit
- Premium Support: 24/7 monitoring: $500-$2K/month
$5-$15 per token transaction, 70% gross margin at scale.
5-Year Projections
| Year | ARR | Customers | Notes |
|---|---|---|---|
| Y1 | $500K | 5 | Pilot phase |
| Y2 | $2.5M | 25 | Product-market fit |
| Y3 | $8M | 75 | Market leadership |
| Y4 | $18M | 150 | Cross-vertical scaling |
| Y5 | $35M | 250 | Regional dominance |
Competitive Positioning
| Competitor | Weakness | DUAL Advantage |
|---|---|---|
| Legacy DB Providers | No cross-org portability | Distributed settlement |
| Public Blockchains | Immutable-only, expensive | Mutable state, low-cost |
| SaaS Leaders | Vendor lock-in, limited composability | Open standard |
| Custom DIY | High build/maintenance cost | Out-of-box solution |
Go-to-Market
Target 5 pilot customers, prove ROI
Expand to 25+ customers, build partnerships
Cross-vertical expansion, 100+ customers
90-Day MVP
- Core token schema with immutable/mutable/compliance layers
- State machine with 5-6 transitions
- REST API for token lifecycle operations
- Audit logging and compliance reporting
- Basic dashboard for monitoring
- Integration test suite with 80%+ coverage
Risk Factors
Tokenization may require securities licenses
Mitigation: Engage legal counsel early, target compliant verticals
Enterprises slow to adopt new standards
Mitigation: Focus on high-ROI problems, build proof-of-concept
Incumbents may adopt tokenization
Mitigation: Build network effects, maintain innovation velocity
State consistency in distributed systems
Mitigation: ACID compliance, comprehensive testing, gradual rollout
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.
## Design the SubFlow Token Architecture Your goal: Create a complete DUAL token schema that enables Enterprise SaaS License Optimization and Reallocation on the DUAL platform. **Start with:** 1. Immutable fields (identity, timestamps, core properties) 2. Mutable fields (status, ownership, metrics) 3. Compliance rules (state transition constraints) 4. Token lifecycle (5-6 state machine) 5. User journey with named actors 6. Competitive comparison **Key constraints:** - Every field must have clear owner and mutability rule - Every state transition must be audit-logged - Design for 10x scale, not just 2x - Focus on cross-org composability **Deliverables:** - Token schema JSON (15+ fields) - State diagram (5-6 states) - 5-6 user journey steps - Compliance rule set - Integration playbook