> That’s when I decided to dive deeper into analyzing what other problems Microsoft Teams users were facing and what kind of service I could offer them. I was confident I’d find a niche because the traffic and activity on the marketplace were high — a ready-made customer base was just in front of me. I just needed to find a product idea that would solve a real problem.
> I started reading forums, comments, and online discussions. It turned out the built-in Wiki in Microsoft Teams annoyed users really a lot. It was slow and inconvenient.
OP has done actual research and found a real problem to solve. Amy Hoy has been popularizing this exact approach under "Sales Safari", but it boils down to "find your user's watering holes and listen to what they complain about to each other."
> That’s when I decided to dive deeper into analyzing what other problems Microsoft Teams users were facing and what kind of service I could offer them. I was confident I’d find a niche because the traffic and activity on the marketplace were high — a ready-made customer base was just in front of me. I just needed to find a product idea that would solve a real problem.
> I started reading forums, comments, and online discussions. It turned out the built-in Wiki in Microsoft Teams annoyed users really a lot. It was slow and inconvenient.
OP has done actual research and found a real problem to solve. Amy Hoy has been popularizing this exact approach under "Sales Safari", but it boils down to "find your user's watering holes and listen to what they complain about to each other."