Delivery Hub
Scaling Roadmap
From foundation to autonomy -- five phases to a self-running delivery platform.
Phase 1: Foundation
What was built
Delivered
CMT-driven workflow engine (5 workflow types, 71 stages)
Multi-entity data model (NetworkEntity isolation)
Sync Engine V3 (push/pull, echo suppression, GlobalSourceId)
Portal + REST API for non-Salesforce clients
Document engine (invoices, agreements, status reports)
Ghost Recorder activity tracking
Architecture Principles
The overarching design philosophy that guides every phase of the roadmap.
CMT as the extension mechanism
No code changes for new workflows. Deploy Custom Metadata records and the entire stack -- board, dashboard, ETA service, escalations -- automatically adapts.
Entity isolation at the query layer
Safe multi-tenancy without row-level security complexity. Every controller filters by NetworkEntity, so each client sees only their data across boards, dashboards, and API.
Single package, single repo
Simplicity over modularity. The CMT hierarchy IS the extension mechanism -- no need for separate repos or packages. One version to track across all orgs.
API-first for non-SF
REST endpoints mirror every LWC capability. Any system can integrate -- CI/CD, mobile, web, CLI. Token-based document access, no auth needed for public links.
Progressive automation
Everything starts manual, gets automated incrementally. The action plan has 6 phases -- each one removes a manual step until the platform runs itself.
Status Summary
Where each phase stands today.
| Phase | Status | Key Metric |
|---|---|---|
1Foundation | Done | 5 workflow types, 71 stages |
2Polish | Done | 89% coverage, 820+ tests |
3Self-Service | Done | One-click onboarding |
4Intelligence | Done | 150+ classes, 63 LWCs, 866+ tests |
5Autonomy | Planned | 6 automation phases |
Related Pages
Dive deeper into the architecture, intelligence features, or the full automation action plan.