I started ARYS Intelligence because I kept watching associations and nonprofits make the same architectural mistakes I had already seen, and fix, in other industries. The patterns are not new. The stakes, for member-driven organizations, just happen to be higher.
The short version of the resume: twenty-five years across enterprise technology, beginning in small-business consulting and e-commerce, then ERP and CRM implementation in foodservice distribution, then a $125M enterprise IT program in industrial manufacturing and distribution, and most recently leading data-platform and digital-transformation work inside large membership organizations. Along the way I have built the data warehouses, stood up the lakehouses and real-time pipelines, implemented enterprise CRM and ERP platforms, and shipped production AI: recommendation engines, demand forecasting, and LLM-based assistants that actually made it past the demo.
What ties it together is a bias toward architecture over tooling. The organizations that struggle are rarely missing a product. They are missing a coherent way for their systems to share a single, trustworthy view of the people they serve. That is as true for a 50,000-member association as it was for a $125M distributor.
What I work on now
ARYS is a practitioner-led consultancy for associations, nonprofits, and mission-driven organizations. The throughline of the writing on this site is a single argument: the AMS-as-monolith era is structurally finished, the data warehouse is becoming the system of record, and Member 360 is an operating model rather than a project. AI only pays off once that foundation exists.
I write about all of this weekly in From the Mind of Ravi Rooprai, and at length in the perspectives. Both are written for the people making the architectural decisions, not the people selling them.