Loading case study…
Product Marketing & GTM Leader in Technology & Software
When I joined Classy (now GoFundMe Pro, GoFundMe’s B2B nonprofit software business) as its first customer marketing hire, the company was at an inflection point. In my first two weeks, we closed our Series D funding, the founder stepped down and named the new CEO, and we were about to double the product and engineering team and ship 30+ new products and features over the next few years.
I was responsible for building demand generation for the customer base, driving upgrades and expansion for the new post-sales team, and leading product marketing and adoption for existing customers. Our customers were U.S. based nonprofits, with the largest opportunities concentrated in the mid-market and enterprise segments and their multi-person buying committees.
Classy Pay—the company’s payment product and strategic foundation for future innovation—processed about 60% of gross donation volume (GDV); the other 40% ran through multiple processors. Meanwhile, we were about to launch a suite of new payment options, recurring frequencies, and reporting features, and annual nonprofit donation volume would grow from $1 billion to $2.6 billion in my tenure.
Getting customers onto Classy Pay was the moment that mattered: without broad adoption, the next phase of product growth would be harder to unlock.
The company’s objective was to make Classy Pay the default payment solution for the customer base: the fiscal-year target was 85% of gross donation volume (GDV), with a longer-term goal of 100% adoption.
My objective was broader than promoting a feature. I owned the product marketing and customer marketing strategy end to end—value propositions, audience segmentation, messaging, landing pages, email and in-product programs, post-sales playbooks, and the adoption funnel—while being accountable for customer growth, upgrades, expansion, and retention.
The biggest constraint: This was a full migration, not just an adoption campaign. It was equal parts product marketing, B2B sales, and customer adoption.
Customers had to accept contract changes, new pricing and transaction fees, and the operational challenge of moving payment processing inside complex B2B finance and reporting workflows. I also inherited the initiative in my first two weeks, from a previous PMM, with an unfinished product-marketing foundation just as the company was launching a new website, brand, and marketing automation platform.
Spread the word and give this marketer’s work the audience it deserves.
Share this case study with your network
I had to build the engine while plugging into a fast-moving product and engineering release cycle. Timing added pressure: I started in late March, and needed to maximize adoption before November and December, when roughly 30% of annual donation volume came through the platform. Success meant exceeding the 85% fiscal-year GDV target and ultimately getting as close to 100% as possible.
I started by architecting the go-to-market foundation in a multi-tab spreadsheet — or my analogy of "dumping the Legos on the floor." This helps me audit the “from → to” states across product value, existing messaging, channel assets, planned innovation, customer lifecycle, highest-value accounts, and points of friction.
I anchored the strategy in segmentation, targeting, and positioning (STP) — segmenting customers by type, lifecycle stage, processor, revenue potential, buying persona, and objection.
I also flexed the messaging by buyer and moment using a Gain, Logic, Fear (GLF) framework I learned in B2C financial services. For example, a gain appeal focused on improved conversion and a better donor experience, logic highlighted industry trends, ROI and performance data, and fear appeals could spotlight the risk of staying on inferior infrastructure, superior uptime, or fraud protection.
The first real decision was structural. I rejected a one-off launch campaign in favor of an always-on adoption engine. I mapped the funnel from awareness through interest, commitment, activation, realization, and expansion. Then paired trigger moments and contextual entry points—a campaign launch, reporting activity—with a relevant message and one clear next step across web, email, in-product prompts, and post-sales plays.
My operating principle was simple: reinforce the last positive behavior and prescribe the next valuable step.
Mapping the funnel helped me diagnose the market and adapt more quickly. It also exposed a key insight from this project: a “stalled activation” cohort of customers who signed the contract but never turned it on. The problem wasn’t awareness or intent; these accounts had already committed. They were stuck between the signature and the switch. That insight moved the work from “promote a payment product” to “remove the specific friction keeping committed customers from going live and realizing value.”
I built targeted interventions for that cohort—lifecycle emails, in-product messages, ROI calculators, and post-sales re-engagement playbooks. I worked with Ops to operationalize the system across teams: adoption dashboard, target-account lists, and a self-serve landing page and opt-in flow. Weekly cross-functional reviews with product, engineering, post-sales, lifecycle, and operations surfaced blockers such as rate objections and evaluation friction; we responded with new solution maps, promotional packages, and product prompts.
Finally, we made a concerted effort to close the loop with value realization—showing customers before-and-after performance, such as mobile conversion—so activation also built trust for the next product launch and adoption decision.

I built and connected everything using our new martech stack: Marketo Engage handled marketing automation and email campaigns, including the landing page and workflows I built for Classy Pay. That kept every CTA and form submission inside the same system, where it could trigger follow-up by the account team instead of leaving leads in a campaign queue. I also built upgrade, expansion, and marketing playbooks for the post-sales and CSM teams using Gainsight CS.
Salesforce Sales Cloud was the operational backbone. It connected the marketing activity to post-sales contracting and upgrade workflows, while our operations team used it to build the unified Classy Pay adoption dashboard. The dashboard gave teams sortable views by account segment, account owner, and adoption stage, so we could prioritize high-value accounts and see where an account was stalled without reconciling separate spreadsheets.
For contextual in-product messaging and lifecycle prompts, we used Pendo. It let us reach customers at relevant moments inside the product rather than relying entirely on email—for example, when a customer was already engaging with reporting or another related workflow.
AI only played a limited role since this took place in 2021, before it was a regular part of the operating model. The most important capability was not any individual tool, but the connection between systems, strategy, and the internal teams across product, marketing, and customers. Today, I would keep that unified workflow and add AI to accelerate and scale customer insights, message testing, and campaign analysis—but not at the expense of a clear strategy and compounding GTM engine.
We exceeded the 85% fiscal-year target, moving Classy Pay from 60% to 88% of platform gross donation volume (GDV) by the year-end giving season. Within 12 months, adoption exceed 98% of total GDV—making Classy Pay the payment solution for every customer, minus a few edge cases, and setting the foundation on which all future innovation would be built. That represented more than $1M ARR from contract upgrades and millions in annual transaction fees.
The work also changed how the company managed adoption. “Stalled activation” became a named stage in the funnel, and “customer value realization” became a core principle in how I approach product marketing.
Most importantly, the engine became a reusable model that helped fuel the growth and success of the many product launches to come. This was a fun project and the result was a company-wide effort, so the internal alignment and cross-functional operating cadence we established were keys to success. Our jobs as marketers is to own the diagnosis, strategy, sequencing, and cross-functional alignment needed to turn a hard migration into near-total adoption.
Product Marketing & GTM Leader in Technology & Software
Founder at Dusted
Anna Startseva set out to launch ServiceNow’s AI-native ITSM solution as a solo PMM. She aligned stakeholders, researched buyers, built a Messaging House, and used grounded AI tools to scale messaging, enablement, sales Read more
Senior Manager, Marketing Operations in Technology & Software
The author set out to eliminate missing event and webinar context by tracing approvals, connecting intake, Asana, Google Drive, Slack, and Dust, and deploying agents to distribute briefs, update tasks, and escalate unres Read more
Senior Manager, Marketing Operations in Technology & Software
The author set out to connect Asana’s project planning with Slack’s existing conversations, reducing missed updates and manual follow-up. They linked projects to channels and built Dust workflows to create channels, surf Read more
Comments
No comments yet. Be the first to share what you think.