Solution building block

B2B

Business buyer first

Operator dashboard access

An operator can see workspace health, lead flow, and production readiness from one place.

Used by business operators, agencies, and internal teams to run fulfillment.

Included in: Starter, Growth, Professional

What the customer uses

A usable piece inside a launched package.

Dashboard route plus a public example operator snapshot.

How it is produced

What powers it in the deployed product.

Dashboard routes are deployed; sensitive mutations remain authenticated.

Done when

This is how you know the deliverable is complete.

Dashboard URL is present after onboarding.
Health, leads, routing, and activation status are visible.
Protected actions remain behind operator auth.

Implementation guide

Operator dashboard access is a working building block inside a complete Lead OS solution. It exists so the business buyer can understand exactly what was created, how it is used, and how completion is verified.

Start here

Read the buyer outcome first.
Confirm whether the block is B2B internal or B2B2C customer-facing.
Review the delivered artifact and backend reality before using the example.
Run or inspect the live example on this page.

Implementation steps

Use the block inside a package workspace, not as a disconnected asset.
Match the block to the client success metric before presenting it as value.
If the block touches downstream customers, verify the copy, consent, routing, and escalation expectations.
If the block depends on live account access, use safe sample or managed-handoff mode until approved access exists.
Document the next operator action in the client delivery hub.

Operating workflow

Capture or inspect the input.
Produce the visible artifact.
Route the result to the correct business or customer-facing next step.
Measure the result against the acceptance criteria.
Improve the package workflow if the artifact does not advance the promised outcome.

If unclear or blocked

If the artifact looks like a sample, treat it as a demo until connected package data is present.
If the next action requires a client-owned account, do not represent it as live until approved access exists.
If the block does not map to the selected package outcome, return to the package delivery hub.
If the customer cannot tell what to do next, use the implementation steps and acceptance checklist before handoff.

Next milestones

Today: confirm the block exists and the acceptance criteria are visible.
This week: connect it to a package workspace or run a sample scenario.
This month: use reporting evidence to decide whether the surrounding package should be optimized, expanded, or bundled.

Surface	State	Operator meaning
API	live	Public runtime is responding.
Dashboard route	live	/dashboard/control-plane is deployed.
Database	configured	Durable data requires DATABASE_URL.
Billing	configured	Stripe account access is required for live checkout.
Live sends	enabled	Provider account access and LEAD_OS_ENABLE_LIVE_SENDS=true required.

This mirrors the operator health snapshot customers should see before launch.

Loading…

Implementation steps

Use the block inside a package workspace, not as a disconnected asset.

Match the block to the client success metric before presenting it as value.

If the block touches downstream customers, verify the copy, consent, routing, and escalation expectations.

If the block depends on live account access, use safe sample or managed-handoff mode until approved access exists.

Document the next operator action in the client delivery hub.

If unclear or blocked

If the artifact looks like a sample, treat it as a demo until connected package data is present.

If the next action requires a client-owned account, do not represent it as live until approved access exists.

If the block does not map to the selected package outcome, return to the package delivery hub.

If the customer cannot tell what to do next, use the implementation steps and acceptance checklist before handoff.

Surface

State

Operator meaning

API

live

Public runtime is responding.

Dashboard route

live

/dashboard/control-plane is deployed.

Database

configured

Durable data requires DATABASE_URL.

Billing

configured

Stripe account access is required for live checkout.

Live sends

enabled

Provider account access and LEAD_OS_ENABLE_LIVE_SENDS=true required.