Hey IH folks!
I’m working on a productivity tool and I’m at a crossroads. Would love some feedback to help shape where I go next.
Most to-do lists are just lists. They collect tasks but do little to help you process or prioritize them in a way that keeps you focused.
Over time, they become bloated and overwhelming, and you end up spending more time cleaning them up than doing actual work (ask me how I know 😅).
Kando is my attempt to fix that. It’s a productivity tool that guides you through:
✅ Refining your tasks—think of it like a backlog cleanup assistant that nudges you to size, prioritize, and organize tasks easily.
✅ Daily stand-ups—quick guided reviews that help you commit to just the work you can realistically focus on today.
Early feedback has been promising, and I would love to hear yours (check out Kando here) but I want to validate something else before going deeper...
What if Kando passively captured tasks for you during the day?
Imagine it listens to your meetings (locally, private, encrypted), picks up on things you say you’ll do, and adds them to your task inbox.
Or it watches your screen (again, local + secure), and when it spots you highlighting text or typing to-dos in notes/slides/emails/Slack, it offers to capture those as tasks automatically.
I’m thinking about how much cognitive load this could save. No more scrambling to write things down or remembering what you promised in a call. That's the idea.
Would guided backlog refinement + daily stand-ups help you stay focused?
How do you currently capture to-dos that come up during meetings or while you’re working?
Would a passive capture system like the one I described help you… or feel invasive/creepy (even if fully local and secure)?
Anything else you’d love to see in a productivity system like this?
Happy to hear any and all feedback! And if you’ve seen anyone solving this in an interesting way, I’m all ears.
Thanks, IH 🙏
— Sebastiaan
Love how clearly you framed the “task-list bloat” pain.
One conversion tweak I’d test first: make above-the-fold a single before/after promise (from messy backlog to “today’s top 3 tasks”) and move feature detail below that. Then add one tiny proof artifact right under CTA (15-sec GIF or one user quote) so trust lands before scroll.
If useful, I can share a fast teardown with exact copy/layout edits. I’ve been doing these for founders here: https://roastmysite.io/?src=external_manual_nonhn_20260328T145652Z_subagent_r1_ih_productivitysystem_usd_presell_hv
Interesting direction. Disclosure: I’m helping with Wispr Flow outreach, so I’m coming at this from the dictation / capture side.
The strongest distinction I keep seeing is active capture vs passive capture:
If Kando explores capture, I’d test a lightweight "speak a task anywhere -> drop it into inbox" flow before screen watching or meeting monitoring. That feels like the lowest-friction version with the least creep factor.
That same pattern is also nice for standups and backlog grooming: rough-draft the task by voice, then refine / prioritize it in the app.
Curious what your early users ask for more: automatic extraction from meetings, or just a much faster way to capture tasks the moment they occur?