You came for the mission, not the follow-up
A handful of people carrying donors, volunteers, the board, grant funders, and the people you serve, with no operations hire to catch what slips. this+that reads what lands across every channel, turns it into tracked work, and drafts the replies for you to approve, so the thank-you, the re-engagement, and the deadline stop falling through.
The loudest thing gets handled, everything quieter slips
A donor gives and deserves a thank-you the same day. A volunteer signs up and needs an answer before they drift. A board member emails a question that has to be addressed before the next meeting. A grant funder sets a reporting deadline three weeks out, and an event needs a dozen small confirmations chased across half a dozen inboxes. All of it arrives while your tiny team is running the program, and there is no operations person to sort it first.
So you handle what is on fire and promise yourself the rest can wait for a quieter week. It does not come. The thank-you goes out late or not at all. The lapsed volunteer is never re-engaged. The reporting deadline arrives before you have started, and the event lives in scattered threads that no one fully owns. None of it was hard work; it just needed someone whose whole job was to watch the follow-up, and on a team your size that someone does not exist.
The operations help you cannot afford to hire
this+that pulls every channel you connect into one place, from Gmail and Outlook to Slack, Google Chat, and Telegram, so donor mail, volunteer questions, board threads, and funder messages stop living in separate inboxes. Each incoming message can become a task in a shared DoBox list with a due date attached: a donation to acknowledge, a volunteer to onboard, a grant report to file. You can keep separate lists for donors, volunteers, and grants, assign items to whoever owns them, and see everything still outstanding in one view instead of buried under everything newer.
Then it drafts the replies. A volunteer asking how to get involved, a member asking about a program: the answer comes back grounded in your own policies and program FAQs, written in your voice, waiting in your queue. You write those facts down once, in a shared knowledge page called the brain, and this+that uses them rather than guessing. That keeps replies consistent no matter who is covering the inbox that week. Nothing sends until someone approves it. You read the draft, fix a line if it needs one, and hit send, and once you trust how a kind of message gets handled, you can let those go out on their own.
Automations built for how a small nonprofit actually runs
You describe what you need in plain English and this+that sets it up and runs it. These are the kinds of things small nonprofit teams ask for, typed the way you would say them out loud.
Tied to the tools you already use, including the ones we are not
this+that is not a donor database, a fundraising CRM, or your accounting system, and it does not process donations. What it does is connect to the tools that do, through MCP, an open standard for letting software talk to AI agents. The donor CRM, the fundraising platform, and the accounting tool you already run: this+that reaches into them and drives them from the same plain-English workflows that handle your inbox.
So a new donor recorded in your CRM can trigger a drafted thank-you waiting in your queue, and a first-time volunteer can be added to the right list without anyone copying anything over. The work that used to mean jumping between your inbox, your CRM, and a spreadsheet becomes one workflow, started by a message and run for you. this+that ties your messages to the systems you already use, including the ones it does not replace.
A filter sorts mail, this reads it
Inbox filters only move mail around. They cannot tell that one message is a major donor worth thanking today and the next is a newsletter, and the one thing that could tell the difference, a dedicated operations hire, is out of reach on a small nonprofit budget. this+that reads each message, works out what it is actually asking for, and either drafts the reply or opens the task. The follow-up gets handled in the background, and the program work you joined for stays where your hours go.
See what is waiting in your inbox
Connect your inbox and it will surface everything waiting on a reply, from the donor thank-yous to the grant deadlines. Takes under 2 minutes, and there is no signup to do it.