THE BUSINESS BEFORE THE SYSTEM
Living Wholistically is a holistic wellness coaching business built around an 8-week transformation program. The coach, MJ, works with clients on nutrition, herbal support, lifestyle changes, and weekly accountability. The program is real, the results are real, and the clients were there.
The delivery system was not keeping up. Here's what running one client through the program actually looked like:
- The personalized protocol lived in a Google Doc, shared by link
- Meal guidance and herb recommendations were sent as separate PDFs
- Audio content was uploaded somewhere and linked manually
- Weekly check-ins happened over DMs — mixed in with every other conversation
- Notes about each client lived in the coach's head, or in scattered messages
None of this was broken in an obvious way. Every individual piece worked. But the experience clients paid a premium for arrived looking like a pile of links, and every week of the program generated manual work that didn't need to exist.
The pattern worth noticing: the business didn't lack vision or clients. The technology around the business hadn't caught up to the quality of the work. This is the exact gap ZELYQOR exists to close — and this project is where that realization came from.
WHAT THE SYSTEM NEEDED TO DO
Before writing any code, the scoping conversation was about how the business actually runs — not about features. Two distinct users emerged, with two distinct problems:
THE CLIENT SIDE
Clients needed one place to log in and find everything that was previously scattered: their personalized protocol, weekly phases, meal guidance, herbal recommendations, audio guides, and a way to submit their weekly check-in notes. No hunting through DMs. No "can you resend that link?"
THE COACH SIDE
MJ needed a dashboard — a private admin view to manage clients, read check-in submissions as they came in, leave notes on each client, upload new content, and control what each client sees based on where they are in the program.
That second part is what makes this infrastructure rather than a website. A public site markets the program. The portal runs it.
THE TECHNOLOGY DECISIONS
The stack was chosen for speed of delivery and long-term ownership — not novelty:
- Next.js — one codebase for the client portal and the coach dashboard, server-side rendering where it matters
- Supabase — Postgres database, authentication, and row-level security so each client can only ever see their own data
- Vercel — deployment and hosting, zero server maintenance for the business owner
- Resend — transactional email for the flows that need it
The row-level security piece deserves a mention. In a system where client A must never see client B's health information, access control can't be an afterthought bolted on in application code. Supabase RLS enforces it at the database level — even if the application layer has a bug, the database refuses to hand over rows that don't belong to the logged-in user.
AI-assisted development ran through the entire build — research, code generation, and debugging. That's a big part of why a full-stack, database-connected platform with two user roles shipped in under two weeks instead of two months. But every architecture decision above was a human call, made because of how this specific business works.
WHAT CHANGED FOR THE BUSINESS
The before-and-after is the whole story:
- Onboarding a client went from assembling a pile of links to creating an account
- Check-ins went from DM archaeology to a submissions inbox with client context attached
- The premium program finally felt premium from the first login
- Every piece of content now has one home, updated in one place
And the part that's harder to measure: the coach's attention moved back to coaching. The system absorbs the administrative load that used to leak into every week of the program.
THE LESSON THAT BECAME A COMPANY
This build is why ZELYQOR exists. Watching a real business run on disconnected tools — not because the founder lacked vision, but because custom software always felt out of reach — made the gap obvious. There are a lot of businesses in exactly that position: strong ideas, real expertise, and technology that hasn't caught up.
AI changed the economics of closing that gap. What used to require an agency and a six-figure budget is now within reach of a focused builder and a clear understanding of the business. The vision still has to come from a person. The system is now buildable.
Vision deserves infrastructure.
Want to see it? The portal has a live demo — client and coach side both. Credentials are on the Work page. And if your business is running on the duct-tape stack this note describes, tell us what you're building.