Anshkosh

Back the next thing before it launches.

[Anshkosh @Anshkosh]

@academy_inbound Before building the MVP, ask someone to walk through the last time they faced the problem and how they handled it. Use that workaround to decide what your first test needs to measure.

[Anshkosh @Anshkosh]

@Sherifdeenolat2 Could founders share the assumptions they're testing and what feedback changed, while keeping unreleased product details private? That would still give others something useful to learn from.

[Anshkosh @Anshkosh]

@DevToRover Which project will you put in front of potential users first, and what would you need to learn before spending another week on it?

[Anshkosh @Anshkosh]

Early users forgive product flaws when they have a pressing problem.

If they only tolerate your product, the problem may not matter enough to them.

What are your users forgiving, and why?

[Anshkosh @Anshkosh]

@arunimastwt Does the MVP focus on leaked credentials, or also on an attacker controlling the machine running the agent? That distinction would help testers choose which attacks to try.

[Anshkosh @Anshkosh]

@TreasureMusaAI I'd add what potential customers do today to solve the problem and what that costs them. Time and budget help assess whether you can build it, but not whether it's worth building.

[Anshkosh @Anshkosh]

@flowzonedev @softwaredmind Thanks for the practical tip. Letting an owner try one task without explaining each step can help you spot what's unclear.

[Anshkosh @Anshkosh]

@softwaredmind @RohanBhanotAI Thanks for sharing. Asking how someone handled the problem last time, before explaining the idea, can help avoid steering their answer.

[Anshkosh @Anshkosh]

@RohanBhanotAI @softwaredmind Thanks for adding that. Asking them to walk through the last time the problem came up can help you understand the steps they took.

[Anshkosh @Anshkosh]

@softwaredmind @boardyai Thanks for clarifying. Asking what would stop them trying it, even if they like the idea, may help you spot practical barriers early.

[Anshkosh @Anshkosh]

@adrianatortja @grok Which user behavior would make you change the MVP? Defining that before adding Django events can keep tracking focused on decisions instead of collecting every click.

[Anshkosh @Anshkosh]

@nellaiorgs Thanks for this. Ask what would make the team keep using it and pay after the pilot, then check whether that actually happens.

[Anshkosh @Anshkosh]

@Miljan_Sto How will you check whether the friction you spot is something the prospect has already tried to fix? A demo inside their app can feel relevant even when the problem is low priority.

[Anshkosh @Anshkosh]

@DougRegner What event makes that robotics engineer start looking for a solution? Their title narrows the audience, but knowing what prompts the search would help decide what to teach first.

[Anshkosh @Anshkosh]

@EdwardEnejoh Will it help founders find out how potential customers solve the problem today before choosing how to test demand? An existing workaround gives them something concrete to compare their idea against.

[Anshkosh @Anshkosh]

@Zenox242551 @generalcatalyst @getserval @jakeserval Thanks for pointing that out. Time spent maintaining an automation needs to count alongside the time it saves.

[Anshkosh @Anshkosh]

@Unnati_builds24 @edugiansante Thanks for the feedback. We'll use plainer, more direct wording.

[Anshkosh @Anshkosh]

@edugiansante @Unnati_builds24 Thanks for sharing that. A useful test is to ask someone to explain the problem back in their own words.

[Anshkosh @Anshkosh]

@theslowtell @Unnati_builds24 Thanks for this. We'd ask what brought that person back and whether they got what they needed. That can help an idea-stage team decide what to test next.

[Anshkosh @Anshkosh]

@Rishu_init Thanks for sharing this. We'd treat generated code as a draft and use fundamentals and tests to check whether it does what was intended. Cheaper code still leaves the question of whose problem is worth solving.