We're building a simple app that lets you automatically extract and manage to-do tickets right from your team's conversations.
I'm building this because my team and I constantly face a problem: actionable items get lost in the stream of our chat app (Slack, Teams, etc.), or we waste time manually moving them to a separate task manager like Jira or Notion. This manual copy-pasting is our biggest friction. When you move a task, you lose the original context of
why that task was created in the first place.
This context-switching kills our productivity.
Our solution makes this process seamless. Here’s how it works:
You chat with your team, yourself, or an integrated AI assistant.
The AI understands the dialogue (e.g., "Could you fix the deployment bug by Friday?") and automatically suggests creating a to-do ticket from that message.
Of course, you can also manually turn any message into a ticket with a single click.
Each ticket is intrinsically linked to the conversation thread, so the full context is always preserved. These tickets can then be managed on a Kanban board or a calendar without ever leaving the app.
Essentially, our goal is to eliminate the 'collaboration tax' by merging the place of discussion with the place of action.
My questions for HN are:
Would you or your team use a tool like this?
What are your biggest frustrations with your current chat + task management workflow?
Does the "automatic task extraction" sound genuinely useful, or does it feel like a gimmick that might get annoying?
For this to be a "must-have" product for you, what feature would it absolutely need to get right?
Thanks for your feedback!
leakycap•4h ago
My feedback is that
> a simple app that lets you automatically extract and manage to-do tickets right from your team's conversations
would immediately cause me and my coworkers in any office to find another tool to discuss things on, that wasn't extractable by a tool
I've seen people have the "real" chat and talk be on some unmonitored tool in every larger team I've worked on
In other words
> context-switching kills our productivity
Is true, but confidentiality and the ability to discuss things privately is key in today's world... and tools like this can end up being not used if they're not designed around human nature to CYA in team environments
PaulShin•4h ago
Thank you, this is incredibly valuable feedback. You've hit on a critical point about trust and privacy, and I want to be very clear that we agree with you completely.
If my description made it sound like a "Big Brother" tool that monitors conversations, that's a total failure of my explanation, and I'd like to clarify.
The "automatic extraction" is not a secret surveillance process. The AI assistant is designed to act like a helpful teammate, not a spy. It operates openly in-channel and essentially asks, "Hey, that sounds like a to-do item. Should I create a ticket for you?"
The key is that
the user is always in control. Nothing gets turned into a formal to-do item without a user's explicit confirmation or manual click.
So the goal isn't to monitor the "real" chats, but to help the team capture the action items they've already publicly agreed to, acting more like a personal assistant for the team members themselves, not for management.
You are absolutely right about the human nature to CYA in team environments, and our design philosophy must respect that.
This feedback is a gift because it shows our messaging is causing the exact wrong impression. Thank you again. With this clarification, does the concept feel less like surveillance and more like a potentially useful tool?
leakycap•3h ago
I'm not sure I'd be swayed if what I was typing was going through the analysis; I've seen simply logging chats be enough to cause a team to find an alternate route to discuss what's going on and how to fix it (which is where this tool wants to be)
A team I work with now uses an AI tool to get tasks from meetings; some people don't like it for various reasons, so as a compromise it is used only when we are summing up a discussion amongst ourselves (which usually happens after the kind of ideas/discussions that people want off the record)
PaulShin•4h ago
We're building a simple app that lets you automatically extract and manage to-do tickets right from your team's conversations.
I'm building this because my team and I constantly face a problem: actionable items get lost in the stream of our chat app (Slack, Teams, etc.), or we waste time manually moving them to a separate task manager like Jira or Notion. This manual copy-pasting is our biggest friction. When you move a task, you lose the original context of
why that task was created in the first place. This context-switching kills our productivity.
Our solution makes this process seamless. Here’s how it works:
You chat with your team, yourself, or an integrated AI assistant.
The AI understands the dialogue (e.g., "Could you fix the deployment bug by Friday?") and automatically suggests creating a to-do ticket from that message.
Of course, you can also manually turn any message into a ticket with a single click.
Each ticket is intrinsically linked to the conversation thread, so the full context is always preserved. These tickets can then be managed on a Kanban board or a calendar without ever leaving the app.
Essentially, our goal is to eliminate the 'collaboration tax' by merging the place of discussion with the place of action.
My questions for HN are:
Would you or your team use a tool like this?
What are your biggest frustrations with your current chat + task management workflow?
Does the "automatic task extraction" sound genuinely useful, or does it feel like a gimmick that might get annoying?
For this to be a "must-have" product for you, what feature would it absolutely need to get right?
Thanks for your feedback!
leakycap•4h ago
> a simple app that lets you automatically extract and manage to-do tickets right from your team's conversations
would immediately cause me and my coworkers in any office to find another tool to discuss things on, that wasn't extractable by a tool
I've seen people have the "real" chat and talk be on some unmonitored tool in every larger team I've worked on
In other words
> context-switching kills our productivity
Is true, but confidentiality and the ability to discuss things privately is key in today's world... and tools like this can end up being not used if they're not designed around human nature to CYA in team environments
PaulShin•4h ago
If my description made it sound like a "Big Brother" tool that monitors conversations, that's a total failure of my explanation, and I'd like to clarify.
The "automatic extraction" is not a secret surveillance process. The AI assistant is designed to act like a helpful teammate, not a spy. It operates openly in-channel and essentially asks, "Hey, that sounds like a to-do item. Should I create a ticket for you?"
The key is that
the user is always in control. Nothing gets turned into a formal to-do item without a user's explicit confirmation or manual click.
So the goal isn't to monitor the "real" chats, but to help the team capture the action items they've already publicly agreed to, acting more like a personal assistant for the team members themselves, not for management.
You are absolutely right about the human nature to CYA in team environments, and our design philosophy must respect that.
This feedback is a gift because it shows our messaging is causing the exact wrong impression. Thank you again. With this clarification, does the concept feel less like surveillance and more like a potentially useful tool?
leakycap•3h ago
A team I work with now uses an AI tool to get tasks from meetings; some people don't like it for various reasons, so as a compromise it is used only when we are summing up a discussion amongst ourselves (which usually happens after the kind of ideas/discussions that people want off the record)