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.

Good feedback needs a location. A decision needs a version.

I built FrameProof to bring both into one image-review workspace for designers and small creative teams.

Pin feedback directly on the artwork, keep replies beside the detail, compare revisions and record a decision on the exact version being reviewed. Private projects and expiring guest links keep the sharing workflow focused.

The design stays deliberately quiet: warm neutrals, a restrained terracotta accent and an uncropped canvas that gives the work room to breathe. Underneath it, React, TypeScript and Supabase handle the application, roles and private storage. Built with Bolt, then refined through focused engineering and testing.

The narrated walkthrough shows the complete workflow. The demo uses fictional artwork, so you can explore without uploading client files.

Case study: https://contra.com/p/UY3B7obe-frame-proof-visual-feedback-and-version-approval

Source kit ($99): https://contra.com/products/mHxtVfQw-frame-proof-or-visual-review-source-kit

What causes more friction in your review process: scattered comments or uncertainty about the final version?