IntentOne · Tenant Manager · Product roadmap

See every client first, then health, then setup that runs itself.

The goal: one internal place where Intent HQ staff see every client and every environment we run. Where it runs, which version it's on, whether it's healthy, what we bill and what it costs us. Later, new clients get set up automatically. Customer Success, Delivery, Cost and Tech Ops all use the same data, each with their own view.

KEY Click to filter
Product delivery
V1No dates yet

Each milestone gives staff something new they can use. The screens and the data behind them ship together.

Open questions

  1. Where the client and environment list lives: inside the new sign-in system (option A) or in its own store (option B)? Engineering recommends B. The CTO decides.
  2. Single sign-in: is Zitadel our one sign-in system, with WorkOS, Google and Okta plugged in underneath?
  3. Screens or questions first: do we build screens first, or let staff ask an AI assistant and add screens later?
  4. Who can see what: is one read-only role enough for all four teams, or does Cost need its own?
  5. Shared environments: can one environment serve many clients? Shared ones already do.

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.

Privacy: what leaves an environment

Applies from the first heartbeat.

  • Counts only. Rates, durations, states, versions and money.
  • No people. No profile IDs, device IDs, emails, names or phone numbers.
  • No content. No message text, questions, previews or search terms.
  • Small numbers hidden. User counts under 5 aren't shown.
  • Two identifiers only. The client ID and the environment ID.
  • Logs stay where they are. The Tenant Manager stores no logs.
  • Client clouds. The client can see exactly which fields leave.

Out of scope / Later

  • Billing clients. The Tenant Manager shows billing but never bills anyone.
  • Secrets. It only stores references, never passwords, keys or tokens.
  • Manual "break-glass" deploy. Only for rare emergencies, reviewed and logged.
  • AWS Marketplace. Google Marketplace first, AWS later.
  • SAML sign-in. Only if a named customer needs it.
  • Directory sync (SCIM). Deferred on purpose.
  • Freezing a single service. Freezes cover a whole environment.