Satispay
The first mistake most fintech startups make with buyer persona is defining it too broadly: "anyone with a bank account". Satispay did the opposite.
Satispay's original buyer persona was almost photographic: Marco, 25, lives in Milan, works at a tech company or creative agency, goes out with friends every weekend, regularly splits restaurant bills or holiday costs, and finds the combination of "I don't have cash" + "wait, I'll send a transfer" + "I'll give it to you next week" genuinely frustrating.
This hyper-specific profile guided every product and marketing decision in the early years. The app design was intended to be used at the table, in front of friends, without embarrassment. The "request money" flow was more prominent than the "pay" flow because Marco was the one collecting dinner money, not the one sending it.
The buyer persona also guided the channel: peer word of mouth worked because Marco and his friends shared the same problem and the same solution. No explanation was needed — it was enough for one person in the group to have it.
When Satispay scaled to merchants, the buyer persona evolved — but the clarity of the initial user had already created the critical mass needed.
A buyer persona is useful when it is specific enough to exclude someone. If it includes "everyone who might benefit from the product", it is not a persona — it is a market segment.