At a glance
What we built
A provider-discovery marketplace with location and treatment search, ratings, profiles and enquiry journeys connected to operational lead routing.
| Product | Best Med Spa |
|---|---|
| Interfaces shown | Desktop / web |
| Technology | Next.js · SQL · CRM integration |
| Core work | Location, treatment and rating filters · Provider profiles and comparison · Structured enquiries and CRM routing |
Product flow
How it works
Location, treatment and rating filters
Provider profiles and comparison
Structured enquiries and CRM routing
The interface
Inside the product
Desktop interface · 01
Location, treatment and rating filters
Design notes
Decisions behind the experience
The discovery question
Help a visitor find a provider that fits their treatment and place
- Treatment and location search
- Provider detail and comparison
Read the context
People looking for aesthetic treatments usually begin with a service, a location and a set of practical constraints. The discovery experience turns those inputs into provider results that can be compared before a visitor makes contact.
Profiles carry the detail the listing card cannot: treatment coverage, location, ratings and the provider information needed for a considered enquiry.
The enquiry path
Carry intent from search into a usable lead
- Structured enquiry forms
- Saved leads and CRM handoff
Read the context
The enquiry belongs to the provider and treatment the visitor chose. The site records the request before handing it to the CRM, so a temporary integration problem does not erase the visitor's action.
Follow-up actions are attached to the saved lead. That gives an operator a way to see whether the visitor wanted an appointment, a callback or more information, and to move the contact through the right next step.
Supply quality
Make the comparison worth trusting
- Structured provider records
- Reviewed listing changes
Read the context
Search quality depends on provider data. Profiles need usable treatments and locations, and ownership claims are reviewed separately so a provider cannot silently replace the listing a visitor sees.
The public discovery path and the provider-management path therefore meet at a controlled record. Visitors see a coherent profile while owners and staff maintain its accuracy.
How it was built
Keep search and follow-up connected
- Next.js and SQL
- GoHighLevel lead routing
Read the context
The Next.js site uses SQL-backed provider, claim and lead records. Matching logic narrows the candidates; the lead API saves the enquiry and records the outcome of its GoHighLevel handoff.
That design keeps the customer-facing search responsive while preserving a trace from the selected provider to the team's follow-up.
Design and development
What powers it
Platform and technology
Next.js · SQL · CRM integration
Core capabilities
- Location, treatment and rating filters
- Provider profiles and comparison
- Structured enquiries and CRM routing
Questions about the product
Questions about this product
What does this product help people do?
Help people compare providers by treatment, location and the details that matter to their search.
Which screens can I explore?
Location, treatment and rating filters.
What capabilities are covered?
Location, treatment and rating filters, Provider profiles and comparison, Structured enquiries and CRM routing.
Commerce & Platforms projects



