Funding Architecture

Development built as a system: donor pipeline, grant calendar, matching machinery, restricted-fund discipline.

In most organizations, development is a person and a season: one set of relationships, one annual event, and a spike in the giving chart that the rest of the year lives on. When the person leaves, the pipeline leaves with them. This is the dysfunction the firm treats in founder-led companies, a systems problem misdiagnosed as a talent problem, and the cure is the same: specify the motion as workflow, and let machinery carry the parts that are structure.

Specified, development looks like this: a donor pipeline with stages, owners, and next actions rather than a spreadsheet of names; a grant calendar worked like a deal calendar: deadlines, letters of intent, and reporting obligations tracked as commitments instead of discovered as emergencies; corporate matching run as machinery, with eligibility checked inside the gift process rather than left to donor initiative; lapsed donors treated as a recoverable asset with an owned re-engagement motion, not an embarrassment nobody mentions.

Underneath it sits restricted-fund discipline: every restricted dollar traceable from pledge to expenditure, so the organization can demonstrate compliance before an auditor, a foundation, or a skeptical major donor asks. This is the fundraising infrastructure the practice promises, specified line by line, with the ledger to show it.