4
5 Comments

I've had a working product for months. This is week 1 of actually trying to sell it.

Lintract has been live for months. $12 AI contract reviewer, no subscription, no signup. The product works.

What I didn't do: sell it. I kept "improving" it instead.
This week I forced myself to stop building and start distributing. 1 hour/day, 30 days, no new features.
Week 1 numbers:

20 cold emails to staffing agencies → 0 replies so far
3 Reddit replies (r/digitalnomad, r/FreelanceIndia) → some upvotes
1 tweet → expected silence (new account)
1 IH post → 1 real comment

No sales yet. But for the first time I'm actually talking to people about it instead of hiding behind the code.
The hardest part wasn't the emails. It was accepting the product is good enough to sell.
lintract.com

on June 5, 2026
  1. 1

    The 30 day rule is solid. I would add one constraint: every outreach message should test a different buyer anxiety, not just a different channel. For Lintract that might be contractor risk, freelancer payment terms, client liability, or “is this clause normal?” pain. Then judge replies by which anxiety gets people to explain their situation back to you.

  2. 1

    This hits hard.

    I had a very similar trap: I kept treating “improving the product” as progress, but the only moments that actually moved the needle came from distribution.

    In my case, a couple of community posts drove the only real sales I got. Then traffic went back to zero because I had no repeatable channel.

    Your “1 hour/day, 30 days, no new features” constraint is probably the right move. I’m starting to think distribution has to become part of the product routine, not a launch event.

    Curious: after week 1, are you planning to double down on cold email, or test one channel at a time until something replies?

  3. 1

    Hi Gino, I'm in a similar situation, a production-ready product struggling to get an audience. I checked out your site lintract.com - looks good! I got some ideas for you...

    Have you ever search a car VIN number online? You start by checking, then you get "we found xx many records on this car" a teaser, and then after the site have made you curious enough by confirm that it has valuable information about that vehicle, it introduce the price and the checkout for the full report. Annoying as hell, but it works.

    Another idea that might be of interest; whats expected in a rental contract vs an employment contract vs a freelancer contract is not the same. You can use this to your advantage to build trust - Organize contracts into categories. Instead of keeping the customer in the dark, just saying that you going to sprinkle som AI on it, call out that the customers contract is checked for abnormalities against xxxx number of contracts within the same category. This would probably be a good confidence boost for your systems conclusion, and any customer who actually want to challenge the findings. The best of luck to you and your product Gino!

  4. 1

    One thing I'd be careful with:

    20 emails and 0 replies may not be a volume problem yet. It may be a framing problem.

    A staffing agency probably doesn't care that Lintract reviews contracts with AI.

    They care about avoiding signing something that creates client, contractor, or margin risk.

    That's a different conversation.

    The reason I mention it is that a lot of founders start optimizing outreach volume before they've pressure-tested whether the first message is selling the right pain.

    Happy to put the outreach angle in writing if useful. I think the bigger risk right now is collecting data from the wrong message.

    1. 1

      You're right, and this is exactly the kind of feedback I needed.
      The current email leads with the product. A staffing agency doesn't wake up thinking "I need an AI contract reviewer", they wake up thinking "I hope none of our contractors sign something that blows up a client relationship."
      Would love your take on the framing. The core insight I'm working with: staffing agencies place contractors who sign client agreements without anyone reviewing them. One bad clause becomes the agency's problem when the contractor comes back angry.
      Thanks for the answer brother!

Trending on Indie Hackers
Your build-in-public audience is not your market. I learned the difference the slow way. User Avatar 257 comments Most founders don't have a product problem. They have a visibility problem User Avatar 59 comments Day 4: Why I Built a $199 Workspace Nobody Asked For User Avatar 39 comments How to automatically turn customer feedback into high-converting testimonials User Avatar 39 comments Built a "stocks as football cards" thing. 5 days in, my launch tweet got 7 views. What am I missing? User Avatar 34 comments Spent months building LazyEats AI. Spent 1 day realizing I have no idea how to get users. User Avatar 29 comments