How to Build a Customer Persona for Low-Income and Informal-Market Customers in Africa

Standard customer persona templates assume a customer with a smartphone, a bank account, a regular salary, and reliable internet. Most African social enterprise customers have none of these. Here is how to build a persona that actually reflects the people you are serving — and why it changes everything about your product, your pricing, and your communication.

Customer personas are one of the most widely used tools in product design and marketing. They are also one of the most widely misused — particularly in the African social enterprise context, where the customer templates available online are built for middle-class consumers in high-income countries, and applying them to a smallholder farmer in western Kenya or an informal market trader in Kumasi produces something that is simultaneously accurate on the surface and useless in practice.

The problem is not with personas as a tool. It is with what the standard persona captures. Age, gender, income bracket, education level, job title — these are the conventional building blocks of a persona. And for the customers that most African social enterprises are trying to serve, they tell almost nothing useful about how the customer makes decisions, what constrains their choices, what they trust, how they communicate, and what a product needs to do to earn and maintain their loyalty.

This post explains how to build a customer persona that actually works for low-income and informal-market customers in Africa — one that captures the things that matter, is built from real conversations rather than assumptions, and generates the specific insights that improve your product, your pricing, and your communication strategy.

Why Standard Personas Fail in African Markets

Before building the right persona, it helps to understand specifically where the standard ones go wrong.

They assume digital access that does not exist. The standard persona template asks about social media platforms used, websites visited, and preferred digital communication channels. For a customer who uses a 2G feature phone, whose internet access is intermittent and expensive, whose “digital” behaviour is primarily WhatsApp voice messages and SMS, this section of the template captures something real — but not in a way that is actionable for a product team that has been trained to think about digital touchpoints in terms of apps, emails, and social media advertising.

They assume stable, formal income. Income bracket — a standard persona field — is a deeply misleading concept for customers with irregular, seasonal, or multiple-stream livelihoods. A smallholder farmer who earns the equivalent of $800 in a good harvest season, nothing in the lean months, and supplements with casual labour and small trading has an annual income figure. But that figure tells you almost nothing about when she has cash available, what she can afford to pay at different points in the year, and how she makes financial decisions under the constraint of unpredictable income timing. Pricing and payment structure decisions that do not account for this cash flow reality will consistently fail.

They assume individual decision-making. Standard personas focus on the individual: her goals, her pain points, her decision-making process. In many African contexts — and particularly in the communities most African social enterprises serve — decisions are made collectively or within household and community structures that significantly constrain individual choice. A woman smallholder farmer in rural Uganda may want to adopt a new agricultural practice but faces household decision-making dynamics that require her husband’s agreement. An informal trader in Lagos may be part of a rotating savings group whose collective decisions affect her individual financial behaviour. These social and relational dimensions of decision-making are invisible in a standard persona.

They focus on stated wants rather than real constraints. The standard persona asks: what are her goals? What does she want to achieve? These are important questions, but for low-income customers in African markets, the more important questions are often: what stops her from achieving those goals? What resources — time, money, information, social permission, physical access — does she lack? What would she need to change to be able to use your product? Understanding the constraint architecture is the difference between designing a product that is attractive to her and designing a product that she can actually use.

The Seven Things a Useful Informal-Market Persona Captures

A customer persona for low-income and informal-market customers in Africa should be built around seven dimensions that standard templates miss or under-specify.

1. Income Pattern, Not Income Level

Rather than asking “what is her monthly income?”, ask:

How does she earn? (Single employer, multiple clients, harvest-based, trading, casual labour, mixed)
When does she have cash? (Daily, weekly, monthly, seasonally)
What triggers a cash crunch? (School fees due, medical emergency, planting costs, lean season, loan repayment)
How does she smooth income across cash-poor periods? (Savings group, informal credit, reducing consumption, selling assets)

The answers to these questions tell you what payment structure your product needs to offer — whether daily micro-payments work better than monthly fees, whether the lean season is when your customer needs your product most or when she cannot afford it, and what the emergency cash needs are that compete with spending on your product.

2. Decision-Making Structure, Not Individual Preferences

Map the household and community decision-making environment, not just the individual’s preferences:

Who else has authority over decisions related to this purchase? (Spouse, parent, village elder, savings group members)
What is the individual’s level of financial autonomy? (Controls own income, requires approval for significant purchases, operates within collective household budget)
What social permission structures govern adoption of new products or practices? (Early adoption is respected / early adoption is stigmatised / adoption requires community validation)
Who are the trusted influencers whose endorsement matters? (Peer farmers, faith leaders, respected community members, local government agents)

This mapping tells you who the real decision-maker is (it is often not the person using the product), what the full adoption pathway looks like, and who you need to communicate with to generate trust and endorsement.

3. Trust Architecture, Not Brand Awareness

In low-income and informal markets in Africa, trust is built differently from the way it is built in formal markets. Ask:

What sources of information does she trust? (Government extension workers, peer farmers, faith leaders, radio programmes, family members, mobile messages from known numbers)
What has caused her to distrust products or organisations in the past? (Promises not kept, poor quality, unexpected costs, agents who misrepresented terms)
What does proof of quality or legitimacy look like to her? (Certificate on the wall, referral from someone she knows, physical presence in the community, government logo, local language communication)
What is her experience with organisations that initially seemed trustworthy and then disappointed her?

Trust architecture tells you what communication channels work (not just which ones are accessible), what evidence you need to provide at each stage of the customer relationship, and what the trust-destroying behaviours are that you must avoid — particularly in early interactions.

4. Physical Access and Mobility Constraints

Standard personas assume that the customer can access your product if it is technically available. In informal African markets, physical access is frequently the binding constraint. Ask:

Where does she spend her time? (Home, market, farm, roadside stall — and at what times of day)
How far does she travel for different categories of purchase? (Daily market vs. town centre vs. district capital)
What modes of transport does she use? (Walking, bicycle, boda boda, public minibus — and at what cost and frequency)
What days and times are accessible for service or information? (Market days, after school run, before farm work)
What physical barriers exist? (Distance, cost of travel, safety concerns for women travelling alone, childcare responsibilities)

Physical access constraints tell you where your distribution point needs to be, what hours of operation make sense, and whether the assumption that your customer will come to you is realistic.

5. Literacy, Language, and Communication Preferences

Ask:

What language does she communicate in at home, in the market, and in formal settings? (These are often different)
What is her practical literacy level? (Reads formal documents / reads basic text / can read numbers / is functionally non-literate)
How does she receive information she trusts? (Radio, voice messages, face-to-face conversation, visual demonstrations, SMS)
What communication style feels respectful and appropriate? (Formal and deferential / peer-to-peer and conversational / through a trusted intermediary)
What numeracy skills are relevant to using your product? (Can read a price, can calculate a discount, understands interest rates, can interpret a graph)

Communication preferences tell you what your marketing materials need to look like, what language your service agents need to speak, and whether your onboarding process assumes literacy that your customer does not have.

6. Competing Claims on Her Time, Attention, and Money

Standard personas ask about goals. Equally important is what your customer is already managing:

What are the non-negotiable financial obligations that come before any discretionary spending? (School fees, household food, rent, transport, remittances)
What are the seasonal financial spikes that create cash pressure? (Harvest season input costs, festive period spending, school term start)
What time demands already structure her day? (Market hours, farm work, childcare, community responsibilities)
What other products or services is she already using that address adjacent needs? (And what are their strengths and weaknesses from her perspective)

Competing claims tell you what your product needs to cost — not just in money but in time and cognitive load — to be within the range of what she can realistically manage. They also tell you which competitors you are actually competing with, which is often not the product you think of as your direct competitor.

7. Aspiration and Identity, Not Just Need

This is the dimension that most impact-sector personas undervalue. Low-income customers are not defined by their constraints. They have aspirations, identities, and self-perceptions that shape what they buy and how they respond to how they are sold to.

Ask:

How does she see herself? (Entrepreneur, farmer, provider, progressive community member, responsible parent)
What does using your product say about her? (To herself and to her community)
What future is she working toward? (Children’s education, expanding the business, building a home, community respect)
What are the status signals in her community? (What products or practices signal success, modernity, respectability — and which ones signal the opposite)
What does she not want your product to make her feel? (Pitied, patronised, categorised as poor, seen as a charity recipient)

Aspiration and identity tell you how to frame your product — not as a poverty solution but as a tool that supports the future she is building and the person she understands herself to be. It tells you what language and imagery to use, and what to avoid.

How to Build the Persona: The Research Process

A customer persona is only as good as the research that underlies it. For low-income and informal-market customers in Africa, the research process requires specific disciplines.

Go to where she is. Market visits, farm visits, household visits — not focus group facilities or office meeting rooms. The environment shapes what she says and how she says it. A trader in her stall, surrounded by her products and her customers, will give you different and more useful information than the same person in a formal research setting.

Use conversational interviews, not questionnaires. Structured questionnaires with fixed-choice responses produce data that is easy to analyse and frequently misleading. Open-ended conversational interviews — guided by a loose set of topics rather than a fixed set of questions — produce richer, more honest, and more actionable information. Train your research team to listen and probe rather than to read questions and record answers.

Talk to her peers, not just to her. The social and relational dimensions of decision-making are only partially visible in individual interviews. Conversations with peer groups, savings group meetings, and community conversations — where the social norms and collective decision-making dynamics are visible — fill in what individual interviews miss.

Interview across the adoption spectrum. Talk to customers who are using your product and love it, customers who tried it and stopped, customers who considered it and decided not to try, and customers who have never encountered it. The reasons for non-adoption and dropout are frequently more instructive than the reasons for adoption.

Interview across the gender dimension. Male and female customers in the same household or community often have different decision-making roles, different financial autonomy levels, different trust networks, and different access constraints. A persona based only on one gender will miss systematically important insights.

How to Use the Persona

A customer persona is a reference tool, not a filing exercise. The disciplines that make personas genuinely useful:

Make it visual and accessible. A persona document that lives in a folder on someone’s computer does not inform product decisions. A persona that is printed, displayed in the office, and referred to in product and marketing conversations does.

Name her and give her a face. A named character — “Amara, 34, market trader, Tamale” — is more cognitively accessible than “Urban Informal Retailer Segment B.” Use a real photograph from your research (with permission) rather than a stock image.

Update it regularly. Customers change. Markets change. Regulatory environments change. A persona built in 2022 may not accurately represent your customer in 2026. Build an annual review of your persona into your operations cycle.

Test product and communication decisions against her. When your team is debating a pricing structure, a packaging decision, or a communication channel, the question “what would Amara think about this?” is a genuinely useful filter — but only if Amara is based on real research rather than assumptions.

Build multiple personas if your customer base is genuinely heterogeneous. Most social enterprises serve more than one customer type. A persona for your corporate B2B client is a very different document from a persona for your community beneficiary. Both are necessary.

The Bottom Line

The customer persona is not a bureaucratic requirement of product development methodology. It is the most efficient way to ensure that the decisions your team makes about product design, pricing, communication, and distribution are grounded in the actual reality of the people you are trying to serve — rather than in assumptions that feel plausible from the inside of an office.

In the African social enterprise context, where the gap between the assumptions built into standard tools and the reality of informal-market customers is enormous, building a rigorous, Africa-specific customer persona is one of the highest-return investments a founding team can make.

The persona is not the customer. But a persona built on real research is the closest you will get to having your customer in the room when you make every product decision that follows.