DEV Community: Jayesh somani

A Shark Tank Startup Didn't Pay a Freelancer. What Happened on the Recorded Call Is Every Freelancer's Nightmare.

Jayesh somani — Mon, 09 Mar 2026 16:23:21 +0000

This story isn't mine. But it could be any freelancer's.

A motion designer took on a project with a startup that had appeared on Shark Tank India. Reputable brand. Real company. Standard payment terms — 50% upfront, 50% after delivery. The kind of setup every freelancer uses.

He delivered everything. Fully documented. 100% complete.

Then the startup did what startups sometimes do when they don't want to pay.

They changed the story.

The work was suddenly "incomplete." The same deliverables that had been received without complaint were now apparently not good enough. And then came the moves every freelancer recognises immediately — ghosting, delays, being redirected to someone else, then someone else again.

He chased the payment for months. Followed up politely. Sent emails. Made calls. Did everything you're supposed to do.

Eventually he gave up for his own mental peace. Seven months passed.

Then something unexpected happened.

He was accidentally added to an internal strategy call the startup was running for another freelancer. The CEO was on the call.

He thought — this is my chance. The CEO is right here. I'll just ask.

The moment he started speaking about the pending payment, the CEO instantly left the call. Then the person he had been dealing with directly started verbally abusing him. Then left too.

The entire thing was on a recorded call.

This isn't an isolated story.

When I posted one question on Reddit asking freelancers how they protect themselves from payment ghosting, 3,200 people read it in 4 days. 58 comments. Every single one had a version of the same story.

Delivered the work. Client disappeared. Zero leverage because the files were already sent.

The advice in the comments was always the same — get paid upfront, use contracts, take deposits, follow up professionally. All valid. All things the motion designer in this story did.

And none of it protected him.

The real problem isn't behaviour. It's structure.

Contracts tell a client what they should do. They don't stop a client from ghosting. A well-worded invoice doesn't prevent someone from leaving a call the moment you ask about payment.

The only thing that changes the dynamic structurally is leverage. And the only leverage a freelancer has is the deliverable itself — before it's been handed over.

Once the files are sent, the leverage is gone. Everything after that is chasing.

The fix isn't a better contract template. It's a system where the files never leave until the payment clears. Not as a punishment. Not as a trust issue. Just as how the project works — agreed upfront by both sides.

No awkward follow-up emails. No recorded call confrontations. No seven months of mental load. Just a clean handover that happens automatically when payment clears.

That's what I'm building at klovio.co.

Files lock behind payment and unlock automatically when the client pays. The freelancer doesn't have to chase, follow up, or confront anyone. The system handles it.

I'm still in the early stages — waitlist open, product in development. But stories like this one are exactly why I'm building it.

If you're a freelancer who has been through something similar — I'd love to hear your story. And if you want to be protected from this the next time, the waitlist is at klovio.co.

Because nobody should have to join a strategy call just to ask for money they already earned.

I Asked Reddit One Question. 3,200 Freelancers Responded. Here's What I Built.

Jayesh somani — Mon, 02 Mar 2026 04:40:54 +0000

A story about validating a SaaS idea the right way — before writing a single line of product code.

It Started With a Simple Observation

I kept hearing the same story from freelancer friends.

Deliver the work. Client says "looks great, will pay Friday." Friday comes. Silence. Follow up. More silence. Three weeks pass. The freelancer has zero leverage because they already handed everything over.

I wanted to know if this was a widespread problem or just bad luck.

So I posted on Reddit.

The Post

I went to r/Freelancers and asked one question:

"Sent final files to a client, they went silent for 3 weeks. How do you protect yourself from this?"

I wasn't pitching anything. I wasn't promoting a product. I genuinely wanted to understand how freelancers deal with this.

What happened next surprised me.

3,200 Views. 58 Comments. Same Story Every Time.

Within 48 hours the post had 3,200 views and 58 comments from freelancers with anywhere from 2 to 30 years of experience.

The comments came from the US, India, UK, Pakistan, and dozens of other countries.

And almost every single one told the exact same story.

"Sent files. Client said will pay Friday. That was 3 weeks ago."

The advice in the comments was predictable — get paid upfront, use contracts, take deposits. All valid. All things freelancers already know.

But nobody had a tool that actually enforced any of it automatically.

The 3 Problems That Kept Appearing

Reading through all 58 comments carefully, three core problems came up again and again:

Problem 1 — Files delivered before payment = zero leverage

The moment you hand over the final work, your leverage disappears completely. You're no longer negotiating — you're begging. Every experienced freelancer in the thread knew this but had no structural solution beyond hoping clients pay.

Problem 2 — Manual follow-ups are exhausting and awkward

One commenter said they spent 2 hours in a single week just writing follow-up emails. Not doing client work. Not building their business. Just writing politely worded versions of "please pay me for work I already did."

The emotional labour of staying professional while chasing payment is something nobody talks about openly. It drains freelancers in ways that don't show up in any invoice.

Problem 3 — Proposals take too long

Multiple freelancers mentioned spending 2-3 hours writing proposals that never get accepted. High rejection rates mean hours of work with zero compensation. No standardized format, no AI assistance, starting from scratch every single time.

What I Decided to Build

The insight from the thread was clear.

The problem isn't that freelancers don't know what to do. They know — get paid before delivering, follow up systematically, write better proposals.

The problem is that the right behaviour requires constant discipline and manual effort across every single project. The moment you get busy or distracted, the system breaks.

What freelancers needed wasn't advice. They needed infrastructure.

So I started building Klovio.

The core idea is simple:

Files lock behind payment automatically. Client pays → files unlock. No payment → no access. No willpower required.
AI generates proposals from your meeting transcript in 30 seconds. Paste your Zoom transcript, get a full professional proposal.
Automated follow-ups that stop the moment the client pays. Never write another "just checking in" email.

What Happened After I Validated

Armed with real validation from 3,200 freelancers I did a few things:

Built a landing page first, not a product.

klovio.co went live within a week of the Reddit post. No product yet — just a clear explanation of what we're building and a waitlist form.

Got feedback from a real founder.

A verified founder with 1,800 followers on Twitter reviewed the landing page and gave me detailed honest feedback — missing privacy policy, unclear messaging, email going to Promotions. All fixable. All valuable before spending weeks building the wrong thing.

Started building in public.

Every day I post an update on what I'm building, what I learned, what broke. Not to show off. To stay accountable and to keep the feedback loop open.

What I Learned About Validation

A lot of first-time founders skip this step. They have an idea, they think it's good, they build for 3 months, they launch to silence.

The Reddit thread took me one afternoon. 3,200 people read it. 58 people responded with detailed personal experiences confirming the problem exists and is painful.

That one afternoon potentially saved me months of building the wrong thing.

The best validation is when people describe your product to you before you've told them it exists.

Multiple commenters in that thread said things like "someone should build a system where files literally can't be accessed until payment clears." That's exactly what Klovio does. I didn't plant that idea — they arrived at it independently because it's the logical solution to the problem.

That's when you know you're onto something real.

Where I Am Now

Day 5 of building in public.

✅ Landing page live at klovio.co
✅ Email collection working
✅ Privacy policy, terms, cookie compliance done
✅ Google Search Console set up
❌ 0 organic waitlist signups yet
🔨 MVP development starting soon

The 0 signups doesn't worry me. The Reddit validation does the job of confirming the problem is real. Now the work is getting the solution in front of the right people.

The Stack (For the Technical Readers)

When I do build the product:

Frontend: Next.js on Vercel
Auth: AWS Cognito
Database: AWS RDS PostgreSQL
File Storage: AWS S3 + CloudFront
Payments: Stripe Connect + Razorpay
AI: OpenAI GPT-4o
Email: AWS SES
Scheduling: Cal.com (self-hosted)

The file delivery flow specifically:

Freelancer uploads file → stored in private S3 bucket
Invoice sent to client
Client pays via Stripe
Webhook fires → Lambda confirms payment
S3 presigned URL generated via CloudFront
Client receives download link (expires 48 hours)
File auto-deletes after 30 days

Simple. Enforceable. Automatic every time.

If You're a Freelancer

The waitlist is open at klovio.co

Early members get:

First access before public launch
3 months free Pro plan
Direct input into what we build first

If You're a Founder

The lesson here isn't about Klovio specifically. It's about the value of talking to real people before building anything.

One Reddit post. One afternoon. 3,200 data points.

That's the cheapest market research you'll ever do.

Building Klovio in public — follow along on Twitter @Jayesh_Somani_

Questions or feedback? I read every message — jayesh@klovio.co