Where the pathway breaks — and how we close it
The clinical week is invisible between sessions
A client gets four sessions a month. The other 26 days — where the patterns actually run — produce no clinical signal at all. The industry knows follow-through between visits is where care breaks: NCQA maintains entire HEDIS measure sets (follow-up after hospitalization, treatment initiation and engagement) because the gap between clinical contacts is the highest-risk terrain in behavioral health.
Cost when unaddressed: The therapist reconstructs the week from memory and self-report, one client at a time, across the whole roster.
Daily check-ins, pre-session brief
Every seat gives every client a daily check-in — a six-area read of how the week is actually going — and gives the clinician a pre-session brief before every appointment. The therapist walks in already knowing what kind of week it was, on every chair in the practice.
The office work competes with the clinical hour
Post-pandemic demand for care rose and stayed up, and the operational load rose with it. The APA's Practitioner Pulse surveys document sustained elevated demand, waitlists, and workload across U.S. practice settings — and the administrative side of that workload lands after hours, on the same clinicians the waitlists are waiting for.
Cost when unaddressed: Group practices solve this with unpaid clinician evenings or paid admin headcount. Both come out of the same margin.
Shaula — a free local assistant for the office side
Shaula runs the non-clinical office work — and refuses the clinical kind. No session notes, no billing, no PHI: she is built to say no to all three. She is a free local assistant — a separate free download that runs on the clinician's own computer. There is no per-task pricing and no add-on module.
AI diligence is now a federal expectation, and vendors answer it with sales layers
Since January 2025, ONC's HTI-1 Final Rule sets transparency and risk-management requirements for AI-enabled decision support in certified health IT. Buyers are expected to run real AI due-diligence — which model, whose infrastructure, what touches PHI. Most vendors route those questions through an SDR, a sales engineer, and an account executive before anyone who can answer them appears.
Cost when unaddressed: Clinical directors burn weeks in qualification calls with people who cannot answer the diligence list.
The first call is the call
The 30-minute discovery call is with Matthew Sexton, LCSW, NATC — founder, architect, and a practicing clinician who runs his own caseload on the product. Model, infrastructure, BAA scope, data boundaries, rollout, and price get answered in one sitting, by the person accountable for them. No SDR, no qualification script, no hand-off.
Third-party AI vendor BAA gaps are a named industry risk
The American Hospital Association's trustworthy-AI guidance names the failure mode plainly: healthcare organizations rolling out AI without executed BAAs covering inference, and PHI leaking into consumer AI endpoints and training pipelines. In behavioral health the stakes are the therapy relationship itself.
Cost when unaddressed: One unanswered subprocessor question in diligence stalls a rollout. One real gap ends it.
One inherited BAA chain, one named model
AI inference runs on Gemma, an open-weight model served on Amazon Bedrock, under an executed AWS Business Associate Agreement that also covers compute and the RDS Postgres database with pgcrypto encryption at rest. Client data never trains a model and never touches a consumer AI endpoint. Your rollout inherits that chain at provisioning — there is no practice-side cloud-vendor BAA negotiation. AI interactions are pooled across seats and sized to your rollout, in plain English.
Benefits nobody uses
The EAP industry's own operational baseline is roughly 5% utilization per year. The benefit exists, the deck says wellness, and 95 of 100 employees never touch it. For employers, that is a line item with no line back.
Cost when unaddressed: Utilization this low means the people the benefit was bought for meet it for the first time in a crisis, or never.
A companion built for daily use, reported in aggregate only
VibeCheck.luxury is designed as a daily habit, not an incident response — a check-in that takes less time than a coffee order. Organizations see engagement in aggregate only, by architecture: nobody's boss ever sees a check-in. That boundary is structural, and it is why people actually use it.
Margin-squeezed clinicians, opaque software pricing
In the APA's 2024 Practitioner Pulse Survey, 82% of psychologists who left insurance networks cited low reimbursement as the reason, and 34% of practicing psychologists were not in-network with any insurer. Clinician margins are under real pressure — and the software sold to those same clinicians is priced in tiers, per-employee-per-month formulas, and feature ladders that hide the number.
Cost when unaddressed: A group practice cannot budget a platform whose price depends on which features it will be punished for wanting later.
One price, stated exactly
$77.77 a month is the MWS membership — the VibeCheck.luxury seat and everything the association builds around it. One membership, one price. Every seat gets the entire product — the between-session companion and the client app — and the EMR module lands inside the same seat when it ships. Twenty seats is $1,555.40 a month; the math is the whole pricing table. Enterprise is a conversation about rollout, never a higher price.
Methodology
How we measure
Go-live runs a seven-checkpoint sequence, measured wall-clock from BAA execution to first client invitation: discovery call complete and engagement scoped (checkpoint 1), BAA addendum executed (2), practice configuration captured — roster, branding, notification windows (3), seats provisioned with database-level pgcrypto encryption keys (4), clinician onboarding walkthrough (5), first client cohort invited (6), full-roster enrollment open (7). For a group practice on the standard path the clock runs in days, not procurement quarters; anything that extends it — EHR integration scope, an employer's HRIS variance, a staged multi-site rollout — is named and scheduled on the discovery call, not discovered afterward. The engine behind VibeCheck.luxury was proven in production before VibeCheck.luxury carried it; everything it learned ships inside VibeCheck.luxury today.
What counts
- Group-practice seat rollouts on the standard seven-checkpoint path
- Organization and employer rollouts with aggregate-only reporting, scoped on the discovery call
- Every seat at $77.77/mo flat — the price does not change with rollout size
What doesn't count
- Custom EHR integration beyond the FHIR R4 / HL7v2 baseline (scoped and scheduled during discovery)
- Bring-your-own-LLM requests (gated by partner BAA execution — not available today)
- The EMR module (in development; it ships inside the same $77.77 seat when it ships — see vibecheck.luxury/emr for the honest status)
- Crisis-routing opt-outs (documented program-specific exception only)
How we compare
Sourced from primary citations — not vendor marketing claims.
| Us VibeCheck.luxury (Mental Wealth Solutions) | vs Typical enterprise wellness platform | vs Typical EAP | vs Consumer AI chatbot | |
|---|---|---|---|---|
| First-call decision-maker | Founder — practicing LCSW, scopes the engagement on call one | SDR → sales engineer → account executive | Broker or account manager | No call — self-serve app |
| Pricing model | One membership: $77.77 per clinician seat/mo, flat — every seat gets everything | Tiers + per-feature ladders | Per-employee-per-month, utilization-insensitive | Freemium + subscription upsell |
| Who sees an individual's data | The client and their clinician. Organizations see aggregate only, by architecture | Varies by contract | Varies by contract | The vendor, per its consumer terms |
| AI infrastructure | Named open-weight model (Gemma) on Amazon Bedrock under executed AWS BAA | Typically undisclosed | Typically none or undisclosed | Consumer endpoints, no BAA |
| Clinician's role | Signs every note, approves every draft, can suspend the companion per client | Outside the product loop | Gatekeeper to sessions only | None — no clinician in the loop |
| Crisis handling | 988 on every client surface; signals route to the client's clinician | Varies | Phone line during business hours | Disclaimer text |
Frequently asked questions
- What does a group practice actually get per seat?
- Everything, on every seat: the between-session companion (daily client check-ins, the six-area read, a pre-session brief before every appointment) and the client app. Part of the MWS membership — $77.77/mo, unlimited clients per seat. Shaula, a free local assistant for the non-clinical work, is a separate free download. When the EMR module ships, it lands inside the same seat at the same price. There is no feature ladder and no tier above or below this.
- What happens on the 30-minute discovery call?
- Five things, in one sitting: fit (does VibeCheck.luxury match your practice or organization, or should you be buying something else — and if so, what), AI diligence (which model, whose infrastructure, what touches PHI, answered directly), BAA scope (what your rollout inherits and where your existing vendor BAAs sit alongside it), rollout (seats, cohorts, timeline against the seven checkpoints), and price (there is one: $77.77 per seat per month, so this part is short). The call is with Matthew Sexton, LCSW, NATC — founder and practicing clinician. No SDR, no qualification script, no sales engineer hand-off.
Cited: onc-2024-hti-1-final-rule
- Do we need our own cloud-vendor BAAs?
- No. The platform operates under an executed Business Associate Agreement with Amazon Web Services covering compute, AI inference on Amazon Bedrock, and the RDS Postgres database with pgcrypto encryption at rest. Your rollout inherits that chain at provisioning. PHI never leaves BAA-covered infrastructure and never reaches a consumer AI endpoint. If your organization holds BAAs with other vendors — your EHR, your billing clearinghouse — those continue to govern your existing data flows; VibeCheck.luxury operates alongside them via FHIR R4 and HL7v2 exchange.
Cited: aws-2024-hipaa-eligible-services , hhs-45-cfr-164-312-technical-safeguards
- Which AI model runs it, and can we bring our own?
- Production inference runs on Gemma, an open-weight model served on Amazon Bedrock under the executed AWS BAA — no consumer AI endpoints, no multi-model menu, and client data never trains a model. Bring-your-own-LLM is not available today; it is gated behind partner BAA execution, because a vendor without a BAA does not touch PHI on this platform, full stop. Four human gates stand between the AI and your clients: the clinician signs every note, approves every draft, sets every guardrail, and can suspend the companion for any client at any time.
- How is crisis safety handled?
- The companion never handles a crisis alone. Crisis resources — 988 call and text — are present on every client surface, and crisis signals route to a human: the client's clinician, with the escalation path agreed during onboarding. Organizations do not opt into crisis safety; it ships on, and turning any part of it off requires a documented program-specific exception with executive sign-off.
- Is there volume pricing? An enterprise tier?
- No, deliberately. $77.77 per clinician seat per month at five seats and at five hundred. Twenty seats is $1,555.40 a month — you can do the whole pricing table in your head, which is the point. "Enterprise" at Mental Wealth Solutions means the conversation gets bigger — rollout staging, BAA addenda, reporting needs — never the number. If a flat price sounds like it leaves money on the table, it does; it buys the thing that actually closes group practices: a price everyone in the room can verify.
- We're an employer, not a practice. Does this replace our EAP?
- VibeCheck.luxury is not an EAP and doesn't impersonate one — it's the between-session layer your people use daily, alongside whatever clinical benefits you already offer. You see engagement in aggregate only, by architecture: nobody's manager ever sees a check-in. Start at mentalwealthsolutions.org/for-employers, or bring your current utilization number to the discovery call and we'll show you what the gap looks like.
Why this exists
The first call is the call. $77.77 a seat — at five seats and at five hundred.
Every enterprise platform I evaluated while building this company sold the same way: an SDR call, a qualification script, a sales-engineer hand-off, and somewhere past the third call, a person who could finally answer a clinical question. That sales motion is the product warning label. If the people who understand the workflow only appear after the people who understand the contract, you already know which one the company is built around.
So the engagement here runs the way a clinical referral runs: direct, scoped, and honest about fit. The first call is the call. I am the founder, the LCSW behind the clinical frameworks, and the architect of the platform, and I will tell you in 30 minutes whether VibeCheck.luxury fits your practice — and what to buy instead if it doesn't.
Two receipts matter more than anything else I can say. First: my own clinical practice is the platform's first production user — if VibeCheck.luxury cannot run my caseload cleanly, I have no business selling it to yours. Second: membership is $77.77 a month per seat, flat, at every rollout size, and it is printed on every page of this site. The engine underneath was proven in production before VibeCheck.luxury carried it; everything it learned ships inside VibeCheck.luxury today. One product, one price, one person accountable on the first call. That is the whole model.
Matthew Sexton, LCSW Founder · Mental Wealth Solutions Inc.
Citations
- (2024). HEDIS Measures: Follow-Up After Hospitalization for Mental Illness and Initiation and Engagement of Substance Use Disorder Treatment. National Committee for Quality Assurance.
Source
- NCQA HEDIS quality measures defining the industry-standard expectations for follow-up after psychiatric hospitalization (FUH) and substance use disorder treatment initiation and engagement (IET).
- Health-plan performance on FUH and IET HEDIS measures directly impacts NCQA accreditation, Medicare Advantage Star Ratings, and Medicaid managed care quality reporting.
- Establishes the industry-standard quality-measurement framework that anchors closed-loop referral and engagement expectations across health plan, ACO, and EAP delivery channels.
“NCQA HEDIS quality measures for follow-up after psychiatric hospitalization and substance use treatment engagement define the industry-standard quality framework that anchors closed-loop referral and engagement expectations across health plan and EAP delivery channels.”
- (2023). 2023 Practitioner Pulse Survey. American Psychological Association.
Source
- APA Practitioner Pulse Survey of licensed psychologists documenting workload, telehealth adoption, waitlist length, and burnout indicators across U.S. practice settings.
- Majority of surveyed psychologists report sustained increase in demand for services post-pandemic, with significant proportions reporting waitlists for new patient intake.
- Telehealth adoption among practicing psychologists has stabilized at substantially elevated levels relative to pre-pandemic baseline, with hybrid practice models becoming the dominant operational pattern.
“APA Practitioner Pulse Survey data document sustained post-pandemic demand pressure and stabilization of telehealth-enabled hybrid practice as the dominant operational model among U.S. licensed psychologists.”
- (2024). 2024 Practitioner Pulse Survey: Insurance Participation and Reimbursement. American Psychological Association.
Source
- In the APA's 2024 Practitioner Pulse Survey (December 2024), 34% of practicing psychologists were not in-network with any insurance.
- The most-cited reason for leaving insurance was low reimbursement rates (82%).
- Patients are more than ten times as likely to go out-of-network for mental health care as for other specialty medical care.
- (2024). Health Data, Technology, and Interoperability — Certification Program Updates, Algorithm Transparency, and Information Sharing (HTI-1) Final Rule. HHS ONC.
Source
- ONC HTI-1 Final Rule (January 2024) establishes the first federal regulatory framework for AI/algorithm transparency in certified health IT — including 'Decision Support Interventions' (DSI) certification criteria for predictive AI/machine-learning models embedded in EHRs.
- DSI certification requires source attribute disclosure for predictive models, intervention risk management practices, and feedback mechanism for end users — establishing the baseline transparency requirements for AI-enabled clinical decision support.
- Anchored the regulatory baseline for AI in certified health IT — vendors offering AI/ML-enabled clinical decision support to ONC-certified EHRs must satisfy DSI transparency and risk-management requirements as of January 1, 2025 effective date.
“ONC HTI-1 Final Rule establishes the first federal regulatory framework for AI/algorithm transparency in certified health IT — DSI certification requires source attribute disclosure, intervention risk management, and end-user feedback mechanisms for predictive AI/ML models.”
- (2024). AHA Cybersecurity and Risk Advisory Services — Trustworthy AI in Healthcare. American Hospital Association.
Source
- AHA cybersecurity advisory documents healthcare-specific AI deployment risks: training-data PHI exposure, model output containing PHI, third-party AI vendor BAA gaps, prompt-injection vulnerabilities in LLM-enabled clinical applications, and model-drift detection requirements.
- Documents AHA-recommended trustworthy AI deployment framework: vendor due-diligence with executed BAAs covering AI training and inference, PHI-minimization in prompts and outputs, audit logging of all AI inference calls, and clinical-validation evidence requirements before deployment.
- Anchored the hospital-association consensus framework for AI deployment in HIPAA-regulated environments — covered entities deploying AI in clinical workflows must address vendor BAAs, PHI minimization, audit logging, and clinical validation as deployment baseline.
“AHA's cybersecurity advisory establishes the trustworthy-AI deployment framework for HIPAA-regulated environments — vendor BAAs covering AI training and inference, PHI minimization, audit logging, and clinical validation as deployment baseline requirements.”
- (2023). Leveraging behavioral science and artificial intelligence to support mental health in the workplace: a pilot study. Frontiers in Psychiatry.
doi:10.3389/fpsyt.2023.1219229
- Documents EAP industry benchmark utilization rate of 5% per year as the operational baseline against which engagement interventions are measured — corroborating the persistent single-digit utilization pattern.
- Behavioral-science email campaign delivered via reinforcement-learning agent achieved 22% click-through and EAP-site login among 773 employees over 12 months versus 5% benchmark — a 4-fold engagement lift through messaging redesign alone.
- Demonstrates that EAP underutilization is an engagement-architecture problem, not a clinical-need problem: targeted behavioral-science messaging can move utilization from low single digits to double digits without changing the underlying clinical service.
“EAP industry benchmark utilization sits at 5% per year — behavioral-science messaging quadrupled engagement to 22% in a 12-month pilot, confirming the bottleneck is engagement architecture, not clinical service.”
- (2024). HIPAA Eligible Services Reference. Amazon Web Services.
Source
- AWS HIPAA Eligible Services Reference documents the comprehensive list of AWS services covered under the AWS BAA — currently 175+ services including EC2, RDS, S3, KMS, Lambda, Bedrock, SageMaker, CloudWatch Logs, Systems Manager, and Aurora.
- Critical HIPAA-architecture services for healthcare workloads: RDS (encrypted PostgreSQL/MySQL with pgcrypto), S3 with SSE-KMS encryption, Bedrock for LLM inference (BAA-covered foundation models), Systems Manager Session Manager (CloudTrail-logged session-data S3 archival), and CloudWatch Logs for audit trail.
- Established the AWS BAA-covered services baseline enabling HIPAA-eligible cloud-native architecture for healthcare workloads — key infrastructure enabling HIPAA-eligible deployment without requiring on-premise hosting or self-hosted security infrastructure.
“AWS's own HIPAA Eligible Services program covers 175+ services under BAA — including RDS, S3, Bedrock, SageMaker, and Systems Manager Session Manager — establishing the AWS BAA-covered services baseline for HIPAA-eligible cloud-native healthcare architecture.”
- (2013). HIPAA Security Rule — Technical Safeguards (45 CFR § 164.312). Code of Federal Regulations, Title 45 — Public Welfare.
Source
- Mandates access control, audit controls, integrity controls, person-or-entity authentication, and transmission security as technical safeguards for ePHI.
- Encryption and decryption are addressable specifications under access control and transmission security — required unless an alternative measure is documented as equally protective.
- Audit controls require hardware, software, and procedural mechanisms to record and examine activity in systems containing or using ePHI.
“A covered entity or business associate must implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights.”
- (2013). Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules — Omnibus Rule. HHS Office for Civil Rights.
Source
- HHS HIPAA Omnibus Rule (effective March 2013) implementing HITECH Act provisions — established business-associate direct liability for HIPAA violations, expanded breach notification requirements, and updated marketing/fundraising restrictions.
- Established that business associates (including health-IT vendors and cloud-service providers handling ePHI) are directly liable for HIPAA Security Rule and Breach Notification Rule violations — extending HIPAA enforcement to the entire ePHI handling chain rather than only covered entities.
- Anchored the modern HIPAA enforcement framework: covered entities and business associates each carry direct compliance obligations, with Business Associate Agreements (BAAs) as the contractual instrument establishing the compliance chain.
“The 2013 HIPAA Omnibus Rule established business-associate direct liability for HIPAA violations — extending enforcement to the entire ePHI handling chain with Business Associate Agreements as the contractual compliance instrument.”