When the plan is done and the operation is not ready
Every July, development teams do the same thing. They close out the fiscal year, pull the final numbers, and start building the annual fund plan for the cycle ahead. Goals get set. Timelines get mapped. Someone makes a calendar. The plan looks right because nothing is running yet, and when nothing is running, nothing is visibly broken.
Then September arrives.
The CRM has contacts that were never updated after last year’s appeal. The gift officer who owned the mid-level portfolio left in March and the caseload was quietly redistributed to no one. The acknowledgment letter is still the version from 2023. The reporting structure was built around a goal framework that changed when the strategic plan changed, and no one has touched it since. None of this showed up in the plan because the plan was not looking there. It was describing what the organization intends to do. It was not asking whether the operation underneath is ready to carry it. Those are different questions, and most planning processes only ever ask the first one.
Underneath every annual fund are eight systems that either work or they do not. People: who arrives, who exits, and who actually owns what when the dust settles after a transition. Tools: the CRM holding the donor data, the project management system moving work through the team, the AI layer that is either reducing noise or generating more of it. Guides: the SOPs that document how things actually run, the reporting structure that tells you whether you are on track before it is too late to course correct, the content planning system that keeps communications from being built at the last minute by whoever has time that week.
When those eight systems are working, the plan becomes executable. Goals connect to portfolios, portfolios connect to caseloads, caseloads connect to people who are in their seats with the information they need to do the work. The acknowledgment goes out on time because there is a process. The mid-year report reflects what actually happened because the reporting structure was designed to capture it. The new gift officer can carry the portfolio because ownership was documented when the last one left.
When those systems are not working, the plan becomes a description of an organization that does not yet exist. And the gap between the plan and the operation does not show up in July. It shows up in October, when the appeal is behind and the data is a mess and someone is doing four jobs because the person who used to do one of them is gone.
The fix is not a better plan. It is an honest read of the operation before the plan goes final. Not an audit for its own sake, but a specific question applied to each of the eight systems: is this ready to carry what we are about to ask of it? Most of the time, two or three of them are not. That is not a failure. That is useful information, and it is only useful if you have it before September.
If your annual fund plan for the coming cycle is drafted or close to it, this is the right moment to run that read. Not to slow the planning down. To make sure the plan means something when the calendar starts moving.
We work with development teams and operations leaders who are ready to ask that question.
Erin Peshoff is the Founder of Vivid Operational Advisors. She has spent thirty years inside nonprofit operations, helped raise over $100 million for institutional missions, and built Vivid around the operating discipline most strategic engagements skip.
