Your name leads
Alumni see your center’s identity first. Alumni Co-Pilot stays in the background as the provider.
For treatment centers
Your name on it. Your community inside it.
Alumni Co-Pilot carries your center’s name, look, and identity. To an alumnus it feels like your center’s own app, because everything they see is yours.
The problem on your side of the desk
You need to know how your alumni are actually doing — for your own program review, and for the conversations you have with families and referral partners. Gathering that has meant cold-calling graduates or emailing survey links: slow, easy to ignore, and mostly unanswered.
Here the picture builds itself. As alumni simply use the app, participation information accumulates as a byproduct of people staying connected.
The limit that makes it adoptable
The center-facing view is built so it cannot single out, score, or rank an individual member. It answers “how is our community doing,” never “what is this person doing.” That constraint lives in the database rules, not only in policy — and it is the reason a center can adopt this without turning aftercare into surveillance.
How it works, with no jargon
What an alumnus does
- They get an invite from you. A link, a QR code, or a short center code — whichever is easiest to hand out at discharge.
- They land in your community. Your logo, your colors, your welcome message. They see your center, not a generic app.
- They use it because it is useful. Recovery time, a private check-in, meeting search and attendance, and the people they went through the program with.
- They ask for help when they need it. A check-in includes a plain way to ask a real person at your center to reach out.
What your staff does
- Sign in to a browser. No app to install, no database to run, no IT project to manage.
- Publish what alumni need. Your meetings, events, announcements, resources, and aftercare steps.
- Work one short list. Who asked for support, and who has gone quiet — each row with an owner and a status.
- Reach out like a human. The product surfaces a prompt for a person to make contact. It never produces a clinical score or a risk rating.
Setup, realistically. We create your center’s space; you add your branding, invite your team, and invite alumni. Most centers can be live without a technology team. There are no servers for you to run.
Your app, your identity
Your logo
Upload it once. It leads the experience and appears on the recovery-time cards your alumni share.
Your colors
A primary and a secondary color carry through the app your alumni use.
Your voice
Your welcome message, support contact, resources, aftercare steps, and meetings.
Your community, walled off. Each center’s community is private to that center. Your alumni see your people — not a public network, and not the members of any other center. Access is scoped to a member’s own center in the database rules, on every read.
What we have decided never to build
Each of these is cheap for us to avoid now and expensive for a center to undo later. Each is the kind of thing a competitor may offer you as a feature.
Per-member engagement scoring
We will not build a view that ranks, scores, or compares named members. It would be easy to build and would convert a support product into a surveillance one.
Anything derived from private writing
No center-facing measure will ever be derived from the content of journals, reflections, or gratitude entries.
A treatment referral pathway
We do not route members to treatment providers and do not accept referral fees.
Where we are on compliance, honestly
There is no such thing as a certified product here. HHS does not certify software; compliance is a property of a deployment — the center’s role, the data flow, the signed agreements, and the configuration.
Our position is that the app is built to operate as a service organization to your center and to hold as little information as possible. We keep a written posture document covering how the architecture relates to HIPAA and 42 CFR Part 2, what is built today, and what still requires a written agreement between us. Your compliance team can have it, and we will answer their questions directly.
We would rather you hear this from us. Any vendor who answers that question with a flat yes is describing a badge that does not exist for software. What we offer is a defensible posture and a set of signed agreements.