Hi Product Hunt, I built Pointwise for two fairly simple reasons. First, I've used a lot of planning poker tools over the years and never found one I particularly liked. They did the basic job, but the overall experience always felt clunky and disconnected from the actual development workflow. Second, and much more importantly, when it came time to estimate a task, I'd regularly find myself staring at a task thinking: I don't actually know how complex this is. You read the ticket, make a few assumptions, pick a number and hope everyone else's educated guess is somewhere nearby. That's the problem I really wanted Pointwise to tackle. Pointwise runs planning poker around the actual GitHub issue. Your team estimates independently and reveals together, but Pointwise can also analyse the issue and its context using GitHub Copilot to help the team understand the work, identify complexity and spot things that might have been missed before settling on an estimate. The aim isn't to have AI choose a story point for you. It's to give humans better context before they make the decision. I wanted the whole thing to feel lightweight: connect GitHub, find an issue, bring in the team, understand the work, estimate it, review the result and get back to building. Pointwise is now at the point where I want to get it outside my own testing bubble and into the hands of real development teams. I'd love to hear how other teams deal with that moment when everyone is supposed to estimate a ticket but nobody is entirely sure what horrors are hiding inside it. Thanks for checking out Pointwise.

Pointwise

Planning poker built around your GitHub issues

Planning poker built around your GitHub issues