Twelve weeks to a site that actually converts. The build cadence, the non-negotiable technical floor, and the launch-day measurement contract that separates a real deliverable from a brochure.
A healthcare practice website has one job: close the patient who found you. Every decision, the layout, the copy, the schema, the form architecture, is a decision about conversion.
Most agency builds miss this because they treat the site as a design deliverable instead of an operating system. They ship a beautiful brochure, bill for three months, disappear, and the practice discovers in month four that the Lighthouse score is 42, the forms leak PHI into analytics, and the schema graph is missing the Physician type that would have unlocked the Knowledge Graph panel.
SitePRO is the antidote. Twelve weeks, standardized cadence, measurable outputs, technical floor written into the contract. This is how it actually goes.
Practice audit, competitor deep-dive, patient-journey mapping, content inventory of the existing site, analytics review of the last twelve months. Output: a twenty-page scope document with the sitemap, priority order, and content requirements per page. Signed before design starts.
Brand tokens, typography scale, editorial patterns, component library. Not Figma slideshow. Design built against real content with real copy. Core Web Vitals architecture designed in from the start, not patched later. Output: an interactive design prototype for three key page types (home, service, location).
JSON-LD graph architected: Organization, LocalBusiness or MedicalBusiness, Person (physicians), Service or MedicalProcedure, FAQPage, BreadcrumbList. Content briefs per page. Medical reviewer assigned if YMYL. Output: content draft for every page, approved before code.
Custom theme built in Next.js (headless) or WordPress (Macbach-hardened theme on Kinsta). Pages built against real content, not lorem ipsum. Schema embedded server-side on every page. Core Web Vitals measured continuously during build. Output: fully populated staging site.
Forms built with server-side validation, no PHI in analytics, no PHI in remarketing, no non-BAA'd intermediaries. Call tracking wired to GA4 and the client's CRM. Conversion events defined and tested. BAA signatures where appropriate. Output: HIPAA-audited form flow, integration smoke-test passing.
Final QA: Lighthouse 90+ on every templated page, WCAG 2.1 AA clear, schema validated in Google's Rich Results Test, 301 redirects mapped from the old site. Launch. Launch-day proof report: measured LCP/CLS/INP on the new site vs. the old one, before and after Lighthouse scores, schema coverage diff.
Every SitePRO build ships with a technical floor we sign into the contract. Not targets we aspire to. Gates we will not launch without hitting.
Core Web Vitals green on every templated page. Mobile LCP under 2.5 seconds. CLS under 0.1. INP under 200 milliseconds. Measured via Lighthouse and PageSpeed on actual URLs, not local builds. The launch gate is a three-run median.
WCAG 2.1 AA clear. Axe-clean at every heading level. Keyboard-navigable end to end. Screen-reader tested on the three most-used page types. Color contrast passing on every surface.
Schema graph complete. Organization, LocalBusiness or MedicalBusiness, Person for each physician, Service or MedicalProcedure for each offering, FAQPage where the content earns it, BreadcrumbList on every page. Validated against schema.org and Google’s Rich Results Test.
HIPAA-safe forms. Server-side validation. No PHI in analytics, no PHI in remarketing pixels, no non-BAA’d intermediaries in the form flow. Tested on launch-day with a scripted walkthrough.
Analytics reconciled. GA4 firing, events named correctly, conversion events marked, cross-device stitching working, server-side Conversion API live for paid channels when paid is part of the engagement.
If any gate fails, we do not launch. We extend. SitePRO builds have blown their original launch date before. They have not blown their launch-day gates.
We have tried shorter timelines. They produce brochures. The reason is not complicated: the schema + content phase (weeks five and six) is where the practice’s actual differentiation gets captured. Rushing that phase means shipping generic copy against a generic schema graph and calling it a custom site.
We have also tried longer timelines. They produce over- iterated designs and stale content. Beyond twelve weeks, every additional week adds scope drift without adding conversion value.
Twelve weeks is the shortest interval that accommodates real discovery, real schema work, real HIPAA review, and a real launch-day measurement gate. Core build takes weeks three through eleven; week twelve is where we earn the gates.
Before scoping SitePRO, run the Site Vital Check on your existing site. It will tell you whether the build is a rebuild, a rescue, or a refresh, and what the actual performance floor looks like today.