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.
If you cannot say what is in your pipeline right now, you are not behind and you are not alone. It is one of the most common things a development leader runs into, and it is rarely about the software.
The spreadsheet was doing two jobs at once: holding the friction and holding the knowledge. Automating the follow-up can oversaturate the people you were carefully tending. The wrong system does not just fail to help; it quietly erases the thing that was generating the growth.
The development director could not fully answer the board’s question about the pipeline because the data was in two CRMs, three spreadsheets, and a pile of handwritten notes from the gala. The system had not broken that week. It had been broken for a while, and that week was when the cost happened to be sitting at the head of the board table.