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
SupportLab is a comprehensive platform that empowers businesses to build, deploy, and manage intelligent AI voice agents. It acts as an automated, real-time support desk that handles customer phone calls, seamlessly queries internal knowledge bases, and resolves complex issues instantly without human intervention.
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
Here's exactly what it looks like to work with me 👇
Hiring someone you've never worked with is a leap of faith... and honestly, most "hire me" posts don't help. They tell you what someone offers, not how it actually goes. So let me close that gap.
Before we even start: a quick discovery conversation
No commitment, no pressure. We talk through what's actually eating your time, what "support" would ideally look like for you, and whether I'm the right fit. If I'm not, I'll tell you and probably point you somewhere better.
Week one: I get the lay of the land
This isn't me disappearing into a task list. I ask questions about your tools, your workflow, your pet peeves, the thing you keep meaning to fix but haven't had time for. By the end of week one, I've usually already spotted at least one small inefficiency worth flagging.
Ongoing: communication that doesn't require babysitting
You'll get regular updates on what's moving, what's done, and what needs your input on a cadence we agree on upfront (daily check-in, weekly summary, whatever actually fits how you work). No mystery. No "what has she even been doing" moments.
What "done" looks like
Done means the task is complete and handed back in a way you can actually use labeled, organized, explained if needed. I don't consider something finished just because it's off my plate; it's finished when it's usable on yours.
The honest part: I'm not going to pretend every project is flawless from day one. Systems get refined. But refinement happens through clear communication, not radio silence and that's the part I take seriously.
If the biggest thing holding you back from hiring support is "but what am I actually getting into?" hopefully this answers it.
💬 Got a question about how this would work for your specific situation? Ask. I'd rather answer it now than have it be the reason you don't reach out.
: Hi everyone!
AI Lead Qualifier — chat agent that qualifies leads before your manager picks up the phone.
THE PROBLEM
78% of buyers choose the vendor who answers first. Most inbound leads wait hours for a human.
THE SOLUTION
An AI agent answering every lead within seconds, 24/7: short dialog → structured data (need, budget, timeline, contact) → A/B/C grade → instant Telegram alert with a full lead card. Everything logged to Google Sheets.
BUSINESS IMPACT
• Response in seconds, not hours
• 50–70% of routine questions off your sales team
• Structured lead card for every inquiry
• Self-hosted — no monthly SaaS fees
PROVEN IN A LIVE TEST
From "can you make a website for my store?" the agent extracted need, timeline, budget, name and phone in 2 messages, scored the lead class A, and alerted the manager — automatically.
Built on n8n + LLM + Telegram. Details in my profile — DM me.
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.