2
3 Comments

I turned "just one small thing" into a problem I could actually price — so I built a fix

Backstory: I went looking at what's actually costing freelancers and small agencies money, and two things kept showing up — scope creep (57% of agencies lose $1,000-$5,000/month to unbilled extra work, and 78% say they rarely or only sometimes charge for it at all — Ignition's 2025 Agency Pricing & Cash Flow Report) and non-payment (62% of surveyed NY freelancers have been stiffed at least once, 53% of those for $10k+ — Freelancers Union/Authors Guild, May 2022).

The pattern in the actual complaints (Hacker News, G2/Capterra reviews, freelancer interviews) wasn't "I don't have a contract" — it was "my contract doesn't have the specific clause that would've stopped this." No scope-lock clause. No change-order process. No late-fee clause with real teeth. No deposit ask, or no script for how to ask for one without it feeling awkward.

So I built Scope Lock: 15 fill-in-the-blank contracts with those clauses already in them, 23 scripts for the actual conversations, a pricing calculator, and a non-payment recovery kit. $67-$397 depending on tier (Starter/Pro/Premium), 30-day refund, one-time payment.

Genuinely curious from this crowd: if you freelance or run a small shop, does this match what's actually happened to you, or is the real pain somewhere else in the process? I'd rather know now than find out from a refund request.

https://baibhab3.gumroad.com/l/scope-lock?utm_source=indiehackers&utm_medium=post&utm_campaign=launch

on August 10, 2026
  1. 1

    The part that stands out to me is that scope creep rarely announces itself. It shows up as a handful of small favors nobody writes down anywhere, and by the time someone notices the pattern there is no clean record showing when it actually started. Does Scope Lock help people catch that drift while it is happening, or is it mainly the language you fall back on later when a client pushes back on the invoice?

  2. 1

    The insight that lands here is that you didn't just identify "freelancers are getting ripped off" - you measured it. 78% don't charge for extra work. 62% have been stiffed. That specificity is everything.

    Once you can measure a problem that specifically - "this exact percentage loses this exact amount" - it becomes priceable. It goes from "I feel frustrated" to "I know what I'm losing" and from there to "I'd pay to fix this."

    But the leverage is deeper: you then measured where the friction actually lives. Not "contracts are bad" but "contracts are missing these three specific clauses." Not "people avoid negotiation" but "people don't have scripts for how to ask without it feeling awkward."

    That's why the product works. You didn't build a contract template (thousands exist). You built a measurement system that lets someone see exactly where they're leaking money, then gave them the specific tools to stop that leak.

    Most founders measure "do people want this" and get feedback that's too vague to be useful. You measured "what specifically keeps losing them money" and got a measurement system you could price directly.

  3. 1

    The “my contract doesn’t have the specific clause that would’ve stopped this” pattern is interesting. I’d be curious whether the bigger problem is actually knowing what to put in the contract, or getting clients to follow the process once the work starts.

Trending on Indie Hackers
Co-founders suck… User Avatar 82 comments I built an AI that finds the right product for your customers User Avatar 45 comments I built a tool to find people already talking about problems your product solves User Avatar 34 comments The easiest version of generation history was probably the least useful one User Avatar 32 comments What 100B+ Claude tokens actually look like inside a tiny company User Avatar 24 comments 4 months to go. Chrome extension live. Web search integrated. 4 users. $0 revenue. Still here. User Avatar 15 comments