Here's the fifth "Meet the Batch" thread for YC's S21 batch. The previous thread was
https://news.ycombinator.com/item?id=28073548, and if you're wondering what it's all about, the description is at
https://news.ycombinator.com/item?id=27877280.
There are 7 startups in this thread. The initial order is random:
Clarity (YC S21) - Run your distributed team with a single weekly doc - https://news.ycombinator.com/item?id=28128962
Mentorcam (YC S21) - Get advice from public figures - https://news.ycombinator.com/item?id=28128958
Sirka (YC S21) - Tackling obesity in Southeast Asia - https://news.ycombinator.com/item?id=28128964
Echoes HQ (YC S21) - Measure the effectiveness of engineering organizations - https://news.ycombinator.com/item?id=28128961
PayHippo (YC S21) - Loans to small businesses in Nigeria - https://news.ycombinator.com/item?id=28130022
ContraForce (YC S21) - All-in-one cybersecurity platform - https://news.ycombinator.com/item?id=28128959
Palenca (YC S21) - Payroll API for Latin America - https://news.ycombinator.com/item?id=28128960
I’m passionate about developer empowerment and building engineering organizations. This is what got me into engineering management in the first place, and why I later joined Docker to lead the core team. Throughout my career I’ve come to realize that organizations are often held back not by a lack of developer productivity or talent, but by the lack of proper context to achieving good results (a theme commonly discussed here in comments).
To help companies solve this, we surface why engineers are doing what they do in the simplest way we could think of. You define within Echoes what you’re investing efforts into (e.g., the categories of work, ongoing initiatives, or OKRs relevant to your organization), which Echoes publishes across all of your GitHub or GitLab repositories as labels. Applying these labels on pull requests is all it takes to surface how teams are truly allocating their efforts over time. You can later connect intents to external measurements, showing you whether efforts are actually making a difference.
Engineering managers can use this data to inform decisions on priorities, confront the plans to the reality, and communicate on the activity to their CEO / bosses / business partners with the right level of detail. One of the first use case we're using to illustrate what Echoes can do is the very common challenge of balancing the amount of efforts that should go into features versus technical work (https://www.echoeshq.com/recipes/managing-technical-debt).
If you'd like to learn more: we have a two-minute demo video (https://youtu.be/3ZRGdZq7v24), or I'd be happy to discuss and run you through a live demo (https://calendly.com/arnaudp/echoes-demo). We look forward to hearing your feedback and answering your questions!