Most of what a therapy practice needs from the internet is a website: a place that explains who you are, what you treat, and how to reach you, that shows up when someone searches, and that doesn't cost you $80 a month forever. That's the bulk of the work described on this site, and it's genuinely almost always the right answer.
Almost always. Every so often a practice asks for something a website can't do, because the thing they're describing isn't a page. It's software.
The actual difference
A website is read. A visitor loads a page, gets information, maybe fills out a form. A web application is used: someone logs in, does something, and the site remembers it and changes state. A client books a real appointment slot instead of emailing to ask if Tuesday works. A team updates a shared record instead of texting it around. A practice manager pulls a report instead of reconstructing one from memory. If your mental picture involves a login screen and an ongoing relationship with data, you're describing an application, not a page, and that's a different build with a different price shape, because it needs a database and hosting that isn't free.
Examples that actually come up
- Client portals. Secure document sharing, intake forms that save progress, a place clients log back into instead of re-filling a PDF every visit.
- Booking systems you actually own. Not a $30/month third-party embed with someone else's branding bolted onto your carefully designed site, a scheduler that looks like you and doesn't hand a vendor your client list.
- Internal tools. A group practice's referral tracker, a shared intake queue, anything currently living in a spreadsheet that six people email back and forth, where someone's always working off the wrong version.
- Directories & interactive assessments. Searchable, filterable tools, quizzes that branch based on the answer given, the kind of thing The Safer Sounds Club's workshop quiz does. More program than page.
If you're not sure which one you need, that's a reasonable place to start the conversation, not a prerequisite for having it.
Where that work happens
therapistweb.design stays intentionally narrow: static, hand-coded, no database, no server, no monthly bill, because that constraint is what makes the no-platform-fee promise possible in the first place. A real application needs a database, authentication, and ongoing hosting that costs something, different tools for a different job. I build that end of things under a separate studio, Studio Null. Current resident project over there is a site whose entire HTML is generated live by PostgreSQL, which should tell you roughly how much I enjoy this side of the work.
Not sure whether what you're picturing is a page or a program? Tell me about it either way, I'll point you at the right build, mine or otherwise.