Patient portal, membership billing, and lab-credit token economy —
unified across the network, branded per site.
VBWD is positioned for clinic groups and lab networks operating 10–500 sites,
not individual practitioners. Multi-tenant routing, per-site branding,
centralized billing, multi-locale patient portal, token-economy primitive
for test credits or membership tiers. Compliance work (HIPAA / GDPR Art 9)
is implemented by certified partner agencies on top of the base platform.
GDPR-grade base platform HIPAA / Art 9 via partner
Time to first site
90 days (network rollout: 6–12 months)
Problem
VBWD for Networks · Problem
Why clinic networks reach a fragmentation wall at ~20 sites.
A network is not a federation of websites.
Most clinic groups grow site-by-site. Each new acquisition arrives with its
own appointment system, its own website CMS, its own billing tool, its own
patient list. After 5 sites it's annoying; after 20 sites it's a strategic
liability. The network can't see consolidated revenue, can't run a unified
loyalty program, can't ship a single patient app, can't enforce branding,
and can't comply with anything at scale.
▤
N billing tools, N reports
Each site invoices through whatever it inherited. Month-end consolidation
is a spreadsheet job. VAT compliance becomes per-site work. Revenue
recognition is impossible to automate. The CFO is the bottleneck.
⌖
N patient portals
A patient who moves between two sites has to register twice, gets two
different emails, sees two different brand identities. The network's
promise of "one experience" is broken at the digital surface.
⚠
N compliance footprints
Per-site GDPR consent records, per-site data residency, per-site
cookie banners. Audit-readiness varies. One slow site puts the whole
network's compliance posture at risk.
The honest framing. The compliance heavy-lift (HIPAA-grade
storage in the US, GDPR Article 9 in EU, e-prescription rails in DACH) is
a partner-agency conversation, not a base-platform feature. VBWD ships
the unification layer. Compliance is a deployment-level workstream that
a certified partner does on top.
VBWD for Networks · Problem
02 / 12
Solution
VBWD for Networks · Solution
One backend, every site, branded per-tenant.
One platform. Per-site brand. Network-wide data.
VBWD's multi-tenant routing lets a single platform instance serve N sites,
each on its own subdomain or path-prefix, each with its own branding, its
own CMS pages, its own staff RBAC, its own appointment slot rules — while
the patient, billing, invoice, payment, and analytics surfaces are unified
at the network level. The network's IT team operates one platform, not N.
Patient portal
One identity, every site
Patient registers once at the network level. Books appointments at any
site. Sees invoices and history from every site in one timeline.
Multilingual; per-site theme applied based on which site the patient
is currently visiting.
Single user table · per-site routing
Membership + plans
Subscription billing at scale
Network-level membership plans (annual checkup package, lab credit
bundle, family plan). Per-site upgrade flows, central billing.
Per-membership token allocation for "X tests included" or "Y appointments
included" semantics.
VBWD subscriptions + token economy
Reporting + RBAC
Network-wide visibility, site-level autonomy
Network CFO sees consolidated revenue. Site managers see their own.
Staff RBAC enforces "this nurse can manage these patients at this site."
Audit log captures every action with site + actor identity.
Tenant-scoped RBAC · cross-site analytics
What VBWD does NOT replace. Your EMR (Epic, Cerner, local
equivalents). Your lab-results system. Your insurance-claim adjudicator. Your
e-prescription terminal. VBWD is the patient-facing + billing-facing layer;
it integrates with the clinical systems via webhooks and REST.
VBWD for Networks · Solution
03 / 12
Features
VBWD for Networks · Feature breadth
Network-grade primitives — already on the platform.
On your network's infrastructure or a HIPAA-eligible hyperscaler. Data residency in your control.
VBWD for Networks · Features
04 / 12
Plugin · Mainchat
VBWD for Networks · Patient-facing chat
A patient-facing chat that routes by site, by service, and by language.
Mainchat is the public chat surface — sits on every site's homepage,
contact page, services page. Network-level intelligence: a patient
landing on the Munich clinic site asks about "blood test pricing", the
chat answers from the Munich price list, in German, and offers booking
slots at Munich. The same patient on the Hamburg site gets Hamburg
slots in the same conversation primitive.
⌖
Site-aware routing
The widget knows which site the patient is on. Booking offers,
staff availability, and pricing come from that site's tenant scope.
Cross-site referrals are explicit ("we can refer you to our Berlin
site if you'd prefer") — never accidental.
▤
KB-aware from the CMS
FAQ answers pulled from your network's CMS — house rules, insurance
accepted, parking, opening hours. Marketing edits a page; the chat
answers update. No medical-grade NLU pretending to be a doctor.
📞
Triage + hand-off
Bot greets, classifies (admin question / booking / billing /
clinical concern), and either answers from the KB, books a slot, or
escalates to a human at the right site. Clinical questions are
always escalated, never answered.
⚠
Not a medical advisor
Mainchat answers logistical and administrative questions only.
"Where's the clinic?" Yes. "Should I be worried about this symptom?"
No — routed immediately to a human triage workflow with timestamp
captured for medico-legal records.
↯
Audit log + retention
Every conversation logged with timestamp, site, locale, classification.
Retention policy per jurisdiction (configurable by partner during
compliance setup). Conversations that touch PHI are flagged for
tighter retention controls.
⌘
Different from LLM-Chat
Mainchat is FREE for the patient — no token metering, no
generative output. It's a structured, KB-backed surface. LLM-Chat
(separate plugin) is for metered AI features where applicable.
Available add-on: Token-Exchange. The Mainchat plugin
ships with a Token-Exchange feature available for clinic-network
installations — patients gift test credits to family members, admin
transfers credits between sites, support tips for after-hours response.
Activate during deployment; no extra license tier required.
Why networks deploy this first. Mainchat is the lowest-risk
patient-facing AI surface — answers logistical questions, never clinical
ones, fully audited. A network typically lights it up in week 2 of the
pilot at one site, sees a 20–35% reduction in phone-call FAQ load,
and rolls it out network-wide by month 3.
VBWD for Networks · Mainchat
05 / 12
Compliance honesty
VBWD for Networks · What we ship vs what the partner builds
The honest compliance picture. Read this before the demo.
Healthcare compliance is the most consequential procurement question, and
we'd rather lay it on the table than have you discover the boundary three
months into evaluation. VBWD's base platform is GDPR-grade and engineered
to support healthcare deployments; HIPAA-eligible deployment, country-
specific e-prescription rails, and DiGA-equivalent certifications are
implementation-level work done by certified partner agencies.
What VBWD base platform ships today
GDPR-grade architecture. Per-user consent records, right-to-erasure tooling, audit log, encryption at rest (DB-level), encryption in transit (TLS-only).
Self-hosted deployment. You control where data lives, who has shell access, how backups are encrypted, where they sit.
Telemedicine video. Plug-in for Whereby, Doxy.me, or proprietary stack.
Compliance audit + sign-off. Annual review by a qualified auditor on the partner agency's bench.
Why this structure. Healthcare compliance is country- and
jurisdiction-specific in ways a generic platform can't pretend to solve.
Certified partners specialize in their regions and bring the audit-trail,
legal sign-off, and ongoing recertification. We do not ship a
HIPAA badge we can't honor. We do ship the platform that those
partners build on.
VBWD for Networks · Compliance
06 / 12
Pricing
VBWD for Networks · Pricing
Per-network licensing. No per-patient fees.
Network-scale platforms typically charge per-patient, per-site, or per-user
— at clinic-network volumes (50K–500K patients, 10–500 sites), those
metering schemes balloon into 5–6 figures monthly. VBWD licenses per network,
flat annual fee, regardless of patient count. The cost of partner
compliance work is separate (negotiated with the agency).
Network Starter
Up to 10 sites · pilot phase
First-year discount for networks evaluating VBWD. Includes Professional
support SLA, 1 architecture review with our team, partner-agency
introduction for compliance work. Renewable.
$9,999 / first year · $14,999 / renewal
Network Standard
Up to 100 sites · production
Full Enterprise support (4h SLA, dedicated engineer), 40h custom plugin
dev / year, quarterly architecture reviews, partner-agency co-selling
for new compliance regions.
$29,999 / year
Network Plus
100+ sites · multi-country
Multi-region deployments, dedicated engineering capacity, on-call SLA,
co-development of network-specific features. Custom contract with
capped-cost guarantee.
From $59,999 / year
The price of NOT having this. Most clinic networks at 20+
sites are paying $5K–$30K per month combined for fragmented appointment
tools, billing systems, patient portals, and integration glue. VBWD
consolidates the platform layer for $2,500–$5,000 per month, plus
partner-agency compliance work. The integration glue you no longer build
is the line item that pays for the whole platform.
VBWD for Networks · Pricing
07 / 12
Next step
Section opener
Ready to unify the network?
Three paths to one network platform.
Network briefing · 3-site pilot · Healthcare-IT partner.
VBWD for Networks · Next step
08 / 12
CTA · Briefing
Network briefing call
60 minutes. Your network's CFO, CIO, and us.
This is a B2B2B conversation. Network briefings are 60 minutes, scheduled at
the network HQ (in person or video), and include both the CFO (who cares
about billing consolidation, revenue visibility, vendor reduction) and the
CIO (who cares about EMR integration, compliance, deployment topology). We
bring an architecture-grade view of your current footprint and a 12-month
rollout plan that matches your network's reality.
What we cover in the briefing
Map of your current SaaS surface (appointment, billing, portal, CMS).
Cost-consolidation projection — what stays, what VBWD replaces, what stays separate.
EMR integration strategy (HL7 / FHIR / vendor API) for your specific systems.
Compliance pathway: which partner agency handles your jurisdiction(s).
12-month rollout plan — site-by-site sequencing, staff training, switchover.
Pilot-phase scope: which 3 sites first, what success looks like, exit ramp.
How to schedule
📞
Direct call
networks@vbwd.cc — include network size, countries, current vendor stack.
🤝
Via partner agency
If you're already working with a healthcare-IT consultancy, ask them to introduce. They'll handle the compliance conversation in parallel.
Not for individual practitioners. If you're a solo doctor,
a single-site dental practice, or a small clinic without a network IT team —
VBWD as positioned today is over-engineered for you. We'd rather say that
up front than waste your evaluation cycle. (We'll point you at the right
tool for your size if you ask.)
VBWD for Networks · Briefing
09 / 12
CTA · Pilot
Three-site pilot · 6 months · decision-grade
Three sites. Six months. Decision-grade pilot.
Pilots at network scale require structure. We deploy VBWD for three sites
you choose (typically: one urban, one suburban, one new acquisition still
being integrated), wire up the partner-agency compliance work, train staff,
and measure agreed metrics over six months. At the end you make a
network-wide go/no-go decision with real data, not a sales-driven
projection.
Months 1–2
Deploy + integrate
VBWD stood up. Partner agency engaged for compliance setup (HIPAA-eligible
hosting, country-specific compliance). EMR bridge for the three sites.
Branding + CMS pages migrated. Staff RBAC configured.
Pilot fee: $19,999 setup · partner work separate
Months 3–6
Run + measure
Production traffic on the three pilot sites. Weekly check-ins with our
team. Monthly metrics review with the CFO + CIO: revenue visibility,
patient NPS, staff satisfaction, integration latency, incident count.
Included in setup · no per-site monthly
Month 6 decision
Roll out or roll back
Network leadership reviews pilot data. Convert to Network Standard
license ($29,999 / year) and plan the rollout to the other sites, OR
decommission the pilot. Patient data is exportable either way under
GDPR-grade portability.
$29,999 / yr Standard if green-lit
Money-back terms. If the pilot doesn't meet the success
metrics you set at month 0, the $19,999 setup fee is refunded. Your data
is exported. The partner agency's compliance work is billable to them
separately — those terms are between you and the agency. We don't profit
from a failed pilot.
VBWD for Networks · Pilot
10 / 12
CTA · Partner
Healthcare-IT agency partner program
Healthcare-IT agencies: VBWD is your platform layer.
If you specialize in healthcare-IT (HIPAA-eligible deployments, e-prescription
adapters, FHIR integration, telemedicine, country-specific compliance) —
VBWD is the platform you ship your work on top of. Your network clients
need a unification layer; you do the compliance heavy-lift and the
integrations. We split the platform license; you keep 100% of the
compliance + integration work that your network clients pay you for.
Registered
Free · evaluation
Get certified on VBWD architecture. 20% commission on every network
license you sell. Listed in the partner directory. Partner Slack.
No annual fee.
Free / year · 20% commission
Certified Healthcare Partner
For active healthcare-IT shops
25% commission. Healthcare-specific certification track (8 weeks,
compliance modules per region). Joint architecture-review entitlement
for new prospects. Early access to FHIR / HL7 / e-prescription plugins.
$2,499 / year · 25% commission
Regional Premier
Country / region exclusivity options
30% commission. Inbound network leads in your region routed to you.
Optional exclusivity for a country/region (negotiated annually).
Featured listing. Monthly strategy call. Path to managed-services
billing on top of compliance work.
$7,499 / year · 30% commission
Partner economics — one engaged network deployment.
A 50-site clinic network pays ~$29K / year for the VBWD license (your
commission: ~$7K). The compliance + integration + custom-plugin work for
that deployment is typically $80K–$250K billed by the partner agency
(HIPAA setup, EMR bridge, telemedicine integration, custom workflows).
That margin stays with you. Apply at vbwd.cc/partner.
VBWD for Networks · Partner
11 / 12
VBWD for Clinic & Lab NetworksOne platform, every site2026
Thank you.
One platform. Every site. Network-wide visibility. The
unification layer your network needed at 20 sites and couldn't build at
50. Honest about what's base-platform and what's partner-agency work.
Sold to network leadership, deployed by healthcare-IT agencies,
run by your IT team.