From capstone pitch to monetized product line
Conceiving, launching, and pricing guided learning paths at an online education platform
Context
A self-paced online learning platform with a subscription model: members enrolled in individual courses à la carte. The catalog was deep, but the experience was a library, not a journey — members assembled their own sequence or didn't.
The tension
The idea had two origins, and the timing of their collision is the story. I had developed the concept of guided learning paths — curated course sequences anchored to a defined outcome — as my capstone in a product marketing certification program. Then our own leadership published a case study on learning paths in the broader education space, with strong completion and retention results. The external proof point now existed, published under our own name — and the product didn't exist on our own platform. Our data told the same story their case study did: members who self-assembled a coherent sequence finished at far higher rates than members enrolling in isolated courses. Meanwhile, the topic was generating real buzz at industry conferences and on social — and no direct competitor had shipped it.
I used the certification's frameworks to build the business case and pitched it to the CEO and board as a new product line. The answer: take charge.
The decision
Two decisions defined the launch, and both were about restraint.
Scope. The full vision — a dynamic, personalized path builder — was a multi-quarter engineering lift on an unvalidated premise. I challenged the working group to define a 1.0 we could ship without it: curated, fixed-sequence paths assembled from existing catalog metadata, each anchored to a clear member outcome. Engineering's footprint shrank from a platform feature to a packaging-and-presentation layer. The custom builder went on the shelf, pending proof.
Pricing. My pitch positioned this as a paid product line, and the intent never wavered. But monetizing an unproven product meant the first data we'd collect was purchase hesitation, not usage truth. So I sequenced it: launch free to all existing subscribers, measure adoption and completion, and let engagement data carry the monetization case. Validate first, charge second.
The build
I assembled a working group across curriculum, operations, and account management — no dedicated team, no new headcount. Curriculum designed the first paths around the member outcomes our data showed people already pursuing. I owned positioning and go-to-market: naming, the messaging hierarchy ("a guided route to the outcome, not another course list"), launch tiering — in-product placement first, email announcement second, account-management talk track third — and internal enablement so support and AM could speak to it on day one.
The results
In the first 90 days, 28% of active subscribers started a path. Path-based completion ran at 41%, against a 23% baseline for standalone course enrollment, and member feedback was strong enough that account management began leading renewal conversations with it.
Then the validate-first sequencing paid off. Six to eight months after launch, we monetized: three paid paths priced at $99–$149 — pricing I set with the curriculum team, scaled to content depth — structured as one introductory path and two specialist paths, with two to three more on the roadmap. The product that launched as a free engagement play became a revenue line, in a market where competitors were still talking about the concept on conference stages.
What underperformed: the email announcement. It drove a minority of initial enrollments; the in-product entry point drove the majority. Members didn't need convincing — they needed to encounter the paths where the decision happens. Placement inside the product beats persuasion outside it.
What I'd do differently
Instrument the path-abandonment points from launch day. We knew who started and who finished; we learned too late where the middle leaked. The 2.0 scope included it because 1.0 didn't.