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
Back to feedPost
A slow SaaS product isn’t always caused by slow code.
Often the real issue is the full request path: inefficient queries, too many round trips, large payloads, duplicate frontend requests, or unnecessary processing.
I approach performance work by measuring each layer first, then fixing the actual bottleneck instead of guessing.
If your app works correctly but starts feeling slower as users and data grow, that’s the kind of problem I enjoy solving.
#SaaS #FullStack #BackendEngineering #Performance #SoftwareEngineering
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
Challenges
View all
Related posts
SaaS Explainer Video — AI-Native Software Engineering.
A cinematic SaaS explainer created to communicate a simple business message: AI can build an app, but building software that works reliably for a real business takes much more.
The video combines an AI presenter, product interface visuals, technical environments, and cinematic storytelling to explain the difference between a quick AI prototype and production-ready software.
The goal was to make a technical SaaS product feel clear, modern, credible, and easy to understand while keeping the story engaging from beginning to end.
Tools & techniques: AI video generation, AI visuals, product visualization, cinematic storytelling, motion design
AI ArtAI Content CreationGoogle FlowGoogle LabsRunwayaivideoproductionaiartistaivideoproducerAI Video Production
the saas shot is clean.
Too many thoughts , Keyframes, Layers.....Build Up Saas Motion graphics... a glimpse of our upcoming Saas demo 🚀
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.