founo.Free website reviewStart a project
A replay of the Aliya’s Beauty landing page. An eye drawn from lash fibres opens under the headline. The fibres scatter and sort into trays beside the studio’s method. The eye then wears each lash set in turn, each with its price, then brows are shaped above it, and it closes for the skin treatments.

Case studyAliya’s Beauty

A salon’s website, booking and staff tools. Built as one system.

Aliya’s Beauty is a brow and lash studio in South Shields. We designed and built its landing page, the booking flow, the client accounts and the staff portal behind them.

Client
Aliya’s Beauty
Where
South Shields
What we built
Website, booking, client accounts, staff tools

LaunchThe landing page

We built the landing page around a single eye.

It is drawn from lash fibres, and it wears the treatments as you scroll. This is the page itself, replayed.

  1. The welcomeTheir headline, with a button to book straight away.
  2. The methodThree lines on how the studio works, as the fibres sort into trays.
  3. LashesEach lash set in turn, with its name, its price and a button to book it.
  4. BrowsShaped, tinted and laminated, with the price list beside them.
  5. SkinFacials and waxing, under a single drop.

The page goes on to their photographs, the lash training on its way and how to find the studio, and closes on one more way to book.

AutomateThe booking

We built the booking in five steps.

One page takes a client from choosing a stylist to paying the deposit. As treatments are added, the price and the time add up at the foot of the screen.

  1. StylistWho the visit is with.
  2. TreatmentsOne, or a few together.
  3. Day and timeOnly the times that fit are offered.
  4. DetailsAlready filled in for a client with an account.
  5. SummaryA deposit by card now. The rest is charged before the visit.
The Aliya’s Beauty booking flow on a phone. A stylist is chosen, then a lash treatment, then a day and a time. The details step opens with the demo client’s details already filled in.
Recorded with a demo client account.
The same booking flow on a laptop. The eye and the booking so far take the left of the screen; the list of lash treatments takes the right.
On a laptop the booking so far sits on the left and each step’s choices on the right.

LaunchEvery other page

We designed every other page to match.

Signing in, the booking confirmation, the training waitlist, the journal, the policies and the page for a wrong address all share one frame.

  • The Aliya’s Beauty sign-in page: the open eye above the words Welcome back and a sign-in form
    Sign in
  • The booking confirmation: the open eye above the words Booking confirmed, then the day, the time, the treatments and the studio’s address
    Booked
  • The lash training scene: lashes drawn into a ring inside the words Lash training, coming soon, then training, accreditation and further courses listed as on their way, and a button to join the waitlist
    Training
  • The studio’s journal page, with no articles published yet
    Journal
  • The page shown for a wrong address: the eye is shut above the words Nothing to see here
    Page not found
  • The studio’s privacy policy, set on a sheet of paper under the eye
    Policies

BuildClient accounts

We gave clients an account.

A client can see what is booked and what has been paid, save a treatment to book again, and leave a review after a visit.

  • A client’s home screen: a welcome back by name, their visits and spend so far, and the next visit with its day, time and treatments
    Home
  • A client’s visits: the next one, with its deposit paid, and a tab for the visits before it
    Visits
  • A client’s payments: the total paid, then each payment by month, from the deposit on the next visit back to visits paid in full
    Payments
Visits
Upcoming and past, with cancelling built in.
Payments
Deposits, full payments and refunds, visit by visit.
Saved, reviews, details
Treatments to book again, a review after a visit, and their own details and notifications.

Shown with a demo client account.

BuildStaff tools

We gave staff the controls.

The studio runs its diary, its treatment menu and its hours from the same system. Changing a price or a shift does not need a developer.

  • The staff schedule: the week across the top, then the day’s bookings, each with its time, client, treatment and payment, and a line for now
    Schedule
  • The staff services screen: treatment categories, with lash treatments open to show each price, length, location and consent form
    Services
  • Staff shifts: a stylist’s working hours for each day of the week, with a switch to take a day off
    Shifts

In the staff portal

  • Schedule
  • Clients
  • Services and prices
  • Shifts and holidays
  • Team and permissions
  • Payments
  • Analytics
  • Email campaigns
  • Consent forms
  • Training waitlist
  • Settings

Switch a day off in Shifts and it stops being offered for booking.

The services screen on a laptop: each lash treatment with its price, length, the locations it is offered at and the consent form it needs
Services on a laptop. Each treatment carries its price, its length, where it is offered and the consent form it needs.

The diary is shown with demo bookings. Every name in it is made up.

What this shows, and what it doesn’t.

The brief
A booking is a chain of decisions: treatment, time, stylist, deposit. Staff had to be able to change treatments and hours without breaking it.
What we built
The landing page, the booking flow, client accounts, the staff portal, card payments, the emails, the consent forms and the training waitlist.
How it runs
As one system. A booking, a payment and a change to the menu all land in the same records, so the site, the accounts and the diary agree.
Not claimed
No figures for bookings, revenue or traffic. Those are the studio’s own, and we don’t publish them.

Now picture yours.

Every project starts with what the business does. Tell us where yours gets stuck and we’ll say where we would start.

Start a projectSee pricing