Or takes forever building the feature and/or takes forever getting it right, and the one customer who wanted it gives up and leaves in the meantime. Or even worse they hang on with some tiny engagement that turns out to not actually bring in a lot of money, but still sucks up 15% of developer time (not to mention customer support reps & business development people constantly having to keep them happy) and adds extra value for no other customers.
Having team use their own product for same reasons as customers is a great investment to reduce these issues. Ideally from launching as a new customer to daily tasks.
I try and do this at everyplace I work. Usability issues become completely obvious very fast.
Idea struggles if customers are wanting to adapt your product to them. Best if Customer is able to adapt business to product.
In general, this is excellent advice. But we were running marketplace for food ingredients. And while my co-founder had lots of experience in the industry, there was no realistic way to dogfood it.
You have a handful of customers using a product. One point of data comes in. The team, hungry to build a product customers want, jumps on that one point of data and builds a whole feature around it. Nobody uses the feature.