Bay Area Youth Foundation, a Bay Area faith-based youth nonprofit, was hiring a Director of Development. Most candidates would walk in with a slide deck. I walked in with the working version of the role.
Bay Area Youth Foundation, a forty-two-year-old faith-based youth nonprofit in the Bay Area, wanted to double annual fundraising from $1.5M to $3M across a four-year arc and was hiring a Director of Development. The existing development infrastructure was a spreadsheet and a CRM that nobody on staff fully trusted. The board needed a credible operating plan. The team needed a daily cadence. The major-donor pipeline needed real architecture.
Most candidates were preparing slide decks about what they would build. I built the working version of what the development office could look like on day one of the role. Solo. Seven days. End to end.
Four artifacts, each tied to a specific operating function the new Director would have to run from day one.
Weekly operating review built in. Donor retention, segment mix, pipeline coverage, and major-gift cadence visible in one view. Designed for a Monday-morning glance with the Executive Director.
Artifact · 12-slide deckTwelve-slide deck designed for $50K to $250K major-donor conversations. Covers the case for the next year, the operating plan behind the goal, and the specific commitments the donor's gift unlocks.
Artifact · donor CRMAirtable architecture with relationship + giving history schema. Donor segmentation, moves-management staging, and an inbound-touch tracker. Auditable, exportable, and scalable beyond seventy-five donors without breaking.
Artifact · operations playbookOperating cadence for the new Director: donor touch frequency, board reporting rhythm, major-gift moves-management protocol, and the recurring giving program activation sequence.
The thesis was simple. Walking in with the working version of the role beats walking in with a slide deck about the role. Every time. It signals four things at once:
That you build instead of describe. That you can ship complete artifacts in a real timeline. That you understand the operating cadence the role will demand from day one. And that you treat the pre-interview moment the way you would treat the first thirty days of the role itself — as an operating problem, not a sales pitch.
The seven-day window was the constraint that made the work meaningful. Two weeks of build time would have been a strategy memo. Seven days forced every artifact to be tied to a specific operating function. The constraint produced the architecture.
Three things stayed with me from the build. The pre-interview moment is itself an operating problem. Treating it that way changes what you produce and how the recipient receives it. Mission-driven settings respond to operating discipline the same way commercial settings do. The vocabulary is different. The structure isn't. The architecture of a development office is the architecture of any operating function: identify the constraint, install the controls, build the cadence, measure what compounds.
The Bay Area Youth Foundation case study sits next to the corporate operating work in the same way the eighteen-year community thread sits underneath my career. Same operating method, different setting.
The corporate case studies live at Hana Group and Zareen's. The lessons section on the homepage pulls patterns from this build and four others. The full story page tells how this chapter fits into sixteen years.
To talk about operating roles where this kind of build discipline applies, start the conversation.