Best practices I'm seeing for early product-market validation at MIT

One of the biggest questions every early-stage founder faces today is: How do I launch my startup in this new era of AI-driven product development? It’s so easy to build quickly now. Do I build first or validate first?

Personally, I’ve seen hundreds of startups born in the past year. I’m a grad student at MIT, and I created an AI accelerator for MIT and Harvard, so a lot of those startups have had amazing founding teams. I want to share some of the best practices I’m seeing for getting products into market in an era where a lot of the old best practices seem to be shifting.

1. Identify a problem

Everything begins here. The strongest ideas come from real-world experience. Draw on what you’ve seen firsthand in your work, side projects, or daily life.

Reddit and online communities can also be a goldmine for spotting early signals and understanding how people talk about their frustrations.

We’ve even seen benefits from using simulated interviews with AI characters to get an initial feel for a problem space. This doesn’t replace talking to real users, but it can be a huge head start during the ideation process.

2. Deepen your understanding of what customers care about

There is still no replacement for interviews. Interviews are the best source for intimately getting to know your customers. They help you see how potential users think, act, and work. This is where you find the raw insights that no search data can give you.

Take the stance of trying to learn as much as possible without having an opinion already. You’ll benefit from being open-minded because this can help uncover flawed assumptions you may have held.

In the past, many successful companies would spend months in this phase. Now, with AI tools, you can move faster, but it’s essential that you do not skip talking to customers.

3. Confirm the size and scope

Once you find the core pain points, confirm how big and widespread they are. Get nuance on the trade-offs in terms of how users value features and which personas these can serve.

If you have access to a group of potential users, surveys can help validate at scale. But be careful: a poorly designed survey can mislead you. Make sure your questions are clear, unbiased, and tested before going wide. This is actually a difficult challenge we’ve seen for a lot of startups and is where my startup, @pollystack , is building.

4. Build your V1 fast and get real feedback

This is where modern AI tooling shines. Use tools like Lovable, Replit, or Codapt to build a quick prototype. Your goal isn’t perfection or scalability. It’s to make something people can try and react to. What would have taken months of development in the past can now be done in under a week. Take that time to really think through the user flows, screens, and overall design. The backend and all the features do not need to be fully functional, but you should have enough to explain how they will work.

Then, pick a small group of potential users you trust. Make sure these people are actually indicative of your ideal customer profile (ICP), or the feedback you’re getting may lead you astray. Ask them to think aloud as they go through your prototype. Listen closely to where they get stuck, what confuses them, and what excites them.

Write everything down. You’ll start to see patterns. Some of the feedback should prompt you to make instant changes, so you can show an updated version to the next interviewee. Other points should be thoroughly evaluated before adding to the roadmap.

5. Differentiate between niche needs and broad signals

Some feedback will be unique to one person’s workflow. Other comments will point to bigger frustrations that show real market opportunities.

Your job is to figure out which is which. This is how you separate noise from signal and shape your roadmap.

6. Start to build the product in production

Use what you can from your initial prototype, but understand that you may need to revisit a lot of the code.

Involve users as you build the product out. Invite them to feedback calls, share screen-by-screen updates, and keep them in the loop. This has two big benefits:

They feel invested and develop a sense of ownership.

• You build a pipeline of early champions who are much easier to convert into paying customers later.

• It’s not just about product feedback. It’s also about psychology and trust.

The takeaway

AI has changed how fast we can build. But it hasn’t changed this: you still need to understand your users deeply and involve them in the journey.

Fast iteration, real problem focus, and strong user engagement are what separate AI hype from products that actually stick.