One of the weaknesses of agency-driven products is the lack of market understanding and ongoing connection. It's frequently a sweep up of anecdotes from their d

One of the weaknesses of agency-driven products is the lack of market understanding and ongoing connection. It's frequently a sweep up of anecdotes from their developers, clients, and perhaps some other research. Sometimes it's a vanity project for someone who ultimately knows that they won't turn the agency into a product company and they ultimately move once the product gets attention. You have to wait them out by being selective in how you burn your resources while developing a "brand" that's different from an agency. Be genuinely interested in solving the problems that your users have. Devtools have always been attractive as products to developers, but they are notoriously difficult to be successful with. You need to find all of the workflows that your users have and optimize them effectively. Sometimes the things that are needed are dull and boring, but if they visibly take someone's time then there is long-term value. Be careful about supporting esoteric approaches that will disappear, but also be aware that this can help with locking in some customers at the right point. Agencies tend to be bad at support. They are optimized for making new things and moving on. You have an opportunity to provide a strong support experience which is coupled with intelligence gathering on developer needs.