Lash studios · CRM
Keep each client's set, sensitivity and infill date where the whole studio can see it.
A CRM for a lash studio is a single record of every client: the style they wear, the adhesive used, any sensitivity noted and the date the infill falls due. GullySales sets up the fields and the habits so that the record is used, not just filled.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For lash studios
Where it usually goes wrong, and what we would do.
“Clients keep their details in a technician's head”
The technician remembers the curl, the length and the allergy, and the book says only a name and a time. When the artist is away or leaves, the next person starts from nothing and the client notices.
“A patch test needs a record, not a memory”
Whether a patch test was done, on what date and with what result belongs in a place any technician can find before applying a set. A paper note in a drawer fails the moment two people share a client.
“Infill timing is personal”
A client's natural lashes shed at their own pace, so a standard reminder date fits few of them. The record should hold the last visit, the set and the date the technician suggested, so the reminder matches the person.
“Spreadsheets fill and are abandoned”
A studio starts with a sheet, adds columns and stops updating when the day gets busy. A CRM that asks only for what the technician needs at the chair survives the busiest afternoon.
What we do
What we deliver for lash studios.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A client record built for lash work
Fields for style, curl, length, adhesive, patch-test date, sensitivities and the technician, and nothing the studio will not use.
Result: A technician opens the record and knows the client.
A rule for what is recorded at the chair
A list of what is noted at each appointment and who notes it, short enough to be done before the next client arrives.
Result: The record is current.
Infill dates held per client
The date the technician suggests for the next visit, recorded at checkout and linked to a reminder.
Result: Reminders match each client.
A view of lapsed clients
A list of clients whose infill date has passed without a booking, for a personal message.
Result: Quiet clients are noticed.
Source and technician tagging
Each client tagged by where they came from and who looks after them, so the studio sees which source and which artist build repeat income.
Result: You can see what the diary rests on.
Care for personal data
A short note on who can see the records and how consent for photographs and contact is kept.
Result: The studio handles client details with care.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Hold the record that lets any technician pick up a client's history with care.
- Name, number and preferred contact way
- Filled at booking by whoever takes it, so reminders go by the route the client chose.
- Set type, curl and length used
- Entered by the technician after each visit, so an infill matches the original and the client does not have to explain again.
- Patch test done and date
- Recorded by the technician with the outcome in a word or two, so the next visit starts from what happened.
- Known allergies or eye concerns
- Noted as the client states them, with the date, kept to the technician and owner only.
- Next infill date asked
- The date the client said they would return, which drives the reminder and the lapsed-client list.
- Technician and source
- Which technician served the client and how the client found the studio, for the owner's own review.
Who it is for
This is written for these lash studios.
- Dedicated lash extension studios
- Lash lift and tint specialists
- Studios that combine lashes with brows and threading
- Salon-based lash technicians who rent a chair
- Home-based lash artists by appointment
- Lash academies and training studios
- Bridal lash artists who work with makeup artists
- Premium studios with volume and mega-volume sets
Before you decide
When this may not be the right fit.
- Your clients are few and the technician remembers each, and a CRM would add admin without a gain yet.
- You have no rule on who sees health notes, and these must stay with those who need them.
- You plan to move clients to a new tool without their agreement to hold their details, which you should settle first.
Before you decide
Agree the work. Know how to judge it.
CRM for lash studios: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from lash studios. Anything missing is noted in the written scope, with who will supply it.
- The client list and booking app export
- Whatever holds your clients now, as a file or in photographs, including the notebook a technician keeps for personal clients if they agree to share it. Without it, the record starts empty and the history builds visit by visit, so the lapsed-client view stays thin for the first season.
- Dates of the last visit for regular clients
- The date of each regular's last infill, so due dates can be set. Without it, due dates start from the next visit.
- A decision on what the technician may note
- Which details are recorded about sensitivity or reactions, written as the client reports them. Check with your own adviser what the law expects for personal data. Without a rule, the notes field is left empty.
- One person who owns the client data
- Someone who can correct, export and delete records, and who decides what stays when a technician leaves. Without one, the record drifts into personal phones.
- Technicians willing to test the screen
- Two technicians who will try the test copy on real visits. Their feedback sets the fields. If nobody can be spared, we test alone and the first live week needs more correction.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Follow one client from enquiry to infill
We take three recent clients and trace each from the first message through the patch test, the first set, the aftercare message and the first infill. You tell us who touched each step. The trace shows what the record must hold, and where details now sit in a technician's memory or a notebook.
- 2
Decide what is recorded at the chair
We agree the short list of facts a technician enters after each visit: the style, the curl and length, the adhesive, the date the infill falls due and any sensitivity the client has told you about. You decide who writes it. We keep out anything that is a medical judgement.
- 3
Load ten clients into a test copy
We build the record in a test space and enter ten real clients with their last visits. A technician adds a new client and moves one through the stages. You see whether the screen matches how the studio talks, and we rename fields that the technicians read differently.
- 4
Bring in the contacts and remove duplicates
We bring in the client list from the booking app, the phone and any notebook, and merge the duplicates. A client who changed numbers appears once. You decide how far back to import, and clients who asked to stop hearing from the studio are marked so they are never contacted.
- 5
Practise the habit with the technicians
We agree the one action after each visit: open the client, note the set, set the infill date. We practise on real visits from the past few days, so the first live entry is not the first attempt, and we watch where two technicians describe the same set in different words and agree one wording for each curl, length and adhesive. You set the rule that a client is not rebooked until the record is updated, and that notes record what the client says, not a judgement.
- 6
Switch over and read the lapsed-client view
When the switch is made, the notebook stops being the record. After a period of use, we compare infill dates stored, clients rebooked and lapsed clients found against the figures taken at the start. You decide who owns the data, what happens to a technician's clients when they leave and who may see the notes, and we write those three rules on one page that is kept at the front desk.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Which tool should a small studio use?
Can we move our existing client list in?
What if a technician leaves?
How long should the studio keep client records?
What should the notes field hold after a patch test?
Who in the studio may see the client's notes?
How much does it cost?
How long is the contract?
Who will actually do the work?
What do you need from us?
More for lash studios
Related work to consider.
Closest to this: leads and follow-up
Also for lash studios
Or start from the overview: sales and marketing for lash studios.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.