Founding Facility Pilot pricing is scoped by request.
VeriSight does not publish internal beta pricing as market pricing. Pilot pricing depends on facility count, monthly referral packet volume, implementation scope, workflow complexity, and support needs.
Founding Facility Pilot
Pricing is reviewed after a short workflow discussion. The goal is to scope a pilot that is credible for your admissions team and sustainable for implementation support.
Pilot pricing depends on the shape of the workflow.
Six variables move pricing. Knowing them ahead of the screening call usually saves 30 minutes and gets you a quote in the same conversation.
Facility count
Single-facility, small chain (2-5), and 6-10 facility pilots have different configuration, support, and rollout cadence. Multi-facility pilots include cross-facility analytics in the readout.
Monthly packet volume
30-60 packets/month is a typical single-facility SNF; 60-90 is a high-volume facility; portfolios scale linearly. Volume affects per-packet review cadence and the staff training approach.
Payer mix complexity
Heavy MA mix means more authorization-readiness review cycles. Heavy Medicare-A means more PDPM/margin review cycles. Both adjust which surfaces AdmitScore™ weights heavier in the workflow.
Users and roles
Admissions only, or admissions + clinical + finance + administrator? More concurrent reviewers = more configuration of the role-based score visibility (Referral Fit for all, Margin Score admin-only).
Implementation scope
Synthetic-data demo only, or live-data pilot? Live-data pilots require BAA, secure workflow contracting, and longer kick-off. Synthetic demos are lighter-touch and start sooner.
Outcome tracking depth
Basic accept/defer/decline tracking is included. Detailed payer-by-source pattern analysis or custom decision-telemetry exports are scoped separately during the workflow review.
What's in scope vs out of scope.
AdmitScore review on 60 days of live referral packets, role-based access for up to 8 users, kick-off + mid-pilot + readout calls, founder-led implementation support, decision telemetry for outcomes review, BAA and secure workflow scoping, and a written end-of-pilot recommendation.
Approved packet-intake workflows scoped during pilot kickoff, custom output format changes beyond standard configuration, multi-facility analytics dashboards, and detailed denial-pattern exports beyond the standard outcome tracking.
Replacing your CRM, EHR, or care-management platform. AdmitScore is a focused referral-review layer that sits next to your stack. Pilot scope reflects that.
Continuation is a fresh conversation, not an auto-renewal. If AdmitScore fits the workflow, we scope continuation pricing. If it doesn't, the pilot ends and you keep your decision-history export.