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
Approval-aware browser automation
A technical article showing how to separate preparation from consequential actions, handle credentials, make retries safe and verify external results at the authoritative layer.
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
Just deployed a waitlist for my upcoming product Crank. It's what I like to claim as the ultimate developer tool. Well not just for devs ofcourse.
Imagine an AI Harness that can reshape itself to your needs!
Are you a video editor? Are you a frontend dev? Maybe you're a trader? or do you you just want an AI harness to run as your server and autofix issues when an error occurs?
And if that doesnt sell you, it uses 64% less tokens than other harnesses, generates clean uncluttered code. its coding strictly forbids cutting corners or generating any slop.
Join the Waitlist HERE
ROSIF-HEX: An all-in-one Engineering tool.
This is an engineering software I built for a shell-and-tube heat exchanger operations and analysis used in the oil & gas industry, food industry, derived from the principles of thermodynamics, hydraulic performance, heat transfer, mathematical modelling, optimization, and simulation.
It calculates the outlet temperatures of the hot and cold stream with other output parameters and runs 50 iterations for the Pareto solution, the thermal & hydraulic performance with hand calculation and gives tables and plots - thereby eliminating the need of navigating different softwares.
It also does inverse calculation of desired outlet temperature of any fluid stream which is suitable in the design, fabrication, and optimization of the exchanger.
I can build your software or tool, I can compute your manual tasks and operations into autonomous software systems.
The side-by-side published-reference vs model-calculated table with a %deviation column is what makes this trustworthy for an engineer - you can see exactly how far off the simulation runs before you rely on it.
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.