Modern practice infrastructure for independent healthcare and holistic wellness practices. Lead capture, AI chatbot, booking page, blog, content system, SEO setup — all designed to route prospective patients to your existing EHR. I don't build patient portals, EHR replacements, telehealth platforms, or anything that handles patient health information. Front office infrastructure only.

Independent healthcare and holistic wellness practices in the United States, excluding California and New York. DPC, functional medicine, wellness, chiropractic, PT, health coaches, nutritionists, herbalists — any direct-pay or membership-based practice that needs a modern front office without the agency overhead. Practices that use Hint Health, Atlas.md, Elation, Jane, Spruce, Cerbo, Practice Fusion, Practice Better, or similar platforms for billing and clinical workflow. Works for practices pre-launch (0–90 days from opening) or established practices modernizing.

Clinical AI Audit ($2,500 flat, 2–3 weeks) — diagnostic audit of your digital stack, 25-page PDF plus walkthrough call. $2,500 applies as 100% credit toward Pro or 75% credit ($1,875) toward Lite. Launch Stack Lite ($3,950 flat, 3–4 weeks) — template-based practice website, ships fast. Launch Stack Pro ($7,500 flat, 6–8 weeks) — practice website built from scratch, with blog, RAG chatbot trained on your content, welcome email automation, advanced SEO, analytics dashboard. Flagship. Care Plan ($295/month, ongoing) — hosting, maintenance, monthly content updates, uptime monitoring, quarterly performance review.

If you're an established practice unsure whether your current site is the problem: Clinical AI Audit. If you're pre-launch with a tight budget and content ready: Launch Stack Lite. If you're established, well-funded, and ready for the flagship build: Launch Stack Pro. If you're on the fence between any of these, the 20-minute intro call usually lands on a clear recommendation.

Probably not. The four products are intentionally the entire catalog. Custom scoping kills solo operations. If your scope fits within the four products or the published add-ons, great. If it doesn't, I'll usually refer you to a specialist. Exceptions are rare and require a good reason.

Because the bottleneck isn't the website — it's the integration. A working practice front office needs a non-PHI intake that hands off cleanly to your EHR, an AI front desk that knows your service tiers and can answer patient questions, payment routing, a lead capture system wired to your calendar, and a launch sequence that doesn't break on day one. ChatGPT can write you copy. Squarespace can give you a template. Neither ships you a practice. That's what this does.

The $2,000 agencies ship template swaps on WordPress. I ship Next.js builds from scratch with AI chatbots, custom content systems, lead capture pipelines, welcome email automation, and production-grade deployment. For comparison: healthcare-focused agencies at my feature level typically charge $8,000–$15,000 and take 3–6 months. I'm in the middle at a tighter timeline because I'm one person with a tight stack. If $7,500 is out of budget, Launch Stack Lite at $3,950 handles the core practice site in a faster timeline.

The Launch Stack payment schedule is 50% at kickoff and 50% on launch. For Launch Stack Pro that's $3,750 upfront and $3,750 on launch, 6–8 weeks later. That's the only split offered. No monthly payment plans, no financing, no installments. If the 50/50 structure doesn't work, the engagement doesn't work — that's usually a signal we're not a fit.

No. The flat pricing is the pricing. The only formal price reduction is the Audit credit — if you do the Audit first ($2,500) and upgrade to a Launch Stack within 30 days, the $2,500 applies as 100% credit toward Pro or 75% credit ($1,875) toward Lite. That's the only mechanism. Negotiation off the published rates isn't on the table, and pushing on it on an intro call usually ends the conversation politely.

Depends on why. If the timeline slips because of client-caused delays (content arriving late, decision-maker unavailable, scope change requests), the launch date moves and the second 50% invoice is still due on the originally-scheduled launch date. If the timeline slips because of my own issues, the launch date moves and invoicing moves with it — you never pay for my delays. I communicate delay causes in writing as soon as they happen, not retroactively.

I don't handle Protected Health Information. My site routes all patient data directly to your EHR, which handles HIPAA compliance. Hexidus Labs is not a Business Associate under HIPAA because we don't store, process, or transmit PHI. This keeps builds fast, affordable, and out of regulatory scope. If you need infrastructure that actually handles PHI (patient portal, telehealth video, messaging with clinical content, prescription workflows), you need a different vendor. I'll refer you.

I don't integrate with Hint's API. Hint API access requires partnership approval that takes weeks to secure, and deep integration adds complexity that doesn't fit my 3–8 week build timelines. What I do instead: build your site with a clean HTTPS link from "Become a Member" buttons to your existing Hint enrollment URL (memberships.hint.com/your-practice/join). Same outcome for the patient, zero integration delay. Works for Atlas, Elation, Jane, Spruce, Cerbo, Practice Fusion, and every other major DPC EHR.

No. Patient portals handle PHI and require HIPAA-compliant infrastructure, authentication, audit logging, and ongoing compliance maintenance. Your EHR already does this. I don't build parallel patient portal infrastructure. If you need enhanced portal functionality, that's a conversation with your EHR vendor, not me.

Email content that references a specific patient's clinical information is Protected Health Information. Hexidus doesn't send that — Resend (my email service) doesn't sign BAAs, and building PHI-handling email infrastructure isn't part of the scope. For appointment reminders with clinical content, use your EHR's built-in reminder system (most modern practice EHRs have this) or a HIPAA-compliant service like Paubox. My welcome emails are practice-level only: hours, services, membership info, newsletter updates.

California and New York have enacted state-level AI regulations that create unclear compliance obligations for small studios using AI in client-facing applications. Rather than hire a lawyer to interpret ambiguous requirements for every build, I've opted out of both markets for 2026. If the regulatory picture clarifies in 2027, this may change. Until then, CA and NY practices need a specialist comfortable with state AI compliance — I'll refer if asked.

Launch Stack Lite: 3–4 calendar weeks from kickoff to launch, assuming content is delivered by end of Week 1. Launch Stack Pro: 6–8 calendar weeks same assumption. If content arrives late, the launch date moves one-for-one. If a client needs faster, rush delivery isn't offered in 2026 — I'd rather decline than rush. If a client needs slower, we can space milestones over a longer calendar if your team has capacity constraints.

Three things. First, content delivery in Week 1 — copy, images, practice info, branding assets. Second, review and approval on milestones (I send Loom videos weekly; you watch them and approve or request changes in writing). Third, decision-maker availability for the weekly Loom feedback loop. Total time commitment: maybe 8–12 hours over 6 weeks for a Pro build, mostly asynchronous. No weekly status meetings.

No. Weekly status calls are a form of make-work. Instead, I ship a 3–5 minute Loom video every week covering what shipped, what's next, and any blockers. You watch it on your time and respond in writing. If something urgent comes up, I'll Slack or email directly — and you can do the same. Intro call at the start, handoff call at the end, Loom updates in between. That's the full call structure.

You choose. Default path: Care Plan at $295/month for hosting, monthly content updates, uptime monitoring, and quarterly reviews. Most practices choose this path for at least the first year — it keeps the site current without needing a developer on retainer. Alternative path: $500 one-time transition engagement that transfers the code, repo access, and deployment credentials to your team or your chosen developer. No pressure either way. We'll usually decide on the handoff call in the last week of the build.

Next.js 16 (App Router) with TypeScript in strict mode. Tailwind CSS v4 for styling. shadcn/ui for component primitives. Framer Motion for animation. Supabase (standard tier) for lead capture. Resend for transactional email. Cal.com for consult booking. Claude API and OpenAI API for the chatbot. Vercel Pro for hosting. Google Analytics 4 for marketing page metrics. Same stack every build — no client-specific exceptions. If you need a tool outside this stack, it's quoted as a custom integration add-on.

You always own: your content, your branding, your domain, your Cal.com account, your Google Business Profile, and all your business data (leads captured, analytics, customer info). Those are yours from day one, every day. On Care Plan, the code itself lives in Hexidus's GitHub organization and runs on Hexidus Vercel infrastructure — transferring for a one-time $500 when you decide to self-host. Off Care Plan (self-hosting from day one), everything transfers at the $500 transition fee at launch. Either way, you're never locked in.

Content that's in the code (page copy, services list, pricing, team bios) requires a deploy, which means submitting an update request through Care Plan or deploying yourself if you're self-hosting. Content that's in external systems (Google Business Profile, Cal.com availability, chatbot FAQ in Supabase) you can update directly through those tools' dashboards without touching the code. The handoff documentation covers exactly what's where. Most DPC practices find Care Plan easier than managing deploys themselves.

Works fine. Any developer comfortable with Next.js and TypeScript can read the codebase. The code uses standard tooling (pnpm, ESLint, Prettier) and follows conventional architecture patterns. While you're on Care Plan, I'd appreciate a heads-up before another dev pushes to the repo so I can coordinate branches, but it's your code. Off Care Plan, your repo, your rules. No license lock-in, no proprietary frameworks.

Every Launch Stack requires a signed Master Services Agreement and Statement of Work before kickoff. The Audit requires a signed SOW only, no MSA. Care Plan is a click-through monthly terms agreement at signup. All three documents are short (4–8 pages total combined for a Launch Stack) and written in plain English. No aggressive IP assignments, no indemnification clauses that would make a lawyer nervous, no non-competes. Read them, sign them, we move forward. I'm happy to send samples before the intro call if it helps.

Audit: full refund if canceled before the kickoff call; non-refundable after kickoff call is held. Launch Stack kickoff payment: full refund if canceled before kickoff call; non-refundable after. Launch Stack launch payment: due on the originally-scheduled launch date regardless of client-caused delays, but never due if the delay is my fault. Care Plan: no refunds; cancel anytime with 30 days notice and you're billed through the end of the notice window. Add-ons: non-refundable once work begins, full refund if canceled before work starts.