← Portfolio
Build Orchestrator
Build plan + OKRs, RAG milestones, build coordination, the delivery gate, spend / runway and the Scaleup handover to Growth.
Venture Guide: Servicely — The critical hypothesis lacks register-grade evidence — lock it before you trust the sizing.
Hand over to Growth
T2
Trigger the Growth OS handover at Scaleup (locked until ready, with reason).
Connect to Exponic Growth OS
Not connectedDevelop this venture on Exponic’s platform: record the intent at the Go decision, choose the build path in build coordination, and connect at Scaleup. Connecting makes the venture a managed tenant — its Growth OS reads are consent-gated from that point on.
IntentStep 5 · Go decision
Not recorded yet — set the intended build path at the Go decision (step 5).
Opt-inStep 7 · Build coordination
Choose the build path below — in-studio, or connect to Exponic Growth OS.
ConnectedStep 7 · Growth handover
Connect at Scaleup with the handover below (locked until the venture is incorporated and Scaleup-ready).
The connection is recorded via the live commit below; Growth OS reads only once the venture is connected and consented (not yet wired to live Exponic data).
ServicelyService-tech / field servicesNo Growth OS tenant yet
Servicely has not reached this step yet — it is at Validation (step 3).
Stage
Validation
Build-readiness
4/10
Gate
VALIDATING
Incorporated
Not yet
Growth OS — no tenant yet (binds at the Scaleup handover)
No Growth OS tenant yet. A venture binds its Growth OS only when it incorporates (step 6) and reaches the Scaleup handover (step 7) — until then there are no platform packages to read, and the studio never fabricates them.
Depth
Live commit · demo store
Locked — this venture has not incorporated yet (step 6). Seed the cap-table before the Growth handover.
TALK TO THE PROGRAM — about this sub-step