3-Month Target
6,000
Customers
EML Scale Readiness
EML Requires Scale-Ready Visibility From the Start
The system must be ready for 6,000 customers in 3 months, 100,000 in 12 months, and 500,000 in 2-3 years. Manual review will not hold at that scale.
12-Month Target
100,000
Customers
2-3 Year Target
500,000
Customers
Readiness Score
44 / 100
Current average readiness
Open Dependencies
3
API, customer records, collections feed
Reporting Automation
35%
Current readiness
Scale timeline
Customer growth targets
3 months6,000
12 months100,000
2-3 years500,000
Projected vending events
Illustrative daily event volume
6,000 customers18,000
100,000 customers300,000
500,000 customers1,500,000
Operational pressure indicators
Projected support tickets
120 daily at 6,000 customers; 2,000+ daily at 100,000 customers
Projected asset signals
Meter heartbeat, vending status, customer issue, gateway health, tariff records
Data volume implications
Bulk ingestion, event filtering, alert queues, audit logs, and report automation
Monitoring requirements
Signal freshness, failed event classification, health scoring, and exception ownership
Collection visibility requirements
Expected vs actual collections, weak zones, failed vending, payment delay indicators
Staffing implications
Role-based queues and escalation logic before operational teams are overloaded
What breaks if this is managed manually?
Customer complaints become the first signal of system failure.
Finance reconciliation becomes delayed and disputed.
Device events cannot be reviewed one by one.
Customer service queues grow without asset or revenue context.
Management reports depend on manual summaries instead of operating evidence.
What the platform must handle before scale
Automated data feeds and searchable customer or asset records.
Queue-based alerts with owner, severity, age, and next action.
Bulk data handling, audit logs, API governance, and performance testing.
Role-based dashboards for finance, operations, technical, and executive users.
Automated reports tied to live exceptions and FundCo AI actions.
EML makes the scale issue clear. The platform must be designed as infrastructure, not as a small internal dashboard.