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.
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.
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?
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.)
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?
I spoke with an admittedly small set of potential companies, both B2B and B2C. There's enough value in replacing the current way of communicating updates with customers which involves: newsletters, notifications, emails, blog posts, release notes, PDFs (B2B mainly), etc.
Just to note, really didn't use producthunt as an inspiration. Simply tried to make a "blob" with the letter P in it. Not sure how the colors are similar?
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?