this+that vs Chaser
Excellent inside Slack, but work does not only arrive there
Chaser is task and project management built to live entirely inside Slack, which is a large part of why teams actually adopt it. this+that starts a step earlier and covers more ground: it reads email, Slack, Teams, Google Chat, and WhatsApp Business, turns the requests inside them into tracked tasks on its own, and can run a workflow and send the reply back through the channel it came from.
A tracker your team will actually use, or a place all your work arrives
Chaser made a smart bet. Project management usually fails on adoption rather than on features, so putting the entire product inside Slack, with no second app to open and no new login, removes the most common reason people abandon it. The task features are mature, and a few are genuinely theirs: follow-ups that chase people for updates on their own, round-robin and group assignment, time tracking, and dashboards for reporting on throughput. Its native MCP integration means an assistant like Claude can create tasks, assign them and run reports without anyone leaving chat. If your team lives in Slack and your work begins there, it is a strong choice and we will not pretend otherwise. The limit is the boundary itself. Slack is one channel, and for most teams it is not the channel customers use. The brief that starts a project, the client asking to move a deadline, the supplier flagging a delay: those tend to arrive by email. this+that reads Gmail and Outlook alongside Slack, Teams, Google Chat, and WhatsApp Business, pulls the requests and commitments out of them without being asked, and is also the place you read and answer those messages rather than a tracker you visit afterwards. Tasks are one output of that. Workflows act on the message and can send the reply back through the channel it arrived on, and a brain holds the context those conversations carry.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Chaser | this+that |
|---|---|---|
| Core idea | Task and project management that lives inside Slack, so there is no separate tool to adopt. | A place every channel arrives, where incoming messages become tracked work and workflows act on them. |
| Where it runs | Entirely within Slack, on your existing accounts. No separate app to open. | A web and mobile app that holds each channel as its own stream, plus a Gmail add-on and a Chrome extension. |
| Channels it reads | Slack only. Email and other chat tools are outside its boundary. | Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business. Instagram and Facebook Messenger are awaiting platform approval. |
| Where tasks come from | A person creates them in Slack, or an assistant creates them when asked over MCP. | Messages are read as they arrive and the requests, commitments and deadlines inside them become tasks without anyone asking. |
| Task structure | Recurring tasks, checklists, tags and a calendar view, plus task templates, round-robin and group assignment, time tracking and reporting dashboards. | Recurring tasks, checklists, labels, priorities, due dates, comments with mentions and attachments, and multi-participant assignment on shared team lists, plus a calendar view across Google and Outlook. No templates, and status is open or resolved rather than custom stages. |
| AI and agents | A native MCP server, so Claude or ChatGPT can create and assign tasks, check status and run reports when you ask them to. | The reading and extraction run on their own, with nothing to configure. Workflows can also reach other systems over MCP, including Atlassian Rovo. |
| Workflow automation | Automatic follow-ups and reminders, plus Zapier, webhooks and an API for connecting other tools. | Workflows described in plain language and triggered by an incoming message, with a broad action set, conditional logic, loops and sub-agents. |
| Answering the sender | Not its job. The loop ends when the task is marked done inside Slack. | A workflow can draft or send the reply back through the channel the message arrived on, so the loop closes where it started. |
| Knowledge layer | Not a feature. Chaser is focused on tracking work. | A brain with version history that grounds what the AI does in what your team has written down. It does not update itself from your messages yet; that is coming. |
| Pricing | $16 per seat per month, or $11 billed annually. A Full Workspace plan is $7 per seat annually but has to cover every member of the Slack workspace. 14-day trial with no card, and single-channel guests are free. | Free during beta. No credit card required. |
- Lives entirely inside Slack, with no second app and no separate login, which makes adoption its strongest suit.
- Automatic follow-ups that chase teammates for updates without anyone remembering to, which is where the product began and where it shows.
- Round-robin and group assignment, so incoming work distributes across a team on its own.
- Time tracking, dashboards and status reports, for teams that have to report on throughput.
- Task and checklist templates, for work that recurs in the same shape.
- A native MCP integration, so an assistant you are already talking to can create tasks, assign them and pull reports.
- Simplicity. One channel, one surface, and nothing to reconcile across tools.
- Reads email as well as chat: Gmail, Outlook, Slack, Teams, Google Chat, and WhatsApp Business, which matters because most customer work arrives by email.
- Tasks are extracted from messages automatically, rather than created by a person or by an assistant that was asked to create them.
- A real collaborative task manager underneath: shared team lists, multi-participant assignment, priorities, due dates, labels, checklists, recurring tasks, and comments with mentions and attachments.
- A universal inbox: the place you read and answer messages is the same place the work lives, with each channel keeping its own stream.
- Workflows are triggered by an incoming message and can send the reply back through the channel it came from.
- A brain that grounds the AI in what your team has written down, so the work it does carries your context.
- Built for work that starts outside the company, which is where most of it starts.
What is Chaser?
Chaser is task and project management that lives entirely inside Slack. It turns the messages a team already sends into tracked, assignable tasks and then chases people for updates, which is where the name comes from. Chaser is built in Toronto, founded in 2021, ran an open beta from 2024, and launched out of beta on June 25, 2026 alongside a native MCP integration for Claude. At launch the company reported more than 500,000 users across over 1,000 companies during the beta period. The feature set is mature for pure task work: recurring tasks, checklist templates, group and round-robin assignment, tags, time tracking, dashboards, a calendar view with Google Calendar sync, and Zapier, webhook and API access.
How much does Chaser cost?
Chaser is $16 per seat per month, or $11 per seat billed annually. There is also a Full Workspace plan at $7 per seat annually, though it has to cover every member of your Slack workspace rather than just the people using it. All plans carry the same features, so the difference is billing frequency and scope rather than capability. The trial is 14 days with no card required, single-channel guests and external connections are free, and registered nonprofits get 50% off. this+that is free during the open beta.
Who should choose Chaser?
If your team genuinely lives in Slack and the problem is that tasks get agreed in a thread and then forgotten, Chaser is a strong answer and probably a faster one than us. There is no second app to open and no new login, which is most of why adoption works. It is also more mature than we are on task structure itself, and the follow-up behavior it was built around is better than ours. Teams whose work starts and finishes inside Slack should look at Chaser first.
Looking for a Chaser alternative?
The reason to look elsewhere is usually that Slack is not where the work starts. The brief that kicks off a project, the client moving a deadline, the supplier flagging a delay: those arrive by email, and Chaser cannot see them. Its MCP integration lets an assistant create a task when you ask for one, which is a different thing from work being noticed without anyone asking. this+that reads Gmail, Outlook, Slack, Teams, Google Chat and WhatsApp Business, extracts the work from all of them, and can reply through the channel the message arrived on.
Your work is not only in Slack
Connect your email and your chat and this+that reads both. The requests and commitments buried in them become tracked work, and a workflow can answer them without you starting it.
Free during beta · No credit card required