GridFlow
Demand-Response Verification and Settlement Ledger
Executive Summary
GridFlow is a demand-response settlement ledger that verifies DR events, mints credits, and reconciles payments for Community Choice Aggregators (CCAs), Virtual Power Plant (VPP) operators, and deman Large, high-growth market with strong regulatory tailwinds.
Token Data Schema
What this token holds — every field is specific to GridFlow:
{
"immutable": {
"event_id": "uuid v4",
"utility_id": "ISO operator code (CAISO|PJM|ERCOT)",
"aggregator_id": "aggregator entity id",
"site_ids": ["site_1", "site_2", ...],
"event_start": "ISO 8601 timestamp",
"event_end": "ISO 8601 timestamp",
"baseline_consumption_kw": "float, pre-event average"
},
"mutable": {
"event_status": "Active|Closed|Disputed",
"reward_rate_usd_per_kwh": "float",
"reduction_target_kw": "float",
"actual_consumption_kw": "float, real-time",
"verified_reduction_kw": "float, after audit"
},
"compliance": {
"meter_data_hash": "SHA-256 of meter log",
"anomaly_score": "0-100, fraud risk",
"iso_audit_status": "Pending|Verified|Disputed",
"iso_audit_log": ["check_1", "check_2", ...],
"settlement_amount_usd": "float"
}
}User Journey
Deploys demand-response event; specifies energy reduction target and reward rate.
Token: event_id, reduction_target_kw, reward_rate_usd_per_kwh, event_window
Enrolls customer sites; broadcasts event details; calculates baseline consumption.
Token: site_ids[], baseline_consumption, aggregator_fee, event_status=Active
Shifts load: reduces consumption during peak window; smart meter reports reduction real-time.
Token: actual_consumption, reduction_achieved_kw, performance_pct, meter_timestamp
Validates consumption reduction against baseline; flags anomalies or gaming.
Token: verified_reduction_kw, anomaly_score, verification_status, audit_log_entry
Calculates reward: verified_kw × reward_rate; distributes to aggregator and customer.
Token: reward_amount_usd, customer_share, aggregator_share, settlement_status=Paid
Token Lifecycle
State machine transitions:
Why Not Just a Database?
| Approach | Portability | Mutable State | Cross-Org | Compliance |
|---|---|---|---|---|
| Traditional Database | Utility owns consumption data; customer cannot port | Consumption edited post-hoc; gameable | Single ISO; no inter-region settlement | Manual audit; offline meter logs not integrated |
| Blockchain (Public) | Fully transparent consumption data (privacy risk) | Immutable consumption; but rewards still mutable | Cross-region possible; too slow for real-time settlement | No meter validation; on-chain governance too slow |
| SaaS Platform (Stem) | Customer data in Stem silo; cannot switch aggregators | Consumption and reward mutable; opaque calculations | Single aggregator only | Proprietary audit; ISO cannot independently verify |
| DUAL Token | Customer owns consumption & reward token; aggregator-agnostic | Mutable demand event + immutable consumption record | ISO, aggregator, customer all see real-time settlement | Meter data cryptographically verified; ISO audit-ready |
Market Opportunity
Demand-response verification and settlement ledger for one CCA or virtual power plant operator. Smart meters report reduced demand; DUAL tokens represent DR credits. Event Bus verifies against baseline; immutable audit satisfies FERC/state PUC verification.
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
Deploy with CAISO or PJM; enroll 100 sites via 1-2 aggregators; validate meter integration & settlement accuracy.
Onboard Stem, Sunrun, Fluence; expand to 500+ sites; launch ERCOT & ISO-NE pilots; establish settlement SLA.
Become standard settlement layer for all US ISOs; 10,000+ enrolled sites; $50M+ annual demand-response rewards flowing through platform.
90-Day MVP
- Real-time consumption data ingestion from smart meters (AMERA/OpenADR protocol)
- Demand-response event orchestration engine (target allocation, verification rules)
- Baseline consumption calculation with anomaly detection
- Settlement calculation & distribution to aggregators and customers
- ISO audit integration with cryptographic verification of meter data
- Aggregator API for enrollment and customer attribution
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.
# GridFlow Token Deep-Dive You are building the token system for GridFlow on DUAL Network. ## Context - **Concept**: GridFlow - **Alias**: Demand-Response Verification and Settlement 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.