See payer risk and margin before the bed is held.
AdmitScore™ reviews referral packets so your team can decide on admissions with payer, authorization, documentation, and financial context already on the page. The pilot is a structured 90-day evaluation with hands-on launch support — billed monthly, no auto-renewal.
- 90 days
- Kick-off, mid-pilot review at day 30, conversion discussion at day 75, readout at day 90.
- Founder-led
- Direct access to Jack and Peter throughout; no tiered support queue.
- BAA before PHI
- Public forms stay PHI-free; secure intake is scoped at the kick-off call.
- No auto-renewal
- Continuation is a fresh conversation; you keep your decision-history export.
Pilot pricing is scoped, not retail. Public forms remain PHI-free; secure data workflows are scoped separately under a signed BAA.
Built by people who have done admissions and operations.
Builds AdmitScore™ with healthcare operators in mind. Owns product, engineering, and pilot scoping for every pilot facility.
Licensed Nursing Home Administrator with frontline operations and turnaround experience. Translates pilot findings into staff-friendly workflow.
One flat monthly fee — confirmed in one screening call.
Every pilot is a single flat monthly fee — no per-seat charges, no platform minimums — for a 90-day evaluation, billed monthly, with no auto-renewal. Request pilot pricing and the screening call confirms your exact number from real scope, in writing. The pilot pricing page breaks down the structure and what is in scope vs out of scope.
- Facility count: single facility or portfolio of locations.
- Monthly packet volume: estimated referrals reviewed during the pilot.
- Payer mix complexity: MA-heavy vs Medicare-A-heavy review weighting.
- Users and roles: how many reviewers and which role-based score views.
- Implementation scope: synthetic-data demo or live-data pilot with BAA and secure workflow contracting.
- Outcome tracking depth: standard decision tracking or separately scoped exports.
Pilot pricing is one flat monthly fee per facility; the confirmed quote follows the 15-minute screening call so it reflects your actual facility count, packet volume, and implementation scope. Continuation is standard month-to-month pricing, confirmed at the day-75 conversation — never an auto-renewal.
From kick-off to readout, concrete deliverables.
Each checkpoint produces something you can show your team. Dates are illustrative; actual cadence is set during the kick-off call.
-
Day 1
Kick-off call
Walk through facility count, packet volume, payer mix, current intake process, decision roles, and success measures. Confirm BAA scope before any PHI workflow.
-
Day 3
Synthetic packet readout
Founder reviews a synthetic AdmitScore output with your team so everyone sees the six surfaces (payer, MA auth, documentation, medications, financial, verify) before any live packet enters the workflow.
-
Day 7
Live with first 5 packets
Once BAA + secure workflow are in place, AdmitScore reviews your first 5 real packets. Staff verify each output against source documents.
-
Day 14
Workflow check-in
Founder-led 30-min review of fit, friction points, role-based feedback. Adjust review categories or output format before scaling up.
-
Day 30
Mid-pilot review
Outcome trends so far: accepted, deferred, declined, and follow-up patterns by payer, source, and risk type. Flag where AdmitScore output is changing decisions vs informing them.
-
Day 75
Conversion discussion
An explicit conversation about continuing past the pilot: standard rate, scope, and whether AdmitScore has earned a place in the workflow. No auto-renewal — continuing is a decision made together, not a default.
-
Day 90
End-of-pilot readout
Summary of usage, workflow fit, recurring risk patterns, and a recommendation on scope for continuation. No surprise auto-renewal. Continuation is a fresh conversation.
Throughout the 90 days: direct founder access, weekly check-ins, and the ability to request output-format changes if the structured review isn't fitting how your team already works. Billed monthly. Cancel before your next monthly charge.
Teams that need a more consistent referral review process.
Admissions leaders
Teams reviewing payer, documentation, service-line fit, and acceptance questions under time pressure.
Administrators and operators
Leaders who want visibility into why referrals are accepted, deferred, declined, or followed up.
Clinical and finance reviewers
Staff who need payer, medication, documentation, PDPM, and care-cost context before the decision.
A practical rollout, not a generic demo account.
Workflow review
Current intake process, decision roles, payer mix, packet volume, and follow-up patterns.
Configured review categories
Payer risk, authorization readiness, documentation gaps, medication flags, facility fit, and financial context.
Hands-on launch support
Training, usage review, support during early adoption, and refinement based on staff feedback.
Outcome tracking
Accepted, deferred, declined, and follow-up outcomes tracked by payer, source, risk type, and facility.
Security planning
Public forms stay PHI-free. Any live-data workflow requires appropriate contracting and secure workflow review.
End-of-pilot readout
Summary of usage, workflow fit, recurring risk patterns, and recommended next steps.
What we ask from your team during the 90-day pilot.
Reviews AdmitScore™ output on real referrals and confirms or adjusts the workflow flags.
Watches admissions decision patterns, payer mix shifts, and staff feedback; signs off on pilot scope changes.
Verifies medication, documentation, and PDPM context on flagged packets before acceptance.
Joins the kickoff call and the mid-pilot review with VeriSight Analytics™.
Commitment is structured to fit normal workflow. Pilots end with a written readout and no obligation to continue.
Defined scope keeps the pilot useful.
Pick pilot users
Admissions, administrator, clinical, finance, and implementation contacts are defined before launch.
Set packet volume
We agree on approximate monthly packet volume and the types of referrals the team wants to evaluate.
Review outcomes
We look at decision consistency, missing documentation patterns, payer issues, and staff feedback.
Clear limits make the evaluation more credible.
AdmitScore supports review. Facility staff remain responsible for final admission decisions.
Revenue and margin outputs are planning estimates, not reimbursement guarantees.
AI-extracted payer, authorization, and clinical information should be verified before action.
Do not submit patient records or confidential clinical information through public contact forms.
After you click “Request a Pilot.”
Timeline assumes a standard pilot scope. Multi-facility or custom security workflows extend kickoff by a few weeks.
Questions buyers ask before requesting a pilot.
Do we need a signed BAA before the pilot starts?
Yes for any live patient data workflow. The screening call covers the BAA template and contracted secure data exchange before AdmitScore™ reviews real referral packets. Public website forms remain PHI-free at all times.
How long is the pilot and what's the time commitment?
The pilot is a 90-day evaluation from kickoff, billed monthly. Roles and weekly time are listed in the “Time commitment” section above. Around day 75 we schedule an explicit conversion discussion; pilots end with a written readout and no obligation to continue.
What integration is required to start?
None. AdmitScore can review referral packets through approved intake workflows scoped during kickoff. The pilot can run alongside the facility's existing EHR, CRM, and referral management process.
How does pilot pricing work?
Pilot pricing is one flat monthly fee per facility with no per-seat charges — request pilot pricing and your number is confirmed in the 15-minute screening call, in writing. The variables that shape the confirmed quote are listed in the “Pricing structure” section above. The pilot is a 90-day evaluation, billed monthly, with no auto-renewal; around day 75 we schedule an explicit conversion discussion, and continuation is standard month-to-month pricing confirmed then.
What does VeriSight Analytics™ do during the pilot?
Hands-on launch support, weekly check-ins, and direct founder access for the duration. Mid-pilot review at day 30. End-of-pilot readout with recurring risk patterns and recommended next steps.
What if AdmitScore doesn't fit our workflow?
The pilot is designed to surface that. If AdmitScore is not the right tool, the end-of-pilot readout says so and the engagement ends cleanly. No automatic conversion to a paid contract.
Request an AdmitScore™ Pilot.
Tell us your facility count, referral volume, biggest admissions challenge, and what you want to evaluate.
Request a PilotNo PHI on public forms · Staff verify every output and make the final call · BAA in place before any pilot uses real data.