SaaS / Healthcare Training · Provider Directory · Geospatial Product
Graston Growth Engine
I shipped a Next.js App Router front end with Supabase PostgreSQL as the system of record for profiles, tiers, training levels, and support tickets.
For Graston Technique, the provider directory is the primary patient acquisition touchpoint — but it was built like a static list, not a growth asset. Signal: Real-time viewport spatial search
Real-time viewport
spatial search
$27k+ projected
Premier provider revenue
Provider hub
+ admin command center
This build supports CRM Architecture & Marketing Systems
Problem / System
The provider directory rebuilt as a two-sided product — map-synced search, Premier ROI visibility, and AI-accelerated support.
For Graston Technique, the provider directory is the primary patient acquisition touchpoint — but it was built like a static list, not a growth asset.
The Challenge
For Graston Technique, the provider directory is the primary patient acquisition touchpoint — but it was built like a static list, not a growth asset. Patients could not filter by location with precision. Providers had no honest view of profile performance. Clinical education was buried in manual support work that self-service and automation could absorb.
Scale broke in two directions: the patient path was too slow and imprecise for high-intent local search, and the provider path gave clinicians no reason to stay engaged between certification renewals.
The answer was not cosmetic search UI. It was treating the directory as a two-sided marketplace — measurable ROI for providers, real-time relevance for patients.
The Approach
I shipped a Next.js App Router front end with Supabase PostgreSQL as the system of record for profiles, tiers, training levels, and support tickets.
Spatial search is the technical spine: Google Maps exposes the viewport LatLngBounds; a debounced idle listener (300ms) batches fetches so the provider list stays synced with the map without hammering the database — the same pattern premium real estate products use.
The Provider Hub makes retention rational: profile views, site click-throughs, and funnel metrics tie to Premier positioning, including projected annual revenue under stated patient volume assumptions. The AI Assistant Console layers keyword-based ticket routing, after-hours auto-replies, and VIP escalation so corporate support scales without losing quality.
What got rebuilt
Map-Synced Spatial Directory
Viewport-bound Supabase queries against provider LatLng data with debounced updates — patients see who is actually near them as the map moves.
Provider Hub & Premier ROI Surface
Per-provider analytics plus Recharts dashboards that make profile performance and upgrade economics visible — including projected revenue for Premier tiers.
Admin Command Center
Operations view for support load, VIP alerts, and automation performance so the team can manage a national network without flying blind.
AI Assistant Console
Rules-driven routing for billing vs clinical vs onboarding paths, after-hours coverage, and escalation — less manual triage on repetitive tickets.
Supabase Schema & Membership Logic
Normalized model for profiles, membership tiers, and tickets so directory, analytics, and support share one source of truth.
The Process
How the system got built
Product framing
Defined two-sided success metrics — patient relevance and provider ROI — before touching schema design.
Spatial + data layer
Implemented Supabase spatial filtering, map integration, and debounce strategy for production-scale queries.
Provider + ops surfaces
Built Provider Hub analytics, Premier storytelling, admin command center, and automation console in parallel.
Launch & iteration
Rolled out on Vercel with continuous tuning on performance, SEO-critical directory pages, and support workflows.
The Outcome
Patients moved from paginated lists to real-time, map-aligned discovery. Providers shifted from passive listings to an active hub with defensible reasons to maintain profiles and consider Premier investment.
The automation layer multiplied clinical team capacity — faster routing, fewer repetitive touches, clearer escalation — without adding headcount.
This build sits inside the larger Graston platform story: +212% qualified leads, 95% overhead reduction, and 48 hours per week returned across the automation program. The Growth Engine is the public proof that the directory itself became revenue infrastructure, not a brochure.
What This Means For You
If your "directory" is really a database dump with a map pin on top, you are leaving patient intent and provider retention on the table. I build directories as products with measurable economics. That is what I build.
This build supports CRM Architecture & Marketing Systems
Ready to turn your directory into a growth and retention engine?
Let's talk about what that looks like.