this+that vs Cora
An inbox that gets quieter, or work that actually moves.
Cora is a considered answer to inbox overload: it screens Gmail for what matters, batches everything else into a brief you read twice a day in about thirty seconds, and drafts replies in your voice into your drafts folder. It deliberately can’t send or delete. this+that’s aimed at a different problem. We read email and team chat continuously, what arrives becomes tracked work that lands with a person, and workflows carry it through to the reply.
Reading less, or doing less
Cora rests on a clear opinion, and it’s a good one: most email doesn’t deserve your attention, and the fix is to stop looking at it. Important messages surface, a twice-daily brief summarizes everything else, and Cora drafts replies in your voice for you to approve. It holds no permission to send or delete, which is a deliberate safety decision rather than a missing feature, and it’s refreshing that they say so plainly.
The result is a quieter inbox. What it isn’t is a system that does the work. A brief tells you a customer asked for a renewal quote. Someone still has to write the quote, remember the follow-up, and make sure it did not fall to a colleague who never saw the thread. Cora is for one person reading less. It is Gmail only, there’s no shared task list, and it assigns nothing to anybody.
this+that starts where that stops. It reads every message arriving in Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business for what needs doing, and the requests and commitments inside them become tasks in DoBox with an owner, linked back to the message they came from. You set up the workflows, and they act on those tasks, drafting or sending on the channel the request arrived on, with approval gates where judgment is needed. What those workflows learn goes into a shared knowledge layer we call the Brain, so the next answer starts from what the company already knows.
So the split. If your inbox is loud and you want to spend less time in it, Cora is a focused, well-made tool and it will do that on day one. If the problem is that work is getting lost between people rather than piling up in front of one person, a calmer inbox doesn’t fix it, because reading a summary of a dropped ball is still a dropped ball.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Viktor | this+that |
|---|---|---|
| The core idea | Read less. Important mail surfaces, the rest is summarized into a brief you read twice a day in about thirty seconds. | Do less. What arrives is turned into tracked work and, where you’ve set up a workflow, carried through to the reply. |
| Email providers | Gmail and Google Workspace only. Their FAQ states Outlook and other providers aren’t supported yet. | Gmail and Outlook, both read continuously as inbound channels. |
| Team chat | None. Cora is an email product. | Slack, Microsoft Teams, Google Chat, and WhatsApp Business, read the same way email is. |
| Can it act? | No, by design. Cora drafts into your drafts folder and states it holds no permission to send or delete email. | Yes, and gated. Workflows can reply, route and file, drafting rather than sending by default on anything outbound, with approval steps where you want them. |
| Tasks and ownership | No task manager and no assignment. The brief tells you what happened; tracking it’s yours. | DoBox: tasks extracted from messages across every connected channel, with per-person assignment, due dates, comments, and a link back to the source message. |
| Team or individual | Individual. Each person gets their own quieter inbox. | Team. Work is assigned, visible to the people it affects, and survives someone being away. |
| Shared knowledge | Learns your writing voice and what you tend to read from your own mail history. | The Brain: a writable team knowledge layer that workflows read from and write back to as they run, so it grows out of the work rather than being maintained by hand. |
| Drafting | Drafts replies in your voice from your email history, left in your drafts folder for approval. | Drafts replies grounded in the Brain, so a quote or an answer starts from your pricing and what this customer was already told. |
| Security and compliance | Google Verified and CASA Tier 2. GDPR and ISO 27001 compliant. States it never trains on your data. | CASA Tier 2, revalidated February 2026. SOC 2 Type I as of July 31, 2026, with Type II underway. Message content, tasks and knowledge pages are envelope-encrypted under dedicated customer-managed keys. Employees read customer content only with the customer’s permission or for emergency support, and that access is temporary and logged. Your data never trains a model. |
| Pricing | Professional $20/month for 2 email accounts, Unlimited $39/month for unlimited accounts, both billed annually. | Free during beta. |
- The brief is an idea, not a feature. Twice a day, thirty seconds, and the rest of the day you’re not in your inbox at all. If reading email is the thing eating your week, that’s the most direct fix on this list.
- It can’t send or delete, and they say so up front. For anyone nervous about handing an agent their mail, that’s a stronger guarantee than any approval setting.
- ISO 27001 alongside CASA Tier 2 and Google verification, plus a stated policy of never training on your data.
- Voice-matched drafting from your own mail history, which is the feature people in this category actually keep using.
- A clear, opinionated product with a point of view about how work should feel. That is rarer than it sounds.
- The work leaves your head. Requests and commitments become tasks with an owner and a due date, linked back to the message they came from, instead of a summary you still have to act on.
- Email isn’t the whole job. Slack, Teams, Google Chat, and WhatsApp Business are read the same way Gmail and Outlook are, because the request that goes missing is as likely to be in a channel as an inbox.
- Outlook works. Cora is Gmail only, which rules it out for most companies on Microsoft 365.
- Workflows close the loop. Describe a piece of inbound work in plain language and it runs, drafting or sending on the channel the request arrived on, with approval gates on anything that matters.
- It is built for a team. Tasks are assigned and visible, so work surviving a holiday doesn’t depend on one person reading their brief.
- The Brain gets better as you use it. Workflows write what they learn back into a shared knowledge layer, so the next draft starts from your pricing and your history with that customer.
- Free during beta.
See what's waiting in your inbox
Connect your inbox and this+that starts reading it. The tasks, follow-ups, and open commitments buried in your messages become tracked work, and what your team knows starts collecting in one place.
Free during beta · No credit card required