Websites, intake, online booking, AI tools, payments, and ops for independent healthcare and 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 systems only.

Independent healthcare and wellness practices in the United States, excluding California and New York. DPC, functional medicine, wellness, chiropractic, PT, health coaches, nutritionists, herbalists — any direct-care 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 care workflow. Works for practices pre-launch (0–90 days from opening) or established practices modernizing.

Practice Growth Audit ($1,500 flat, 4 weeks) — diagnostic clarity before you buy AI tools or commit to a build. You get a 90-minute discovery call, three weeks of analysis, a 15–20 page written report, and a 60-minute readout call. Practice Website + Intake Build ($3,000 flat, 21 days) — a 5–7 page Next.js site with Tally or Typeform intake, Cal.com booking, on-page SEO, GA4, and full code/project ownership transferred at launch.

Start with the Audit if you're not sure what to automate, which tools are worth buying, or whether your current site is actually the bottleneck. Start with the Build if you already know you need a credible site, patient intake, booking, SEO basics, analytics, and ownership in 21 days. If you're on the fence, the 20-minute intro call usually lands on a clear recommendation.

Probably not. The two offers are intentionally the core catalog. Custom scoping kills solo operations. If your scope fits the Audit, the Build, or a clearly bounded post-launch add-on, 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 whole front office. A working practice 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. AI tools can help you draft copy. Squarespace can give you a template. Neither gives you websites, intake, online booking, AI tools, payments, and ops working together. That's what this does.

The Build is tightly scoped: 5–7 pages, patient intake, booking, on-page SEO, analytics, deployment, and ownership transfer. That scope is large enough to launch a real independent practice site and small enough to ship in 21 days without agency overhead. Introductory pricing is for the first cohort; the standing price is expected to be higher once the process is fully proven.

Both offers use a 50/50 split. Audit: $750 deposit to confirm the engagement and $750 on report delivery. Build: $1,500 deposit to confirm the slot and start, then $1,500 on launch day. No monthly payment plans, financing, or installment schedules.

No. The flat pricing is the pricing. The only formal credit is this: if you complete the Practice Growth Audit and engage Hexidus for a Practice Website + Intake Build within 60 days, $750 of the audit fee credits toward that build. Negotiation off the published rates isn't on the table.

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 systems that actually handle 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 systems, authentication, audit logging, and ongoing compliance maintenance. Your EHR already does this. I don't build parallel patient portal systems. If you need enhanced portal functionality, that's a conversation with your EHR vendor, not me.

Email content that references a specific patient's care information is Protected Health Information. Hexidus doesn't send that — Resend (my email service) doesn't sign BAAs, and building PHI-handling email systems isn't part of the scope. For appointment reminders with care details, 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.

The Practice Website + Intake Build takes 21 calendar days from kickoff to launch, assuming content input and feedback arrive on schedule. The timeline is structured: discovery and content scoping up front, build through days 6–14, review days 15–17, polish days 18–20, launch on day 21. If content or feedback arrives late, launch moves one-for-one.

Three things. First, complete the structured questionnaire and provide practice info, images, branding assets, and tool access early. Second, choose a design direction when the preview is ready. Third, review the site during the day-15 review window and send written feedback within 48 hours. Most of your work is asynchronous.

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.

The Build includes a 30-day post-launch support window for bug fixes and minor adjustments. You receive the GitHub repo, Vercel project, and ownership handoff at launch. After day 30, new changes are quoted as bounded hourly work or a separate add-on engagement.

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. AI tools 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 own your content, branding, domain, Cal.com account, Google Business Profile, analytics, intake submissions, and business data from day one. For the Build, the GitHub repo and Vercel project transfer to your account at launch. No platform lock-in, no proprietary framework, no forced maintenance plan.

Content that's in the code (page copy, services list, pricing, team bios) requires a deploy. Content that's in external systems (Google Business Profile, Cal.com availability, Tally or Typeform questions, analytics) can be updated directly in those dashboards. The handoff documentation explains what lives where and how to make routine changes.

Works fine. Any developer comfortable with Next.js and TypeScript can read the codebase. The code uses standard tooling and follows conventional architecture patterns. After transfer, your repo is your repo. No license lock-in, no proprietary frameworks.

Every paid engagement uses a short, plain-English agreement before kickoff. The Audit uses a diagnostic SOW. The Build uses an SOW that covers scope, timeline, ownership transfer, payment schedule, revision limits, and launch handoff. No aggressive IP assignments, no non-competes, no mystery terms.

Audit: full refund if canceled before the discovery call; non-refundable after the discovery call is held, unless I determine after discovery that AI or automation will not meaningfully help your practice in the next 12 months. Build deposit: full refund if canceled before kickoff; non-refundable after work begins. Build launch payment is due on launch day, but never due for a delay caused by Hexidus.