Projects
Products, tools, and market systems built alongside the research.
These projects reflect how Stephen Omukoko Okoth approaches execution: start with a real friction point, build the smallest useful system around it, and keep the economics visible.
Decision tools
LeadAfrik Calculator
An embedded decision workspace for rent versus buy, job offers, retirement sustainability, and college versus retirement tradeoffs.
Why it matters
Brings model-backed economic decision support directly into LeadAfrik instead of leaving users with static articles alone.
Stack
FastAPI, React, Vite, Next.js integration
Property operations
Rentflow
A property-operations workspace for rent collection, occupancy, service recovery, notices, and portfolio control.
Why it matters
Extends the LeadAfrik product story from market discovery into landlord operations, giving users a direct path from the platform into a working property-management tool.
Stack
Next.js, operations workflows, payment and document tooling
Marketplace
Agrisoko254
A Kenyan agricultural marketplace connecting farmers, traders, agrovets, and buyers across all 47 counties.
Why it matters
User-provided operating note: founded and led with a five-person team, reaching roughly 100 users and 11 listings within the first two months.
Stack
React PWA, marketplace workflows, direct buyer-seller discovery
Consumer product
Jali
A privacy-first care coordination app for families and close friends, built around reminders, shared care groups, and exportable journals instead of feeds or contact scraping.
Why it matters
Turns intentional care into a product system with shared accountability, lightweight collaboration, and reminder-driven follow through.
Stack
React, TypeScript, Vite, Firebase Auth, Firestore, Cloud Functions
How they fit together
LeadAfrik is the umbrella.
The work is not limited to one lane. Some projects are public-economics products, some are consumer tools, some are marketplaces aimed at improving discovery and execution in fragmented markets, and some are property-operations systems built for day-to-day execution.
What ties them together is a consistent operating style: clear user intent, strong information design, and a bias toward building systems that people can use immediately.