My longer writing on the shift that’s reshaping associations and nonprofits: composable member stacks, the data warehouse as system of record, AI infrastructure, Member 360 as an operating model, and the case against another AMS migration. I wrote them for the leaders who have to make these calls, and who’ll live with them for the next decade.
The AMS-as-monolith model is structurally finished. Here’s what the most progressive associations are building instead, and why getting the architecture right is the most consequential decision your association or nonprofit will make this decade.
I've watched too many associations pay to migrate to a slightly newer version of the same broken architecture. The AMS-as-monolith model is structurally finished. Here's what the most progressive associations are building instead.
The most progressive associations have flipped the architecture entirely. The warehouse is the spine. The AMS is just one input. Here's why this inversion matters more than any AMS decision you'll make this decade.
Most associations treat Member 360 as a data project to schedule someday. The associations winning at retention treat it as the operating model itself: identity at the center, systems at the edges.
92% of nonprofits use AI. 7% report major strategic impact. Most of the rest are on what the report calls the efficiency plateau. The gap isn't about prompts or models. It's about the foundation most associations have been deferring.
For a mid-to-large association, a traditional AMS migration is a long project that costs well beyond the license quote, and it lands in the same architecture it left. Here's the path some associations are taking instead, one component at a time.
Every perspective on this page started as a real association’s real architecture problem. Tell me yours. The first conversation is free, honest and short.