Problem and customer segmentالمشكلة وشريحة العملاء

The segment is the group you are building for, and the problem is what hurts them enough today to pay for a fix. What kills most FinTech products is a segment written as something as wide as "young people" or "small businesses".

Begin with the moment when one identifiable person is forced to move money in a painful way.

Why pick a segment? Everyone needs money

This is the rational objection in any other product, and a fatal error in financial ones specifically.

A food delivery app really does serve everyone, because an order is an order whoever placed it. A financial product has its rules change with who uses it.

Picture a wallet serving a student, a migrant worker and a small shop owner at once. The student needs low limits and a one-minute signup. The worker needs outbound remittance and verification against a residency permit that may expire in two months. The shop owner needs to accept payments from strangers, which is an entirely different regulated activity.

You are not building one product for three people. You are building three products with three risk profiles, three onboarding paths and possibly three licences. In a startup that usually means doing none of them well.

There is a harsher second reason: vagueness kills you at the regulator before it kills you in the market. The first question in any licensing file is exactly who your customers are. Answering "everyone" reads as someone who has not yet thought about their own risk.

Specificity here is not marketing cleverness. It is an operating requirement.

A situation is narrower than a demographic

Segmentation means choosing a group that shares a situation you can build for. Labels such as students, young professionals, and middle-income earners are too broad. A student receiving a regular allowance has little in common with an international student waiting for a cross-border transfer. Their ages match; their financial needs and risks do not.

A useful description combines a person, a moment, an obstacle, and an observable result. A freelancer waiting 60 days for an invoice may be unable to pay rent today. A restaurant whose card sales settle after two days may lack cash for tomorrow morning's ingredients. Each case is buildable because the pain and desired result are specific.

Do not begin with a feature such as a better-looking card or faster transfers. Customers are trying to complete a blocked job, not acquire a feature. Write one sentence: this product serves this person when this event happens, so they can achieve this measurable result.

Test the problem before building

Evidence comes from real behaviour, not polite approval in an interview. Ask a restaurant owner about the last delayed settlement, what they did, and what the workaround cost. Do not ask whether they would use an app that settles faster. A friendly yes is not demand.

Find the current solution, however poor. A freelancer may borrow from family, delay rent, or pay a fee for invoice finance. Spending time or money is evidence that the problem matters. A complaint followed by no action may be an irritation rather than a market.

Compare repeated cases. Ten merchants telling the same story with similar sales patterns begin to form a segment (الشريحة). If every interview has a different cause and solution, you have collected people, not a market. Narrow the description until product, risk, and distribution decisions align.

Write down whom you will refuse

Risk appetite (شهيّة المخاطر) is the amount of risk the company has formally agreed to accept. It becomes limits on countries, occupations, transaction sizes, and sources of funds. The board approves those limits; product and operations apply them.

An app may serve Saudi-based freelancers paid against documented local invoices. It may refuse cash businesses without invoices, customers outside its licensed territory, or payments beyond its loss capacity. Refusal does not label a person as bad. It says the product lacks the permission, data, or capital to serve them safely.

Write the refusal list before marketing. A campaign attracting cross-border merchants to a locally licensed product creates wasted cost and distrust. If support staff invent reasons case by case, similar customers receive different decisions. The list is simultaneously a risk, training, and design document.

The licence marks the market boundary

A licence determines what the business may do. A company offering accounts through a sponsor bank has different freedom from the bank itself. Invoice finance and a marketplace displaying third-party offers may look similar on screen, but carry different legal responsibility.

Test every segment with three questions. Does the licence permit it? Can you verify the customer and activity? Can the company absorb a plausible worst loss? One failed answer makes the segment unsuitable today. A new partner, stronger control, or more capital may change that later.

Trust belongs in the product definition

Trust means customers expect their money to arrive and expect an explanation when it does not. They see it in a clear legal name, total price, understandable status, and support staff with answers. Hidden fees and unexplained status changes destroy it.

A merchant may tolerate an old bank interface because the bank will investigate an error. The same merchant may reject a faster unknown app that cannot explain where balances sit. Potential loss outweighs interface comfort, so test the trust promise alongside the problem.

Distribution comes before features

Distribution is the route by which a product reaches a customer and borrows or earns trust. Accounting software already meets thousands of merchants when they issue invoices. An employer already meets workers when salary is paid. Both have a stronger route than an advertisement for an unknown money app.

A slightly better app is rarely enough to overcome a new identity check, account link, pricing model, and risk of error. A weaker product can win because it sits inside a channel the customer already uses. A segment definition should therefore include where customers can be reached and at what cost.

Turn the description into decisions

Create a one-page segment card before drawing the first screen. Record the situation, current workaround, price already paid, refusal boundary, trust reason, and distribution route. Add three observed facts from interviews or data.

Test each new request against that card. A loud customer outside the segment should not redirect the whole product. A repeated need among the chosen customers is stronger evidence. This discipline produces a product compliance can justify, sales can explain, and customers can trust.