Start building
Before you build

Design the operating model before you scale the traffic.

The rules every implementation keeps, and the questions buyers ask early.

Start with invariants

Five rules anchor every implementation.

  1. 01Patients experience the customer’s brand, not Ambition Health.
  2. 02Every workforce action resolves an explicit tenant, brand, role, and environment.
  3. 03Video is a policy or clinical decision, never a universal default.
  4. 04Programs and sites publish immutable versions with evidence and rollback.
  5. 05Unknown, conflicting, stale, or incomplete dependencies block activation.
Evaluation FAQ

The operating questions buyers should ask early.

Clear boundaries before implementation prevent expensive surprises later.

01Whose brand do patients see?

Patients use the customer’s brand, support identity, legal terms, and domain. Ambition Health remains the workforce control plane and infrastructure provider.

02Who owns the patient relationship and data?

The customer operates the patient relationship under the approved service and data agreements. Tenant, brand, environment, and audience boundaries keep each workload scoped.

03How long does implementation take?

Timing depends on program complexity, states, clinical and 503A relationships, delivery path, integration depth, and approval readiness. The workspace makes every dependency and owner visible before a launch date is committed.

04Do all states require a video visit?

No. Modality is resolved from the approved program and state policy plus encounter facts and clinical escalation. Unknown or conflicting policy blocks progression instead of guessing.

05How do 503A connections work?

Each pharmacy is set up with its eligibility, product mappings and agreement. The pharmacy’s software remains the dispensing and fulfillment system of record, and order status and exceptions come back to the console.

06What can we integrate?

A hosted site under your brand, or your own front end on versioned APIs: formulary, marketing-claims rulebook, claim scan and service status, with signed webhooks and a delivery log. The API reference lists every call.

07How do payments work?

Patients pay through your storefront and the revenue is paid out to your brand. Payments turn on per brand, after that brand's launch checks pass.

Turn the blueprint into a workspace

Plan the full system in your own workspace.

Tell us what you want to launch. Once you're in, agents build your site and your launch plan.