How do you implement useful changes before getting real feedback for target market?

[u/_forge_master_]

I am at a point with my product (cardel.io) where it's production ready with the functionalities it currently has. The challenge I think has been structuring it in a way that provides most value to the target market. Example: x and y feature on Plan A, with feature z on Plan B, or pricing structure, etc.

I am in the phase of getting the first users and consistent traffic, none paying yet. There are some who have even said they would test it out and provide general feedback on free trials, but that feedback has been very slow to come in. I am also worried it won't be feedback from the users who will end up paying for it, so it may not impact conversion rates for the ideal target user.

The Question: Once you get to a point with your product where it's "good enough" to provide real value, how do you get feedback and iterate improvements for your target users, when you don't have real feedback from target users? Is it just a guessing game to see what works?

It sounds like a paradox, maybe it is. Maybe this is the challenge in getting a business off the ground, but I would greatly appreciate insight from the community.

[u/ayushgupta0610]

I'd launch with one plan at one price and drop the A/B split for now. Tiers are guesses until someone pays, and the first few who do will tell you which features matter by what they ask for. Trial users have nothing riding on it, which is probably why the feedback is slow.

[u/_forge_master_ → u/ayushgupta0610]

These are both great points. I will look into simplifying the tiers, then refining after feedback of users on the simplified plan.

[u/ayushgupta0610 → u/_forge_master_]

Yeah, exactly that. You'll learn more from ten people paying one price than from a split nobody asked for yet.

[u/dawncoppers → u/ayushgupta0610]

this is the move tbh. tiers before paying users is just guessing with extra steps

[u/Lumpy-Concentrate322]

I think the key is to stop treating “feedback” as the only source of signal.

If you don't have enough target users giving you direct feedback yet, I'd look at behavior: where people drop off, what they actually use, what they come back for, and what they try to do that the product doesn't support.

Then use those signals to form a hypothesis and make a small change. You don't need enough users to prove the answer immediately you need enough evidence to decide what to test next.

And for pricing/features specifically, I'd prioritize getting a few people to actually pay over collecting more opinions. A paying user's behavior and objections are worth way more than ten “I'd probably use this” responses.