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
Nudge is an AI powered workspace collaboration platform and Founder's OS designed for software teams and product owners to manage the entire lifecycle from idea to market.
It unifies real time team communication, task management, live video calling, and GitHub telemetry with an autonomous AI engine that proactively detects project bottlenecks and keeps teams shipping on schedule.
Key Technical Highlights:
Frontend & UX: Built a real-time multi tenant workspace using Next.js, React, TypeScript, Tailwind CSS, and Framer Motion.
AI Engine: Developed an autonomous background agent system using Python (FastAPI) and LangChain for real-time task stall detection and predictive nudges.
Real-Time Infrastructure: Integrated Supabase Realtime for instant messaging/presence and LiveKit for embedded WebRTC video conferencing.
Integrations & Cross-Platform: Implemented deep GitHub API integration for commit/PR tracking, VAPID Web Push notifications, PWA installability
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
What I love about AI is the creative freedom it offers. In the past, we were limited by budget or resources. Today, if I want a scene featuring a pink convertible, I don't necessarily have to rent one, just the right prompt, and it's done. I can create campaigns all over the world without leaving my workspace, and that’s what’s amazing.
pretty visual
Recent work for Avallon AI, a YC-backed startup building AI infrastructure for hospitality.
The challenge was explaining a technical product in a way that feels clear to hotel operators, partners and technical teams.
The website was structured around the product story, core capabilities, use cases and proof. Each section helps visitors understand what Avallon does, where it fits and why it matters.
Framer was used to move quickly while giving the team full control after launch. Reusable components and CMS collections make it easier to publish new content, expand the website and keep everything consistent.
The scope included:
• Website design
• Framer development
• Responsive layouts
• CMS architecture
• Custom code
• SEO setup
• Analytics and conversion tracking
The result is a clearer product story and a flexible marketing system that can grow with the company.
Full case study on my profile.
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.