SendSasa (@sendsasallc) header
SendSasa (@sendsasallc) profile picture

WhatsApp-Native Financial Operating System for Africa

El Paso, Texas
Joined May 2025
Photo by SendSasa (@sendsasallc)Photo by SendSasa (@sendsasallc)Photo by SendSasa (@sendsasallc)Photo by SendSasa (@sendsasallc)Photo by SendSasa (@sendsasallc)Photo by SendSasa (@sendsasallc)
Most apps only store the current state. Balance: XAF 15,000. Tomorrow it's XAF 30,000. You update the record. Fine for most apps. But for fintech, banking, inventory, logistics, trading platforms, hospital systems, storing only the current state isn't enough. Because the real question isn't "what's the balance now?" It's "how did it get here?" That's where event sourcing comes in. ๐—˜๐˜ƒ๐—ฒ๐—ป๐˜ ๐˜€๐—ผ๐˜‚๐—ฟ๐—ฐ๐—ถ๐—ป๐—ด: ๐˜€๐˜๐—ผ๐—ฟ๐—ฒ ๐˜๐—ต๐—ฒ ๐˜€๐˜๐—ผ๐—ฟ๐˜†, ๐—ป๐—ผ๐˜ ๐—ท๐˜‚๐˜€๐˜ ๐˜๐—ต๐—ฒ ๐—ฟ๐—ฒ๐˜€๐˜‚๐—น๐˜. Instead of storing "balance: XAF 30,000," you store: account created โ†’ XAF 50,000 deposited โ†’ XAF 20,000 withdrawn. Add it all up, and you get XAF 30,000. Think of El Clรกsico. Ask who won, someone says "Barcelona demolished Real Madrid, 4โ€“0." ๐Ÿ˜„ (@10Ronaldinho is why I fell in love with this club.) That's current state. Event sourcing is minute-by-minute: goal at 12', goal at 38', goal at 61', goal at 85', Madrid never even got a shot on target. Now you know exactly how the beatdown happened, not just the final score. When a customer asks "why did my balance drop?" you don't guess. You check the events. Money in here, transfer out there, fee deducted here, reversal there. Your system has memory, not vibes. ๐—–๐—ค๐—ฅ๐—ฆ: ๐˜€๐˜๐—ผ๐—ฝ ๐—ณ๐—ผ๐—ฟ๐—ฐ๐—ถ๐—ป๐—ด ๐—ฟ๐—ฒ๐—ฎ๐—ฑ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐˜„๐—ฟ๐—ถ๐˜๐—ฒ๐˜€ ๐˜๐—ผ ๐˜€๐—ต๐—ฎ๐—ฟ๐—ฒ ๐—ฎ ๐—บ๐—ผ๐—ฑ๐—ฒ๐—น. Command Query Responsibility Segregation. Big name, simple idea: separate the side that writes data from the side that reads it. Commands are actions โ€” create account, place order, send money, approve loan. They need validation, business rules, security, consistency. Queries are questions โ€” get balance, fetch order history, show dashboard. They need speed, filtering, search. Small apps can use one model for both. Fine. But at scale, forcing reads and writes into the same structure just slows everything down. It's a kitchen and a serving counter. The kitchen (writes) is where the strict, careful work happens. The counter (reads) is where customers grab what they need, fast. Force everyone through the kitchen, and the whole place backs up. ๐—–๐—ผ๐—บ๐—ฏ๐—ถ๐—ป๐—ฒ ๐˜๐—ต๐—ฒ๐—บ, ๐—ฎ๐—ป๐—ฑ ๐˜๐—ต๐—ถ๐—ป๐—ด๐˜€ ๐—ด๐—ฒ๐˜ ๐—ถ๐—ป๐˜๐—ฒ๐—ฟ๐—ฒ๐˜€๐˜๐—ถ๐—ป๐—ด. Write side stores events: order placed โ†’ payment received โ†’ order packed โ†’ shipped โ†’ delivered. Read side builds different views from the same events: a customer sees "your order is on the way," admin sees "243 orders shipped today," finance sees "XAF 18M received this week," logistics sees "27 packages pending." Same events. Different views. That's the power. But don't misuse this. Don't bring event sourcing and CQRS to a to-do app. If your system just needs create, read, update, delete โ€” plain CRUD is enough. Use it and sleep well. The skill isn't knowing these patterns exist. It's knowing when they actually earn their complexity. Where's the line for you, when does a system stop being "CRUD is fine" and start needing its full history?
1
3
190
Every startup has that one dependency that, if it goes down, takes the whole product with it. One payment provider. One AI API. One SMS gateway. One email service. One cloud storage. One npm package installed because @StackOverflow said so. Everything works. The demo is smooth. Investors clap. Two weeks later: the SMS provider goes down. The payment webhook starts delaying. The AI API returns garbage. The email provider blocks your domain. That npm package gets compromised. Cloud storage says "degraded performance." Degraded performance for them. Cardiac arrest for you. That's the moment you realize: your architecture was never a system. It was a prayer request. If one dependency going down can send your entire product to the grave, you didn't integrate a service, you married your destiny to another company's uptime. That's not partnership. That's technical bondage. ๐—›๐—ผ๐˜„ ๐˜๐—ผ ๐—ฎ๐—ฐ๐˜๐˜‚๐—ฎ๐—น๐—น๐˜† ๐—ฏ๐˜‚๐—ถ๐—น๐—ฑ ๐—ณ๐—ผ๐—ฟ ๐—ถ๐˜: ๐Ÿญ. ๐——๐—ฒ๐˜€๐—ถ๐—ด๐—ป ๐˜„๐—ถ๐˜๐—ต ๐—ณ๐—ฎ๐—ถ๐—น๐˜‚๐—ฟ๐—ฒ ๐—ถ๐—ป ๐—บ๐—ถ๐—ป๐—ฑ Every dependency can fail, payment provider, AI model, Redis, database, email. Treat failure handling as part of the product, not an afterthought. ๐Ÿฎ. ๐—œ๐˜€๐—ผ๐—น๐—ฎ๐˜๐—ฒ ๐—ฒ๐˜…๐˜๐—ฒ๐—ฟ๐—ป๐—ฎ๐—น ๐—ฑ๐—ฒ๐—ฝ๐—ฒ๐—ป๐—ฑ๐—ฒ๐—ป๐—ฐ๐—ถ๐—ฒ๐˜€ Don't let a vendor's SDK scatter through your entire codebase. Build your own wrapper, a payment service, an email service, an AI provider service. Your app talks to your interface; your interface talks to the vendor. If the provider fails you tomorrow, you swap the wrapper. You don't rewrite the company. ๐Ÿฏ. ๐—ง๐—ถ๐—บ๐—ฒ๐—ผ๐˜‚๐˜๐˜€, ๐—ฟ๐—ฒ๐˜๐—ฟ๐—ถ๐—ฒ๐˜€, ๐—ฐ๐—ถ๐—ฟ๐—ฐ๐˜‚๐—ถ๐˜ ๐—ฏ๐—ฟ๐—ฒ๐—ฎ๐—ธ๐—ฒ๐—ฟ๐˜€ Non-negotiable for anything you don't control. ๐Ÿฐ. ๐—ค๐˜‚๐—ฒ๐˜‚๐—ฒ ๐—ฒ๐˜…๐˜๐—ฒ๐—ฟ๐—ป๐—ฎ๐—น ๐˜„๐—ผ๐—ฟ๐—ธ Sending email, SMS, or a slow job? Accept the request, store the state, process in the background, retry when needed. Your user's experience shouldn't collapse because a vendor is slow. ๐Ÿฑ. ๐— ๐—ฎ๐—ธ๐—ฒ ๐—ผ๐—ฝ๐—ฒ๐—ฟ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ถ๐—ฑ๐—ฒ๐—บ๐—ฝ๐—ผ๐˜๐—ฒ๐—ป๐˜ If the same operation runs twice, it shouldn't cause double damage. Period. ๐Ÿฒ. ๐—™๐—ฎ๐—น๐—น๐—ฏ๐—ฎ๐—ฐ๐—ธ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—ด๐—ฟ๐—ฎ๐—ฐ๐—ฒ๐—ณ๐˜‚๐—น ๐—ฑ๐—ฒ๐—ด๐—ฟ๐—ฎ๐—ฑ๐—ฎ๐˜๐—ถ๐—ผ๐—ป Always have one. Always. ๐Ÿณ. ๐— ๐—ผ๐—ป๐—ถ๐˜๐—ผ๐—ฟ ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฑ๐—ฒ๐—ฝ๐—ฒ๐—ป๐—ฑ๐—ฒ๐—ป๐—ฐ๐—ถ๐—ฒ๐˜€ Track latency, error rates, timeout rates. Your system should know a vendor is sick before your users tell you on Twitter. ๐Ÿด. ๐—ฃ๐—ฟ๐—ผ๐˜๐—ฒ๐—ฐ๐˜ ๐—ฎ๐—ด๐—ฎ๐—ถ๐—ป๐˜€๐˜ ๐—ฐ๐—ผ๐—บ๐—ฝ๐—ฟ๐—ผ๐—บ๐—ถ๐˜€๐—ฒ๐—ฑ ๐—ฑ๐—ฒ๐—ฝ๐—ฒ๐—ป๐—ฑ๐—ฒ๐—ป๐—ฐ๐—ถ๐—ฒ๐˜€ Review packages. Use lock files. Run dependency scans. Remove what you don't need. Least privilege. Keep secrets out of your code. "We trust this package" is not a security strategy. ๐Ÿต. ๐——๐—ผ๐—ฐ๐˜‚๐—บ๐—ฒ๐—ป๐˜ ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฒ๐˜…๐—ถ๐˜ ๐—ฝ๐—น๐—ฎ๐—ป Before you depend heavily on any provider, ask: Can we export our data? Switch API keys? Route to another provider? Change the implementation without breaking the product? Every serious dependency needs an exit door. Trust providers, but don't worship them. Integrate dependencies, but isolate them. Use external services, but protect your own core. Automate retries, but avoid duplicate damage. Monitor everything. Plan for failure. If one dependency can take down your whole product, that dependency is no longer a tool. Now it's your co-founder. And some co-founders resign without notice. What's the one dependency your product would not survive losing tomorrow?
3
1
3
283
collecting for a birthday, a trip, or a shared expense? create a pot. share the code. SplitChat tracks who paid and who hasn't. money releases when you hit your target. no chasing. no drama. #SendSasa #SplitChat #MobileMoney
1
2
81
the address book holds 20 contacts. after that, older ones disappear. SasaNames has no ceiling. claim [yourname].sasa, anyone pays you, no number, no list, no limit. #SasaNames #SendSasa #MobileMoney
4
3
42
4/ The address book is for your inner circle. SasaNames is for everyone else. grace.sasa ยท duclair.sasa ยท shop.sasa
11
3/ So we built past it. SasaNames โ€” claim [yourname].sasa โ†’ Anyone types your name to pay you โ†’ They don't need your number โ†’ They don't need to be in your contacts โ†’ No ceiling. No list. No limit.
12
2/ After 20, older contacts start falling off the list. Fine for most people. Not fine if you're a merchant with 50 regulars. Not fine if you're a freelancer with 30 clients. Not fine if strangers pay you daily at a market stall.
11
1/ The address book is one of the best features in SendSasa. Save "Mom." Save "Landlord." Save "Boss." One tap. Transfer done. But it has a ceiling โ€” 20 contacts.
16
She's "Mama" in your phone. Not "+237 678 901 234." Your transfers should know that too. โ†’ Save names, not numbers โ†’ Lock in your amounts โ†’ Send in one message Smart Address Book โ€” SendSasa ๐Ÿ’™โšก
1
2
106
Patrick is in Montreal. His crew is in Douala. Every Friday he calls his brother to hand out cash โ€” because no Canadian bank reaches MTN MoMo. We're building the fix inside WhatsApp. Type. Approve. 8 wallets credited in Douala. From Canada. SendSasa ๐ŸŒ #Fintech #MobileMoney
2
3
113
African SMEs don't have a talent problem. They have a "how do I invoice my client in Texas" problem. We're solving it, inside WhatsApp. No bank. No app. No terminal. Just a message. A link. And money in your mobile wallet. SendSasa ๐ŸŒ #Africa #Diaspora #Fintech #MobileMoney
2
4
133
Send money home faster than typing "I love you" ๐Ÿ’› No app. No bank account. No crypto knowledge. Just open WhatsApp, type the amount, and your family has it in 60 seconds. sendsasa.com #SendSasa #Remittance #Africa #WhatsApp #Stellar #Fintech
1
2
93
Welcome Duclair Fopa @BlockchainMonk_ , CTO @mobilewalletinc to the ๐ŸŒŠAquarium Incubator cohort 8 on Social Impact at XRPL Commons, Paris.
We just got accepted into The Aquarium residency in Paris. 12 weeks to build what traditional finance fears most: - WhatsApp remittances in 60 seconds (<1% fees) - Crypto ATMs across Africa (BTC, ETH, USDT, SOL) March 27th, we launch. ๐Ÿ‡จ๐Ÿ‡ฒ๐Ÿš€ #XRPL #Crypto #Africa
1
4
15
1,109
We just got accepted into The Aquarium residency in Paris. 12 weeks to build what traditional finance fears most: - WhatsApp remittances in 60 seconds (<1% fees) - Crypto ATMs across Africa (BTC, ETH, USDT, SOL) March 27th, we launch. ๐Ÿ‡จ๐Ÿ‡ฒ๐Ÿš€ #XRPL #Crypto #Africa
4
2
1
14
1,858
Michael Seibel on how to create a great startup pitch In the clip below, former Y Combinator CEO Michael Seibel breaks down the two types of pitches every startup founder needs: a 30-second elevator pitch and a two-minute pitch for investors. โ€œA lot of people practice 10-minute, 30-minute, hour-long, pitches. I think thatโ€™s all garbage. I think you can get all of your points across in two minutes. And one thing I like to tell founders is that the more you talk, the more you have an opportunity to say something that people donโ€™t like.โ€ 30-Second Elevator Pitch: You should be able to explain to anyone you come across what your company does in 30 seconds. This should be three sentences: 1. What does your company do? Assume the person youโ€™re talking to knows nothing. This should be a 1-sentence explanation that your mom or dad can understand (e.g. โ€œWeโ€™re Airbnb and we allow you to rent out the extra room in your houseโ€ NOT โ€œWeโ€™re Airbnb and weโ€™re a marketplace for spaceโ€). 2. How big is the market? Do a couple hours of research so that you can give investors a rough approximation of the size of the market youโ€™re in (e.g. Airbnb might give the size of online hotel booking market) 3. How much traction do you have? Ideally you can say something like: โ€œWe launched in January and weโ€™re growing 30% month over month. We have $ X sales and Y users.โ€ If youโ€™re pre-launch, you need to convince investors that youโ€™re moving quickly (e.g. โ€œthe team came together in January. By March we launched our beta. By April we launched our product.โ€). Two-Minute Pitch: This pitch is for people youโ€™re actually trying to convince of something (e.g. investors, potential employees, etc.). You basically want to simply explain what you do and then ask for money. There are 5 key components: 1. Clear 30 second pitch (everything mentioned above) 2. Unique insightโ€”what do the biggest players in your market not understand? This should be 2 sentences. 3. How do you make money? 4. Team. If your team has done something that has made investors money, you should mention that (e.g. โ€œweโ€™re the founders of PayPalโ€). If you havenโ€™t, donโ€™t go on about the awards youโ€™ve won or PhDs you hold. What investors want to hear is: how many founders? (hopefully 2-4) how many of the founders are technical? (hopefully 50% or more engineers) How long have you known each other? (ideally youโ€™ve known each other either personally or professionally for at least 6 months) Are you all full-time? 5. The Big Ask ($$$). You have to know what youโ€™re talking about when you ask for money. Are you raising on a convertible note or a SAFE? Whatโ€™s the cap of the SAFE? How much money are you raising? Whatโ€™s the minimum check size? If you donโ€™t know these things, investors wonโ€™t think youโ€™re serious or that you havenโ€™t done your homework.
12
133
8
638
80,720