01 — Core Architecture
One Platform, Specialty Workspaces
NXTLVL OS is the platform. VZN and DNTL are the experiences.
There is one software platform — NXTLVL OS — with a single codebase, single login, and shared infrastructure. Practitioners never see 'NXTLVL OS.' They see their specialty workspace: VZN practices log in and see VZN. DNTL practices log in and see DNTL. The platform is invisible infrastructure. Cross-specialty capabilities — Revenue Intelligence, coaching tools, membership management, community — live at the platform level and are available to every workspace.
Platform Architecture
NXTLVL OS (the platform everyone runs on)
VZN
Workspace
DNTL
Workspace
NXTLVL
Membership
Revenue Intelligence (shared layer)
Patient Analytics · Payment Reconciliation · Cost Analysis · Practice Performance
Coaching · Content · Community · Membership Management
02 — Workspaces
What an optometry practice sees when they log in. Contains: Quote Tool, optical inventory, frame management, vision-specific clinical workflows, and optical-specific Revenue Intelligence metrics.
The practitioner thinks 'I use VZN' — the platform underneath is invisible.
What a dental practice sees when they log in. Contains: treatment planning, dental lab management, hygiene workflows, and dental-specific Revenue Intelligence metrics.
The practitioner thinks 'I use DNTL' — same relationship as VZN to the platform.
Future workspace — available when both VZN. and DNTL. operating models are deployed together in one practice. Practices running both specialties will see both workspaces unified under one login — one patient membership that covers dental + vision.
The ultimate proof of the integrated care thesis. Current dental deployments use the VZN workspace (VZN. Level 3).
For practices that want intelligence + coaching but aren't on a VZN or DNTL operating model. Revenue Intelligence is the anchor feature. NXTLVL-branded experience.
This is where the NXTLVL brand is the user-facing identity.
03 — Shared Platform Capabilities
These capabilities live at the NXTLVL OS level — not inside any single workspace. They're available across all specialty workspaces and the standalone membership.
Revenue Intelligence
Healthcare-native financial analytics: patient analytics, payment reconciliation, cost analysis. Each workspace surfaces specialty-specific metrics, but the intelligence engine is shared.
Capability name, not a product. No separate brand, domain, or login.
Coaching & Content
Business education, frameworks, and playbooks for practice owners. Cross-specialty knowledge that applies regardless of whether you're in vision, dental, or both.
Delivered through the workspace experience, not as a standalone tool.
Community
Peer-to-peer network of practice owners sharing operational knowledge. Cross-specialty by nature — the same business problems exist regardless of specialty.
Accessible from any workspace or the standalone membership.
Membership Management
Patient membership plan management — enrollment, billing, renewals, cross-specialty benefits. Handles the unified membership that covers dental + vision in DNTL.VZN practices.
Platform-level because memberships can span specialties.
04 — Naming Rules
| Thing | Call it | Never call it |
|---|---|---|
| The platform / software | NXTLVL OS (internal), or just 'the platform' | VZN OS — the platform is cross-specialty |
| What VZN practices log into | VZN (their workspace) | NXTLVL — they don't care about the platform name |
| What DNTL practices log into | DNTL (their workspace) | NXTLVL — same reason |
| The financial analytics layer | Revenue Intelligence (capability name) | A separate product with its own brand or domain |
| The standalone membership | NXTLVL Membership | Revenue Intelligence (the membership is broader) |
| The optical quoting software | VZN Quote Tool | NXTLVL Quote Tool |
| Future specialties | New brand per specialty (like VZN/DNTL pattern) | Extensions of VZN or DNTL |
05 — Domain Strategy
Marketing sites are brand-specific. Software is unified.
Practitioners discover us through specialty brands (VZN, DNTL). They buy through specialty brands. Once they're customers, they log into one platform. This mirrors the operating model — you enter through a specialty, but you're on the NXTLVL platform.
Marketing & Company Domains
nxtlvl.care Company site, investor info, master brand NXTLVL vzn.care Vision operating model marketing, VZN landing pages VZN dntl.care Dental operating model marketing (when ready) DNTL dntlvzn.com Flagship product marketing, dental-first landing pages DNTL.VZN Software / App Domain
app.nxtlvl.care
The single software login for all practitioners. VZN practices log in here and see VZN workspace. DNTL practices log in here and see DNTL workspace. DNTL.VZN practices see combined workspace. NXTLVL Members see membership dashboard.
app.vzn.care → app.nxtlvl.care Loads VZN workspace app.dntl.care → app.nxtlvl.care Loads DNTL workspace Vanity domains let a VZN practice feel like they're 'using VZN' while technically on NXTLVL OS. The redirect is invisible.
Domains Not Needed
revenueintelligence.com (or similar) It's a capability, not a product — no separate domain nxtlvlos.com 'NXTLVL OS' is an internal architecture term, not user-facing branding Separate domains per feature Features live inside workspaces, not as standalone products 06 — Why This Architecture Works
One login, one platform
Practitioners don't juggle multiple software products.
Specialty branding preserved
A VZN practice identifies with VZN, not NXTLVL. The platform is invisible infrastructure.
Cross-selling built in
A VZN practice already has access to NXTLVL capabilities; adding DNTL is just activating another workspace.
Revenue Intelligence scales
It's not a vision product or dental product — it's a platform capability that gets better with each specialty added.
Future specialties are easy
Audiology, esthetics, etc. just become new workspaces within NXTLVL OS, each with their own brand.
Domain simplicity
One app domain, specialty-specific marketing domains, no sprawl.
Matches the business model
Practices buy an operating model (VZN/DNTL), not software. The software is embedded in the model.