Client Case Studies
Associations don't hire consultants for effort. They hire them for results. Here's what that looks like in practice — real engagements, specific outcomes, no filler. This library grows with every engagement. Watch this space.
-
Most AMS migrations don't fail because of the technology. They fail because the data going in was never clean, consistent, or fully understood to begin with.
jnsankey Consulting was engaged by a consultancy as the project lead responsible for preparing their clients for successful AMS data migrations — ensuring that what moved into the new system was accurate, structured, and ready to perform from day one.
The problem
Each client arrived at migration with the same underlying condition: departments operating from disconnected, outdated spreadsheets that were unreliable the moment they were exported. No one had a complete, authoritative view of their own customer data — and without that foundation, a migration isn't a fresh start. It's just moving the mess.
-
A national association engaged jnsankey Consulting after a critical AMS billing implementation stalled — leaving staff overwhelmed, member data compromised, and leadership losing confidence in both the system and the project.
Upon entry, the scope of the problem became clear immediately: 827 erroneous invoices had been generated, ledger accuracy was compromised, membership statuses were misaligned, and no documentation existed to guide resolution. The internal staff lead was new to the role, unfamiliar with the AMS's data model, and had no structured process to work from.
-
The organization already had the answers. They just didn't know it.
Their AMS contained a fully built executive dashboard — real-time membership retention, attrition, revenue, events, publications, certifications, and renewals — sitting unused because no one on staff understood what it showed, how it was populated, or what administrative actions affected the data they were seeing.
jnsankey Consulting was engaged to close that gap.
-
The Problem
Not every membership model fits neatly into an AMS out of the box. For one national trade association, organizational membership came with a level of structural complexity that required more than standard configuration — it required careful translation of business rules into technical logic, and rigorous testing before any of it reached the client.
The membership structure worked like this:
A parent company held the primary organizational membership.
Subsidiaries of that parent could join independently under a tiered membership model.
The tier — and therefore the dues amount — was not self-reported. It was driven by each subsidiary's confirmed annual revenue.
On paper, this sounds straightforward. In practice, configuring it inside an AMS required the system to correctly associate subsidiaries to their parent, apply the appropriate revenue tier, calculate dues accordingly, and handle the full renewal cycle without breaking the relationship logic. Any misconfiguration would mean members being billed incorrectly, relationships not recognized, or revenue data failing to drive the right outcome.