Hello PH👋 I have built MeritFlow as a solution to a recurring problem I’ve come across - at review time, many of the contributions engineers have made over the year become increasingly difficult to remember. The obvious ones are still there - tickets, pull requests, releases - but a lot of value has gone elsewhere - reviews, mentorship, architectural decisions, an engineer unblocking another, cleaning up someone else’s mess or even just consistently improving how a team operates. And I wasn’t looking for an answer involving "tracking engineers more." I have always been uneasy about tools that tried to distill engineering performance down to commit counts, screenshots, rankings and various other activity metrics. Which meant that one of the key constraints from the start has been that MeritFlow should be useful without becoming a monitoring tool. MeritFlow integrates with existing team tools and helps preserve engineering context that becomes helpful for deliveries, reviews, recognition and development. It may be used for resolving delivery bottlenecks, review processes, contribution documentation, goals, competencies and AI-assisted review drafts. But just as importantly, it doesn’t read your source code, screen capture, or keystrokes or rank your engineers based on their activity level. We’re making MeritFlow available publicly in beta today and I would love to hear from any engineering managers, technical leads, or founders who have been faced with this challenge themselves. Something I am particularly interested in hearing: What type of engineering work do you feel gets ignored the most when conducting performance reviews? Thanks for looking – happy to answer any questions here.

MeritFlow

See the story behind the engineering work

See the story behind the engineering work