A buyer-ready walkthrough from public signup or SSO into onboarding, clinic launch, Smart Insights, and AI review.
Public signupOwner onboardingClinic scorecardAI review
Workflow
How This Flow Lands In The Product
1
Public plan catalog
Open the public plans page first so buyers see the commercial story before they see the admin shell.
2
Public signup or SSO
Show email and password signup plus Microsoft or Google SSO using the same central identity stack.
3
Owner onboarding
Walk through clinic basics, branding, demo data choice, readiness check, and launch clinic from the self-serve onboarding surface.
4
Clinic switcher and Demo Concierge
Show assigned clinics, healthy versus degraded demo state, and one-click provision or reset actions with evidence and smoke status.
5
Tenant dashboard
Open the buyer-facing clinic scorecard and readiness cards to prove the product fails soft when schema, queue, or demo data are incomplete.
6
Smart Insights
Move into Smart Insights for daily, weekly, and executive summaries that frame operations before AI review.
7
AI Run Log
Show queued, stale, failed, and approved runs with source summary, draft preview, freshness badges, and regenerate lineage.
8
AI Settings
Prove provider health, capability toggles, retention, adoption counters, and ROI signals are visible to clinic admins.
9
Approve a draft
Open a patient-safe draft, point out redaction badges, and approve, discard, or regenerate it.
10
Return to platform health
Close on cross-clinic health, demo readiness, subscription posture, and usage visibility without exposing PHI at platform level.
Details
Two Acceptance Paths
Operix now has two first-class launch stories and both must pass before a release is considered demo-ready.
Public path: public signup to verify or auth to checkout or trial to owner onboarding to clinic launch to clinic switch to tenant dashboard to Smart Insights to AI Run Log to AI Settings to Platform Health.
Admin path: platform login to provision or select clinic to clinic switch to tenant dashboard to Smart Insights to AI Run Log to AI Settings to Platform Health.
Healthy demos prove the polished buyer story, while degraded demos prove that blocked readiness is visible and repairable rather than hidden behind 500 errors.
Details
What Sells The Product
The strongest demo arc is not the raw number of modules. It is the progression from platform control into guided onboarding, clinic proof, and AI review with explicit human control.
Lead with one URL and many clinics to frame the product as a platform, not a single-site app.
Use the public plan catalog, signup, and dual-SSO entry to prove the SaaS is self-serve as well as sales-assisted.
Use the onboarding wizard and demo concierge to show that owner launch, platform setup, demo reset, and readiness live in one control plane.
Use the clinic scorecard and role-shaped dashboard summaries to prove the product is operationally legible before you dive into modules.
Use Smart Insights and AI Run Log to show leverage without overpromising autonomous medicine.
Close on reviewability, audit, permission gating, and non-PHI platform oversight.
The commercial story is visible before any admin needs to intervene.Platform switcher is the buyer's first mental model for the product.Smart Insights turns operational activity into a visible narrative.The review console makes AI safe, inspectable, and operationally useful.
Details
Demo Seed Expectations
The buyer demo should never depend on ad hoc manual cleanup before a meeting. Use deterministic healthy and degraded demo states and keep evidence status visible before every session.
On live installs, run php artisan db:seed --class=Database\Seeders\LiveDemoSeeder --force to create or refresh demo@Operix.test and the sales demo clinic without resetting the current admin account.
Use Demo Concierge to provision or reset a clinic into healthy demo or degraded demo state without touching the rest of the platform shell.
Seed AI runs in pending review, stale, failed, and approved states before capture.
Seed communications backlog, plan posture, and scorecard signals so the dashboard tells a complete buyer story.
Reset a clinic with Operix:reset-demo --clinic={tenant} before buyer-facing screenshots or meetings.
Keep one clinic intentionally incomplete so readiness cards can prove fail-soft behavior instead of hand-waving around breakage.
Refresh cached platform health, commercial snapshots, and evidence or smoke status before screen capture or live demo.