Turning databases into relationships

A national nonprofit had spent years building a loyal community of donors, volunteers, and peer-to-peer fundraisers around a flagship fundraising model people genuinely love. That was the problem. The community knew the model so well that participation had begun to plateau, and the CRM couldn't help, because it wasn't one system. It was Salesforce, Mailchimp, and a proprietary user-management platform, none of which agreed on who a supporter even was, so nobody could see a whole relationship in one place.

Roughly eight months went into replatforming all of it onto HubSpot, then building the program the new system made possible: lifecycle maps for donors, volunteers, and fundraisers, personalized nurture sequences, and coaching emails that met each fundraiser where their campaign actually stood. Someone who had raised nothing two weeks in got a different email than someone closing in on their goal. Meta retargeting synced against HubSpot lists, so lapsed supporters saw consistent messaging in their feed and their inbox, and dashboards kept the whole thing honest week over week.

The list needed as much attention as the platform. It had gone years without real curation, so sunset policies, engagement tiers, and user-quality assessments ran alongside the replatform from the first month. Fewer, better sends to people who demonstrably wanted them is most of what deliverability means in practice, and it's half the story behind every number in this section.

The goal was re-energizing people who had already said yes, not adding names to the list, and the numbers moved the way relationship metrics should: returning fundraiser participation up 18 percent, fundraising page activation up 24 percent, and average dollars raised per participant up 11 percent, with click-through rates climbing from 3.8 to 6.2 percent along the way. The click number is the one I watched. Opens have been directional at best since Apple's privacy changes, so every program on this page was managed to clicks and completed actions instead.

All of it ran inside compliance guardrails that kept moving. CAN-SPAM and GDPR obligations shifted repeatedly across the engagement, and the donor records included minors, which raises the bar on consent, data handling, and what a send is even allowed to say.

An established national nonprofit was launching a new education and advocacy initiative with its own name, audience, and voice. The initiative needed to stand on its own while still borrowing credibility from the parent brand, and it needed marketing infrastructure that would outlive the engagement, not a campaign that would run once and evaporate.

The build started with audience research and worked outward: CRM architecture in HubSpot, twelve audience segments, and nine complete lifecycle journeys covering everyone from first-time visitors to the professional community the initiative served. Eighteen modular email templates gave the team a system rather than a stack of one-offs, and the whole thing shipped with documentation and an implementation playbook written for the people who would run it after me.

It worked as a launch, and it kept working as a program. The welcome series averaged a 58 percent open rate against a nonprofit sector average in the mid-twenties, the educational series held 44 percent opens with a 7.1 percent click-through, newsletter subscriptions grew 36 percent during launch, and resource downloads rose 42 percent. At handoff the team adopted the governance and campaign framework in full, which was the real goal.

A sports gaming platform was heading toward launch with no customers, no data, and no marketing infrastructure. Everything the other projects on this page had to inherit, good and bad, this one was missing entirely: the assignment was a complete HubSpot environment ready to support acquisition, onboarding, engagement, and retention from the first user onward.

That meant designing the invisible parts first. Twenty-two custom contact properties and eight lifecycle stages so the data would mean something, a lead scoring model, marketing attribution, and sixteen tracked conversion events wired through Google Tag Manager. On top of that foundation went fourteen automated workflows, ten email templates, and the onboarding journeys that carry a new user from registration through verification to their first deposit.

Success here wasn't a growth number. The product hadn't launched yet, so the measure was implementation quality: whether the internal team could take the keys and start optimizing on day one instead of building. They could. The engagement closed with dashboards, governance documentation, and training already in place.