Overview
Sedoinsurance is an insurance-focused web platform built for the realities of an emerging market: mobile-native, mobile-money-friendly, and designed to compress the distance between wanting coverage and having it. It presents vehicle, health, life, and property products, with contracts issued through licensed partner insurers.
Problem
Traditional insurance in the region is built around branch offices and paper: slow quotes, cash payments, and claims processes that require showing up in person. For a mobile-first population, every one of those steps is a reason to stay uninsured.
Users
- Individuals seeking vehicle, health, life, or property coverage
- Customers paying premiums through mobile money
- Policyholders filing and tracking claims from a phone
Goals
- Deliver quotes online in minutes rather than days
- Meet customers on the payment rails they already use — mobile money
- Keep the platform compliant by partnering with licensed local insurers
- Design every flow mobile-first
My role
Founder and developer — product concept, user workflows, authentication, database integration, and service-management functionality.
Product strategy
Rather than becoming an insurer, the platform positions itself as the digital layer over licensed partners: it owns the customer experience — quoting, payment, claims — while regulated partners carry the risk. That keeps the product asset-light and locally compliant.
Key features
- Online quoting
- Guided flows produce a quote in minutes for vehicle, health, life, and property products.
- Mobile-money payments
- Premiums are payable through the mobile-money systems customers already trust.
- Phone-first claims
- Claims can be filed and followed from a phone, replacing branch visits.
- Account & policy management
- Authenticated user accounts for managing quotes, policies, and service requests.
Technical architecture
- Mobile-first web application with authenticated user accounts
- Database-backed policy, quote, and service-request management
- Integration-ready payment workflows for mobile-money providers
- Cloud deployment with HTTPS
Security & privacy
- Authentication and access control around customer accounts
- Customer data collected only where the quoting and claims workflows require it
- Regulated risk carried by licensed partner insurers rather than custom infrastructure
Engineering challenges & decisions
Designing trust into a digital product in a market where insurance is bought face-to-face.
Transparent products, plain-language flows, and visible licensed-partner backing stand in for the reassurance of a branch office.
Building payment flows around mobile money rather than card networks.
Payment workflows were designed around regional mobile-money patterns from the start instead of retrofitting card-centric assumptions.
Lessons learned
- Emerging-market products succeed by respecting local rails — mobile money first, not as an afterthought.
- Partnering with licensed institutions is a product decision as much as a legal one.
Future improvements
- Deeper claims-tracking automation
- Expanded partner and product coverage