What happened after my AI contract tool post got 70+ comments
A few days ago I shared my project VIDI here - an AI tool that helps small businesses understand contracts before signing.
I honestly didn't expect the post to get so much attention.
The discussion reached 70+ comments, and I tried to reply to almost every one because the feedback from founders and builders was incredibly thoughtful.
People shared ideas about positioning, pricing, trust, and product direction.
Here’s what happened after that discussion:
• The product passed 2,000+ organic visitors
• New users started uploading real contracts to test the system
• Some early users are continuing to use the product to analyze agreements
• I had conversations with founders about how they currently review contracts
One interesting insight: many small business owners don’t think in terms of “contract analysis.”
They think in terms of:
“Am I about to sign something that could cost me money later?”
That insight alone is already helping me rethink how I explain the product.
Still very early, but discussions like this are incredibly valuable when building a product from scratch.
If anyone wants to test the product or share feedback, here is the link:
https://joyful-granita-8415bc.netlify.app
Curious to hear from others building for SMBs - what was the hardest part of earning user trust early on?
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
This kind of follow-through transparency is rare and valuable. Most people post the launch, disappear, and come back when they have a success story. The gap between the comments post and the outcome post is where the real work happens and almost nobody documents it.
The thing that stands out about the 70-comment thread outcome: community engagement is not the same as product-market fit, even when the engagement is very high. People who comment enthusiastically on a concept are often not the same people who buy. Comments tend to come from builders who find the idea interesting - buyers tend to lurk or find you through search. Conflating the two is one of the most common early mistakes I see.
Curious what the conversion rate looked like from commenters specifically - did any of the people who commented in the original thread actually buy? And what did the buyers who did convert look like compared to the people who engaged with the post?
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
that reframing insight is gold, honestly. going from "contract analysis" to "am i about to sign something that'll cost me later" is the difference between a feature description and a pain point. i'm building an AI tool in the ads space right now and had a similar moment, i kept saying "ad optimization" but what people actually wanted was "stop wasting money on ads that don't convert." completely changed how i talk about it. how are you handling the trust factor with people uploading real contracts to an AI though?
That's a great point.
Trust is definitely one of the biggest challenges when asking people to upload real contracts.
Right now I'm trying to keep the experience very transparent - explaining clearly what the system analyzes and focusing on helping users understand risks rather than replacing lawyers.
Also starting with early adopters (founders and small business owners) who are curious about testing new tools helps a lot.
Still experimenting and learning from each user interaction.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The reframe from 'contract analysis' to 'am I about to sign something that could cost me money' is exactly the right move — outcome language vs. mechanism language.
On earning SMB trust early: the thing that accelerates it is showing you understand the specific financial exposure they're trying to avoid. SMBs don't buy features; they buy protection from a known bad outcome.
Slightly tangential but relevant to your journey: the 2000+ visitors and real contract uploads are a strong signal. Once you have paying users, one thing worth setting up proactively is automated recovery for failed Stripe payments. SMBs often have outdated cards, and at your early stage losing one customer to a failed payment stings more than it does at scale. A Day1/Day3/Day7 email sequence via tryrecoverkit.com/connect handles this automatically — worth setting up once before you need it.
Congrats on the organic traction — the founders-discussing-your-product-before-you-ask-them-to dynamic is hard to manufacture.
Appreciate the thoughtful feedback.
Framing it around the financial risk someone might be taking before signing definitely seems to resonate more with founders than technical descriptions of contract analysis.
And thanks for the tip as well - right now the main focus is learning from early users and improving the core workflow, but it’s helpful to keep those things in mind as the product grows.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The gap between engagement and conversion is one of the most disorienting things in early-stage distribution. High-comment posts create the feeling that you are solving a real problem - and you probably are - but comments measure curiosity, not purchase intent.
The question that matters most after a high-engagement post: how many of those commenters ended up on your site, and how many of those took any action? If you have analytics you can segment it.
My guess at the conversion pattern: the people who comment are often evaluating from a distance. The people who buy without commenting are the ones who immediately recognized the problem because they are actively feeling it right now. The 70-comment crowd might skew toward "interesting, might need this eventually" vs "I need this today."
The follow-up move that tends to work after a viral post: a direct outreach to the commenters who asked specific questions or described a specific problem. Not a pitch - a genuine "you mentioned X, I built Y to solve it, would you test it?" The conversion rate on that is usually much higher than the organic rate from the post.
What was the outcome in terms of signups or trials? Curious whether the engagement translated at all.
The gap between engagement and conversion is one of the most disorienting things in early-stage distribution. High-comment posts create the feeling that you are solving a real problem - and you probably are - but comments measure curiosity, not purchase intent.
The question that matters most after a high-engagement post: how many of those commenters ended up on your site, and how many of those took any action? If you have analytics you can segment it.
My guess at the conversion pattern: the people who comment are often evaluating from a distance. The people who buy without commenting are the ones who immediately recognized the problem because they are actively feeling it right now. The 70-comment crowd might skew toward "interesting, might need this eventually" vs "I need this today."
The follow-up move that tends to work after a viral post: a direct outreach to the commenters who asked specific questions or described a specific problem. Not a pitch - a genuine "you mentioned X, I built Y to solve it, would you test it?" The conversion rate on that is usually much higher than the organic rate from the post.
What was the outcome in terms of signups or trials? Curious whether the engagement translated at all.
The gap between engagement and conversion is one of the most disorienting things in early-stage distribution. High-comment posts create the feeling that you are solving a real problem - and you probably are - but comments measure curiosity, not purchase intent.
The question that matters most after a high-engagement post: how many of those commenters ended up on your site, and how many of those took any action? If you have analytics you can segment it.
My guess at the conversion pattern: the people who comment are often evaluating from a distance. The people who buy without commenting are the ones who immediately recognized the problem because they are actively feeling it right now. The 70-comment crowd might skew toward "interesting, might need this eventually" vs "I need this today."
The follow-up move that tends to work after a viral post: a direct outreach to the commenters who asked specific questions or described a specific problem. Not a pitch - a genuine "you mentioned X, I built Y to solve it, would you test it?" The conversion rate on that is usually much higher than the organic rate from the post.
What was the outcome in terms of signups or trials? Curious whether the engagement translated at all.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The gap between engagement and conversion is one of the most disorienting things in early-stage distribution. High-comment posts create the feeling that you are solving a real problem - and you probably are - but comments measure curiosity, not purchase intent.
The question that matters most after a high-engagement post: how many of those commenters ended up on your site, and how many of those took any action? If you have analytics you can segment it.
My guess at the conversion pattern: the people who comment are often evaluating from a distance. The people who buy without commenting are the ones who immediately recognized the problem because they are actively feeling it right now. The 70-comment crowd might skew toward "interesting, might need this eventually" vs "I need this today."
The follow-up move that tends to work after a viral post: a direct outreach to the commenters who asked specific questions or described a specific problem. Not a pitch - a genuine "you mentioned X, I built Y to solve it, would you test it?" The conversion rate on that is usually much higher than the organic rate from the post.
What was the outcome in terms of signups or trials? Curious whether the engagement translated at all.
Good point.
Some people from the thread did visit the site and a few uploaded real contracts to test the tool.
I'm mainly using these discussions to understand how founders currently review agreements and what problems come up most often.
Still early, but the feedback and real usage signals have been very helpful.
Also appreciate the discussion here - I'll try to keep the thread focused and avoid too many repeated comments so it's easier for others to follow.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
Hey, it looks like you're posting many repeated comments under my posts. Please avoid spamming the thread so the discussion stays useful for everyone.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
Hey, it looks like you're posting many repeated comments under my posts. Please avoid spamming the thread so the discussion stays useful for everyone.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
Hey, it looks like you're posting many repeated comments under my posts. Please avoid spamming the thread so the discussion stays useful for everyone.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
One-time pricing for software gets an unfair reputation as a sign of low quality.
The actual reason to offer it: recurring pricing requires you to justify the subscription every month. One-time requires you to justify it once. If your software solves a stable problem with stable code and doesn't require ongoing data feeds or infrastructure - one-time is simpler for everyone.
The trust signal that makes it work: be specific about what updates are included. "Bug fixes, yes. New tools, no." Ambiguity is what erodes trust in one-time pricing, not the model itself.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
One-time pricing for software gets an unfair reputation as a sign of low quality.
The actual reason to offer it: recurring pricing requires you to justify the subscription every month. One-time requires you to justify it once. If your software solves a stable problem with stable code and doesn't require ongoing data feeds or infrastructure - one-time is simpler for everyone.
The trust signal that makes it work: be specific about what updates are included. "Bug fixes, yes. New tools, no." Ambiguity is what erodes trust in one-time pricing, not the model itself.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
One-time pricing for software gets an unfair reputation as a sign of low quality.
The actual reason to offer it: recurring pricing requires you to justify the subscription every month. One-time requires you to justify it once. If your software solves a stable problem with stable code and doesn't require ongoing data feeds or infrastructure - one-time is simpler for everyone.
The trust signal that makes it work: be specific about what updates are included. "Bug fixes, yes. New tools, no." Ambiguity is what erodes trust in one-time pricing, not the model itself.
One-time pricing for software gets an unfair reputation as a sign of low quality.
The actual reason to offer it: recurring pricing requires you to justify the subscription every month. One-time requires you to justify it once. If your software solves a stable problem with stable code and doesn't require ongoing data feeds or infrastructure - one-time is simpler for everyone.
The trust signal that makes it work: be specific about what updates are included. "Bug fixes, yes. New tools, no." Ambiguity is what erodes trust in one-time pricing, not the model itself.
Interesting perspective. VIDI is still very early, so right now the focus is mainly on learning from real contracts and user feedback before thinking about pricing models.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
That's a great point. It's still very early, so I'm mostly focused on learning from the first users testing the product and seeing which types of businesses find it most useful. As more contracts go through the system, I expect clearer patterns to emerge.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
Interesting perspective, thanks for sharing.
This is exactly the kind of focused, single-purpose tool I love. Did you consider monetizing from day one or keeping it free to grow first?
Right now the main focus is learning from early users and improving the product. Monetization is something I'll explore later once the core workflow and use cases are clearer.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
Interesting perspective, thanks for sharing.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
Interesting perspective, thanks for sharing.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
That's a good point. Filtering feedback and focusing on what actually matters for users is definitely important.
Productized services are interesting because they solve the discovery problem that pure SaaS has at the start.
With SaaS, someone has to find your product, understand what it does, trust it enough to try it, and then convert. With productized services, you can sell the outcome directly in a conversation and fulfill with software.
The unlock: use the service as distribution for the software. Every service client is a potential SaaS conversion if the software is good enough to replace the manual parts of what you're doing.
That's a good point. Filtering feedback and focusing on what actually matters for users is definitely important.
The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.
Once you have 20-30 customers you can look at patterns - same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.
What was the common thread across your early customers? That's usually the most useful thing to write down.
That's a great point.
It's still very early, so I'm mostly seeing people exploring the tool rather than a clear customer pattern yet. Most early users so far seem to be founders or small business owners who review contracts themselves.
I'm hoping that as more contracts get uploaded, it will become clearer which specific use cases show up most often.
The framing here is useful. The research layer before any outreach is what most people skip because it does not scale well manually. But it is where the ROI actually lives - a tight ICP plus context on each target outperforms volume every time.
That's a great point. Taking the time to understand the context around each founder or business can make outreach much more meaningful.
The trust problem with SMBs uploading real contracts has a specific shape: it's not that they don't trust AI, it's that they can't verify the output. A lawyer can check the lawyer's work. A founder can't check the AI's contract analysis.
The fastest way to build trust I've seen: give them one thing they can verify themselves in 30 seconds. If your tool says "this contract has a 90-day auto-renewal clause with 60-day notice required," the user can ctrl+F "auto-renew" and find it. That one verifiable hit makes everything else feel trustworthy.
The tools that fail trust with SMBs usually output conclusions without evidence. The ones that succeed show their work — here's the clause, here's why it matters, here's what it means for you. The explainability is the trust signal, not the accuracy score.
What format is your output in currently — summary, flagged clauses, or something else?
That's a really interesting point about verifiability.
Right now the output mainly focuses on highlighting specific clauses and explaining them in simpler language so users can quickly see where the risk might be in the contract.
I agree that showing the exact clause and context is important so users can verify it themselves.
The trust gap you're describing with SMBs is real. A big part of it is output consistency, users uploading similar contracts and getting different risk summaries each time makes them distrust the tool fast.
One thing that helped me with a similar problem: structuring the underlying prompt into explicit blocks (role, constraints, output format) rather than one flat instruction. Models produce more consistent output when the prompt shape is stable across runs, which matters a lot when you're analyzing different contract types against the same criteria.
I built flompt.dev for this kind of prompt iteration work, a visual builder that decomposes prompts into semantic blocks and compiles to Claude-optimized XML. Open-source: github.com/Nyrok/flompt
That's a really good point. Consistency in the output is definitely important, especially when users compare similar contracts.
I'm still experimenting with different ways to structure the analysis so the results stay reliable across different agreements.
Appreciate you sharing your experience.
That insight about users thinking “am I about to sign something that could cost me money later?” instead of “contract analysis” is really interesting.
It’s a great example of how founders often describe products in terms of features, while users frame the problem in terms of risk or outcomes.
Once the wording matches the user’s actual concern, the value becomes much easier to understand.
Curious if that realization changed how you’re positioning the product on the landing page.
That's a great point.
I haven't updated the landing page yet, but that insight definitely changed how I'm thinking about positioning the product.
Right now I'm experimenting with framing it more around helping founders understand potential risks before signing a contract.
Hello founders,
I represent a group of companies looking to invest in promising startups and scalable projects.
If your startup has growth potential, feel free to share a brief overview or message me directly.
+62 831-5298-7392
I think focusing on early users is the right move. The conversations you get at that stage usually shape the product far more than outside interest or investment offers.
Those early insights about how people actually describe the problem can completely change positioning.
Thanks for the interest. Right now I'm focused on learning from early users and improving the product.
2,000 organic visitors from a single post is a real signal — that's the community validating your positioning in real time.
The reframe you described is important: 'Am I about to sign something that could cost me money later?' is the actual job-to-be-done, not 'contract analysis.' That's the difference between feature-speak and outcome-speak, and it usually unlocks the right landing page copy.
On earning trust with SMBs: the fastest path is usually specificity. A tool that analyzes 'contracts' is abstract. A tool that specifically flags payment terms, auto-renewal clauses, and liability caps in vendor agreements is immediately legible. The more specific the contract type and the risk being surfaced, the more trustworthy the product feels — because the user can verify one claim in 60 seconds.
The question 'could this cost me money?' has a sharper version: 'What's the worst clause in this contract?' If your tool can answer that in one line, that's your trust moment.
That's a really insightful way to put it.
The idea of surfacing something like “the worst clause in this contract” is actually very close to how I'm starting to think about the product. Most users don't want a full legal breakdown - they just want to quickly understand if there's anything risky before they sign.
And your point about specificity makes a lot of sense. Instead of just saying “contract analysis,” it's much clearer when the tool highlights things like payment terms, auto-renewal clauses, liability exposure, or termination conditions. Those are the parts people immediately worry about.
I'm still learning a lot from the contracts people upload, but comments like this are really helpful in shaping how the product should communicate value.
Really interesting insight about how people frame the problem.
“Am I about to sign something that could cost me money later?” feels much more intuitive than “contract analysis.” It's a good reminder that users usually think in terms of risk or outcomes, not features.
I'm curious if the early users who uploaded real contracts were mostly founders or small business owners themselves, or if some were freelancers reviewing client agreements.
Also impressive to see 2k organic visitors from a single discussion. That shows there’s clearly curiosity around the problem.
That's a great point.
From what I’ve seen so far, it’s a mix. Some uploads seem to come from founders or small business owners reviewing vendor or partnership agreements, and some look like freelancers checking client contracts.
Interestingly, there are also a few users who started using the tool right after the launch and are still uploading contracts from time to time. And at the same time, new users are still discovering the Indie Hackers discussion and trying the product with their own agreements.
how many files in the limits?
Right now there is no strict limit on the number of files.
Users can upload multiple contracts and analyze them one by one. I'm still experimenting with limits as usage grows to keep the system stable.
The goal is to make it easy for small businesses to quickly review agreements whenever they need to.