Pilot program

Start with one unit. Prove the outcome.

A two-month paid pilot on a single behavioral-health unit, engaged through a signed letter of intent, with the success criteria agreed before it starts. If SecureScribe doesn't move your after-shift charting numbers, there is no site license to sign.

$2,000Total cost — two months, one facility
2 monthsMeasured use, from a signed letter of intent
1 unitA single unit, not the whole facility
3 criteriaAgreed in writing before go-live

The pilot is measured, not impressionistic.

Three numbers decide whether the pilot succeeded. They are agreed in writing up front, measured against your own unit's baseline, and reported at the end of month two.

Target success criteria · 2-month pilot
30%
Reduction in after-shift charting
95%
Required-field completeness
70%
Use across eligible nursing shifts
$2,000total · two months · one facility

These are the targets we commit to in the letter of intent. SecureScribe is pre-first-pilot — no facility has completed one yet, so these are agreed goals rather than reported results.

Request a Pilot

How each number is defined

Agreed in the letter of intent before baseline, so the result cannot be argued about afterwards.

MetricOperational definitionMeasured
After-shift chartingMedian documentation minutes occurring after scheduled shift end, per eligible nursing shift.Baseline week vs. month two
Required-field completenessShare of eligible events where every facility-required element is present at the time the note is approved.Per event, continuously
AdoptionShare of eligible nursing shifts on the pilot unit where SecureScribe was used for at least one documented event.Per shift, continuously

“Eligible” means shifts and events covered by the workflows configured for your unit. Excluded categories are listed in the letter of intent, not decided later.

What the pilot includes

Everything needed to run SecureScribe on one unit for two months and produce a defensible result.

INCLUDED 01

Workflow configuration

Your facility's required documentation elements are mapped for PRNs, refusals, behavioral events, milieu events, safety events, and family contacts.

INCLUDED 02

On-device deployment

Installation on hardware already present on the unit. No cloud inference, no new server procurement, no GPU cluster.

INCLUDED 03

Nurse onboarding

Short, shift-length onboarding for the nursing staff on the pilot unit, plus a written reference for float and per-diem staff.

INCLUDED 04

Baseline measurement

We measure your current after-shift charting time and documentation completeness before go-live, so the comparison is against your unit rather than an industry average.

INCLUDED 05

Mid-pilot review

A check-in at week four to adjust workflow rules, address nurse feedback, and correct adoption gaps while the pilot is still running.

INCLUDED 06

Outcome report

A written report at month two against the three success criteria, suitable for presenting to nursing leadership and finance.

How the two months run

From first conversation to outcome report, a pilot typically spans about ten weeks.

Week 0
Scoping

Scope the unit and the events

A short call to confirm the pilot unit, shift structure, nurse headcount, and which documentation events carry the most burden.

Week 0
Letter of intent

Sign the LOI

A one-page letter of intent fixes the $2,000 fee, the pilot unit, the two-month window, and the three success criteria with how each will be measured. Nothing starts before both sides have signed what "worked" means — which is the point of doing it in writing.

Week 1
Baseline

Measure where you are today

We capture current after-shift charting time and required-field completeness on the pilot unit. Without this, a percentage improvement at the end means nothing.

Week 2
Deploy

Configure and install

Documentation rules are configured to your facility's requirements and SecureScribe is deployed on existing unit hardware. Nursing staff complete onboarding.

Weeks 3–6
Month one

Live use, first month

Nurses document events during their shift. SecureScribe structures them, flags missing fields, and drafts the shift note. Every draft still requires nurse review before posting.

Week 6
Mid-point

Mid-pilot review

We review adoption, nurse feedback, and any workflow rules that need adjusting — while there is still a month left to act on it.

Weeks 7–10
Month two

Live use, second month

Steady-state measurement against the agreed criteria, then a written outcome report and a decision on the annual site license.

What we need from your facility

Deliberately short. A pilot that requires a six-month IT project isn't a pilot.

  • One pilot unit. A single behavioral-health unit — not the whole facility.
  • A clinical sponsor. Usually the clinical director or nurse manager for that unit.
  • Existing unit hardware. Whatever nurses already use to document. No new procurement.
  • Access to baseline data. Enough visibility into current charting time and completeness to establish a starting point.
  • Two months of use. Long enough for adoption to stabilize past the novelty period.

What we don't need

No EHR replacement. No integration project before go-live. A narrower security review surface: there is no third-party cloud inference and no external LLM vendor processing PHI. Your IT and security teams still review the deployment — there is simply less of it to review. No enterprise infrastructure commitment.

Read the clinical safety model

After the pilot

A successful pilot converts to an annual site license. An unsuccessful one doesn't.

If the criteria are met

Annual Site License

$20,000/ facility / year
  • Unlimited nursing users at the licensed facility
  • All behavioral-health event workflows included
  • On-device deployment on existing hardware
  • Documentation completeness reporting
  • Ongoing workflow configuration support
Ask about licensing
If they aren't

You walk away

The pilot is scoped so that a negative result is a real possible outcome, not a formality. You keep the baseline measurement and the outcome report either way — both are useful to nursing leadership regardless of what you decide about SecureScribe.

  • No multi-year commitment attached to the pilot
  • No infrastructure left behind to decommission
  • Written outcome report is yours to keep

We haven't run one yet. That's the offer.

SecureScribe is pre-first-pilot. Being early costs you a defined $2,000 and buys you disproportionate influence.

EARLY 01

Your workflow shapes the product

Required-field rules are configured to your facility first. The first units to run SecureScribe define what the defaults look like for everyone after them.

EARLY 02

Direct line to the builder

No support tier, no ticket queue. Issues raised during the pilot go straight to the person who can change the software that week.

EARLY 03

Priced accordingly

$2,000 for two months reflects that you are taking a chance on unproven software. The site license price is what it costs once it is proven.

Request a pilot

Tell us about your unit and we'll come back with a scoped two-month pilot and the three success criteria we'd measure against. Nothing is committed until a letter of intent is signed.

or email pilot@securescribe.health

We use this only to scope your pilot. No patient information — please don't include any here.

Sacramento, California · 1st place, Carlsen Center pitch competition · 3rd place, Pitch Elk Grove 2026

Pilot questions

The practical ones that come up before a clinical director will take this to their administrator.

How much does a SecureScribe pilot cost?

$2,000 total for two months at one facility, starting from a signed letter of intent. There is no separate setup fee and no per-seat charge.

How long does the pilot take?

Two months of measured use, preceded by roughly one to two weeks of scoping, configuration, and nurse onboarding — about ten weeks end to end.

What hardware does the pilot require?

SecureScribe runs on everyday clinical hardware already on the unit. Because the model runs locally rather than calling a cloud service, no enterprise-scale infrastructure or GPU cluster is required.

Does the pilot require an EHR integration?

No. The pilot runs alongside your existing record. SecureScribe produces a review-ready draft that the nurse approves; it does not replace or rewire the EHR.

Who needs to approve a pilot at our facility?

Typically the clinical director or nurse manager for the pilot unit, plus whoever signs off on a $2,000 expenditure. Because clinical information stays on-device, the review surface is narrower than a cloud AI vendor assessment — though your IT and security teams will still review the deployment.

What happens if the pilot doesn't hit the criteria?

Then it didn't work on your unit, and there is no site license to sign. You keep the baseline measurement and the written outcome report.