BESPOKE ITGet an estimate

Zovi OSClinic and workforce SaaS

Branded clinic apps, run on one CRM engine.

Zovi gives aesthetic clinics, medspas, skin clinics, beauty studios and wellness centres the CRM and patient-engagement infrastructure behind their own branded mobile apps.

Enquire about this project (opens Sam's calendar in a new tab)
Client
ZoviOur own venture
Platforms
iOS, Android, Admin dashboard
The Zovi OS clinic dashboard on a laptop, with a client profile window in front of it

Overview

Zovi OS is the engine behind branded clinic apps. Aesthetic clinics, medspas, skin clinics, beauty studios and wellness centres run their patient relationships on it, and their patients use an app with the clinic's own name on it.

Why we built it

Clinics in the beauty sector want what large brands have: an app with their own name on it, and memberships, loyalty and offers that bring patients back. Building that from scratch is out of reach for a single clinic, and booking tools stop at the appointment. We saw the gap and built the platform ourselves, as our own venture.

What we built

Two layers that work as one. Zovi OS is the clinic CRM: clinic configuration, patient records, memberships, loyalty, offers and engagement, with dashboards for revenue, returning patients and the most booked treatments. On top sit white-label iOS and Android apps in each clinic's branding, with direct booking, push campaigns and Klarna instalments for eligible treatments where the clinic enables them.

How we worked

We set the clinic model and the patient journeys down first, then built the engine every clinic runs on before the apps that sit on top of it. Loyalty, offers and campaigns came next, then payments and analytics. Because every clinic runs on the same engine, a new clinic is a configuration, not a new project.

The technical choices

White label was the core decision: one engine, with each clinic's branding, plans and offers held as configuration. Booking connects to the systems clinics already use instead of replacing them. AI-powered marketing turns patient activity, treatment history and booking behaviour into personalised offers, and Klarna checkout follows each clinic's configuration and the provider's terms.

Where it is now

Zovi is live, and we run it. Clinics use it on a recurring B2B SaaS subscription, and Beauty Circle is the patient experience on the same platform. In the words of the investment team at Salford Ventures, the engine was built with real care: clean architecture and steady releases.

How it was built

Zovi OS, phase by phase.

What each stage of the project delivered, in the order we built it.

  1. Phase 1

    Scope and foundation

    The clinic model, the patient journeys and the white-label approach, set down before the build.

  2. Phase 2

    Zovi OS, the CRM engine

    Clinic configuration, patient records, memberships, loyalty, offers and engagement in one engine that every clinic runs on.

  3. Phase 3

    Branded patient apps

    White-label iOS and Android apps in each clinic's branding, with direct booking and connections to existing booking systems.

  4. Phase 4

    Loyalty, offers and campaigns

    Points, redemption and referral incentives, personalised offers from patient activity, and manual and automated push campaigns.

  5. Phase 5

    Payments and analytics

    Klarna instalments for eligible treatments where the clinic enables them, and dashboards for engagement, offers, memberships and revenue.

What we built

The product, feature by feature.

Clinic CRM

  • Zovi OS CRM engine

    Clinic configuration, patient records, memberships, loyalty, offers and engagement.

  • Membership management

    Recurring plans, benefits, member pricing and subscriptions.

  • Business analytics

    Dashboards for engagement, offers, membership performance and revenue.

Patient apps

  • White-label apps

    Clinic branding and branded patient experiences on iOS and Android.

  • Appointments and booking

    Direct booking journeys and connections to existing booking systems.

Engagement

  • Loyalty and referrals

    Points, redemption, referral incentives and repeat-visit engagement.

  • AI-powered marketing

    Personalised offers based on patient activity, treatment history and booking behaviour.

  • Push notifications

    Manual and automated campaigns.

Payments

  • Klarna checkout

    Instalments for eligible treatments, subject to the clinic's configuration and the provider's terms.

Inside the product

Zovi OS clinic dashboard with revenue, live activity and repeat patient charts
Clinic dashboard with revenue, returning patients and the most booked treatments
Zovi OS payments page with a filterable list of transactions
Payments ledger listing every transaction with its method, status and date
Zovi OS client profile with spend, visits, points and an insights panel
Client profile with visits, loyalty points, appointments and AI insights
The Zovi OS website hero with treatment photos arranged in a ring around the headline
The Zovi OS website that introduces the platform to clinics

Testimonial

In their words.

As investors we watch how a team builds, not only what it shows in a deck. The engine behind Zovi OS was built with real care: clean architecture, steady releases and a CRM the beauty sector actually needs. That made our conversations about Zovi very easy.

Marija

Investment team, Salford Ventures GmbH

Zovi OS, the CRM engine for the beauty industry

Industries

The same problem, industry by industry.

The industry this project sits in comes first. Pick another to see how the problem shows up there, and what we build for it.

Healthcare and clinics

The problem

The front desk spends the morning on reminder calls and rebookings. Patient records sit in one system, invoices in another, and nobody sees which patients have quietly stopped coming back.

What we build

An agent that answers booking and aftercare questions around the clock and passes anything clinical to a person.

Usually connects to

Talk about your industry

Every patient, every site, one view.

A surgical team at work while patient recalls and bookings run in the background

Professional services

The problem

Senior people spend their evenings on time sheets, engagement letters and status reports. Knowledge lives in inboxes, so every new case starts from a blank page.

What we build

An agent that drafts first versions of letters and reports from your templates and past matters, for a person to review and send.

Usually connects to

Talk about your industry

The firm's memory, finally searchable.

Two advisers in a meeting while a drafted document waits for partner review

Manufacturing

The problem

Orders arrive as PDFs and emails and get typed into SAP by hand. Planning runs on a spreadsheet that one person understands.

What we build

An agent that reads incoming orders and delivery notes, checks them against SAP and asks a person only when something doesn't match.

Usually connects to

Talk about your industry

Orders that reach SAP without a keyboard.

An engineer at a laptop in a robotics lab while an order is matched in SAP

Retail and e-commerce

The problem

Customer service answers the same twenty questions all day. Returns are processed by hand, and by Friday the shop, the stock and the books disagree.

What we build

A support agent that answers order and return questions from your shop data and passes anything unusual to your team with the context attached.

Usually connects to

Talk about your industry

Shop, stock and books that agree on Friday.

A shop assistant smiling at the till while a return is refunded automatically

Logistics and travel

The problem

Bookings, changes and documents arrive by email at all hours. The team types them into three systems, and customers call to ask where things stand.

What we build

An agent that handles booking changes and status questions, and passes disruptions to a person with the full history.

Usually connects to

Talk about your industry

The customer knows before they ask.

A container port at sunset while booking changes flow into the system

Finance and insurance

The problem

Applications and claims arrive as documents and get checked by hand against rules everyone knows by heart. Every audit means a week of collecting evidence.

What we build

An agent that reads applications and claims, checks them against your rules and prepares a decision for a person to sign off.

Usually connects to

Talk about your industry

An audit trail written while the work happens.

Two colleagues reviewing a claim at a desk while the rule checks run

Software and SaaS

The problem

The roadmap is full, support tickets keep pulling engineers off it, and the internal tools are scripts nobody owns.

What we build

A support agent that learns from your docs and past tickets, resolves the routine questions and routes the rest with context.

Usually connects to

Talk about your industry

Engineers back on the roadmap.

An engineering team at work while the support queue links to the roadmap

More projects.

View all projects

Want a system like this one?

From the first call to a system in production.

The people you meet in the audit are the people who build and run it.

Two colleagues smiling at a laptop after booking a call