Brief one executive, or run the whole team's work
Bond is an AI chief of staff for the CEO. It watches Slack, Jira, Notion, GitHub, and the rest, then sends a morning brief on what moved, who is blocked, and what needs attention, and tracks the threads you owe a reply. this+that is the layer the whole team works in. It reads every channel, drafts and sends the replies, and turns messages into shared, assignable tasks and workflows, grounded in a team brain. Bond tells the exec what to look at; this+that does the work and routes it across the team. They can sit side by side.
Visibility for the exec, or execution for the team
Bond's bet is that a CEO's hardest problem is situational awareness: the company runs across a dozen tools, and no one person can see all of it. So Bond plugs into those tools, surfaces metrics and risks, sends a one-page brief each morning, ranks what matters with the most important on top, and tracks every "I'll get back to you" so nothing drops. It does that job well, and for an executive who needs to know what is going on, it is a genuinely useful layer. this+that's bet is different. The work that needs doing arrives as messages, and most of it is not the CEO's to do. So this+that reads every channel the team uses (Gmail, Outlook, Slack, Teams, Google Chat, Telegram), drafts the replies, and turns each message into a task the right teammate can be assigned, with workflows running the repetitive parts. Bond is built to brief one person; this+that is built for a team to share the load. If you want an executive radar across your stack, Bond is a strong fit. If you want the communication work actually handled and routed across the team, that is the job this+that owns. The two are closer to complementary than to substitutes.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Bond | this+that |
|---|---|---|
| Who it serves | One executive. An AI chief of staff for CEOs and busy execs, built to give a single leader visibility across the company. | The whole team. A shared workspace where everyone reads, replies, and gets work assigned, not a personal radar for one person. |
| Core job | Watch the tools and brief the exec. Surface metrics, risks, blockers, and wins; rank what matters; flag stalled work. | Do the communication work. Read incoming messages, draft and send replies, and turn them into assignable tasks and workflows. |
| Channels read | Connects to Slack, email, calendar, Jira, Notion, GitHub, Salesforce, and more to pull status and context. | A universal inbox across Gmail, Outlook, Slack, Google Chat, and Telegram, with Microsoft Teams ingested. WhatsApp, Instagram, and Facebook Messenger are coming. |
| Replies | Drafts follow-ups and tracks the open threads you owe a reply, keeping the exec on top of their own correspondence. | Drafts replies for any teammate across every connected channel, grounded in the brain. Sends on approval, so the work leaves the inbox, not just the exec's. |
| Briefings | A daily one-page brief via Slack or email: what moved, who is blocked, and the top priorities. A core, well-built feature. | Not a chief-of-staff brief. The closest equivalent is the task view: every message scanned for what needs doing, surfaced with priority and owner. |
| Tasks | A prioritized to-do list for the exec, with the most important item on top and a view of what the team owes them. | DoBox: tasks auto-created from messages, on shared team lists. Assign teammates, set priorities and due dates, add labels, checklists, comments with mentions and attachments, and recurring tasks. |
| Automation | Delegates recurring, low-value tasks and runs follow-ups, oriented around freeing the executive's time. | Plain-language workflows triggered by your messages, with conditional logic, loops, autonomous sub-agents, and 32 action types. Tools connect over open MCP. |
| Knowledge | Builds company context by reading documents and decisions, improving its recommendations to the exec over time. | The brain: a knowledge layer with version history that grounds the AI's drafts, answers, and workflows. Auto-updating from your messages is coming. |
| Integrations | Slack, email, calendar, Notion, plus broader stack support via MCP. API access noted as coming soon. | Open MCP. Any MCP-compatible tool can be connected as a workflow step. |
| Trust posture | SOC 2 compliant, no model training on your data, deletion after account closure. A strong, clearly stated security posture. | OAuth connections, inference in AWS Bedrock (your data stays in AWS and is not used to train), message content under dedicated KMS keys so no this+that employee has decrypt access. SOC 2 in progress. |
| Pricing | Positions around ~$99/seat, Enterprise custom, with pricing finalized on a demo. Positioned against the cost of a human chief of staff. | Free during beta. |
- Executive visibility. Bond pulls status out of a dozen scattered tools and gives one leader a clear, real-time picture of what is happening across the company.
- The morning brief. A one-page snapshot of what moved, who is blocked, and the top priorities is a genuinely useful way to start the day and a thoughtful replacement for a status meeting.
- Follow-up tracking. Bond watches every open thread and "I'll get back to you" and chases the reply, so commitments do not quietly drop.
- Ranked priorities. Putting the single most important thing at the top is a simple, opinionated take on a to-do list that suits how executives actually triage.
- Meeting prep and delegation. Bond can prep you for the next meeting, draft follow-ups, and take recurring low-value tasks off your plate.
- A strong security posture. SOC 2 compliant, no training on your data, and clear deletion terms.
- Built for the team, not one exec. Everyone works in the same inbox, and tasks can be assigned, reassigned, and tracked across the whole team.
- It does the communication work. Beyond surfacing what needs a reply, this+that drafts the reply across any channel and sends it on approval.
- A universal inbox. Gmail, Outlook, Slack, Google Chat, and Telegram are live, with Teams ingested and more channels coming. Email is a first-class channel, not just a source to read from.
- DoBox as a shared task surface. Tasks auto-created from messages, on team lists, with assignees, priorities, due dates, labels, checklists, comments, and recurring tasks.
- Workflows. Describe an automation in plain language and run it with conditional logic, loops, sub-agents, and 32 action types, triggered by the messages you receive.
- The brain. A knowledge layer with version history that grounds every draft, answer, and workflow, so the team's output stays consistent.
See what your team's inbox is hiding
Connect your inbox and get a free analysis of the tasks, follow-ups, and open commitments this+that would surface across your channels.
Free during beta · No credit card required