The problem wasn't one campaign. It was the system around the customer.
The platform had a strong product, real credibility with its core users, and years of loyalty. But its digital customer experience had grown around the organization rather than around the customer.
I saw it almost immediately after joining. Signing up as a new user meant receiving three to five welcome and onboarding messages within the first day, arriving independently from different parts of the business. Registration asked 15 to 18 questions before a user could reach the product. Once inside, communication ran on internal calendars, not on what the customer had done.
There wasn't one broken touchpoint to fix. The journey had never been designed as one connected system in the first place, which is close to what I'd now call sequencing debt: every individual message made sense on its own terms, and the failure only existed in the gaps between them.
That mattered more as the market normalized. The platform had been especially well positioned during a period of forced digital adoption; as that structural tailwind faded, product quality and word of mouth alone weren't enough.
Marketing also had limited visibility into what happened after acquisition. Before accepting "demand is just softening" as the explanation, I wanted to understand the experience we were creating.
Start with the journey, not the channel
I made the case for a formal customer journey mapping exercise, then facilitated a three-day, in-person workshop with 15 to 20 people across Product, Sales, Customer Success, Support, Product Marketing, Digital Marketing, and senior leadership.
We mapped the journey by persona and stage, connecting entry and exit criteria, internal ownership, the teams and systems touching the customer, available data, known gaps, and desired future-state capability at each point.
The exercise made the fragmentation visible in one place. Communications overlapped. Ownership shifted depending on the touchpoint. Important behaviors went unmeasured. Signup carried unnecessary friction. Teams could hit their own goals with no way to know whether the customer's overall experience was improving.
We prioritized the resulting gaps by expected impact, effort, timing, and the data we'd need to know whether each fix worked. The output wasn't just a map, it became a shared remediation backlog with real owners.
Redesigning ownership around the customer
One of the first changes was deceptively simple: decide, together, which team should own which message.
Product, Marketing, and Customer Success had each been messaging new users independently. Every individual message made sense; together, they created noise. We split the model into two clearer responsibilities: product owned essential transactional communication, marketing owned the lifecycle, governed by opt-in status, behavioral eligibility, and communication caps.
That took Day 0/Day 1 from as many as five messages down to two required ones. From there, we rebuilt six core lifecycle motions: onboarding, trial, nurture, adoption and education, renewal, and win-back, moving most of them away from fixed time-based sequences and toward actual customer behavior and state. The operating question changed from "how many days has this person been in the trial?" to "what have they actually done, and what do they need next?"
Removing friction before trying to educate around it
The journey work also exposed how much unnecessary friction had accumulated at signup, and how little of the onboarding experience had been designed at all. New users were largely left to navigate a blank canvas and discover the product on their own.
Working with Product, we asked a simpler question of every registration field: does this need to happen before first value? Some fields came out of registration entirely. Other information, previously asked of the user directly, could often be inferred from context instead. That's close to what I'd now call the Setup Absorption Model, though the language came later: the goal was never a shorter form for its own sake, it was refusing to make customers perform setup work the system could reasonably absorb itself.
Signup went from 15–18 fields to 9–10, with only 7–8 requiring direct input, roughly halving what a new user had to manually provide. In parallel, we replaced the blank-canvas start with a guided setup and welcome flow, and rebuilt onboarding to surface relevant education and features based on how someone was using the product, not a fixed script everyone saw regardless of behavior.
Making the lifecycle measurable
None of the touchpoint-level work would matter much if marketing still couldn't see what happened downstream. I led the consolidation of a fragmented martech and data stack into a simpler core built on HubSpot, Segment, and the website, owning the workflow logic, properties, segmentation, lead scoring, and tracking implementation.
The resulting model connected campaign, landing page, trial, product activation, paid conversion, and retention into one line of sight, letting marketing finally answer questions channel reporting alone never could: which onboarding communications correlated with activation, where users dropped between registration and real product use, whether a campaign created behavior beyond what a holdout group would have done anyway.
That work also surfaced years of accumulated CRM debt: duplicate records, conflicting properties, inconsistent lifecycle stages. We introduced standardized definitions, cleaner governance, and audit routines. Subsequent audits showed roughly half as many CRM and data-quality exceptions as before.
The website became a consequence of what we learned
The first site overhaul followed directly from the journey work: more deliberate landing experiences, cleaner conversion paths, consistent tracking, treating the site as part of the lifecycle rather than a standalone publishing surface.
Later, both the data and the broader strategy sharpened. Leadership made a clearer choice about who the platform's primary audience was. I partnered with growth and product marketing leadership on that audience strategy and led its digital implementation: conversion strategy, UX, instrumentation, segmentation, lead scoring, SEO alongside growth, and the core value-proposition pages themselves, with product marketing leading core messaging and me contributing direct strategic and editorial input throughout.
Changing the operating model
None of this holds if the organization keeps working the same way behind the scenes. We introduced recurring cross-functional alignment across product, support, and customer success, moved marketing requests into a structured, visible intake process, and treated major initiatives as scoped work with explicit owners, dependencies, and measurement built in from the start.
The operating assumption shifted from "this is how we've always done it" to "why does this work this way, and what evidence would justify keeping it?"
What actually changed
Internal reporting during the optimization period showed a 37% relative lift in trial-to-paid conversion and a 24% improvement in end-of-trial CSAT. HubSpot audits showed roughly half as many CRM and data-quality exceptions following the consolidation and governance work.
Alongside those numbers: signup inputs roughly halved, Day 0/1 communications consolidated from five to two, six lifecycle journeys got rebuilt around behavior instead of the calendar, and marketing gained a real line of sight from acquisition through retention.
The most important change wasn't the website, the martech stack, or any single campaign. It was making the customer journey something the organization could see, own, and improve together, which is what made the later work possible at all.