What we built
- 01
Client records, enquiries, bookings, payments and relationship marketing in one workspace for beauty and wellness operators.
- 02
Branded booking and form journeys, with Stripe payments, email and SMS connected to the client record.
- 03
Magic AI and connected assistants use governed workspace tools, with approval and delivery controls around actions.
- Outcome 01
- A clearer path from first enquiry to booking, payment and a return visit.
- Outcome 02
- Follow-up built around client history and service cycles rather than disconnected reminders.
- Outcome 03
- One workspace for the owner, with AI helping prepare work between appointments.
Product strategyMarket researchPlatform architectureDesign and buildPayments and messaging integrationsAI and MCP tool layer
How it's built
- Workspace and data
- Next.js, React and TypeScript power the web app, with Tailwind CSS, Zustand and Framer Motion. Supabase provides PostgreSQL, authentication, storage and realtime updates, with workspace boundaries enforced on the server and in database policies.
- Payments and communication
- Stripe Connect handles studio payments. Resend sends email and Twilio sends SMS; Gmail and Google Calendar provide connected mailbox and calendar workflows. Provider webhooks update delivery and payment state rather than assuming a request succeeded.
- AI and connected assistants
- The Vercel AI SDK and AI Gateway connect Magic AI to configured OpenAI and Anthropic models. OAuth-protected MCP tools expose the same operating data to external assistants, with approval and delivery controls around writes.
- Operations and hosting
- Vercel hosts the web app, API routes and scheduled jobs. Upstash Redis supports rate limiting, PostHog records product activity, and MJML produces responsive email templates. Live payments and unattended outbound automation depend on studio setup and enabled delivery controls.
The full story
A beauty business CRM built to keep regulars coming back.
MAGIC is our own product for the beauty and wellness businesses where the owner is also the technician. Their day is spent with clients; the messages, admin and follow-up collect around the edges.
The product is built around the customer relationship. A booking tells you when someone is coming. Their service history and usual cycle tell you when they are due back. MAGIC brings those records together so follow-up has useful context rather than being a generic reminder.
The workspace connects enquiries, clients, calendar, bookings, branded forms, proposals, invoices, payments, reporting and campaigns. Owners can connect Gmail and Google Calendar, while public booking and form pages keep the business's own identity.
Underneath, Next.js and React run the web app; Supabase provides PostgreSQL, authentication, storage and realtime data. Stripe Connect handles merchant payments, Resend handles transactional and campaign email, and Twilio handles SMS. Scheduled jobs coordinate reminders, follow-up and operational work.
Magic AI uses the Vercel AI SDK and AI Gateway, with configured OpenAI and Anthropic provider paths. An OAuth-protected MCP endpoint exposes workspace tools to connected assistants. Model reasoning, proposed actions, approval and provider delivery are separate steps, so a draft or an accepted tool call cannot stand in for a completed send or payment.
The product remains in build with invite-gated access. Studio onboarding, delivery settings and payment-provider readiness determine which workflows can run for a particular business; unattended messaging and live money need their own operating proof.
