FollowBot

Alright, so here's the thing. 

Friday afternoon, 15:30. My coworker and I are discussing a critical bug in our production bot. I write: "Okay, we need to fix this by EOD."

He replies: "Adding it to my list."

A week later. The bug is still in production. Turns out "my list" was a Notion database that literally nobody checks. And that Slack message? It got buried under 150 other messages by the next day.

This happened three times a month. Every single time: lost context, angry customers, someone saying "I thought you were handling this?"

That's when I realized the problem wasn't my team. It was the tools.

The Tools Were Killing Us (Silently)

I tried everything:

- Slack reminders (/remind me in 5 days) — Set it and forget it, literally. Three weeks later you have 47 forgotten reminders in your DMs.

- Jira — Context switching tax. Nobody wants to open another app just to add a task.

- Notion — Beautiful, async, completely disconnected from where work actually happens (Slack).

- Custom slash commands — Works until someone forgets the syntax and just... stops using it.

All of them shared one thing: they took you away from Slack. And in a distributed team, taking someone away from your primary communication channel is like saying "this is less important than your current conversation."

Then I noticed something stupid but obvious. People were already using Slack reactions as ad-hoc signals:

- 👀 = "I'll look at this"

- ✅ = "Done!"

- 🔥 = "Urgent"

What if those reactions... actually did something?

The Idea That Changed Everything

What if reacting with ✅ to a message didn't just add an emoji, but:

1. Created a tracked task (with full context preserved)

2. Sent a reminder in your DM

3. Kept you in Slack (no app switching)

4. Actually showed the original message context when reminding you

No switching. No copy-pasting. No Notion database. Just an emoji.

It took me 2 weeks to build v1. Deployed it to our team's workspace.

Then I got a reminder 24 hours later. Not a generic notification. A DM that said:

"Task from #engineering-ops: '@user fix the production deploy error' — React ✅ to mark done"

And it had the full message thread context.

I sat there for a second. This was... clean? Like, weirdly clean. You didn't have to remember what the task was. You didn't have to open another tab. You just saw the context of the conversation that created the task in the first place.

What Actually Works (And Doesn't)

Over the first month, we tracked ~200 tasks. 95% completion rate. That number matters because it means people aren't just creating tasks and forgetting them — they're actually doing the work.

Better yet: nobody turned it off. That's the real test. If your tool sucked, people would disable it within a week.

Some things I got right:

- Simplicity: One reaction. Everything else is automatic.

- Context preservation: You see the original message, not just "do this thing"

- Slack-native: No context switching means it actually gets used

- Personal reminders: DM, not channel noise

Some things still need work:

- Bulk operations (working on this) — "Mark all tasks in #project as done"

- Team views — See what everyone's working on (privacy-safe way)

- Integration with existing workflows — Jira sync, GitHub issues, etc.

Why I'm Launching This Now

Honestly? I almost didn't.

The bot works. My team uses it. That could have been enough. Ship it internally, call it a day.

But I kept hearing the same story from friends' teams: "We tried Jira but it's too heavy. We tried Slack reminders but they're a graveyard. We tried Notion but it's async and disconnected. We just... lose tasks."

If this solves the problem for my team, maybe it solves it for others too.

So here we are. FollowBot is live. Free. No paywall, no weird freemium trap.

Technical Stuff (If You Care)

Built with Flask + Slack API + SQLite. Deployed on Railway. ~200 automated tests. OAuth for auth. Real-time event handling.

Nothing fancy. Just solid fundamentals. The kind of code you can understand and fork if you want.

What I Want to Know

Real talk: What would make this actually useful for your team?

Are task reminders in DMs the right approach, or would you want something different? Should we integrate with GitHub issues or Jira? What about team dashboards?

Or is the idea just not interesting and I'm way off?

Either way, I'd love to hear it.

Try it here: https://followbot.app

React with ✅ to try it in your Slack