Gennie - Online Meetings to Assigned Tasks
Hi All,
We have been using Granola/Fireflies/MeetGeek, etc for almost a year now and quite happy with it.
One issue that kept coming up for us was follow-through after meetings. Things were getting discussed and agreed on, but execution depended too much on someone remembering or organizing tasks afterward.
The meeting summaries and action items are there, but they stay in Granola, etc and soon things gets started missing or losing out.
No one remember after 2 days as what what discussed and who owns which task/action-items from the meeting.
So we built Gennie (https://heygennie.com) to handle this problem:
Before ending any discussion, every action item has to be assigned to a single owner. Gennie does this for you, automatically and push the tasks to Asana, Jira, Slack, Email, etc
No shared ownership, no “we’ll handle it later,” just one person responsible and the data is in your system of records, Asana in this case, with proper due date, assignee, labels, etc.
After doing this more deliberately:
Fewer missed follow-ups
Less back-and-forth clarification
Clearer accountability overall
It added a bit of structure, but didn’t slow things down as much as expected. Hardly takes a few seconds to review and push with one-click to Asana.
Still early, but it’s one of those small operational tweaks that seems to compound over time.
Happy to answer any questions.
Wow, this is a real problem.
Meeting notes help, but I always see the exact same thing happen: everyone leaves thinking they’re on the same page, and two days later no one is quite sure who's actually responsible for what.
I really like the idea of forcing every task to have a single owner before the meeting ends. That small detail easily prevents the classic "I thought someone else was doing it."
I did have one question, though: what happens when the AI gets the owner wrong? Is the review step quick enough for people to actually fix the assignment and due date before it goes to Asana/Jira, or do teams just tend to trust the automation blindly?
Great work on this — it’s exactly the kind of "boring" operational problem that becomes incredibly expensive if you ignore it.
Thanks.
Yes, there is a manual screen which shows up so that you can review everything (spend 5-10 seconds) and then push the trigger, so that everything is 100% correct and AI makes no mistakes of its own.
That makes sense. I like that you kept a human review step before pushing anything into the system of record.
5–10 seconds sounds like a good tradeoff if it prevents bad assignments from becoming “official” tasks in Asana/Jira.
That review screen is probably an important part of the trust layer for the product.
Yes, we felt the same and added that screen. We built the product for our own itch and used it daily, so as to feel and remove the friction points.
Adding to the Monday pile: Congress monitoring was ours for a long time. Two people were splitting the job of checking Congress.gov and sending a Slack summary. Automated it with goffer.ai - it monitors keyword and sponsor filters, auto-labels Gmail by urgency, fires SMS on floor votes. The two people who were doing the manual check now get a 5-minute digest instead of 45 minutes of scanning. The time savings was concrete enough to justify the cost immediately. The hardest part was agreeing on which keywords actually mattered vs which ones created noise.
This is a real fix for the “execution gap” most meeting tools quietly ignore.
What stands out is the forced ownership rule — it removes ambiguity, which is usually where follow-ups die.
I help SaaS teams tighten exactly this kind of messaging-to-action flow (async, no calls) when they’re ready to reduce friction and improve conversions.
This is great. I am going to share it with the AI lead for my business. They are looking for suggestions of how we can use AI to make us more efficient and this solves a real issue of ownership within project management
Sure. Thanks :)
Great work Steven! 🎉
The follow-through problem after
meetings is so real — most teams
lose track of action items within
24 hours.
Love the approach of forcing single
ownership before ending a meeting.
The Asana/Jira integration makes
it seamless for existing workflows.
Thanks :)
This is a real workflow gap. Meeting tools are good at capturing what happened, but the value often dies in the handoff between summary and execution.
The stronger positioning here is not “meeting notes to tasks.” It is accountability transfer: turning agreed decisions into owned work inside the systems teams already use. That is a much sharper angle than competing directly with Granola, Fireflies, or MeetGeek.
One thing I’d pressure-test early is the name. Gennie is friendly, but it may feel a bit generic for an operations/workflow product that needs to earn trust with teams using Asana, Jira, Slack, and email. The product is really about execution reliability after meetings, not just AI assistance.
A name like Xevoa .com would fit that broader workflow layer better because it feels more like a serious productivity/ops platform while still leaving room beyond meetings later.
The product itself is useful. I’d just make sure the brand makes it feel like a dependable execution layer, not another meeting AI add-on.
Thanks for the suggestion. Will check out this angle for sure :)
Appreciate it.
I’d treat this as a positioning decision before it becomes a product decision. If Gennie stays only around meeting follow-up, the name can work. But if you want it to become the execution layer after meetings across Asana, Jira, Slack, and email, the brand may need to feel more operational and less assistant-like.
That’s where Xevoa.com fits much better in my view. I own it, so if that direction is genuinely interesting, happy to discuss privately and keep it founder-friendly.
Yes, looks like you are trying to sell your domains to every other person in the community. Better you stop spamming.
Fair pushback, Steven.
That was not my intention, but I understand how it could come across that way. My point was mainly around positioning and whether the product should feel like a meeting assistant or a broader execution layer.
I’ll leave it there. Appreciate you saying it directly.