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 offer makes sense — Audit, Build, 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)

4 WEEKS · OPTIONAL BUT RECOMMENDED

Practice Growth Audit

Know what's broken before you rebuild.

For practices starting with the Audit: I spend four weeks auditing your practice growth stack end to end. Performance, intake, SEO, competition, reputation, tech stack, patient acquisition economics. You get a 15-20 page PDF, a 60-minute readout call, and a 90-day roadmap.

If you decide to move to a Practice Website + Intake Build within 60 days of Audit delivery, $750 of the $1,500 audit fee credits toward the build.

For practices going straight to the Build: skip this step. You go from Step 01 directly to Step 03.

What you get:

• 15-20 page PDF report covering the key audit domains
• Top findings prioritized by revenue impact
• 90-day implementation roadmap
• 60-minute recorded readout call (you keep the recording)
• 30 days of async email access for follow-up questions

21 DAYS · THE WORK

The Build

Kickoff, weekly progress updates, one revision round.

Kickoff call is 45 minutes. 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 weekly progress updates 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 starts immediately. 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 twenty.

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.

Build timeline:

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 and intake routing tested end to end.

DNS cutover happens in a scheduled launch window. Most launches happen Tuesday or Wednesday mornings. Your site goes live on Vercel before the project transfers to your account. Nameservers point to Vercel. SSL certificate is active within minutes.

Handoff call is 45 minutes. We cover how to access leads, manage intake and booking tools, use the Google Business Profile prep checklist, view analytics, and work with the transferred codebase. You leave the call knowing how to run the site.

Final invoice milestone collected on launch.

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)
• Intake form smoke test
• Cal.com embed smoke test (real booking end-to-end)
• Lead capture test from form submission to destination inbox or CRM
• DNS cutover in scheduled window
• SSL certificate verification
• Google Search Console verification and sitemap submission
• Source code and project ownership transfer
• Handoff call and written runbook delivery

Flat pricing, always.

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

Every offer has a flat price published before the first call. 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 21 days for the Build, 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 weekly 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 progress 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 systems entirely. Your EHR handles patient records, billing, clinical data, and HIPAA compliance. My site handles lead capture, booking, AI tools, and content. The link between them is a plain HTTPS redirect to your existing EHR URL. If you need systems that handle 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.