We niched down our idea

Not sure if I hate myself for saying "niched down" but I'm keeping it.

Our original idea for Marvy was to add async video to how product teams get feedback, bugs, questions, and praise from users.

We had a few calls with customers and tried to Mom Test it.

We didn't talk much about our idea until the end of the calls and mainly focused on how they do things today.

One big thing we learned was the way customers get bugs submitted by users comes with a lot of wasted time.

The bug reports are often just text with no screenshot or video. You have to figure out what the heck it means.

You also may need a follow-up call to see what was happening in dev tools.

We also learned that internally, teams send looms for bugs more frequently than they send product feedback. Not that the latter wouldn't be valuable, it's just not as common.

When they run into a bug, an early thought is capturing a visual to help the engineer who picks it up.

This is great for us - we don't need to climb mountains convincing prospects they should screencast bugs.

So we changed our broad focus on async video between a product team and users and decided to focus on bugs only for now.

This makes our offering much simpler to message and for prospects to grasp.

We can also auto-include console logs and errors with each bug screencast. This is an added layer of value so there is less back and forth wrangling technical details.

Lastly, this is clearly already something customers are paying for today. We aren't the first SaaS to try improving bug reports, though we do have our unique take on it.

We updated our landing page to reflect the new focus: https://www.marvy.so/.