Marcy K Salon is a local salon in Arlington, Tx. She wanted to promote higher cost services and cut down on non-paying customers.

diagnol arrow

The design was done in 3 weeks and the total project was completed in 5 weeks.

icon of people

Me, the UX Designer, Puskar, the developer, and Karina, the salon owner.

A picture showing the front of Marcy K Salon's Suite

What prompted this project?

Her prior website was taken down

The company that created her last website, took it down in demand for more payment. They initially told her she had to pay a one-time fee for her website, but after a year, they wanted her to pay again.

Problems she wanted to address

I condensed the categories further and created this second design which only shows an image when a service is selected.

  1. She had an in-person pay structure and customers would take advantage of this by receiving service and leaving without paying.
  2. Her client’s appointments got lost in her email because she used a contact form that people would fill out which sent to her email.
  3. She had unclear service pricing, so she received a lot of calls from clients asking pricing details.

Stakholder Meeting

I wanted to understand her business needs

In our first meeting, I got to know her business needs and understand the services she offered. I created a quick mockup to show my ideas and make sure we were on the same page.

Next, I met with 5 potential clients

I interviewed 5 women who frequent salons in the DFW area to understand what questions they have before booking an appointment with a new salon. And specifically Marcy K Salon after viewing it on Google maps.

They had questions like...

  • Does she speak Spanish?
  • Does she have a speciality?
  • What does the salon look like?
first wireframe of the salon's home screen.
an image of a brown wave shwoing the design process I followed

With her list of services and FAQ's from her clients, I needed to ensure I organized all this info in a way that made sense to her clients.

A $0 budget meant using a Figjam template

I invited 5 women who frequent salons to my Figjam file to see how they would organize the information. I used the common themes they created and then unique categories for the ones that differed.

a screenshot of a figjam file with a purple card sort

I turned these categories into wireframes and consulted with the Dev

This slowed the load time

He said having a card with an image for each service would slow the loading time and it would be better to dynamically load one image at a time.

two images comparing the layout options for services. The left shows cards with drop down options and the right shows one card which changes depending on which service you select from a menu

This was just right

I condensed the categories further and created this second design which only shows an image when a service is selected.

the Calendly booking page with Marcy K Salons branding colors and logo

Negotiating with Karina

Calendly would help her track her appointments

I considered Google calendar but it was more expensive than Calendly. I showed her how it seamlessly integrated into her website, allowed her to add her brand colors and logo, and sent automatic reminders to her clients. It also worked with Stripe so she can accept a “Deposit” before her clients arrive to ensure they don’t leave without paying.

She agreed to try it

She signed up for the 2 week free-trial and I added every one of her services as a unique booking option in Calendly.

a screenshot of a figjam file with a purple card sort

Outcome

Her domain name was owned by the prior company which meant...

Despite this redesign solving her problems, she did not want to create a new domain name due to branding reasons. She went back to the company that made her initial website and paid the $300 fee for them to reinstate it. The Vercel app is still available, but the Calendly integration is disabled.

What I learned

  1. Approach stakeholder meetings with a detailed plan and talking points.
  2. Communicate with the dev during the wireframe process, so you don’t create something they can’t or won’t code.
  3. Sometimes your design will be compromised due to time constraints or miscommunication in development, so communicate frequently!