Some parts of this page need JavaScript.

Skip to main content

Analytics only if you accept. Privacy

Beauty and wellness

Websites and booking for salons and spas

Online booking, appointment reminders and service pages that link into the booking system you already use.

Beauty & Wellness Digital Solutions

What we build

What a salon needs

  • Online booking

    Clients book online at any hour, with SMS and email reminders and staff schedules in one calendar.

  • Client records

    History, preferences and notes for each client, with rebooking reminders.

  • Loyalty rewards

    Points and member perks for clients who come back.

  • Retail and products

    Product sales in the salon and online, with gift cards.

  • Portfolio and social

    Galleries of your work and links to your social accounts.

  • Reporting

    Booking and sales reports by service, staff member and hour.

How it runs

From a search to a regular client

Booking from any page, reminders that cut no-shows, and a rebook nudge when it is time again.

01 Found02 Book03 Visit04 ReturnGoogle MapsInstagramService pageOnline bookingReminder, then visitReview requestRebook reminderProduct order

Running now

The same systems, running on software we built

Booking and customer records, calls and texts, local search: we build these for ourselves first and run them every day.
  • ButlerCRM, running
    Business Systems

    ButlerCRM

    ButlerCRM keeps contacts, deals, email, calendar and tasks in one workspace that updates live for everyone in it. We rebuilt it on Elixir/Phoenix so changes appear for the whole team as they happen.

    Read the case study
  • NexusDialer, running
    Business Systems

    NexusDialer

    NexusDialer puts outbound calling, the contact record and a personal AI assistant on the same screen, on the web and on the phone. It is our own contact-center product and is being built out now.

    Read the case study
  • Overwatch, running
    Sales & Marketing

    Overwatch

    Overwatch shows how a site is found in classic search, in AI answers and on the local map, then proposes the fixes. Nothing it proposes reaches a live site until a person approves it.

    Read the case study

FAQ

Questions

Do you have experience in my specific industry?
Our own products cover business systems, sales and marketing, finance, privacy and developer tools. Our client builds are med-spa websites, a med-spa Shopify store, an artist portfolio and website care for a home-service business. If we haven't worked in your niche, we say so. The work starts the same way: we learn your workflow, the rules that apply to it and how your customers buy, then build.
How do you handle industry-specific regulations?
We are not legal advisors, and compliance sign-off stays with you. Before a project starts, we ask what rules apply, agree the requirements with you or your compliance team, and build to them. Where a system would handle regulated data, such as patient records or card payments, we keep that data in the platforms built for it and link to them instead of storing it ourselves.
Can you integrate with industry-specific software?
Usually. Most current software has an API, and we connect to it directly. Where there is no API, we use webhooks, a tool like Zapier, or custom code. We will check the specific software you use before we agree the scope, and tell you if a connection is not possible.
What results can businesses in my industry expect?
We don't publish industry benchmarks, because results depend on your starting point, market and competition. Before a project starts, we agree what we will measure, such as leads, bookings or hours spent on a task, and record the starting numbers so you can see the change.

How we work

How a change reaches production

The same five gates for our own products and for yours. Nothing reaches your customers on the strength of a demo.

  1. 01 · Isolate

    Its own branch and workspace

    Every change starts in a separate copy of the code, so work in progress never touches what is live.

    git worktree add .worktrees/your-change
  2. 02 · Build

    Engineers with AI agents

    Agents write and test code beside us. They hold no passwords: every call they make goes through our gateway, which checks it and logs it.

    agent → gateway → policy · audit · call
  3. 03 · Prove

    Evidence, then review

    Tests, before-and-after screenshots of the running app, then independent reviewers. It does not move on until no serious finding is left.

    review: 0 high · 0 medium → pass
  4. 04 · Ship

    Deployed and checked live

    The pipeline builds and deploys. Then we check the running service itself, not just a green build.

    replicas 1/1 · image sha matches · health 200
  5. 05 · Watch

    Checked every night

    Each integration we run is tested against its provider every night, so a changed API is caught before your team notices.

    nightly: each integration vs its provider

Tell us what the business runs on

Send us your website and the booking system you use, and we will tell you what we would change.