A platform for a practice that's about to become a teacher.

An information site that didn't even have a working header.

The desktop version of the prior site was structurally broken. The header only rendered on the 404 page; the rest of the site shipped without navigation. Mobile worked on a coin flip. The information was there, but the chassis was past the point where another patch was going to fix it.

More important than the bugs, the site wasn't the right kind of thing for where the practice was going. Myofascial Pain Solutions has spent 25 years developing a method other practitioners want to learn. The next phase of the business is a teaching practice: courses, certification, and a productized version of the work that has paid the bills for two decades.

“Our patients have been everywhere. PTs, massage therapists, chiropractors, neurologists, orthopedic surgeons. They get here frustrated, wanting answers. The people who refer them want to know how to do this work too.”

Myofascial Pain Solutions, on what comes next

Build the foundation now. Stand the business on it later.

The thing the practice needed wasn't a new homepage. It was infrastructure it could grow into. We treated the engagement as the first phase of a software product, not as a marketing-site rebuild.

What that meant in practice:

• Today, the site is informational. The Root Cause Analysis method is the spine of the homepage, with conditions, techniques, and patient stories sitting around it. Booking is still a real call to a real person.
• Tomorrow, it's a teaching platform. The same Next.js application is built to host gated courses, certification flows, member accounts, and content libraries when the practice is ready to launch them.
• The method is the product. Everything we built treats Root Cause Analysis · Pain Solution System™, SeatGenie®, and Direction Specific Positional Myofascial Realignment™ as named intellectual property the practice will eventually license.
• One codebase, many surfaces. The site is also the starting point for a possible mobile app, a B2B portal for referring providers, and a direct-to-practitioner course platform. Same React components, different front ends.

A real React application, not a brochure with a CMS bolted on.

Stack: Next.js 16 (App Router) + TypeScript + Tailwind, MDX for the long-form condition pages, Vercel hosting. The information layer ships today; the application layer ships as the business is ready for it. Authentication, course content, payments, and community surfaces are scaffolded into the architecture rather than bolted on later.

Accessibility is non-negotiable for a chronic-pain audience. Body text holds at 18px minimum, contrast above WCAG AA, and the hero never traps focus. Mobile actually works on every page, not just the 404.