Ask HN: Hit a wall with our product team. What next?
I wrote a bit about this yesterday[0] and here[1]. The (enterprise) clients we had all valued our work, nobody haggled that much, but we went above and beyond. We did dive into their domain and worked on problems in the banking, energy, transportation, telecom sectors, etc.<p>What we did was to refine the process of consulting: validate the client, walk them through a blueprint for success and be explicit about the requirements and the people who need to be on board before we could start.<p>Then we worked on our platform (<a href="https:&#x2F;&#x2F;iko.ai" rel="nofollow">https:&#x2F;&#x2F;iko.ai</a>) to remove as many tasks off our plate as possible.<p>We also had to think about verticals and we&#x27;ll get there with a package for each vertical if we&#x27;re thinking in terms of sectors, or in terms of functionality when it&#x27;s something common. That&#x27;s why we built our platform with a plugin architecture. It has the time series forecast plugin, the sentiment analysis plugin, etc. And that&#x27;s also why we made sure they had APIs, so we could compose and do interesting stuff instead of re-deploying everything.<p>I&#x27;d say refine your processes and extract common tasks into your own tooling so that you ship faster. You&#x27;ll be in a better position to think, and you may have a product for teams similar to yours.<p>For example, we do ML projects and built our platform to help our own team. There are many teams like us out there. Similarly, there may be many teams like yours out there.<p>- [0]: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26455105" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26455105</a><p>- [1]: <a href="https:&#x2F;&#x2F;iko.ai&#x2F;docs&#x2F;story&#x2F;" rel="nofollow">https:&#x2F;&#x2F;iko.ai&#x2F;docs&#x2F;story&#x2F;</a>