CPI is a change readiness platform built for Tanya de Villiers, UAE, helping users assess where they stand, unlock AI powered insights, and follow a guided path to improve.
What made this project special?
Most software helps people do more.
Very few products are built to help people change better.
We built:
ā 125 question assessment engine
ā AI generated mini + full reports
ā Stripe powered premium unlock
ā 12 week guided action plan
ā Admin panel for assessments, reports, users, and payments
The real challenge was building it in a way that future phases could be added without rebuilding the product.
So we focused on scalable architecture, flexible flows, and future ready product logic.
We delivered Phase 1 successfully.
And the best part?
The client loved it so much, she trusted us to build Phase 2 as well. š
Ledger ā AI CFO Platform
Ledger is an AI platform that acts as an always-on Chief Financial Officer for founders ā connecting to accounts, learning cash rhythm, and surfacing risks before they become real problems. I designed the full landing page.
My role:Ā UI/UX Design
Scope:Ā Landing page
Financial tools for founders usually feel either cold (dashboards) or intimidating (accounting software).
For Ledger, we borrowed from old-world institutional finance instead ā serif type, oil-painting textures, classical architecture ā so an AI CFO feels like real authority, not another app.
Built this over a weekend as an experiment with AI-assisted design and development.
Duo Case is an absurd concept for turning two iPhones into a very unofficial foldable iPhone. The goal was to see how far AI could accelerate the process while keeping creative direction, design decisions and final execution in human hands.
Iāve been building SabiFlow for a while, and honestly, the most interesting part of the project isnāt the code.
It's the problem.
Because it's personal.
I've experienced that thing where money comes in and somehow, without you really noticing, it starts disappearing.
Not because you donāt earn enough.
Not necessarily because you're irresponsible either.
Sometimes money simply has no job when it arrives.
And as an engineer, that got me thinking:
What if the problem isn't budgeting? What if the problem is that weāre asking people to make too many good decisions at the exact moment they have the most temptation to make bad ones?
That question became the foundation for SabiFlow.
Instead of telling someone, "You should save 20% of your income," I started thinking about what would happen if the system simply helped assign every inflow a purpose the moment it arrived.
That led me down a rabbit hole.
Funnels.
Automated distribution.
Wallet infrastructure.
Virtual accounts.
User behaviour.
Transaction flows.
KYC.
Compliance.
Even the psychology behind notifications.
And this is probably my favourite part of being both an engineer and a founder.
I donāt just ask:
"How do I build this feature?"
I ask:
"Why does this problem exist, and what kind of system could make dealing with it easier?"
Then the engineer in me comes along and asks:
"Okay⦠but how do we actually make this work reliably?" š
That tension between the founder thinking about the problem and the CTO thinking about the system is probably what I enjoy most about building SabiFlow.
Iām still figuring a lot of it out.
But I'm curious:
Whatās a problem youāve experienced personally that eventually made you want to build something around it?
The framing around āwhy does this problem exist?ā is exactly the kind of product thinking that keeps a financial tool from becoming another dashboard. SabiFlow sounds strongest where the behavioral insight meets the practical system designāespecially around notifications and reliable follow-through.