The Challenge
A community college with 1,000 users purchased our basic MFA package for $50K. It was one of the smallest accounts in my portfolio, and conventional wisdom would have deprioritized it. But the college was part of a 15-campus state community college system with shared IT governance, and I saw the potential for the small win to cascade.
The Approach
I invested in the small account as if it were a strategic account. I ensured their deployment was flawless, provided extra training sessions, and generated a detailed ROI report at the 90-day mark. The results were impressive: help desk tickets dropped by 55%, student satisfaction with IT services increased by 30%, and the college achieved compliance with their state cybersecurity mandate ahead of schedule.
I then asked the college's CIO to present these results at the quarterly system-wide CIO meeting. He agreed, and I helped him prepare a compelling presentation with before-and-after metrics. The other 14 campus CIOs were immediately interested, and the system CTO proposed a system-wide standardization initiative.
The Result
The system-wide initiative was approved, and deployments rolled out to 12 additional campuses over the following year. The total contract value grew from $50K to $400K, with the remaining two campuses scheduled for the next fiscal year. The community college system became our model for education land-and-expand, and the original CIO became a regular speaker at our events.
Key Takeaway
Small accounts in large systems are Trojan horses for massive expansion. Treating every deployment — regardless of size — as a potential reference account creates opportunities that no amount of top-down enterprise selling could achieve. In education, one campus success story can unlock an entire system.
Get new posts in your inbox
No noise. Tactical field notes when something worth sharing comes up.