The Follow-Up OS

An Abuja cosmetics seller described her business to a developer at a product meetup in June 2026. She did not describe a dashboard problem. She described a list.

"I need to call this customer on Tuesday. She asked about a bridal package in April and went quiet. I have another one who ordered last week but has not confirmed delivery. Someone asked about pricing three weeks ago."

She had eleven customers in her head. None of them were in any system. The developer asked if she used a follow-up tool. She asked what that was.

That question is the product category.

Every software category begins by naming a behavior. CRM named customer management. Spreadsheets named the digital ledger. Email named correspondence. The behavior the Abuja seller described had no software name. It was not lead tracking. It was not pipeline management. It was not automation.

It was a daily list of customers whose attention window was still open.

Seventy-eight percent of Sub-Saharan African small businesses run their sales through WhatsApp, per Innovation Village. WhatsApp surfaces the most recent message. It does not surface the customer from three weeks ago whose intent has not yet expired. The category that would solve this has no clear owner.

The Follow-Up OS is not CRM.

It does not store contact records or configure deal stages. It does not send automated messages without owner approval. It does not require role separation or onboarding flows.

What it does is narrower. It maintains a list of customers whose follow-up window is active. It surfaces each customer at the moment action is needed. It surfaces the timing. The owner decides the action. One tap opens the WhatsApp thread. One tap schedules the next check. One tap closes the loop.

The unit of value is not data stored. It is timing enforced.

The category is not better CRM. It is system-enforced continuity in a market where continuity depends on memory.

A customer who expressed interest last week is still valuable today. That value decays without action. The product does not reverse the decay. It ensures the action happens before the decay is complete.

The window for this category is behavioral, not competitive. African micro-businesses are structured around WhatsApp. They will not migrate to a new channel. The product that wins will sit beside WhatsApp, not ask the owner to leave it.

The initial ICP is narrow. Appointment-based businesses - salons, coaches, tutors, and event caterers - share a structural trait. Every customer who enquires has an implied timeline. A missed follow-up has a definite cost. This is the wedge. A reminder tool designed for this group proves the value loop before expanding into general micro-business use.

The first builder to name this category clearly will own the perception problem the cosmetics seller demonstrated. She did not know she needed follow-up software. She knew she needed to call that Tuesday customer. The product must be findable by someone who does not yet know the category name.

The product specifications follow directly from the constraint. The interface is a phone, not a desktop. The owner and the operator are the same person. No admin panel. No onboarding sequence. The starting action is one question: which customer needs attention today?

WhatsApp integration is not a feature. It is the interface. The owner taps a name and opens the existing conversation. The product schedules the attention. It does not replace the conversation.

Nigerian developer chinenyeegbe named the constraints for wacrm - a WhatsApp-native CRM for African SMBs. Three constraints: multilingual, WhatsApp-length messages, no invented prices. A follow-up tool for African micro-businesses adds one more: zero setup before the first reminder fires.

The Abuja seller had eleven customers in her head. The product that wins this market starts there - with those eleven - not with a CRM import flow.

The category is unoccupied. The customer is already describing it.