Coffee shops · CRM
Remember the usual order, the favourite bean and the office that asked for a quote.
A CRM for a coffee shop is a simple record of the people the shop serves and sells to: regulars, bean buyers, office enquiries and event hosts, with what each one wants and what was last said. GullySales works on choosing a light tool, setting up the fields and getting the team to use it.
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 coffee shops
Where it usually goes wrong, and what we would do.
“The barista holds the CRM in memory”
The person at the machine knows who takes oat milk and who prefers the washed lot. When that person leaves, the knowledge leaves too, and the new hire starts from nothing, asking regulars for orders the shop already knew.
“A spreadsheet works until the second outlet”
One sheet kept by one person survives a single shop. Add a second outlet, an online bean order and an office account, and the sheet splits into several copies, each slightly different, none fully trusted.
“Different buyers need different fields”
A regular needs a usual order and a bean preference. An office needs a contact, a machine and a refill pattern. One form forced onto both leaves blanks in every record, and blanks teach the team to stop filling it in.
“Consent is part of the record”
Every number the shop holds should show whether the person agreed to be messaged, and about what. Without it, a launch message becomes an intrusion, the list becomes a liability and nobody can say who agreed to what.
What we do
What we deliver for coffee shops.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A simple tool chosen for the shop
A comparison of light options such as a shared spreadsheet, a WhatsApp Business contact list or a small CRM, and a recommendation that fits the size of the team.
Result: The shop uses a tool the staff will actually open.
Fields for each buyer type
Separate record layouts for regulars, bean buyers, office accounts and event hosts.
Result: Each record holds what matters for that buyer.
Consent captured with the record
A field and a counter routine that note when and how the person agreed to be contacted.
Result: Every contact shows whether messaging is allowed.
Import of existing contacts
Clean-up of the numbers already in phones and sheets, with duplicates merged and unknown consent flagged.
Result: The shop starts with one list instead of four.
A one-page staff guide
A page showing what to enter, when and who owns the update, written for people working a busy counter.
Result: A new barista can follow the routine on the first shift.
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
The fields a coffee shop's record needs for walk-ins, bean buyers and offices.
- Usual order
- Filled by the barista after the second visit. Lets the next barista greet a regular with the drink already in mind.
- Favourite bean and brew method
- Filled when a bag is sold. Tells the shop which roast to suggest when the bag runs out.
- Consent to be messaged
- Filled when the number is taken. Records the day and the channel, so the shop can write to the customer without doubt.
- Office account and contact
- Filled by the person who quotes. Holds the company, the admin, the supply and the date a quote was sent.
- Event or room booking
- Filled by the owner. Holds the date, the guests, the price and the deposit, so a second enquiry for the same date is caught.
- Source of the customer
- Filled at the first record. Marks whether they came from the counter, a post, a map profile or a friend.
Who it is for
This is written for these coffee shops.
- Specialty coffee shops with their own roast
- Independent neighbourhood coffee shops
- Coffee kiosks and carts near offices and metro stations
- Roaster-retailers selling beans online and in store
- Coffee shops inside co-working spaces and bookshops
- Chain coffee outlets opening in new cities
- Drive-through and highway coffee stops
- Cold-brew and brew-bar counters
Before you decide
When this may not be the right fit.
- The shop takes cash at the counter and holds no customer contacts, so there is nothing yet to record.
- No one will update a record after a sale, so the list would be out of date soon after it is set up.
Before you decide
Agree the work. Know how to judge it.
CRM for coffee shops: 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 coffee shops. Anything missing is noted in the written scope, with who will supply it.
- Contacts held on staff phones
- Numbers of regulars, offices and event hosts saved in baristas' or the owner's phones, shared with the business, with the person's consent. Contacts left on a personal phone leave when staff do. Tell us whose phone holds which contacts, since the data belongs to the business and not to the person. Tell us which numbers you cannot account for.
- A decision on who edits the record
- The owner's choice of which staff may add or change entries and which may only read them. A tool open to everyone fills with mistakes, while one open to nobody goes stale. Without a clear owner, the record fills with mistakes, or nobody opens it after the first week. If the owner holds the keys, say so, and name who should hold them when the owner is away. We set permissions after you decide.
- Your consent wording for customers
- The sentence staff say or the card customers see when asked to be remembered or messaged. It must say plainly what the shop will do with the number. Staff must be able to say it in a few words when the queue is waiting, so we shorten it with them. Check with your own adviser what wording and records the law needs, and we place it as written.
- Office quotes sent in the past
- Copies of quotes or chat messages sent to offices and event hosts, with what happened. These are the nearest the shop has to a pipeline. Include the quantity asked for and any price quoted, since a quote with no price cannot be compared. Even a list of names and outcomes lets us build the first follow-up queue.
- Owner time to review the record
- A moment when the owner will look at the record and correct it, agreed in advance. A record nobody reads stops being trusted. The owner chooses the habit, such as looking over new entries after closing on a quiet evening. We do not set a schedule for you, but we ask you to choose a habit that suits the shop.
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
Name the buyers the shop must remember
We sit with the owner and a barista and list the people who need a record: regulars with a known order, bean buyers, office enquiries, event hosts and room bookers. You strike off anyone who does not need remembering. A regular is a person to remember, and an enquiry is a job to finish, so the two need different records. The list decides the fields and the tool, so we keep it honest and short.
- 2
Choose a light tool staff will open
We compare two or three simple tools against your budget, phones and habits, and you pick one. A tool that needs a laptop will not be used at the counter. Free versions of well-known tools are enough, and we say plainly what each version cannot do. We write down why the tool was chosen, who holds the login and what happens if the owner leaves.
- 3
Set up fields for each buyer type
For regulars the fields might be usual order and favourite bean; for offices, the contact, the quantity and the quote; for events, date and headcount. You remove any field staff would not fill in. A separate field for allergies or health details is not added, because the shop has no need to keep them. A consent field sits on every record, so nobody is messaged without agreeing.
- 4
Import contacts you can account for
We bring in phone contacts, order chats, invoices and event lists, and you check a sample for errors, such as two names for one person. Numbers collected without permission stay out. We also merge the entries that are clearly the same person. Entries that cannot be placed are listed apart for the owner to decide, and none are deleted without asking. The record begins small and accurate, and grows by use.
- 5
Try it on a counter shift
A barista and the owner use the tool for a normal shift: adding a regular, noting a bean order, logging an office call. Where they stumble, we change the screen. A barista tests whether a regular's order can be added in the time the machine is heating. If it is slower than the notebook, we remove fields until it is not.
- 6
Hand over, then read the repeat visits
We give the owner the login, the field list and a one-page guide on who may see what. Later we read the record against the figures given at the start: regulars recognised, bean reorders prompted and office quotes followed up. We also name a person who corrects wrong entries, because a record nobody cleans stops being trusted. You decide which fields to change or remove.
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.
Do we need paid software?
Who should update the CRM?
Is it safe to store customer numbers?
Can the counter staff record a number without asking?
Can counter staff record a number without asking?
What if the owner is the only one who uses it?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for coffee shops
Related work to consider.
Closest to this: leads and follow-up
Also for coffee shops
Or start from the overview: sales and marketing for coffee shops.
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.