Phase A
Decide
Phase B · MVP
See every client and environment
Phase C
Know when something is wrong
Phase D
Know where data goes
Phase E
Setup runs itself
Vision
Long term
Milestonewhat staff get
M0
Agreed scope
Engineering knows exactly what to build and in what order.
M1
Every environment in one list
Staff see where each environment runs, which version it's on and whether it's frozen.
M2
A page per client
Customer Success sees a client's environments, plan, billing, running cost and contacts.
M3
Health and alerts
Staff know when an environment is unhealthy or stops reporting.
M4
Product usage per client
Staff see whether a client is actually using the product.
M5
Where client data goes
Customer Success can answer security and data-residency questions with evidence.
M6
Client setup runs itself
A sign-up or sales order sets up the client. Staff only step in when it fails.
Vision
Contract to live, no engineering
Works the same for every kind of environment.
Tenant Managerscreens
- One design agreed
- List of every field and where it comes from
- Environments list: cloud, region, version, freeze
- Filters by stage, region and platform
- A default view per team
- Read-only, no buttons
- Clients list: environment, how they joined, active users
- Client page: plan, contacts
- Billing from Orb
- Running cost per environment
- Health status per environment
- Alert when one stops reporting
- Error counts by type
- Active users and campaigns on the client page
- Counts only, small numbers hidden
- Data flow view per client
- What leaves the environment
- Residency per data store
- Setup runs screen: which need attention
- Retry, skip with a reason or cancel
- Audit log of every change
Contract to live
Data and platformwhat the screens need
- Decide where the client and environment list lives
- Decide the single sign-in
- Decide who can see what
- Store of environments and their clients
- Versions read from deployments
- Freeze windows read from release rules
- Staff sign-in with a read-only role
- Orb billing link (works today)
- Cloud cost from FinOps
- Contacts per client
- Each environment sends a heartbeat every minute (new)
- Offline sites send a signed file instead
- Fix Mixpanel receiving raw search text first
- Then read usage counts
- Agreed list of regions
- List of what each third party receives
- Connector keys created automatically (by hand today)
- Retry when the Orb link fails
- Marketplace purchases start setup
- Find the sales-order system
Foundationswork underneath, not milestones
Sign-in readinessTest WorkOS working under Zitadel. The new sign-in can't be the only way in until this works.
Heartbeat collectorDoesn't exist yet. The biggest piece of new work for health.
Privacy rules agreed with the DPOOnly counts leave an environment. No names, emails, phone numbers or message text.
Sales-order system identifiedNobody knows yet which system sales orders come from.