---
title: "Comment by Rishita Sharma on \"How to Scope an AI MVP Before Development Begins\" | Hashnode"
description: "I’ve found that the best MVP scope is often defined by the decision the product must support, not by the number of features it can ship. I start with one user o"
url: "https://hashnode.com/posts/how-to-scope-an-ai-mvp-before-development-begins/6abbad245d3c0753560970b8/comment/6abebc34daa82706fdbdacd6"
---

[Discussion](https://hashnode.com/posts/how-to-scope-an-ai-mvp-before-development-begins/6abbad245d3c0753560970b8)

Comment [How to Scope an AI MVP Before Development Begins](https://hashnode.com/posts/how-to-scope-an-ai-mvp-before-development-begins/6abbad245d3c0753560970b8)

[Rishita Sharma](https://hashnode.com/@narawaybuilder)

[Oct 1](https://hashnode.com/posts/how-to-scope-an-ai-mvp-before-development-begins/6abbad245d3c0753560970b8/comment/6abebc34daa82706fdbdacd6)

I’ve found that the best MVP scope is often defined by the decision the product must support, not by the number of features it can ship. I start with one user outcome, identify the riskiest assumption, and design the smallest test that can change our mind. That approach keeps AI work focused and gives the team a clear next step.