Build story

How we built Juniper with Specode in 2 days instead of 8 weeks

Juniper is a patient booking and intake platform with HIPAA safeguards built in. Patients pick a provider, pay a deposit, and do intake from home, and staff get their own side. We built it in 16 hours on Specode, our AI builder for healthcare.
See the build run
With Specode 2 days16 build hours
Traditional build 5 to 8 weeksdeveloper estimates
To scale, in working days.
Patient view
Provider view
Admin view
The challenge

An 8-week healthcare MVP is mostly handoffs

We scoped Juniper the way a cash-pay practice would brief us: patients book, pay a deposit, and do intake from home; providers run their own schedules; admins see all of it.

Our developers put that scope at 5 to 8 weeks. The most optimistic estimate was 2 weeks, and it assumed zero back-and-forth.

That back-and-forth is where the weeks go. Every change routes from product owner to designer to developer to QA and back. Compliance adds a layer that never makes it into the brief: audit logs, MFA, role-based access.

Every change routes from product owner to designer to developer to QA and back, and a half-baked feature can take 5 rounds Product owner Designer Developer QA 5 rounds on a half-baked feature
The solution

Everything before the visit, in one app

All 3 roles share one app. Admins manage providers and schedules, patients book and prepare, providers see intake up front.
Provider management
Admins add providers and manage each profile's name, bio, photo, and details.
Admin
Scheduling and availability
Admins set provider schedules. Providers manage their own time blocks and day overrides, with time zones handled throughout.
Admin
Provider
Discovery and booking
Patients browse providers from the landing page, then book a service with the one they choose.
Patient
Deposits at booking
Patients pay a deposit through Stripe to confirm the booking.
Patient
Digital intake
Patients fill out demographics, medical history, and appointment details before the visit, and can edit parts later.
Patient
Patient records
Intake flows to the staff side, so providers and admins can pull up each patient's history before the visit.
Provider
Admin
How we built it

Specode already knew most of what Juniper needed

If you've built a healthcare app with a general AI builder, you know where the hours go: explaining time zones, roles, and intake from scratch. Specode ships those as skills.
1
A roadmap before any code
The planning agent turned the brief into a roadmap and waited for approval, so scope questions got settled before the first screen existed.
2
Design set once, up front
The design agent defined Juniper's look before screens multiplied, and every later screen inherited it. The design never went to a separate designer.
3
Skills for the repeat work
The patterns every healthcare app repeats came in as tested skills, applied as a configuration step rather than rebuilt by hand.
4
Compliance checked inline
The HIPAA agent scanned Juniper's code for gaps in access control, audit logging, MFA, and PHI exposure, and every finding came with the fix prompt already written.
The design agent works through the screens with ready-made components.
The 3 questions planning stopped on: staff sign-in security, intake timing, and provider profile pages.
Skills go in, the run catches its own code issue, implementation finishes.
“

You can build this in Lovable and it takes you longer. Same with the other builders, because you have to specify every pattern that Specode already knows.

You can hit the same speed in Claude Code if you have a large skill library, but you only have one if you sat down and built it, and you only build it if you already have years of know-how building in that space. You have to hand the agent that knowledge in some form, and you pay for it with your time.

Christoph Hannak
CPO, Specode
The results

A live app worth building on

Juniper went live with logins for all 3 roles. Then one of our developers reviewed the codebase with a single question in mind: keep building on it, or rebuild?

The verdict was keep building. The review found strong UI and UX, and code cleaner than a typical AI-built project.
16hours
Build time, from brief to live app
411
Automated tests passing, with a clean lint runa
89/100a
Specode HIPAA agent score on the finished build
Where the time still went
Speed came from skills, and it slowed wherever a skill didn't exist yet. The patient list, chart views, and profile screens aren't covered by skills, so they need more iterations.

What was left for a developer: 1 to 2 days of refactoring, plus the release. The extra security work Juniper needed is now built into the HIPAA agent.
Ready to build your healthcare app?
Start from what Specode already knows.
Most of what a healthcare app repeats is already in Specode. Send us your scope and we'll map what's covered.

Already started in Lovable or another builder? We can move that code onto Specode.
Schedule demo