DAY 0 · 20 MINUTES

First Contact

A 20-minute call. No pitch.

You book a 20-minute call through the site. No intake form. No long questionnaire. No “please fill out this 30-question brief before we can talk.”

On the call: you tell me about your practice, your timeline, your EHR, and your budget. I tell you which product makes sense — Audit, Lite, Pro, or “you should probably hire someone else.” About one in four first calls ends with me recommending you hire someone else, because the fit isn't right. That's a good outcome for both of us.

If we're a fit, I send a short SOW within 48 hours. You review, sign, and pay the kickoff invoice. That's the full engagement start.

What I'll ask:

• Your practice name, location, and current launch status
• Your EHR or planned EHR (Hint, Atlas, Elation, etc.)
• Your target launch date
• Whether you have a current site, and if so, what's broken about it
• Your budget range for this engagement
• Any hard constraints (compliance, brand, stakeholder approvals)

WEEKS 1-2 · OPTIONAL BUT RECOMMENDED

Clinical AI Audit

Know what's broken before you rebuild.

For practices starting with the Audit: I spend two weeks auditing your digital stack end to end. Performance, intake, SEO, competition, reputation, tech stack, patient acquisition economics. You get a 25-page PDF, a 1-hour walkthrough call, and a 90-day roadmap.

If you decide to move to a Launch Stack within 30 days of Audit delivery, $2,500 applies as 100% credit toward Pro or 75% credit ($1,875) toward Lite. Phase 2 kicks off the same week.

For practices going straight to a Launch Stack: skip this step. You go from Step 01 directly to Step 03.

What you get:

• 25-30 page PDF report covering 9 audit domains
• Top 10 findings prioritized by revenue impact
• 90-day implementation roadmap
• 1-hour recorded walkthrough call (you keep the recording)
• 30 days of async email access for follow-up questions

WEEKS 1-8 · THE WORK

The Build

Kickoff, weekly Loom updates, one revision round.

Kickoff call is 60 minutes for Lite, 90 minutes for Pro. We align on scope, content delivery schedule, decision-maker access, and target launch date. You get a clear calendar — when your content is due, when design review happens, when launch week starts.

I ship updates weekly via Loom video — three to five minutes covering what shipped, what's next, and any blockers. No status meetings. No weekly sync calls. No account manager asking “how's it going?” If I have a question, I'll Slack or email. If you have a question, same.

Content delivery is on you in week one. Copy, images, practice info, branding assets. If content arrives late, the launch date moves by the same number of days. I'd rather be honest on day three than apologetic on day forty.

One revision round is included per build. Revision scope is content edits, copy tweaks, design adjustments within the existing structure — not new pages, not new components, not scope expansion. Additional revisions are $500 per round.

Timeline by product:

LAUNCH WEEK · LIVE SITE

Launch

QA, DNS cutover, handoff training.

Launch week is tight and scripted. Final QA across desktop, tablet, and mobile. Accessibility audit with axe DevTools. Schema validation with Google's Rich Results Test. Lighthouse performance check on every page. Cal.com embed tested. Chatbot tested against edge cases — “Can you prescribe me something?” “What's my diagnosis?” — confirming the clinical safety guardrails hold.

DNS cutover happens in a scheduled launch window. Most launches happen Tuesday or Wednesday mornings. Your site goes live on Hexidus Vercel infrastructure. Nameservers point to Vercel. SSL certificate is active within minutes.

Handoff call is 45 minutes for Lite, 90 minutes for Pro. We cover how to access Supabase leads, read Slack notifications, submit content update requests, manage the Google Business Profile, view analytics. You leave the call knowing how to run the site.

Final invoice milestone collected on launch. First Care Plan month begins.

What happens on launch day:

• Final QA pass across all browsers and devices
• Accessibility audit (axe DevTools, WAVE)
• Schema markup validation (Google Rich Results Test)
• Lighthouse performance scan (target: 90+ across all metrics)
• Chatbot edge case testing (confirm clinical refusals hold)
• Cal.com embed smoke test (real booking end-to-end)
• Lead capture test (form submission → Supabase → Slack)
• DNS cutover in scheduled window
• SSL certificate verification
• Google Search Console verification and sitemap submission
• Handoff call and written runbook delivery

MONTH 1+ · ONGOING

Ongoing Care

Care Plan by default. Or take the code in-house.

You choose. The default path for Launch Stack clients is Care Plan at $295 per month — hosting stays on Hexidus infrastructure, I handle monthly content updates, monitor uptime, and review performance quarterly. You focus on running your practice.

The alternative path is taking the code in-house. One-time $500 transition engagement. I hand off complete GitHub repo access, Vercel deployment credentials, Supabase project ownership, Resend account setup guidance, and a written runbook for ongoing maintenance. 30-day handoff support window included.

About 80% of Launch Stack clients choose Care Plan. The 20% who don't usually have an existing developer or technical partner already in place.

Either way: you always own your content, your branding, your domain, your Cal.com account, your Google Business Profile, and your business data (leads, analytics, customer info). The only thing on Hexidus infrastructure during Care Plan is the code — and that transfers cleanly when you want it.

Flat pricing, always.

No hourly tracking. No scope creep surcharges. No surprise invoices.

Every product has a flat price published on the Pricing page. The price you see on kickoff is the price on the final invoice. Add-ons are quoted upfront before work begins, paid upfront, and never retroactively billed. If a project needs scope beyond the original SOW mid-build, it's a change order — quoted, signed, and paid before work continues. Never invoiced after the fact.

Honest timelines.

I quote realistic windows and stick to them.

When I quote 3-4 weeks for Lite or 6-8 weeks for Pro, that's the real timeline based on my capacity and your content delivery. If something slips — usually because content arrives late or a surprise technical issue eats a Tuesday — I tell you the same week, not the day before launch. The Loom updates make this visible. No "we're on track" when we're not.

Direct access to me.

One operator. One point of contact. No layers.

Every email, every Slack message, every Loom update comes from me directly. No account managers, no project coordinators, no offshore subcontractors, no "we'll get back to you" ping-pong. That's a feature and a limit — I respond within 48 hours on weekdays, not 8 hours, and not on weekends when I'm on night shifts. If that pace doesn't work, we're not a fit.

Strict scope boundaries.

I don't stretch scope to close deals.

Every SOW has a defined scope. Mid-project requests that fall outside it get quoted as change orders — priced, signed, paid upfront. I don't quietly absorb scope creep to stay "easy to work with." It's the single fastest way for a solo studio to go under. Respecting the scope line is respect for the work, for the pricing, and for every other client whose timeline depends on mine.

No HIPAA handling.

Your EHR does HIPAA. My site does marketing.

I architect Protected Health Information out of Hexidus infrastructure entirely. Your EHR handles patient records, billing, clinical data, and HIPAA compliance. My site handles lead capture, booking, chatbot, content. The link between them is a plain HTTPS redirect to your existing EHR URL. If you need infrastructure that handles PHI — patient portals, telehealth video, prescription workflows, condition-specific messaging — I'll refer you to specialists. This isn't a cost-cutting shortcut. It's the architecture that keeps builds fast, prices honest, and legal exposure minimal.