The Situation
When Michigan Virtual adopted HubSpot as its marketing automation platform, the organization had something most nonprofits would be happy to have: a large and growing list of contacts. What we didn't yet have was intelligence. We knew who was in the database. We didn't know who was still active, what they cared about, where they were in a buying relationship with us, or how to reach the right person with the right message without burning goodwill in the process.
K-12 marketing has a particular complication that makes this harder than it sounds. Roughly 20% of school staff change roles, change schools, or retire every single year. A contact database that isn't actively maintained doesn't just get stale. It gets expensive. HubSpot charges by the number of marketing contacts, and bounced emails hurt sender reputation. List decay is not a passive problem. It is an active cost.
My job, as I grew into full ownership of the platform, was to turn HubSpot from a place where contacts lived into a system that actually told us something useful about our audience, our pipeline, and where our attention should go.
The System
What I built in HubSpot wasn't a single project. It was a set of interconnected systems, each solving a specific problem, and each feeding the others. Here is what that looked like in practice.
Built workflows to automatically reclassify contacts as non-marketing when they unsubscribed, bounced more than once, or hadn't opened any of the past 12 emails. This kept the database clean, the sender score healthy, and the billing under control. No manual intervention required.
Created a custom field taxonomy covering blended learning, artificial intelligence, remote teaching, summer school, research, and more. Automations applied those tags based on pages visited and links clicked. Every interaction taught us something. Contacts self-sorted into warm lists by showing us what they cared about.
Built persona definitions for teachers, students, parents, and administrators, anchored to a newsletter signup form added to every page of the site. Custom behavioral fields tracked offline touchpoints too: tradeshow booth visits, in-person trainings, event attendance. The database knew not just who someone was, but how they had engaged.
Developed a lead scoring model in close collaboration with the sales team, calibrated against what we actually knew about conversion behavior. Scores reflected site engagement, content consumption, and product-line interest so sales could prioritize outreach by signal rather than by gut.
Built distinct pipelines for each of Michigan Virtual's revenue-generating business units, with real dollar values attached to each deal stage. When a deal was won, the school or district was marked as a customer and a workflow automatically applied that status to every associated contact. Anyone in the organization could see at a glance whether the person they were talking to came from a customer account.
Owned the monthly newsletter sent to 30,000+ educators, one of the organization's highest-converting marketing channels. Each department competed for placement because newsletter features routinely drove the largest single-month spikes in registrations and sales. Managed the editorial process across the full marketing team, serving as liaison to two departments myself while maintaining final proofing authority.
What It Made Possible
The individual systems mattered less than what they enabled together. Once interest tags, lead scores, and pipeline data were all living in the same place, the conversations with the sales team changed. Instead of "here's a list of schools we haven't worked with," I could say "here are the contacts from that district who have been active on our site in the past 90 days, specifically in the product lines your team is targeting, and here's how warm each of them is."
The goal was never to have a clean CRM. The goal was to give the sales team an unfair advantage in conversations they were already going to have.
On the marketing side, the interest-based segmentation meant we could protect our most valuable personas from receiving anything irrelevant. Superintendents and principals had outsized influence over purchasing decisions, and burning them with a misaligned email was a cost we couldn't afford. The tagging system meant we only reached them when what we were sending was genuinely worth their attention.
The pipeline visibility worked the same way in reverse. I could surface $80,000 worth of deals sitting idle at the stakeholder approval stage and hand that directly to my sales counterpart, who could then redirect their team's attention before those deals went cold. The customer classification system extended that visibility further: when a deal closed, every contact tied to that school was automatically marked as a customer. Anyone in the organization, from customer care to product teams, could see relationship status without running a report or asking marketing. That kind of real-time intelligence didn't exist before we built it.
Adoption & Training
Technical infrastructure is only as valuable as the people who can access and act on it. I developed org-wide HubSpot training and onboarding materials so that staff across departments, not just the marketing team, could pull the data relevant to their role without needing to ask someone to run a report for them. Leaders could check pipeline health directly. Department heads could see how their content was performing. The CRM stopped being a black box that only marketers understood.
That kind of democratized access changed how the organization related to its own data. It also meant that HubSpot governance fell on me in a meaningful way. Maintaining the integrity of a system that many people were now touching required clear conventions, workflow logic that could survive human error, and enough automation underneath that the database stayed clean even when individual users didn't think about it.