Why We Built OpenChair: The Story Behind the Platform

OpenChair started with a simple product question:

What should salon software do for the people actually running the venue?

A salon or barbershop already has enough moving parts. Appointments change. Clients message from different places. A colour service can use a stylist's time differently from a haircut. Someone cancels. Someone else is waiting for an earlier appointment. The team needs client history before the next service. The owner still has to understand what happened at the end of the week.

Software should make those jobs easier to manage.

That became the basis for OpenChair.

Keep the chair working#

A booked hour is part of the venue's capacity.

When it disappears through a cancellation, a missed appointment or poor scheduling, the operator cannot store it and use it next week.

That shaped a lot of the way we think about booking.

OpenChair includes tools for deposits and booking controls, waitlists, Processing Gaps, Gap Fill and Reconnect.

They solve different problems.

A deposit asks for commitment before selected appointment time is held.

Processing Gaps can represent eligible processing time inside services where the stylist is not continuously occupied.

A waitlist keeps track of clients who want another opportunity to book.

Gap Fill can help match an opening with suitable demand.

Reconnect supports configurable follow-up for clients who have not returned.

None of those tools guarantees a fuller diary or more revenue.

The principle is narrower: if time becomes available, or a regular client drops out of their usual rhythm, the system should give the operator a practical way to act on it.

Keep useful client context close to the booking#

The next appointment rarely starts from zero.

A returning client may have previous notes, photos, colour information, forms or a usual staff member.

A new client may arrive with an inspiration image but no idea which service name matches what they want.

We wanted that context to live close to the appointment rather than across screenshots, messages and someone's memory.

That is why OpenChair includes client history alongside more specific workflows such as the Colour Formula Library and Style Match.

Style Match helps a client share their current hair, inspiration and request, then uses the venue's own service catalogue to guide the next step.

It is not a diagnosis and it does not autonomously create a booking.

The same principle applies elsewhere in the product: store the useful information, keep it connected to the client and make it available to the authorised person who needs it.

Build the booking around the venue, not a marketplace identity#

Many salons and barbershops already bring in clients through their own reputation.

Someone finds the venue through Google, follows a stylist on Instagram, hears about it from a friend or returns because they have been there before.

We wanted the next step to remain centred on that business.

OpenChair's storefront can carry the venue's services, team, booking rules and brand into the booking experience. Clients can make an initial booking without first creating an OpenChair consumer account.

Staff can also have public profiles and their own booking links where configured, while the resulting booking still belongs to the venue's OpenChair setup.

That direct-booking model also shapes the commercial side of the product.

OpenChair charges zero booking commission on bookings made through an OpenChair storefront. Card-processing fees still apply.

A marketplace can be valuable when it creates demand for a business. OpenChair's model is built for operators who also want a direct route for the clients they attract themselves.

Reduce admin without taking control away#

AI is useful when it removes a piece of work without quietly making a decision the operator expected to control.

That boundary matters to us.

OpenChair Assistant can work with venue context to answer questions, prepare drafts and surface supported actions.

On Pro, Smart Replies can Auto-send eligible, high-confidence SMS replies through a dedicated number in Australia or the United Kingdom and connected Instagram DMs where configured.

Owners choose the supported intents that have authority to Auto-send.

Confidence, safety and other controls can move a message to Draft or escalation instead.

Email replies remain draft-only.

Booking actions remain review-first.

We do not think the useful version of salon AI is one that pretends the operator no longer needs to be involved.

The useful version handles routine work where the rules are clear and keeps the person responsible for the venue in control of the decisions that need them.

Make the commercial model understandable#

Software pricing should be something an owner can model before adding another person to the team.

OpenChair publishes regional Pro pricing for Australia, New Zealand and the United Kingdom.

The subscription starts with the venue and one bookable team member, then adds a regional charge for additional bookable team members up to the relevant per-venue cap.

Non-bookable access users do not add another bookable-member subscription charge.

The cap applies to the Pro subscription, not every cost associated with running OpenChair.

Card processing, applicable paid usage and optional hardware remain separate.

We keep those distinctions visible because a low headline subscription is not useful if the operator cannot work out what the actual pricing model includes.

The current figures and conditions are published on the OpenChair pricing page.

Build for the working day, not the feature list#

It is easy for management software to become a catalogue of screens.

That is not how an operator experiences the day.

A client books.

The team prepares.

The appointment changes.

Someone messages.

A service runs over.

Another client wants an earlier time.

The appointment finishes.

The client pays.

The team tries to arrange what comes next.

The useful question is whether those steps still make sense when they are connected.

That is why OpenChair's product work tends to follow complete workflows rather than treating booking, clients, messages, payments and reporting as unrelated modules.

The goal is not to have the longest feature list.

It is to make the common pieces of running a salon or barbershop work together without making the operator give up control of the business.

Why OpenChair still focuses on salons and barbershops#

Different appointment businesses can look similar from a distance.

Put a calendar, a customer database and payments beside one another and almost any service business can be made to fit the diagram.

The details are where that breaks down.

Hair salons need to represent processing time and colour history.

Barbershops may need to run appointments and walk-ins together.

A growing team needs individual availability, service eligibility, client context and commission reporting without turning every staff member into a separate business.

Those workflows are why hair salons and barbershops remain OpenChair's clearest focus.

We also support relevant workflows for other appointment-led beauty and personal-service venues, but we would rather describe the capability that exists than claim that one generic setup works identically for every industry.

The product principle underneath it#

The principle behind OpenChair has become clearer as the product has grown:

Keep the chair working. Give the team context. Keep the operator in control.

That means recovering useful capacity without promising every opening will fill.

It means using client information without pretending software replaces staff judgement.

It means applying AI where it can remove routine work while keeping clear approval boundaries.

It means publishing the commercial model instead of hiding the important conditions behind the headline price.

OpenChair is still being built around those decisions.

For the current product, pricing and regional availability, use the live OpenChair website and pricing page rather than treating this founder story as a permanent feature list.