Bring us your documentation workflow. We’ll help you test RelyCare against it.
A RelyCare pilot is a structured evaluation, not a promise that AI will finish every note or replace clinical judgment. You define what matters; we help you test the session-to-SOAP workflow with clear boundaries.
A useful evaluation should include representative documentation challenges, not only a clean demonstration. Together we define which session types are in scope, what clinicians will verify, which errors will be recorded, and what would make the workflow worth adopting—or rejecting.
Define what RelyCare should prove
Show us how your team captures sessions, writes SOAP notes, checks target data, and handles clinical review today.
Confirm privacy and workflow fit
We discuss consent, audio handling, access, and—when applicable—BAA eligibility and required operating conditions before real-session use.
Evaluate with founder support
Pilot scope, duration, onboarding, pricing, and success measures are agreed with your clinic rather than hidden behind a self-serve checkout.
A strong pilot fit
Your clinic wants relief without hiding the evidence.
- You run a US or South African private speech therapy practice or clinic.
- SOAP note drafting regularly extends beyond the clinical day.
- You want target metrics, cueing, retries, and supporting quotes available for review.
- You are willing to keep the SLP responsible for editing and approving every final record.
What to test
Make the pilot answer the questions a polished demo cannot.
A useful pilot creates a decision your clinic can defend. These evaluation areas keep the conversation focused on clinical review, operational fit, and the work that remains after a draft appears.
Test 1
Draft usefulness across real session types
Include the documentation situations that create the most rework: clean drill data, conversational samples, mixed targets, caregiver reports, unclear speaker turns, and sessions where important context is not audible. The test should reveal where RelyCare creates a useful starting point and where the clinician still has to rebuild or add the record.
Test 2
Evidence review and correction effort
Ask clinicians to inspect target labels, first-attempt scoring, cued retries, self-corrections, errors, and representative quotes. Record which details are easy to verify, which require transcript review, and which need correction. A polished paragraph is not enough if the reviewer cannot understand how the draft reached its metric.
Test 3
Fit with clinic governance
Evaluate consent, access roles, audio handling, clinician approval, record handoff, and the current BAA process under the clinic’s actual policies. The pilot should identify the operating conditions required before broader use rather than treating a software feature list as a substitute for clinic privacy and compliance decisions.
Test 4
Adoption without hidden workflow costs
Look beyond the generated note. Test how sessions are started, how drafts enter the review queue, how corrections are made, where finalized output goes, and how exceptions are handled. The result should tell the clinic whether RelyCare reduces the blank-page burden without creating a new administrative process clinicians will avoid.
After you apply
A decision process, not a surprise checkout.
Applying starts a conversation. It does not authorize RelyCare to process patient information, enroll your team, or begin a paid engagement.
Step 1
A fit and privacy conversation
Adham reviews your clinic size and intended outcome, then discusses the documentation workflow, consent expectations, privacy requirements, and whether the current product is appropriate for your use case.
Step 2
A written pilot definition
Before real-session use, both sides agree on scope, duration, pricing, onboarding, operating conditions, and the evidence that would make the pilot useful. Nothing is implied by submitting the form.
Step 3
A review against your criteria
The clinic evaluates whether drafts preserve useful session context and whether clinicians can verify, correct, and approve them inside the agreed workflow. Results are discussed without turning pilot observations into unsupported public claims.
Pilot questions
Know what the application does—and does not—mean.
- How long does a RelyCare pilot run, and what does it cost?
- There is no universal term published yet. Duration, pricing, onboarding, participant count, and success criteria are agreed after the fit conversation so the pilot matches the clinic rather than forcing every team into one package.
- Should I include patient details in this application?
- No. Do not enter patient names, diagnoses, transcripts, recordings, or other protected health information. The form only needs your professional contact details, clinic size, and the workflow outcome you want to evaluate.
- Does the pilot replace our EHR or current clinical system?
- Not by default. RelyCare is focused on session-to-documentation workflows and longitudinal context. During scoping, your clinic can identify where reviewed output should sit alongside existing systems and what manual handoff is acceptable.
- Does applying guarantee faster or more accurate documentation?
- No. The pilot exists to test product fit and establish evidence in your environment. RelyCare creates a draft, and the clinician remains responsible for checking the transcript-linked evidence, editing the note, and approving the final record.
Clinician control
Every final record stays yours.
RelyCare creates a review-ready draft. The clinician corrects, edits, and approves the documentation.
Audio lifecycle
Raw audio is not the final record.
Session audio supports processing and review, then is deleted after the record is finalized.
HIPAA-regulated clinics
Ask about BAA eligibility.
A BAA is available for eligible clinics under the required contractual and operational conditions.