Why Calendly Doesn't Work in Lagos

There's a comfortable explanation for why booking software built in San Francisco doesn't land in Lagos. The tools are good. The market just needs a localised version — put a naira price on it, wire up a Nigerian payment gateway, translate the interface, ship.

I assumed that was the shape of the problem when I started Zest. I think it was wrong, not merely incomplete.

The localisation story assumes these tools fail at the edges. They don't. They fail in the middle, at the specific moment they were built around.

I'm writing this because I started a company on the assumption that it was the first problem, and being wrong about that is more useful to other builders than being right about currency formatting.

On data: I cannot tell you what share of Nigerian service businesses lose clients to a slow reply, and I haven't measured whether client-tracking actually changes anyone's behaviour. What follows is a pattern I see in the conversations I have, plus an argument about the tools themselves — which is weaker evidence than a study, and I'd rather flag that than imply otherwise.

The tools are built around the moment

Almost every scheduling product is organised around one instant: the moment a client picks a slot. Availability grids, timezones, buffer times, confirmations. That thirty-second interaction is the product.

For a Nigerian service provider, thirty seconds is the easy part. It has been solved for a decade, and solving it is not where the difficulty lives.

The business lives on either side of it. Before: has this person booked before, what did they tell me last time, what should I ask before they arrive. After: did they come back, when, are they drifting.

Calendly has no opinion about any of that — and not because the team was careless. Because the data model has nowhere to put the answer. There is no field for "how many times has this person been", because Calendly isn't a relationship. It's a calendar with a signup flow attached.

The strongest objection

The obvious objection is that this is over-engineering. Add WhatsApp, add a transfer reference, ship it.

That objection is correct about the features and completely wrong about the problem. A WhatsApp button and a transfer reference are integrations. They make the thirty-second moment slightly nicer. They do nothing whatsoever about the question the provider is actually asking, which is: who is coming back, and who is quietly disappearing?

You can bolt a payment method onto a calendar in an afternoon. You cannot bolt a relationship onto it, because there is nowhere to keep one.

What I mean by "client memory"

I've started calling the thing I want to build client memory. It's a plain idea: the booking system should know who your clients are, not just when they're free.

Client memory isn't sentiment analysis. It's five questions a calendar cannot answer today:

• How many times has this person booked, and when was the last one?
• Who booked three months ago and hasn't returned since?
• What did they say they needed before they arrived?
• Which of my recent new clients never came back a second time?
• When should I reach out, and what should I actually say?

None of these are about the booking. They're about the person who made it. A calendar can answer the first one badly, and the rest not at all.

The specifics that aren't really about Nigeria

It is tempting to file all of this under "localisation", and the payment layer genuinely belongs there. Bank transfer is the method, the transfer narration is the matching problem, WhatsApp is the channel. Those are real problems and they're worth solving properly.

But underneath them sits one structural fact: the repeat client is the business. The first booking is cheap and easy. The value is in the second, the third, the tenth — the parent who books every term, the couple who returns each year, the client who renews quarterly.

A transaction tool optimises for transactions. If your income comes from transactions, that is correct behaviour. If your income comes from relationships, then a tool with no memory of relationships is optimising the wrong quantity — in every market.

Which is why I don't think this is really a Lagos problem. It is a problem for any business that earns from retention. It is unusually visible here because the payment layer broke first, which made everyone assume the whole stack was broken.

What this isn't

This is not a case against Calendly, Acuity, or Square Appointments. If you run a drop-in clinic or a studio that takes walk-ins, they are good tools and you should use them. The honest answer is that the choice depends on whether you sell appointments or relationships — I compared the options more directly here.

It is also not a claim that the client tracking is finished. It isn't. Zest watches booking patterns and tells you what is changing. It is not a CRM, it does not send marketing email, and it will not build you a funnel. It attempts one thing: telling you who matters and when to do something about it.

And the real limitation — I don't yet know whether providers change their behaviour when they see that information. Noticing a pattern and acting on it are two different problems, and I have only solved the first. The scheduling half of this is something I wrote about separately.

The bigger picture

There is a long list of software that arrived in African markets without being rebuilt for how those markets work. Invoicing, payments, client management. The pattern is consistent enough to be worth naming: the engineering is usually fine and the assumptions are wrong.

The assumptions are almost always the same four. That people pay by card. That email is the channel. That every booking is a cold transaction. That the job is finished when the slot is in the calendar.

I don't think the answer is "build Calendly, but African." I think it's to start from the relationship — the WhatsApp thread, the transfer, the person who has been coming back for two years — and build outward from there.

That is what Zest is an attempt at. Not a scheduling tool. A way to remember your clients.

---

If you're a coach, tutor, therapist, or consultant in Nigeria, I'd like to hear if this rings true. Try Zest at zestbook.org.ng.