(Reposting because it got deleted)

This is pretty neat. I like the positioning of a monitoring service for your data.

As someone who isn't a data engineer: How did you guys come across this problem? Is this something people have often?

This is pretty neat. I like the positioning of a monitoring service for your data.

As someone who isn't a data engineer: How did you guys come across this problem? Is this something people have often?

I agree with your point, but realtors are protected but layers of legislation. In many areas the realtor groups almost operate like the taxi cartels.

Super cool to see how OP considered the value of control buttons and simplified

My side project is a web app to publish product updates (http://productmap.co). Right now, working on letting users leave feedback and suggest things they want to see in your product.

Hi Michael + Aaron,

We're building a smarter way to share product updates (https://productmap.co).

So far we've received a great amount of interest (waitlist) and have users already integrated that are coming back over and over.

The next steps would be to build out some of the feature requests as it's fairly early right now. One of those requests is having custom domains and users are happy to pay $10-$20/mo for it.

The vision for ProductMap is much larger though -- to tackle the fragmented way companies handle communication and feedback with their customers.

Do you think charging for custom domains would be self-limiting in nature? It's a fairly trivial thing to offer for free.

Thank you in advance! (and meeting with Yuri when he's in Toronto this weekend.)

Why do you believe charging for domains would be self limiting?

Users won't be able to use the product for what it's intended value is (better feedback and communication) if they're turned away so early.

Better put, a custom domain isn't part of the value we add, it's just a gateway to realize the value. Should we be charging for something that's not really tied to the value we provide?

Why would custom domains turn users away?

Ex. A user wants to try it out but paying for a custom domain scares them. They stick to a free subdomain, but never really promote it since it conflicts with their own branding.

Admittedly you're making a good point here that users _would_ get more value this way through increased branding.

I think giving your customers what they want is the central theme behind most of our advice

Absolutely, but would charging them for a (technically) trivial feature be self-limiting to our growth?

Another question: Would be worthwhile to apply to YC with a product of this nature?

This was super helpful. Thank you for taking the time Michael.

Addressing your first point, Heroku charges $20/mo for HTTPS support and plenty of people pay for it: https://elements.heroku.com/addons/ssl

You're right, that's a good example. Thanks!

We built ProductMap to have a place to tell users about new features, updates, and product announcements.

Down the road we'll be adding things like voting, user feedback, and automatically posting to social media.

Happy to hear feedback!

Cool, very useful.

Thanks :) I think Jira is more for managing the sdlc and an internal tool.

The focus here would be to have an intuitive interface for product updates and getting feedback on new product decisions.

Thank you! Super helpful feedback. I'll add a second like explaining the problem this solves (replacing release notes, changelogs, etc.)

I'm from Toronto :)

Awesome!

Thank you. That seems to be the feedback here (page isn't clear enough). Considering you run a service, how do you convey tell your users about new features in an engaging way?

At the moment I don't have a defined way of updating users of new features. As I'm aiming to run BugMuncher as openly and transparently as possible, a public road map has been on my todo list for quite a while. I'm very interested in your product, which brings me to my next bit of feedback:

I clicked the 'Get Early Access' button, and it opened what looked like it was going to be a survey, which put me off. I decided to give you the benefit of the doubt and clicked the 'Start' button, but my initial instincts where correct, and there where 8 survey questions to answer. I'll be honest, at that point I closed the tab and went about my day.

I'm BugMuncher's solo-founder and only employee, so all tasks fall to me, this makes me really value my time, to the point where those survey questions where enough to make me move on.

When someone clicks the early access button you should do nothing but capture their email address, so you can keep them updated and notify when beta access is granted. Once I've started using your product I'll be much more receptive to the survey.

Appreciate the honesty here! I'll make sure to shorten that down to 1-2 Qs.