Stop renting your booking app. Build your own.

You pay every month for software that was not built for you

You pay for your booking app every month. You build your client list inside it. Then the price goes up, or a new fee shows up, and you have no say.

It does most things fine. But it was built for every salon in the country, not for your services. Your fill window, your deposit rules, your consent forms, your patch tests. So you work around it with notes, screenshots and paper.

And if you ever want to leave, your client list usually comes with you. Your notes and visit history often take a support request.

It starts by asking what you do

The first thing on the roadmap is a picker. You choose your trade, or a mix of them, because a lot of us do more than one thing: skin and lashes, hair and nails, tattoo and piercing. Something not on the list? Type it in. The roadmap then ticks the features your kind of work usually needs, and you untick or add whatever you like. It only shows you what fits your work, and every other feature is one tap away, from card on file and loyalty cards to classes and bridal bookings. Want something nobody thought of? Type your own idea, and it gets its own prompt, with tips on how to ask for exactly what you want.

Pick more than one and the roadmap builds for the mix: services clients book together in one visit, what has to wait after what, and which forms and rules belong to which service.

Then Claude interviews you, one question at a time, with questions written for your trade: your fill window, your touch-up policy, your patch tests, what you write down after a visit, what you check before you start. Every answer becomes your setting, because every artist does it a little differently.

Some of my services have three parts: application, processing, and finishing. During processing I am free to take another client, but the chair stays held.

In {your app}, let me set the minutes for each part, per service. During processing, let other bookings fit only if they fit inside that gap and do not need the same chair.

Keep this separate from clean-up time, which blocks me completely. Mixing up the two is how stylists get double-booked.

Before you write any code, tell me your plan and which screens change. Then build it, and give me a short list of things to try by hand to check it works.

I am not a tech person. I am the one with the clients.

I needed my client notes, photos, forms and homecare plans in one place that worked the way my room works. Nothing I paid for did all of it. So I built it, at night and between appointments, with Claude doing the code and me deciding what it should do.

I could not afford to do anything twice. So before each step I looked it up until I was sure. That turned into thousands of hours of research and testing, and then into this roadmap.

You do not write code. You describe what you want in plain words, you copy and paste what the roadmap gives you, and you check that it works. The skill you need is the one you already use every day: knowing exactly how your clients should be taken care of.

Times are changing in our field, and so are we. If I could build mine, you can learn to build yours.

Your app changes the day your business does

A booking app you rent changes when its company decides to. Your own app changes when you decide to.

Adding a new service? Changing your deposit policy? Taking a new course and adding brows to your lashes? Your board changed a rule, or three clients asked for the same thing? You describe the change in plain words, Claude makes it, and you check it. Often the same day, between clients.

The roadmap ends with the prompts you use for that, forever: "my business changed, update my app", the five-part feature prompt, and the exact way to ask when something breaks. The app is yours, so it keeps up with you.

What you give up when you own it

Owning your app is a real trade. Here is the other side, before you buy, not after.

Keep your current booking app until yours works. Nothing here asks you to switch on day one. Build it on the side, test it with a few regulars, then move over when you are ready.

The right prompt is the hard part. I did it for you.

Anyone can type a request into Claude. Getting back exactly what you wanted is the hard part. It comes down to the prompt: what to ask, how to word it, what to tell Claude not to touch, and which one comes first. I put thousands of hours into working that out on my own app.

So you skip it. Every prompt that worked is here, in order, with exact directions: where to paste it, what you should see come back, and what to check before the next step. You copy, you paste, and Claude does the work with you. You hit the ground running instead of spending months learning how to ask.

It is one live page you work inside. You tick steps off, it remembers where you got to, and a short walkthrough video shows you how to start.

You pick your trade, your state and your features once. Every prompt then uses your answers instead of a blank.

Everything, on one page, for $97

The whole build, week by week

The weeks show the order, not a deadline. Go at the pace your book allows. Your current booking app keeps running the whole time.

Claude does the work. You check it.

You never sit staring at an empty chat box trying to work out how to word it. Every job on the roadmap already has its prompt written, it fills in with your trade and your choices, and it tells you whether it goes in Claude Chat or Claude Code.

The step people find out about too late

Who this is for

What building your app actually costs

Not what this costs. What your build costs, so you can decide before you spend anything. Most of it is free, optional, or only matters if you go to the app stores.

Once your clients use it, plan on your Claude plan plus hosting each month, and card fees when you take payments. Text reminders add a carrier registration. The app stores are optional, and the roadmap says so in writing.

Questions people ask