[icecrime]

Interestingly we originally designed the product for companies of 50 engineers and above, but we quickly had to add a self-serve onboarding as we were seeing unexpected interest from startups as small as 6 engineers.

I think there are two different challenges at play:

- For larger organizations, the difficulty to understand how efforts are allocated and get a consolidated view they can communicate across the company. Some example we are seeing 1) balancing product and technical roadmaps (for example in companies who have agreed on spending some % of their capacity in paying off technical debt, but who don't know how to measure that) 2) assessing during the course of the quarter whether "the rubber meets the road" and if we're properly executing against our objectives (avoiding the pitfall of realizing only at the end of the quarter that we got sidetracked).

- For startups, the need to be extremely deliberate in how you allocate your limited engineering capacity. This is pretty much our own dogfooding use case at Echoes (a team of 3), where there's an infinite amount of things we _could_ be doing, but we have to be laser-focused on the things we _should_ be doing. In our case Echoes acts as our compass and a forcing function to stay focused.