Every clinician knows the asymmetry, even if they’ve never named it. Take an insurance client and the documentation behind them grows into a paper stack a foot tall — dog-eared, bursting out of its binder clips, a new layer every single week. Take a self-pay client doing the exact same clinical work, and your obligation to the payer collapses to about one well-formed page.
Same human being. Same good work. Wildly different stacks. The gap is real, it’s enormous, and most of the people who feel it are doing the foot-tall version every week without quite deciding to. This post is about why that stack exists, why “just go self-pay” isn’t the answer it looks like, and what we built so a clinician can take insurance clients without becoming the stack.
Two worlds, and the documentation each one demands
The reason the asymmetry exists is that these are two genuinely different jobs that happen to share a name.
Self-pay / out-of-network. The client pays you directly. At some point they ask for a superbill — an itemized receipt with the dates of service, the diagnosis code, the CPT code, and what they paid. They take that one sheet of paper and submit it themselves to their insurer for whatever partial reimbursement they can get. You hand over the receipt and you’re done. The insurer almost never circles back to ask you for anything. That’s the single-page side: your documentation obligation to the payer is essentially one well-formed sheet.
In-network insurance billing. Now you bill the insurer directly. The claim itself is, almost insultingly, just a few codes — a diagnosis, a CPT code, a date, a fee. It would fit on that same single page. But the claim isn’t the work. The documentation behind the claim is the work, because insurers audit, and when they audit, the codes have to be backed by a defensible clinical record. That record is the stack:
- A progress note for every single session. This is the big one — the bulk of the paper. Usually SOAP or DAP, documenting symptoms, the interventions you used, the client’s response, and the continued justification for treatment. Medical necessity has to be visible on the page, session after session.
- A treatment plan with measurable goals, objectives, and target dates — reviewed and updated on a cadence, not written once and forgotten.
- An intake / biopsychosocial assessment — the comprehensive initial evaluation the whole treatment hangs off.
- A diagnosis that the documentation actually supports — not just a code, but a record that justifies the code.
- Sometimes prior authorization before treatment even begins, and concurrent reviews to keep sessions approved as you go.
Look at that list again. Every item is something a good clinician is already doing the thinking for. You already assess symptoms. You already plan treatment. You already track whether the client is getting better. The stack isn’t asking you to do new clinical work. It’s asking you to transcribe the clinical work you already did into a form an auditor will accept — and to do it for every session, on time, in the right format, forever.
That’s the tax. Not the thinking. The transcription.
”Just go self-pay” is a real strategy — and a real trade
Plenty of therapists have looked at that stack and chosen the single page. Go cash-pay, hand out superbills, let clients chase their own reimbursement. It’s a legitimate move, and for some practices it’s the right one.
But be honest about what it costs the people you’re trying to help. Going out-of-network doesn’t make the paperwork disappear — it moves it onto the client, who is now responsible for filing their own out-of-network claims, and onto a population that can afford to float your full fee while they wait on a partial reimbursement that may never come. The clinicians most able to go fully self-pay tend to serve the clients who least need the help affording it. In-network billing, for all its misery, is how a huge number of people actually reach care.
So the honest framing isn’t “self-pay good, insurance bad.” It’s: the stack exists for a defensible reason, and the clinicians who do the harder, more accessible thing get punished with hours of administrative transcription for it. That punishment is the problem worth solving. Not by deleting the stack — auditors are real — but by making the stack stop being something you write and start being something that assembles itself out of the session you already ran.
That’s the line we drew. Here’s how each layer of the stack works in Teja.
The progress note: drafted from the session, not from memory at 9pm
The progress note is the bulk of that foot of paper, so it’s where we put the most. The core idea: the note should be a byproduct of the session, not homework after it.
During the session, the raw material is captured for you. In a telehealth session, an ambient scribe transcribes the conversation live — but only while consent is explicitly on, and the transcript becomes the source the note is drafted from. For in-person work, there’s the Session Pad: a running capture thread you add to during or right after the session. Typed jots. A quick dictated voice clip. A photo of the handwritten notes on your legal pad, which gets read with OCR and turned into text. Moments you marked as important while they happened. It all lands in one place, attached to the appointment.
Then Teja drafts the note from that captured material, in the format you work in — SOAP, DAP, BIRP, and the other standard structures. The draft isn’t the final word; it’s a starting point that already has the symptoms, the interventions, and the client’s response laid out, so your job shrinks from writing a note from a blank page to reviewing and correcting a draft that already reflects the session. You can ask it to rewrite a section. You can fix what it got wrong. And nothing is locked until you sign it.
When you do sign, the note becomes immutable — corrections after that point happen through addenda, the way a defensible clinical record is supposed to work. If you’re a supervisee, the note routes for a supervisor’s co-signature before it’s final. That’s not a feature we bolted on for show; it’s the part of the stack an auditor cares about most, so it’s first-class.
The honest version of the pitch: we don’t make the note for you, and you wouldn’t want us to. We do the transcription so you can do the judgment.
The treatment plan: measurable goals, on a review cadence
A treatment plan that satisfies an insurer isn’t a paragraph of good intentions. It’s structured: goals, each with measurable objectives and target dates, with a defined review frequency so it stays current instead of going stale the day after you wrote it.
Teja’s treatment plans are built around exactly that shape. You write SMART goals, link the plan to the client’s diagnoses, and set a review cadence. The plan moves through real states — draft, approved, active, completed — and a practice keeps one active plan per client, so there’s never ambiguity about which plan is governing care. If you’re under supervision, approval is gated behind a supervisor. You can export the plan as a PDF, optionally de-identified, when you need to share it.
What we don’t do is pretend the goals are ours to invent. You enter the clinical goals — that’s clinical judgment, and it’s yours. The structure, the review reminders, the diagnosis links, the version history an auditor would want to see: that’s ours.
Intake: the assessment that turns into the first note
The biopsychosocial assessment is the foundation the rest of the stack sits on, and it’s usually the most tedious single document to get into the chart, because it’s long and it’s front-loaded.
In Teja, you assign an intake form and the client completes it — through a secure email link or in the client portal — before they ever sit down. When it comes back, two things happen that save you the worst of the transcription. First, you can generate an on-demand summary of the client’s answers: a clinical brief you read to get oriented fast, rather than scrolling pages of raw form fields. (That summary is generated when you ask for it and isn’t stored as the record — your reviewed clinical note is.) Second, the completed intake can seed a progress note directly — the form’s content bridges into your first note instead of being re-keyed by hand. You review, you sign, and the assessment is in the chart having existed, for you, as a review-and-confirm step rather than a blank-page marathon.
Diagnosis: a code your record actually supports
A claim’s diagnosis code is the thing an auditor most wants to see justified. So in Teja a diagnosis isn’t just a code you pick from a list — assigning an ICD-10 / DSM-5 code requires a written clinical justification, and each client has exactly one primary diagnosis, ranked clearly against any secondaries. Changes are never silently overwritten; they’re kept as history, with a reason, so the record shows how the clinical picture evolved.
Two connections make the diagnosis defensible instead of floating. Teja can suggest likely ICD-10 codes from the text of a progress note — reading what you actually documented and surfacing candidates above a confidence threshold, which you accept or reject. And a signed note can cite the specific diagnoses it addressed, through a permanent link between note and diagnosis. That’s the chain an auditor follows: the code points to the justification, the justification points to the notes, the notes point back to the code. In Teja that chain is wired, not assembled by hand at audit time.
The claim itself, and the reimbursement paper trail
Once the clinical stack exists, the actual billing is the small part — and Teja runs it end to end so the codes you already justified flow straight into money.
For in-network clients, Teja manages insurance policies, runs eligibility checks against the payer, handles prior authorization requests and status, builds the claim from your invoice’s service lines, and submits it through a clearinghouse. When the remittance comes back (the 835), payments auto-post against the invoice. Secondary claims and the correct / void / resubmit / record-denial cycle are handled in the same place. The clearinghouse is swappable, so the practice isn’t welded to one vendor.
For self-pay clients, Teja generates the superbill — that single page, done properly: a finalized packet with frozen provider and client details, diagnosis codes, and CPT service lines, numbered and renderable to a PDF you email straight to the client for their own reimbursement. (Superbills are a US feature today.) Both paths read from the same invoices, where CPT service lines carry their required diagnosis codes — so whichever world a given client lives in, the clinical record underneath is the same one.
What we don’t claim
A post like this earns its trust by being honest about the edges, so: Teja handles prior authorization, but it does not yet automate concurrent review — the ongoing reauthorization that keeps a long course of treatment approved. Treatment-plan goals are entered by the clinician, not generated. The intake summary is a convenience you generate on demand, not a stored part of the record. And the specifics of how protected health information is handled with any AI or transcription provider are governed by agreements and configuration we take seriously and verify deliberately — not something a marketing post gets to wave at. If a claim here matters to your compliance posture, ask us directly and we’ll show you the actual boundary.
The asymmetry, taken seriously
The asymmetry stings because every clinician feels it: the same human being, doing the same good work, generates one page in one world and a foot of paper in the other — and the difference is almost entirely who has to transcribe it.
We didn’t build Teja to talk you out of taking insurance. We built it so the stack stops being a tax on the clinicians who do the more accessible thing. The thinking is still yours — the assessment, the plan, the diagnosis, the note, the judgment about whether this person is getting better. What we took off your plate is the part that actually hurts: turning that thinking into a foot of audit-ready paper, by hand, every week, forever.
The note should fall out of the session. The plan should keep itself current. The diagnosis should already point at its own justification. The claim should be the small step at the end. When the stack assembles itself, the insurance side stops looking like a punishment for doing right by your clients.
That’s what we’re trying to make true: same care either way, and roughly one page’s worth of work to show for it.
If you take insurance and you’re tired of being the stack, the first three clients are on us. Bring a real week of sessions and see how much of the paper writes itself.