this+that for marketing teams
You planned the campaign. Nobody planned the week
A campaign lives in a plan, but running it means messages arrive from every direction: the agency asking which headline won, legal wanting one more look, a partner proposing a co-marketing slot, a founder forwarding a competitor’s launch. this+that reads those as they land, turns each into tracked work with an owner, and keeps a link back to the message it came from.
The plan is tidy. The week isn’t
Your calendar says this is launch week. Your inbox says the agency needs three approvals, the designer is waiting on brand feedback, a journalist has a deadline tomorrow, and somebody wants to know why last quarter’s webinar landing page is still live. None of that is in the plan, and all of it has to happen.
Marketing takes more inbound than most functions, from more directions, and and almost none of it is structured. Agencies, freelancers, partners, press, and every internal stakeholder with an opinion about the homepage. The plan tracks the campaign. Nothing tracks the traffic around it, so it lands on whoever opens the mail.
One list for everything the campaign generated
DoBox reads across the mailboxes and channels your team already uses and pulls the open items out of them, whether that’s an approval the agency keeps chasing, a partner request nobody answered, or a correction someone asked for twice. You’re not entering tasks by hand, and nothing depends on the message having been flagged when it arrived.
Each item carries an owner and a link back to the original thread, so the reason a headline changed is one click away rather than a question in Slack. Work that belongs to the agency or another team goes to them from the same view.
Campaign routine that stops needing a person to start it
You describe a workflow in plain English and it’s running in minutes. Every step that sends or publishes anything can wait on approval. Some that marketing teams reach for first:
What you already tried, and why you stopped
Marketing accumulates decisions faster than it records them. Which channel you tested and dropped, why the pricing page says what it says, what the agency was told about tone, which claim legal will not approve. That knowledge lives in threads and in the heads of whoever ran it, and it leaves when they do. The Brain holds it in a shared layer that workflows update as the work happens.
The channel you already killed
Every marketing team relitigates a dead channel eventually, because the reasoning lived in one thread nine months ago. A page per channel, kept current by the work, means the next person reads the result instead of repeating the test.
Positioning and claims, in one place
What the product does, what it doesn’t, the wording legal signed off, the numbers you can quote. Both people and workflows read from the same page, so a drafted reply carries the current claim rather than last quarter’s.
It sits alongside your systems of record
Your CRM, your analytics and your CMS stay where they are, and the Brain holds the operational context around them: the reasoning, the exceptions and who agreed what with whom.
It reaches the tools marketing already runs on
this+that ships twenty connectors, and several serve marketing directly: Windsor.ai for marketing data across 325+ sources including Meta, Google and TikTok Ads and GA4, Meta Ads for campaign reporting, Canva and Figma for assets, HubSpot for contacts and campaigns, and Tavily for web search. this+that also supports arbitrary connectors beyond those, so a tool your team already pays for can drive a workflow once it publishes one.
Ask across the reporting you already have
Windsor.ai reaches 325+ marketing sources, so a workflow can answer a spend or performance question inside the thread that asked it, rather than sending someone to a dashboard to screenshot an answer.
Assets where the request lands
Connect Canva and Figma and a workflow can find the asset a request is about and attach it, instead of the request sitting until someone goes looking.
It runs the other way too
this+that exposes its own connector, so an agent your team already uses can read and write the task list directly.
Your campaign tools run the campaign, not the week around it
Marketing automation platforms run sequences you’ve designed against lists you’ve built, and they do that well. They have nothing to say about the agency thread, the legal review, the partner request or the journalist on deadline, because none of that is a campaign step. this+that reads what arrives and triggers the workflow you built, so the coordination starts from the message rather than from somebody getting to it. A person approves anything that sends or publishes, for as long as you want that. For work that runs on a file rather than a SaaS tool, a deck or a spreadsheet of results, you can hand the task to an agent on your own machine, which currently means an Apple Silicon Mac, with Windows and Linux in progress.
Find the approvals and requests you’ve already read past
Connect a mailbox and watch them come out as tracked work, each one linked to the message it came from. Free during beta, no credit card required.