Korean Dental Clinics Are Quietly Building Their Own Patient Apps
The vertical SaaS world is having a weird year. a16z keeps writing about how AI is eating vertical software, and every week another niche tool announces a raise. Meanwhile, the small businesses those tools are aimed at are doing something quieter. They're building the thing themselves.
I've seen this most clearly with Korean dental clinics.
The pain that never went away
Ask any 원장님 running a 2-chair clinic in Gangnam what actually hurts. It's not the treatment plans. It's the no-shows, the six-month recall reminders that never get sent, the parents of pediatric patients who need three touches before they book, and the fact that every existing patient management system either costs too much or is stuck in 2014.
The global market answer is a Curve Dental or a Dentrix Ascend. In Korea, the local answer has been closed hospital software with a five-figure setup fee and no mobile experience the patient actually wants to use.
What clinics are doing instead
A few clinics I've talked to recently are building small apps that do exactly what they need. Not a full EMR. Just the sharp edges.
Here's a real pattern one clinic wired up:
- Patients log in with Kakao (nobody's going to make a new account for their dentist)
- A recall reminder job runs every morning and finds patients whose last cleaning was 5 months and 3 weeks ago
- It sends them a KakaoTalk-style nudge with a one-tap booking link
- Payment for consultations gets handled through KakaoPay right in the app
- The 원장님 gets a Monday morning digest showing bookings, no-shows, and revenue
Every one of those is a preconfigured DontCode primitive. The cron job, the auth, the payments, the outbound messages. The clinic staff describe what they want; the platform wires it up. The abandoned checkout recovery recipe maps almost 1:1 to a dental recall flow, just with different timing.
Why now
Two things changed.
First, fine-tuned AI got good enough that non-technical clinic managers can describe what they want and get a working app. Not a wireframe. A real deployed thing with a URL.
Second, Korean payment rails and Kakao login stopped being the hard part. When KakaoPay is a toggle, not a three-week integration, the calculus for building your own thing changes.
What this means for anyone in a similar spot
If you run a small operation with 100 to 5,000 customers, you probably don't need the fancy vertical SaaS. You need three things automated, and you know exactly which three.
Pilates studios figured this out first. Dental clinics are next. After that it's veterinary, private academies, small law firms, physiotherapists. Every industry with a booking, a recall, and a payment.
If that's you, take a look at what we're building at DontCode. Or read through what other people have built and steal an idea. Either works.