Something I've been thinking about lately is how much business advice revolves around getting more customers.
Run ads. Improve your website. Post on social media. Get more reviews. Start an email list. Offer discounts.
None of that is necessarily bad advice.
But there's another side of running a business that doesn't get nearly as much attention, probably because it's not particularly exciting to talk about.
The day-to-day operations.
The missed phone calls. The customer who shows up at the wrong time. The appointment that somebody forgot to write down. The employee who has to ask the owner what to do because nobody documented the process. The customer waiting around without knowing whether they'll be served in five minutes or forty.
Individually, these things seem pretty minor.
But they happen repeatedly, and I think that's what makes them worth paying attention to.
A business doesn't have to be terribly mismanaged for small operational problems to accumulate. Sometimes everyone is working hard and doing their best, but the way the business operates makes simple things unnecessarily difficult.
I've been looking at this particularly from the perspective of local service businesses, although a lot of it applies elsewhere.
Here are some things I'd pay attention to before spending more money trying to bring in additional customers.
The first thing I'd check is what actually happens when someone tries to become a customer.
Not what the website says happens.
What actually happens.
Let's say somebody wants to book an appointment.
They find your business on Google, visit your website, and look for a way to book.
Maybe there's a booking form. Maybe there's a phone number. Maybe they're supposed to send a message.
What happens next?
Does someone immediately receive the booking request? Does the customer get confirmation? Does the appointment go into a calendar? Does an employee have to manually transfer it somewhere?
And what happens if the customer calls instead?
Or sends a message through Instagram?
Or walks in?
I think it's easy to underestimate how messy this can get when customers arrive through several different channels.
Imagine a business taking appointments through phone calls, WhatsApp, Instagram, and its website.
Each channel works perfectly well on its own.
The problem starts when there's no consistent way to combine them.
Someone books through Instagram. An employee forgets to update the calendar. Another employee gives that time slot to someone who called.
Now you have two customers expecting the same appointment.
Neither customer did anything wrong.
And the business might have perfectly friendly employees and excellent service, but the experience has already started badly.
This is one of those problems where I wouldn't immediately recommend buying software.
I'd first figure out exactly where every booking goes and who is responsible for recording it.
A shared calendar might be enough.
A notebook might even be enough if it's updated consistently.
The important part is that everyone knows where the actual schedule lives.
Having four different places where appointments might be recorded isn't a system.
It's four opportunities for something to be missed.
Another thing I'd pay attention to is how much time gets wasted on questions that have already been answered somewhere.
Think about the questions a local business gets every day.
Are you open today?
How much is this service?
Do you accept walk-ins?
Can I book for tomorrow?
Where exactly are you located?
How long does an appointment take?
Do you have parking?
Can I pay by card?
Now, obviously, customers asking questions is normal.
But if the same question comes up twenty times a week, it's probably worth asking why people keep needing to ask it.
Maybe the information is technically on the website, but it's buried somewhere.
Maybe the Google Business Profile has outdated opening hours.
Maybe the business has different hours on Instagram and Google.
Maybe the pricing is unclear.
Or maybe there simply isn't a convenient place where customers can find everything.
I think business owners sometimes underestimate how valuable clear information can be.
Let's do a rough calculation.
Suppose an employee spends three minutes answering a routine question.
That doesn't sound like much.
But if it happens 15 times a day, that's 45 minutes.
Across 25 working days, that's almost 19 hours.
Of course, not all of that time can be eliminated. Some customers will always prefer calling, and some questions need a human answer.
But even reducing the number of unnecessary calls could make the workday easier.
I'd start by writing down the ten most common questions customers ask.
Then I'd check whether the answers are immediately available online.
Not technically available after scrolling through three pages.
Actually easy to find.
I'd also ask someone unfamiliar with the business to try finding the information on their phone.
It's surprising how different a website feels when you aren't the person who built it.
And I wouldn't overcomplicate the solution.
A clear FAQ, updated Google listing, accurate pricing, and obvious booking instructions might accomplish more than a complete website redesign.
Waiting times are another interesting one, especially because the problem isn't always how long people wait.
Sometimes it's that nobody knows what's happening.
Imagine arriving at a business and seeing several people sitting around.
You ask how long the wait is.
Someone says, "Not too long."
What does that mean?
Ten minutes?
Half an hour?
An hour?
You don't know.
And because you don't know, you can't really plan around it.
Now imagine being told there are four customers ahead of you and the estimated wait is around 25 minutes.
That doesn't magically make the service faster.
But it does give you information.
You can decide whether to stay, return later, or make other arrangements.
I think this is particularly relevant for businesses that combine appointments and walk-ins.
Barbershops, clinics, repair services, certain beauty services, and plenty of other businesses have situations where the actual waiting time can change throughout the day.
And I wouldn't recommend promising customers an exact waiting time.
That's asking for trouble.
A customer might take longer than expected. An employee might become unavailable. An appointment might run over.
Estimates should be treated as estimates.
But there's a big difference between an honest estimate and leaving someone completely in the dark.
One simple experiment would be to record arrival and service-start times for a week.
Nothing fancy.
Just two timestamps for each customer.
Then look at the results.
Are waits longer on particular days?
Do walk-ins wait significantly longer than booked customers?
Are there certain hours when the queue suddenly builds up?
Does the business have a predictable rush period?
You might discover that the problem isn't the number of employees.
It might be how appointments are distributed throughout the day.
Or you might discover that you genuinely need more capacity.
Either way, it's better to know.
Something that doesn't get discussed enough is the cost of interruptions.
This one is easy to overlook because interruptions don't always show up as a line item on an expense report.
Imagine a receptionist working through a queue of customers.
The phone rings.
They stop what they're doing, answer a question about opening hours, and return to the original task.
Then someone asks about an appointment.
Then another customer needs directions.
Then the phone rings again.
Even if each interruption only takes a minute or two, the employee is constantly switching between tasks.
And when people are switching tasks all day, mistakes become more likely.
An appointment gets entered incorrectly.
A message doesn't get answered.
A customer is told the wrong time.
I'm not suggesting businesses should stop answering calls.
That would obviously be ridiculous.
But I would look at which interruptions are necessary and which ones exist because customers can't find basic information themselves.
If a large percentage of calls are about appointment availability, maybe the booking process needs to be clearer.
If people constantly call asking whether it's their turn, maybe the waiting process needs better communication.
If customers repeatedly ask for directions, maybe the location information is confusing.
The question I'd ask isn't simply "How do we reduce calls?"
It's "Why are people having to call in the first place?"
Sometimes the answer is completely reasonable.
Other times it's a sign that the business could make things easier.
I think no-shows deserve more attention, but not every no-show problem should be treated the same way.
Let's say a business has 100 appointments in a month and 12 customers don't show up.
That's a 12% no-show rate.
Now suppose each appointment is worth $40.
It's tempting to say the business lost $480.
But that isn't necessarily the real financial loss.
Some of those slots might have been filled by walk-ins.
Some appointments might have had variable costs.
And revenue isn't the same as profit.
Still, missed appointments can create real problems, particularly when the business reserves time or resources for individual customers.
I'd want to understand why people aren't showing up.
Are they forgetting?
Are they booking too far in advance?
Are appointments being recorded incorrectly?
Are customers confused about the time?
Is cancelling unnecessarily difficult?
Those are different problems and they need different solutions.
For example, if customers simply forget, reminders might help.
If customers book appointments they don't actually want, reminders alone may not solve much.
If people want to cancel but can't easily contact the business, making cancellation simpler could help the business offer those slots to someone else.
I'd also be careful with deposits and cancellation fees.
They can make sense in some businesses, but they can also discourage bookings if they're implemented badly.
It's worth understanding the actual cost of missed appointments before introducing policies that might frustrate good customers.
One of the most useful things a business can do is write down how it handles situations that happen repeatedly.
This sounds painfully boring.
And it is.
But imagine a small business where the owner knows everything.
They know which customers prefer particular appointment times.
They know how to handle complaints.
They know what to do when an employee is absent.
They know which services take longer than usual.
They know how to handle cancellations.
Everything works because the owner is constantly available.
Then the owner takes a day off.
Suddenly employees are calling them for decisions that should have been straightforward.
This is a sign that too much operational knowledge exists only in one person's head.
I'm not suggesting a small barbershop needs the same documentation as a large company.
But a few simple written procedures can make a big difference.
For example, what happens when a customer arrives late?
Do you still serve them immediately?
Do they move to the next available slot?
Does it depend on how late they are?
What happens when someone arrives without an appointment?
What happens if an employee can't come to work?
What happens when a customer wants to reschedule?
The answers will vary by business.
The important part is that employees shouldn't have to invent a new policy every time the situation occurs.
And policies should be flexible enough to account for reasonable exceptions.
You don't want employees blindly following a checklist when a situation clearly requires judgment.
You just want the routine stuff to be routine.
I'd also look at how much work is being duplicated.
This is something that can happen gradually.
A business starts with a notebook.
Then it adds a spreadsheet.
Then it creates an online booking form.
Then it starts using a separate app for reminders.
Then somebody introduces another system for customer records.
Before long, employees are entering the same information multiple times.
A customer books an appointment.
Someone records it in the booking system.
Then copies it into a spreadsheet.
Then writes it in a notebook because that's what another employee prefers.
Then sends a manual confirmation.
It's easy to see how this happens.
Each tool was probably introduced to solve a legitimate problem.
But the combined workflow becomes unnecessarily complicated.
I'd map out what happens to a single booking from beginning to end.
Every place the information is entered.
Every person who touches it.
Every manual step.
Every notification.
Then I'd ask whether each step is necessary.
Sometimes duplication is intentional. Businesses may need backups or separate records for legitimate reasons.
But entering the same information three times simply because different employees use different tools is probably worth fixing.
Another mistake is treating every customer as if they need the same process.
A first-time customer and a returning customer might need different information.
Someone booking a routine appointment might not need the same amount of preparation as someone booking a complicated service.
A walk-in customer has different expectations from someone who reserved a specific time.
If a business forces everyone through exactly the same process, it can create unnecessary friction.
For example, a returning customer might just want to book the same service they booked last month.
Making them fill out a long form every single time isn't particularly helpful.
On the other hand, a new customer might genuinely need more information before their first appointment.
The challenge is finding the balance.
You don't want to collect unnecessary personal information.
You also don't want to make employees ask the same essential questions repeatedly.
I'd look at which information is actually needed to deliver the service and when it's needed.
Collecting more information isn't automatically better.
Especially for businesses dealing with sensitive customer information, it's important to keep records secure and limit access to people who genuinely need it.
Here's a small experiment I think could be useful for businesses that feel constantly busy but aren't sure where the time goes.
For five working days, keep a simple interruption log.
You don't need to record every second.
Just note recurring problems when they happen.
For example:
Monday:
- Three calls asking about opening hours.
- Two customers arrived without knowing appointments were required.
- One booking wasn't entered into the calendar.
- Four customers asked how much longer they'd have to wait.
Tuesday:
- Five calls asking about appointment availability.
- One customer arrived at the wrong time.
- Two cancellations weren't communicated to the relevant employee.
- Several customers couldn't find the business entrance.
Wednesday:
- Repeated questions about pricing.
- One double booking.
- A customer waited unnecessarily because nobody updated the queue.
These are hypothetical examples, but you get the idea.
At the end of the week, group similar problems together.
You might find that one issue is responsible for a surprising amount of unnecessary work.
And that's where I'd start.
Not with the most exciting problem.
Not with the one that sounds impressive when you describe it.
With the one that's actually happening repeatedly.
If you can eliminate ten small interruptions a day, that might be more valuable than introducing an elaborate system that only gets used once a month.
I also think business owners should be more skeptical of software that promises to solve everything.
There are a ridiculous number of tools available now.
Booking software.
CRM systems.
Scheduling platforms.
Customer messaging tools.
Inventory management.
Marketing automation.
Analytics.
AI assistants.
And plenty of products that combine several of those things.
Some are genuinely useful.
But more features don't automatically mean more value.
Let's say a business pays $30 a month for a tool.
That sounds cheap.
But the subscription price isn't the entire cost.
There's setup time.
Employee training.
Migrating existing information.
Maintaining the system.
Handling problems when something doesn't work.
And potentially paying for other tools that need to connect with it.
I'd evaluate software based on what it actually changes in the business.
Does it remove a repetitive task?
Does it reduce mistakes?
Does it make booking easier?
Does it help customers get information without constantly contacting employees?
Does it give the owner information they didn't previously have?
And importantly, will employees actually use it?
If the answer is no, the software might just become another subscription nobody wants to cancel.
I'd rather see a business use a basic spreadsheet consistently than pay for an expensive platform that everyone ignores.
Something else worth mentioning: not every operational problem is worth fixing immediately.
This might sound contradictory after everything I've written.
But small businesses have limited time and money.
Trying to optimize every tiny inconvenience can become a distraction in itself.
Suppose an issue happens once every two months and takes five minutes to resolve.
You probably don't need to spend three days building a process around it.
On the other hand, if something happens ten times a day and regularly frustrates customers, it's probably worth investigating.
I'd roughly prioritize problems using three questions.
How frequently does it happen?
How much time or money does it cost?
How much does it affect the customer experience?
You don't need a complicated scoring system.
Just be realistic.
A problem that happens frequently and affects customers directly should probably receive more attention than an occasional inconvenience that nobody particularly cares about.
And sometimes the right decision is to leave a process alone.
Not everything needs optimization.
If I had to work through these issues over a month, I'd avoid making too many changes at once.
During the first week, I'd mostly observe.
I'd look at bookings, customer questions, waiting times, cancellations and the things employees complain about.
I'd try to understand how the business actually operates rather than how it's supposed to operate.
During the second week, I'd fix things that don't require major changes.
Update incorrect business information.
Make prices easier to find.
Clarify booking instructions.
Create a consistent place for appointment records.
Write down a few common procedures.
During the third week, I'd look at communication.
Are customers getting confirmation when they book?
Do they know when to arrive?
Are they told when something changes?
Can they cancel without unnecessary hassle?
Are walk-in customers given reasonable expectations?
Then during the fourth week, I'd compare what happened with the first week.
Not just revenue.
I'd look at whether the process became easier.
Were fewer appointments missed?
Were there fewer scheduling mistakes?
Did employees spend less time answering repetitive questions?
Did customers receive clearer information?
Did the business become easier to manage?
And I'd be careful not to overinterpret the results.
Four weeks isn't enough to prove every change worked.
Customer demand fluctuates. Employees have good and bad days. Some weeks are simply busier than others.
But it's enough time to start noticing patterns and deciding what deserves more attention.
One last thing: I don't think the goal should be to remove the human element from small businesses.
Actually, I think it's the opposite.
One reason people choose local businesses is that they like dealing with real people.
They like the barber who remembers their usual haircut.
The receptionist who recognizes them.
The shop owner who knows what they normally buy.
Those interactions matter.
The goal of improving operations shouldn't be to replace them with automated messages and complicated systems.
It should be to give employees more time for the parts of the job that actually benefit from human attention.
If someone spends less time searching through appointment records, they have more time to help customers.
If customers can find basic information themselves, employees can focus on questions that genuinely need an answer.
If waiting times are communicated clearly, the receptionist doesn't have to spend the entire afternoon responding to frustrated people asking when they'll be served.
And if the owner isn't constantly fixing preventable mistakes, they can spend more time working on the business instead of just reacting to whatever went wrong that day.
I think that's the part of operational improvement that gets overlooked.
It's not necessarily about making a business bigger.
Sometimes it's just about making an ordinary Tuesday less chaotic.
And for a small business owner who's already juggling ten different responsibilities, that alone can be worth quite a lot.