What we shipped
We have been quiet for a while. This is the one we were waiting to ship.
Dreamimpact takes the context engine behind Dreamwriter and points it at one thing: high-touch donor stewardship, at scale. It turns donor data, program outcomes and your organizational context into personalized impact reports, donor updates and acknowledgments, and meeting briefs.
That is the short version. The longer version is an argument about a tradeoff that nearly every development shop has quietly accepted, usually without ever naming it out loud.
The choice nobody wanted to make
Ask a development director how they steward donors and you will hear a version of the same answer. The top tier gets people. Everyone else gets a program.
The top tier, meaning the major donors, the board members, the handful of families whose gifts move the budget, gets real attention: a letter someone actually wrote, a report built around the fund they care about, a call before the ask. It works, because it is genuinely personal.
Everyone else gets the newsletter. Four sends a year, one story for fifty thousand inboxes, a subject line vague enough to apply to all of them. It scales, because nothing in it was written for anyone in particular.
Those are the two options, and each fails in the opposite direction. Manual personalization is high quality and low volume. Automated outreach is high volume and barely relevant. Every organization picks a point on that line and then lives with whatever it gave up.
What is worth noticing is that the tradeoff was never really about writing. Nobody chooses the newsletter because writing one donor a specific letter is hard. They choose it because writing forty thousand specific letters is impossible, and because the material required to write even one of them well is scattered across a CRM, a program report, a grant narrative, and somebody’s memory of a site visit. The bottleneck was never the sentence. It was assembling the context behind the sentence.
Your CRM knows who. This knows what to say next.
That distinction is the whole design.
Your CRM is very good at the who. It knows the donor’s name, their giving history, the fund they gave to, when they last opened an email, which event they attended in 2019. It is a system of record, and it records faithfully.
What it does not do is tell you what to say to them next. That requires holding a donor’s history next to what their money actually touched, in the language your organization uses, at the length the moment calls for. That is a different problem, and it is the one Dreamimpact was built to solve.
So the product starts where the record ends. It reads the donor’s relationship with you, the outcomes of the programs they funded, the stories your team has already approved, and your organization’s own voice and guardrails. Then it drafts what a person would have written, if a person had the hours.
What it actually produces
Four things, all of which already sit somewhere in your calendar, and none of which you currently have time to do well for everyone:
Impact reports, built around what a given donor funded rather than summarizing the whole organization.
Donor updates, sent between asks, connecting a specific supporter to a specific outcome.
Acknowledgments, fast enough to land inside the window where they still read as gratitude rather than administration.
Meeting briefs, so whoever walks into a donor conversation knows the history without spending an afternoon reconstructing it.
The pattern is the same in all four. The information was already yours. What was missing was the time to turn it into something addressed to one person.
Four effects follow, and they are worth stating plainly, because they are the actual case for doing any of this. It scales high-touch stewardship, so every donor can get major-gift-level attention instead of just the top tier. It drives emotional engagement, connecting each donor to the programs, outcomes and stories they actually care about. It makes every message relevant, replacing broad-based communication with individualized stewardship. And it supports retention and lifetime value, because stronger relationships are what produce repeat and recurring giving.
Four to five months, or the same week
A real impact report, the kind with verified numbers and a design pass and three rounds of approval, typically takes four to five months from first data request to delivery. With Dreamimpact, a first draft arrives in minutes.
It is quick, and that matters. But speed is the side effect.
The point is that the donor who gave $250 gets a letter that reads like it was written for them, because it was. That donor is not a rounding error. They are the base of the pyramid your major gifts sit on top of, the supporter most likely to lapse quietly, and the one no organization has ever had the hours to write to properly. Compressing the production cycle only matters because of what it makes affordable at the bottom of the file.
One note on what this is not. Nothing publishes itself. Dreamimpact is built around source transparency, controlled inputs, direct editing, and human approval before anything reaches a donor. The draft arrives already inside your guardrails, which is what turns a three-week review into a fifteen-minute one. The judgment stays with the person who knows the donor.
The beta is capped at fifty teams
The founding beta is open now, limited to the first fifty paid reservations at $99 per month billed annually ($1,188 per year), or $120 per month billed monthly, regularly $200 per month. Billing begins October 5, when onboarding starts. There is a free waiting list behind it if you would rather watch first.
https://dreamwriter.ai/dreamimpact/
It was shaped by the universities, independent schools and mission-driven foundation in our early access program, and their feedback is a large part of why the product is as narrow as it is.
And if this is not for you, it may well be for someone you know. A board you sit on, a school, a foundation, anyone who has to thank donors properly and never has the time.
