I’ve been building SabiFlow for a while, and honestly, the most interesting part of the project i...I’ve been building SabiFlow for a while, and honestly, the most interesting part of the project i...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
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.
Exactly @Rohan Ahmed , I mean financial planning is being over rated with systems that sells you the future with out first understanding who you. So, the intelligence part has to kick-in and say... Hey Obi, I'm with you... I understanding but if you spend xyz now, you might suffer x in the...
Your SaaS video might be showing everything except why it matters.
Think about it.
A complex product. Countless features. Technology that might take minutes to explain.
Now imagine communicating all of that in just a few seconds.
That’s the power of a well-crafted SaaS explainer video.
It’s not just about making things move or creating eye-catching visuals. It’s about turning complex ideas into simple, engaging stories.
A confusing workflow becomes a seamless visual journey. Abstract technology becomes something people can actually see and understand. And a list of features becomes a story that shows people why your product matters.
Because great SaaS videos don’t just explain what your product does. They make people understand why they need it.
And that’s what makes them captivating.
Want to take your product to the next level?
Let’s turn your product’s story into something people stop, watch and remember.
Get in touch with us!
agfx.studio
I fix messy HubSpot portals and build the automations that keep them clean.
My path here wasn't a straight line: preschool teacher, then BDR, then leading a BD team, then enablement, and now RevOps. Every one of those jobs taught me the same thing. A system only works when the people using it understand it.
That's how I approach HubSpot work. Before I build anything, I want to know how your team actually sells, where the data stops being trustworthy, and who gets stuck when something breaks.
A few recent results:
• A 2-week portal audit that surfaced 296 unused properties and a prioritized fix list
• A lifecycle-stage bug found and fixed, correcting 128 contact records
• Location values cleaned up from 600+ variations down to 0
What I help with:
HubSpot cleanup: dedupe, property rebuilds, data hygiene