About Peacefull
The interval deserves
an accountable design.
Peacefull is building a clinician-supervised care-continuity layer for adult outpatient behavioral health.
Why this exists
Care is larger than the appointment.
Patients live most of their week outside the clinical encounter. Care teams need preparation and follow-through without turning support into surveillance or an unowned stream of alerts.
From the founder
A letter, brief.
I want to start with something true and uncomfortable: I have a good therapist. I’m lucky to have her. And it hasn’t been enough.
ADHD doesn’t book a 1pm Tuesday slot. The thing I need to talk about happens at 11:47pm, or in the parking lot before a meeting, or in the half-second between waking up and remembering what today is supposed to be. By Tuesday, I’ve forgotten the shape of it, or I’m somewhere else, or I’m trying — really trying — to build trust with someone I get one hour a week with. The signal lives in the 167 hours she isn’t in the room.
I went looking for help with that. What I found was an industry of “mental wellness” apps that positioned themselves as the destination — meditation timers, streak counters, pastel onboarding. None of them treated my therapist as the center of care. None of them tried to carry what happens between sessions into the hour I had with her. They wanted to replace the work. I needed something that could carry it.
That’s what Peacefull is: a clinician-supervised layer that lives in the gap, organizes what real life actually looks like, and hands the care team something honest to start with on Tuesday. A resource and a communication channel — not a replacement for care.
My background is why we are building it this way. For over a decade I architected systems for federal and state agencies — the kind of high-stakes programs where you do not ship without an audit trail, an accountability structure, and a process for shutting things down when they fail. That discipline is not a marketing layer here. It is why this site states our boundaries as plainly as our capabilities, why every material public claim carries an owner and an expiry, and why we would rather under-claim than over-promise.
We are early. We are building this in the open, with design partners, on purpose.
— Khoja Rahimi, Founder & CEO
Who is accountable
Named people, named scope.
Accountability at Peacefull is personal, not institutional. Each person below owns a named part of the operation — and the parts nobody owns yet are stated, not papered over.
Khoja Rahimi
Virginia · remote-firstKhoja previously founded an AI and security startup and spent over a decade in public-sector security — federal and state agencies where high-stakes systems have to stand up to audit, adversarial review, and actual accountability. He is building Peacefull out of lived experience with severe ADHD and a family history of depression and bipolar disorder; the gap between what evidence-based care knows and what apps actually deliver isn’t abstract for him.
Eric Shaklee, MBA
Texas · remote-firstEric has 25+ years leading enterprise go-to-market for national firms across physical security and cybersecurity — sectors where buyers don’t buy on a deck, they buy on proof. He knows the shape of the reviews clinical and health-system buyers run, because he has sold into them before: the security questionnaires, the DPA redlines, the reference calls.
Alejandro Marquez
Remote-firstAlejandro joins Peacefull from digital-health engineering — prior work building HIPAA-aligned patient-facing surfaces that have to hold up to two standards at once: clinical scrutiny (does it respect the workflow?) and patient expectations (is it calm, is it clear, does it feel like it cares?). Both standards matter here, because the product lives in both worlds.
Sohrob Ibrahimi
DC/Baltimore · remote-firstSohrob came to Peacefull from defense engineering — a background where code quality, traceability, and adversarial review are daily practice rather than marketing bullets, and where the cost of silent failure is measured in human lives. That calibration is exactly what the safety-relevant parts of this product require.
Don Redmond, JD
Virginia, USDon has 36 years as a practicing attorney, licensed in Virginia. His experience spans corporate governance, M&A, government relations, and litigation management — across closely held companies and a 15-year tenure in senior legal roles at a NASDAQ-listed public corporation, work that carries the discipline of operating inside a heavily regulated public company.
Jahan Rahim
Virginia · remote-firstJahan has 15+ years of engineering leadership across defense contractors, classified systems, and machine learning — environments where you ship code knowing it will be reviewed by people whose job is to break it, and you design for that review from day one. He brings that discipline to Peacefull’s safety-critical architecture.
Clinical governance
A council with a real veto.
Peacefull’s clinical governance is designed around a council with a binding veto on protocol activation, clinical-content changes, safety-threshold changes, and go-live decisions. The veto is mechanical, not advisory: when the council says no, the change does not ship.
Dr. Davoud Amiri, MD, PhD (Stockholm) is a seated member as Clinical Research Advisor, seated May 23, 2026 — a 32-year clinical practice across three countries, with Specialist Competence in Psychiatry in Sweden and Switzerland and a clinical focus on treatment-resistant depression and psychosomatic care.
The remaining seats — including the Chief Medical Officer seat, currently unfilled — are named only after a member has agreed publicly and their institutional affiliation is confirmed. Unfilled seats are stated as unfilled; that is the standard this page holds itself to.
How we build
Clinical authority and evidence before scale.
We design around intended use, consent, responsibility, review, exceptions, rollback, and measurable burden. The platform’s breadth matters only when it produces a clearer, safer operating workflow.
What comes next
Earn repeatability before expansion.
The current focus is the provider wedge: qualified discovery, bounded design partnerships, operational evidence, and repeatable implementation. Broader payer, employer, or standalone assurance motions wait.
A bounded next step
Start with the workflow.
Compare how your organization handles patient participation, preparation, review, and follow-through between visits.
Start the conversation Do not include patient information or clinical details in email.