← Back to Writing
The infrastructure was never the problem
Founder · 7 min · 2026
Context
I have spent time working in a barbershop. Not as a designer studying user behavior, not as a researcher collecting field notes. Actually working, managing walk-ins, tracking appointments in my head, watching my uncle run a busy shop with a notebook and a WhatsApp group and nothing else.
It works. Until it does not.
Customers who have not shown up in two weeks receive no follow-up. Appointments get missed because there is no system to catch them. Revenue gets counted at the end of the day in cash. None of this happens because barbershop owners are not capable. It happens because nobody has built them the right tool.
This is the observation that started Buzzba. And this term, I decided to examine it rigorously: eight weeks of structured academic research on digital tool adoption and customer retention in small service businesses in urban Ghana. I wanted to know if what I was building was actually solving a real problem, or if I had just gotten too close to one person's shop.
Here is what I found.
Core Idea
The infrastructure is already settled: connectivity and smartphones are everywhere. The real bottleneck is a "utilization gap": the tools that exist were built for other markets, making them too complex and expensive for how informal service businesses actually work.
Visual Concept
Local Adoption Simulator
Toggle environmental parameters to see how software performs on an Accra barbershop floor.
Network Connection
Outreach Channel
Standard Enterprise SaaSFriction: High
Desktop Administration Portal
Warning: Render scaled down for mobile screen width
ClientServiceOutreach
Kojo MensahSkin FadeEmail (Bounced)
Ama SerwaaWash & DyeUnread
Requires Laptop/Desktop Screen:Yes (Layout breaks on mobile)
Confirmations:SMS/WhatsApp Gateway API (High cost)
Offline Behavior:Total operational failure
Buzzba (Mobile-First)Friction: Zero
Cybah Haircut ScheduleBuzzba
Kojo Mensah
Skin Fade · 10:30 AM
confirmed
Ama Serwaa
Wash & Dye · 12:00 PM
pending
Direct WhatsApp Flow
"Hello, this is Cybah Haircut. Confirming your barber booking for tomorrow at 2:00 PM."
Simulator Findings
Device Readiness
Correct. Barbers rely on smartphones. Desktop-based tools result in zero adoption.
Connectivity Fault Tolerance
Network is active, but offline redundancy is mandatory for continuous power cuts.
Engagement Rate
WhatsApp has a 98% opening rate in Ghana. Standard email confirmations have less than 15%.
Breakdown
The infrastructure argument is settled
The first thing everyone assumes when you say "Ghanaian barbershops are not digitized" is that it is an infrastructure problem. No smartphones. No internet. People are offline.
That is not true.
• GSMA (2024) reports 38.95 mobile connections in Ghana, representing 113% of the population. The number exceeds 100% because many people carry two SIMs.
A barbershop owner in Accra almost certainly has a smartphone. Almost certainly uses WhatsApp. Almost certainly has mobile data. The hardware and connectivity prerequisite for digital tool adoption is not just present, it exceeds population size.
So the question is not whether the infrastructure exists. It does. The question is: why is adoption still not happening?
The IFC called it a utilization gap. I think that is exactly right.
The International Finance Corporation published a report in 2024 on digital opportunities in African businesses. The finding that stuck with me was this: firms have access to digital tools but are not using them in ways that actually transform how they operate.
They called it a utilization gap.
I think that framing is honest and useful. It shifts the question from "do people have phones?" to "are the available tools actually worth switching to?" And for most barbershops and laundry services in Accra, the honest answer is currently: no.
The tools that exist were built for different businesses in different markets. They are too complex, too expensive, and they assume a level of operational sophistication that does not match how informal service businesses actually work. A barber who manages ten clients per day does not need enterprise software. He needs something that works the way he already works.
Davis had the right theory. The context changes the weight.
In 1989, Fred Davis published a paper that introduced the Technology Acceptance Model: the idea that people adopt technology primarily based on two things: whether they believe it will help them do their job better, and whether they believe it will be easy to use.
The model has been cited thousands of times. It captures something true about human behavior.
But it was developed in a Western corporate context. Whether it accurately predicts the adoption decisions of a barbershop owner in Accra (operating under different resource constraints, different cultural norms, different expectations of what technology should do for him) is a genuinely open question.
My reading of the research suggests the core constructs hold. Perceived usefulness matters. But ease of use probably matters even more in a low digital-literacy environment than it did in Davis's original experiments. A tool that is hard to learn will be abandoned before it ever demonstrates its usefulness. The ease-of-use barrier is higher here. Which means tool design has to work harder.
When digital tools work, retention improves. That part is clear.
Szwajca and Rydzewska published research in 2025 examining how digital customer service tools affect retention in Polish SMEs. They found a statistically significant positive relationship. Digital tools act as a mediating factor between service quality and customer retention.
Poland is not Ghana. The consumer behavior is different. The business context is different. But the mechanism transfers: consistent, personalized service builds loyalty, and digital tools make that consistency possible at scale. A barbershop that sends appointment reminders and follows up with clients who have not returned will retain more customers than one that does not.
What is missing is a study that examines this specifically in Ghana. That gap is what motivated the research, and what I am building Buzzba to help close in practice.
Implications
The research pointed at three non-negotiables for any tool that wants to actually get adopted in this market.
• Mobile-first architecture: Not a desktop product with a mobile version. Something built for a smartphone from the ground up, because that is the device these owners actually use.
• Offline functionality: Internet access in parts of Accra is intermittent. A tool that fails without connectivity will be abandoned. The tool has to work in the gaps.
• WhatsApp integration: This is where Ghanaian small business owners already communicate with customers. Any tool that ignores that is fighting against existing behavior instead of working with it.
These are not insights from a user research report. This is what I already knew from working at Cybah Haircut and watching what my uncle actually uses every day. The research gave me language for it. The building gave me the conviction.
Eight weeks of structured research confirmed what I already suspected: the infrastructure exists, the adoption does not, and the reason is that nobody has built the right tool for this specific context.
That is both a problem and a market.
There are thousands of barbershops, laundry services, and tailoring shops in Accra alone. They are all mobile-connected. They all have customers they are losing silently because there is no system to follow up. They are all waiting for something that actually fits how they work.
I am building that. The research told me I am building it for the right reasons. The next step is the evidence to guide exactly how.