[fananta]

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?

[mwseibel]

Why would custom domains turn users away?

[fananta]

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.

[mwseibel]

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

[fananta]

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.

[tkmcc]

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

[fananta]

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