The Foundation Under Each Chapter
Nothing in the story was invented to make a point. Every problem Maya hits, and every fix she lands, maps to a real, openly documented operational practice or schema standard. If a chapter raised a question you’re now living with, this is where you go for the how.
Find active tools, templates, and implementation partners at fundcommons.org/ecosystem.
| Chapter | The scene | The method behind it |
|---|---|---|
| 1 | Who do we call? — the lapsed list | Lapsed-donor reactivation (the pain) |
| 2 | Three answers to one question | Donor definitions · ACDM Schema |
| 3 | The number that wouldn’t reconcile | Campaign reporting (forthcoming) |
| 4 | Ruth’s question | The maturity self-assessment |
| 5 | A pledge is not a payment | CRM modeling — commitment vs. transaction · ACDM Schema |
| 6 | We could never leave this system | CRM migration (forthcoming) |
| 7 | The shape | The ACDM vendor-neutral shape — ACDM Schema |
| 8 | Modeled once — households, credits, funds | Crediting · Finance reconciliation · ACDM Schema |
| 9 | The bridge | Finance reconciliation — ACDM Schema |
| 10 | Definitions that don’t drift | Donor definitions · Gift dating · ACDM Schema |
| 11 | The list, re-sorted | Lapsed-donor reactivation — Ecosystem Registry |
| 12 | The week, prioritized | Major-gift pipeline (forthcoming) |
| 13 | The board meeting | Campaign reporting (forthcoming) |
| 14 | Day One, Again | The maturity self-assessment — data governance as a permanent function |
The shape Ruth keeps pointing Maya toward — the open, vendor-neutral Advancement CRM Data Model — is developed in the open at github.com/fundraising-commons/common-data-model. Start anywhere a chapter hurt. Each rung of the maturity model builds on the last.