There is an exercise almost every founder is told to do early in their venture’s life. Define your Unique Value Proposition. Articulate, in one sharp sentence, what makes you different from your competitors and why a customer should choose you. The framework is taught in business schools, repeated in founder programmes, and reproduced endlessly in marketing literature. It is, for many founders, a useful exercise.
For many African founders, it is not. And the reason it is not is structural rather than tactical, which means the standard framework needs to be replaced rather than tweaked when it does not fit. I want to argue in this piece that the UVP framework was built for a particular kind of market problem that most African founders are not actually solving, and that running the framework against the wrong problem produces a UVP that is technically correct and operationally useless.
The fix is not to write a better UVP. The fix is to recognise which of two market situations you are actually in, and to use a different discipline for each.
What the standard UVP framework assumes
The framework as it is usually taught proceeds through five steps. Understand your ideal customer. Analyse your competitors. Reflect on your strengths. Craft a clear statement that combines the three. Validate and refine. The output is a sentence that distinguishes you within a known category.
The framework assumes a particular kind of market. It assumes the category already exists, that customers know they need something in the category, that there are competitors competing for those customers, and that the founder’s job is to claim a defensible position within the category. In a crowded category in a mature market, this is exactly the right discipline. The customer is choosing among options. The founder needs to be one of those options, distinguished from the others on a dimension the customer values.
This is not the situation many African founders are actually in. The situation many African founders are in is that the category itself does not exist in any developed form. The customer is not choosing between providers; the customer has not yet recognised that the problem is solvable. The competitors, where they exist, are weak or partial or operating at a quality level that the customer has resigned themselves to. The founder’s job is not to claim a position within an established category. It is to bring the category into existence, train the customer to recognise the problem as solvable, and arrive in the market with the first credible offer.
If you run the standard UVP framework against this situation, the output is a sentence that distinguishes you from competitors who are not actually competing for customers who are not actually shopping for what you offer. The sentence is technically correct and useless, because the work that needs doing is not within-category positioning. The work is category creation, and category creation requires a different kind of statement.
The two distinct UVP situations
Let me be specific about the two situations and the different disciplines each requires.
The first situation is the crowded category. The customer knows they need something in your category. They are evaluating providers. They have a set of criteria. They will choose someone, and the question is whether they will choose you. In this situation, the standard UVP framework works exactly as advertised. You distinguish yourself within the category on a dimension the customer values, you articulate the distinction crisply, and you let the customer self-select. African founders building, say, a delivery service in Cape Town, or a digital marketing agency in Lagos, are in this situation. The category exists. The customers exist. The competitors exist. The discipline is positioning within the category.
The second situation is the category that does not yet exist. The customer does not know they need what you offer. They have been living with the problem for so long they no longer recognise it as a problem. There are no real competitors because no one is yet seriously competing. The customer is not shopping. They cannot evaluate you against alternatives because they cannot easily imagine the alternatives. African founders building, say, the first credible mobile-first goal-tracking application for African operators, or the first formal-grade B2B SaaS for African SMEs, or the first ride-hailing service in a market that has tolerated unmetered taxis for forty years, are in this situation. The category is being constructed, not joined. The discipline is something else entirely.
In the second situation, what the founder needs is not a Unique Value Proposition. It is what I call a Category Recognition Statement: a sentence that names the problem the customer has been living with as a problem, names the solvable version of the problem as something that can now exist, and positions the venture as the credible first instance of that solvable version.
A Category Recognition Statement does not begin with “we are different from our competitors because.” It begins with “you have been living with X. You did not have to. We built Y.” The structural difference is everything. The first sentence assumes the customer was already shopping. The second sentence wakes the customer up to the fact that they should be.
How to write a Category Recognition Statement
The discipline is harder than the standard UVP discipline because it requires the founder to do work the customer has not yet done. The customer has not yet diagnosed the problem. The founder must diagnose it on their behalf, articulate it crisply enough that the customer recognises themselves in the diagnosis, and then offer the solution.
Three steps work, in my experience.
The first step is to name the resignation. What have customers in your target market been resigning themselves to as the unchangeable texture of their lives? In African contexts, the resignations are often around quality, reliability, time, dignity, and pricing. Customers have resigned themselves to slow service, to unreliable delivery, to unhelpful staff, to opaque pricing, to formats that were not built for them. The first move is to name the resignation specifically. Not “bad service.” Specifically: “the experience of waiting forty-five minutes for a meal in a restaurant where no one will tell you why.”
The second step is to claim the resignation is a choice, not a fate. The customer believes their experience is just how things are. The Category Recognition Statement claims, implicitly or explicitly, that this is not how things have to be. Other markets have solved this. Other ventures have solved this. The resignation is a habit, not a structural feature of reality. This is a confident move and it requires the founder to know enough about the alternative to be credible.
The third step is to position the venture as the credible first instance of the alternative. Not the only alternative. Not the perfect alternative. The credible first instance. The customer does not yet need to be sold on you specifically; they need to be sold on the existence of the alternative, and the venture’s job is to be the most visible first instance of it.
A Category Recognition Statement built this way reads differently from a UVP. A UVP for a Cape Town delivery service might read: “Faster, more reliable last-mile delivery for Cape Town small businesses.” A Category Recognition Statement for the first formal-grade B2B SaaS for Zimbabwean SMEs would read more like: “You have been running your business on WhatsApp groups, paper invoices, and quarterly tax panic. You did not have to. Workzuite is the first operating system built for businesses like yours.”
The first sentence is positioning. The second sentence is category creation. They serve different purposes and the founders who confuse the two get the wrong output.
Which situation are you actually in
The diagnostic question is harder than it sounds, because most founders default to assuming they are in the crowded category situation. The default is wrong almost as often as it is right.
To test which situation you are in, ask three questions about your target customer. First: when they wake up in the morning thinking about the problem your venture solves, do they think about it as a problem they are actively trying to solve, or as a fact of life they have stopped noticing? If the former, you are in a crowded category. If the latter, you are in a category that does not yet exist.
Second: if you took your venture out of the market tomorrow, would your customer immediately switch to a known alternative, or would they go back to whatever workaround they had before you arrived? If the first, the category exists; if the second, you are constructing it.
Third: when your customer has tried to explain your venture to someone else, what category do they say it belongs to? If they have a clean category name, the category exists. If they say something like “it is sort of like X but for Y, except not really,” you are creating a category, and your customer is performing the category-creation work on your behalf, which is exactly the work the Category Recognition Statement should be doing for them.
The answers will reveal which discipline you are actually running. If you are in a crowded category, the standard UVP framework is the right tool, and the work is sharp positioning. If you are creating a category, the Category Recognition Statement is the right tool, and the work is naming the resignation, claiming it is a choice, and positioning as the first credible instance of the alternative.
Most African founders building anything ambitious are in the second situation more often than they realise. The framework most African founders have been taught was built for the first situation. The mismatch is the reason so many UVPs read as forced; the discipline being applied does not match the problem being solved.
The fix is to recognise the problem you are actually solving, choose the discipline that fits, and stop trying to write a UVP for a category that has not yet been brought into existence. The Category Recognition Statement is a sharper tool for the harder, more African problem, and it is the one I have come to use across all the ventures I run.
For the related question of who you should not try to convince, see Beyond Your Sympathy Market. For why a vision that genuinely does work is the precondition for any value proposition, see The Vision That Does Work. For the posture of disrupting a stagnant market, see Be the Disruption Before It Reaches You.
