No Lost Work, No Starting Over

If you run a nonprofit and your fiscal year ended on June 30, you may be in the thick of compiling and drafting your annual report. The books closed a few weeks ago, the numbers are finally reconciled, and the annual report has to be finished before fall, because it has to reach donors ahead of year-end giving. Across the sector, this is annual-report season, and too often one person is carrying most of it.

Jen Allen runs the Friends of the Saratoga Springs Public Library, and she is that person at her organization. I hear versions of her story in conversation after conversation. The director writing the annual report is the same director running the programs, staffing the board meeting, and checking if the social post went out.

Last week I received an email from Jen with a case study attached about building her annual report in BeMo. She knew we were hoping case studies would come out of the beta, but nobody assigned her one. She picked the task, wrote the case study herself in first person, and then went back into the same chat and asked BeMo to shape her draft into something more polished. No one on our team touched a word of it. Her note opened with, "I am truly impressed and having so much fun playing around."

The writing is the small part. The rebuilding is the job.

An annual report can take some nonprofit leaders at least three days to compile. Most of the time goes into rebuilding what the organization already knew.

It is finding the program numbers. It is remembering which version of the impact story you settled on back in March. It is opening last year's report to see how you described a program, then realizing the language no longer matches what that program has become. It is reassembling, out of scattered files and your own memory, nearly everything the organization already knew about itself.

Jen describes the task as sitting "at the intersection of everything that's hard about nonprofit communications: pulling together a full year of work, making sense of the financials, and finding a way to tell our story in a format that feels polished and purposeful."

Pulling together a full year of work. A year of work does not sit anywhere in particular. It has to be pulled.

She Stepped Away for Two Weeks

Her organization's context was already in BeMo's system before she opened a template, because it had read the Friends' website and built her knowledge base out of it. In her words, "when I sat down to work, it already had a solid foundation of who we are, what we do, and why it matters. That alone saved me the usual hour of throat-clearing that goes into starting any major document from scratch."

Then came the interruption that ordinarily makes returning to a document like this feel like starting over. Her year-end financials were not in yet and she was not ready to fill in every section, so she asked whether she could step away and come back.

"It told me that everything is always saved. I could return whenever I was ready and pick up right where I left off. No lost work, no starting over."

A couple of weeks later, financials in hand, she came back and pasted the numbers into the chat.

Important nonprofit documents are almost never completed without interruption. The gala, the grant deadline, the board member who needs something by Thursday. Normally the interruption is the expensive part, because you do not resume, you restart. You spend the first hour back rebuilding what you had already worked out before you got pulled away, and if enough time passes you rebuild it from close to nothing.

No Draft Folder to Hide In

After completing the handful of starter tasks every new beta user gets asked to try first, Jen sent me a one-line email: "I completed all 5 of these tasks. Amazing things in this platform. I am blown away." Then she decided to bring something that actually mattered.

An annual report was a very different test. It is one of the few documents a nonprofit produces that is written specifically to be judged, and nearly everyone who matters to the organization reads it: donors, board members, funders deciding whether to renew, people in the community who have never given a dollar and are deciding what they think of you. There is no draft folder to hide in.

She also knew exactly what it needed to be. She knew what had to be in it, which sections her board would have questions about, and nearly to the hour how long it was going to take her, because she had done it before. Whenever people talk about AI and nonprofits, this is the part that gets flattened, as though the expert is the thing being replaced.

Her judgment was never what was in question. The rebuilding was.

"It didn't just drop the numbers into the report. It made editorial judgments. It highlighted the financial information that tells our story well and thoughtfully suppressed details that a public-facing annual report probably shouldn't lead with. It understood the difference between what a nonprofit needs to document internally and what it should share openly with donors, community members, and partners."

Jen remained the editor and made the final decisions. What changed was that she was reviewing a thoughtful first pass instead of assembling one from nothing.

That distinction, what to highlight and what to leave for internal use only, is not something anybody puts on a features page. It is what made the process feel less like completing a template and more like working with someone who understood the purpose of the document. Her own description of the experience was that it was "like working with a thoughtful colleague who actually wanted to understand the project before diving in."

Her verdict on the result: "The final report was wonderful. It reflected our organization's voice, it handled the financials with care, and it came together in a fraction of the time I've spent on reports in previous years."

By her own account, it took about an hour, against the three days she had budgeted.

Separate Acts of Trust

Getting someone to try software is not the hard part. People open the tab, poke around for twenty minutes, and then the week takes them and they never come back. The hard part is the gap between trying something once and trusting it enough to stop rebuilding the work around it.

I have spent a year and a half listening to nonprofit leaders, and I understand why that gap is wide. Nearly every one of them has a story about technology that was supposed to change everything and instead became one more thing to maintain. Often the software itself was fine. The promise is what broke.

So when Jen's email came in, the hour was not the part that surprised me. It is a real number, it is hers, and I am glad to have it.

What struck me is that she walked away from an unfinished annual report for two weeks, came back, and did not have to reconstruct a thing. Then she trusted the result enough to make it a donor-facing document and wrote a public case study with her name on it and granted us permission to share it. Those are all separate acts of trust.

Start With Something Small

Jen's own case study ends with a paragraph addressed to her peers rather than to us. "If you're an executive director sitting on a to-do list with 'annual report' somewhere near the bottom, the task you keep pushing, I'd encourage you to try BeMo. It met me where I was, worked around my timeline, and helped me produce something I'm genuinely proud of."

I would add one thing. If your annual report is what brought you to BeMo, resist the urge to make it your first test. Start with something small, something where if it goes badly you lose an afternoon and nobody else ever finds out. That is where Jen started, and it is the only honest way to begin with anything you have not worked with before.

The work keeps happening. It just doesn't always build.

Jen left hers sitting for two weeks, came back, and found all of it still there. She did not spend her first hour back remembering where she had been. She started from where she had already arrived. That's where the trust begins.