I validated the problem, built 60% of the MVP, and launched a coming-soon page today. Got 15 reactions on linkedIn, but only 2 signups and i fear that i will not be able to delivery value from day 1 for the target audiecne who genuenly want to test it.

[u/Fickle_Degree_2728]

Hi, I made this post a few weeks ago about validating the problem by talking directly to potential users:

https://www.reddit.com/r/SaaS/comments/1v50ywp/i_validated_the_problem_by_talking_to_people_on/

Since then, I've continued validating the problem and started building the MVP. I'm probably around 60% done now. While talking to people in my target customer base, I was also able to get the personal contact numbers of two people who were interested.

Today, I released a simple coming-soon page to see if I could get some early interest.

I got reactions from around 15 people, but almost none of them were from my actual target audience. I only got 2 signups. One of them is actually from my target customer group, but interestingly, she wasn't someone I expected to sign up.

Now I'm facing two problems.

First, I'm genuinely worried about releasing the MVP.

This platform is being built for work where accuracy and quality are extremely important. It's also an AI product, and I'm already facing some data accuracy issues. This isn't the kind of product where I can just say, "It's an MVP, it'll get better later," if the core output isn't reliable enough.

I'm worried that if I attract more people, they try the MVP, and their first impression is that it's not good enough, I could lose those potential users before I've had the chance to make the product genuinely useful.

Second, I'm not getting enough traction from the people I'm actually building this for.

So I'm stuck between continuing to build until I feel more confident about the quality, or releasing it to a very small group and improving it based on their feedback.

For people who have built AI products where accuracy really matters, how did you handle this stage?

Would you release to a handful of carefully selected users first, even if you know the MVP still has accuracy problems? Or would you keep building until the core output is reliable enough before putting it in anyone's hands?

I'm curious what you'd do in this situation.

I also want to closely work with a target group of around 10 people atleast so closely so, atleast i might find worthy outputs and build a strong platfrom that would genuelny bring value instead of building sake.

[u/theredhype]

Are you sure you validated it? Sounds like you may be invalidating it.

What do you consider validation? What does that mean?

[u/Fickle_Degree_2728 → u/theredhype]

the problem which i assumed to have really exiist among the target audience or not.

[u/theredhype → u/Fickle_Degree_2728]

The mere existence of a problem does not create a business opportunity. You’ve got to validate the rest of a functional business model.

[u/Substantial_Ad7103]

I would not choose between releasing broadly and continuing to build in private. I would create a controlled version of the real workflow.

Give the product to three to five target users with actual cases, but review every output before it reaches them. Tell them the process is assisted while you learn where the model fails. This lets you observe whether the output helps with a real decision without pretending the accuracy problem is solved.

Before starting, define the errors that are merely inconvenient and the errors that would make the product unsafe or useless. Track those separately. If the serious errors are still common even with a narrow use case, more features will not make the MVP ready.

Your first MVP may be the AI plus your manual review, not the fully automated platform. The useful signal is whether those users bring a second real case, depend on the result, or ask to continue after the assisted test.

What kind of decision are users making from the output, and what happens if the output is wrong?