Clinical workflow
StepLadder
A therapist-facing operating system for structured, between-session work.
StepLadder turns therapy homework from vague suggestions into structured, measurable behavior change.
Tech stack
Architecture
Architecture. One Next.js app: therapist/patient UI and JSON APIs together—shared auth and validation.
- Next.js 14 — Layouts for dashboards vs homework flows; server lists where it keeps bundles small.
- React 18 — Forms, modals, worksheets; local state for SUDS and steps, posts to API routes.
- TypeScript — Shared types for assignments and APIs so client and route handlers stay in sync.
- Tailwind CSS — Utility spacing/type for dense clinical screens; breakpoints for phone vs laptop review.
- Supabase client — Browser client for auth-backed reads/writes to the shared Postgres project.
- Recharts — Therapist dashboards: completion, SUDS trends, modality mix from aggregated queries.
- PostgreSQL — Relational model: providers, caseloads, submissions, migrations in repo.
- Zod — Parse route bodies/params before DB; structured 4xx instead of raw constraint errors.
- Custom auth — bcrypt passwords, signed JWTs, role claims for therapist/patient/admin gates.
- Resend — Invites and reminders—templates and deliverability for between-session follow-through.
- Docker — Pinned Node images; one artifact for staging/production clinic demos.
What StepLadder does
- →Therapists assign scientifically grounded worksheets (CBT, DBT, ERP, ACT, and related modalities).
- →Patients complete assignments in a guided, structured interface, not ad hoc PDFs or generic notes apps.
- →The system captures behavioral and emotional data—for example SUDS, completion, and patterns over time.
- →Therapists receive clean, actionable feedback before the next session.
Typical model
1 hour session → nothing structured → next session
With StepLadder
1 hour session → guided work → measurable progress → higher-leverage next session
The core problem
Therapy does not fail in-session. It fails between sessions.
Homework is often assigned verbally or as a PDF. In practice, patients forget it, avoid it, or complete it incorrectly. The following week, clinicians are left with subjective recall: “Did you do the homework?” “Kind of.”
That gap implies:
- No reliable data on what actually happened
- Weak accountability between sessions
- Little room to iterate the treatment plan on evidence
Design insight
Therapy is behavior change. Behavior change depends on structured repetition and feedback. Today, that loop is often broken outside the room.
StepLadder is built to close the loop by turning homework into structured workflows (not vague tasks), trackable behaviors (not only self-report in session), and feedback systems clinicians can use before the next appointment.
Differentiation
Many products operate as content libraries, static worksheet repositories, or documentation helpers. The patient experience can reduce to: receive a file, complete it wherever, little visibility for the clinician.
StepLadder is oriented as execution infrastructure: define an intervention, guide the patient through it, capture execution, and surface outcomes—not only “assign worksheet.”
Contrast
Libraries: Here is material; good luck.
StepLadder: Assign → patient executes in-product → system records data → therapist reviews → next session targets real gaps.
The between-session loop
- Therapist assigns a structured intervention. Modality-specific, not generic busywork.
- Patient executes in the real world. Step-by-step guidance, minimal friction versus paper or unstructured apps.
- The system captures data. Emotional signals (e.g. SUDS), behavioral signals (completion, avoidance, rituals where relevant).
- Therapist reviews before session. What worked, where drop-off occurred, what to adjust.
- The next session is evidence-informed. Less guesswork, more iteration on what the data show.
Why “StepLadder”
The product treats therapy as incremental, progressive steps: climbing difficulty hierarchies, sequencing skills, and making visible where a patient is stuck versus ready to advance.
That maps directly to how ERP uses exposure hierarchies, how CBT sequences cognitive work, and how DBT builds capability over time. The name encodes the interaction model, not just branding.
What StepLadder optimizes for
Not engagement metrics, journaling for its own sake, or a vague “feel better” promise. The wedge is sharper: adherence and correct execution of clinical homework, with signals clinicians can trust.
Source of truth for progress — Grounded in behavioral traces, not only memory or recap in session.
Workflow engine — Assign, execute, review, iterate as a connected system.
Bridge between session and life — Where treatment plans meet everyday behavior.
Strategic framing
The layer between appointment and outcome is still under-built in digital mental health. StepLadder targets that layer explicitly: the system that helps therapy work outside the room, not only document what happened inside it.
Product stance
Design choices prioritize clinical clarity, patient safety, and appropriate scope: StepLadder supports the therapeutic relationship—it does not replace licensed care or emergency services.
Technical implementation favors a web-based, responsive stack so assignments can be completed where patients already are, with privacy and security treated as foundational rather than bolt-on.