Mental health platform AI Product Engineering Leena · May 25, 2026

A therapist-client platform with rule-based matching

A therapist-client platform that handles scheduling, billing, forms, progress notes, and therapist-client matching. Conventional SaaS build with a rule-based matching algorithm (not ML-driven), shipped against a fixed-scope engagement.

Stage
Growth-stage health tech
Team
1 senior + 3 mid full-stack engineers, 1 product designer, 1 product owner

The situation

Therapists running an independent practice juggle the same set of operational problems: scheduling across time zones, billing, sharing intake forms, tracking progress notes, and matching new clients to the right therapist on the team. Leena set out to consolidate that into a single platform serving both sides of the relationship.

The brief was a comprehensive build: therapist-side workflows (calendar, rescheduling, client roster, session notes, invoicing), client-side workflows (booking, profile, forms, progress visibility), and an intelligent matching layer that paired incoming clients to therapists based on specialty, availability, and stated preference.

What we built

The engagement ran as a fixed-scope AI Product Engineering build with a four-person engineering team: one senior and three mid full-stack engineers, paired with a product designer and a product owner.

Therapist-side surfaces cover calendar management, appointment-type configuration, billing, and a back-office admin panel for form management, session oversight, and client data. The client-side surface handles booking, intake forms, and session history.

The Match Flow algorithm pairs incoming clients to therapists. It is rule-based, not ML-driven: the system evaluates therapist specialties, availability windows, and the client's stated preferences, and returns the best fits. The strategy file is explicit that AI claims should not be retrofitted onto cases that did not ship AI features; Leena's matching is intelligent but not AI.

Tech stack: React with TypeScript on the frontend, Django and PostgreSQL on the backend, AWS for hosting, GitHub Actions for CI. Multi-time-zone scheduling support was built in from the start because the client roster spans regions.

Outcome

  • Therapist-side and client-side workflows shipped in a single platform

  • Rule-based therapist-client matching live in production (not ML-driven)

Leena shipped as a working therapist-client platform with both sides of the workflow covered. No quantified user or revenue metrics are on file; Section 5 stays at the engagement-deliverable level rather than padded.

"The team is highly responsive to any needs or adjustments."

— Confidential , Executive , Mental Health Services Company · Canada
react django postgresql aws mental health matching algorithm

Related cases

Patients unable to visit a clinic can now sign treatment contracts digitally

Docbraces

A web application that lets Docbraces clinics across Canada and the US build orthodontic treatment contracts, present payment options to patients, and collect digital signatures. Designed and built from scratch, replacing a complicated spreadsheet-driven process.

AI Product Engineering Read case study
AI analysis of GitHub commit history paired with task estimates running in beta

Leanware

An AI-powered internal tool built by Leanware engineers to measure how accurate task time-estimates were against the actual commit history. CodiQ analyzes GitHub commits with OpenAI and surfaces over- and under-estimation patterns for the team.

Managed Custom AI Agents Read case study
READY?

Stop managing operations. Let the system run them.

Show us the workflow that's eating your week. We will map it, show you what AI can automate, and tell you what we will run for you.

Tell us what you are trying to solve. We will map your workflows and show you exactly what AI can automate, and what we will run for you.