Ask most customer education leaders what they're proud of, and they'll tell you about their content library. How many courses. How many minutes. The production quality. The variety of formats. The volume of completions.
None of that is the point.
Content is not what your customers need. It's the vehicle through which they might — if everything goes right — get to what they actually need: the demonstrated ability to do something useful with your product.
That's proficiency. And proficiency, not content, is where the real value lives.
The reason this distinction matters right now is that content is getting cheaper by the day. What once took a team of specialists and a six-figure budget now takes a prompt and an afternoon. If your commercial model — or your internal value argument — is built on content production, you are standing on a floor that is quietly being removed.
Proficiency doesn't work that way.
You can't AI-generate a demonstrated capability. You can't automate the moment when a customer proves they can solve a real problem in your product under real conditions.
That moment — and the infrastructure required to create, assess, and credential it — is where the value is. And right now, most customer education teams are charging for the vehicle and giving away the destination.
The Bundle Made Sense Once
For a long time, bundling content and certification was a reasonable model. You built a course. You put an exam at the end. You charged for the package. Customers got a learning experience and a credential in one transaction. Renewal cycles kept them coming back.
It was clean, it was scalable, and it worked.
The problem is that the bundle trained everyone — including your own team — to treat the content as the product. The certification became a ribbon on the box rather than a thing with standalone value. And when AI started making the box cheaper to produce, the whole revenue logic started to unravel.
Here's what the bundle actually obscures: content and certification are not the same thing. They serve different purposes, they require different infrastructure, and they should carry different price tags.
Content is about exposure. It moves someone from unaware to informed.
It can do that through a video, a live session, a sandbox walkthrough, a PDF, or a conversation with an AI tutor. The format matters less than most teams think. What matters is whether the person who went through it can actually do something they couldn't do before.
Certification is about proof. It answers a different question entirely: can this person demonstrate capability under defined conditions?
That requires labs. It requires assessments. It requires someone — or something — to evaluate the output and make a judgment call. That infrastructure is real, and it costs real money to build and maintain.
When you bundle those two things together and charge one price, you end up undervaluing the certification and overvaluing the content. You also make it nearly impossible to build a commercial model that survives the current environment — because you've tied your revenue to the thing that's getting cheaper, not the thing that's holding its value.
Free the Content. Charge for the Proof.
The model worth building looks like this: content is free. Certification is not.
Not free as in cheap. Free as in: the barrier to learning shouldn't be financial. Self-paced video, on-demand modules, community resources — these are low-cost to distribute and high-value to keep open.
But format matters.
A live session isn't as scalable, and the one-time fixed costs look very different from an on-demand video library. A pre-conference workshop, a virtual instructor-led cohort, a hands-on training day — those carry real production cost, real facilitation cost, and real time cost for everyone in the room. Charging for those is not only reasonable, it's expected.
The point isn't that content is always free. It's that the fee structure should reflect the actual cost and value of the experience — and that regardless of format, content can only ever prove attendance or participation. An intentionally designed certification process could prove something worth paying for.
What does a well-built certification actually look like in this model?
It's a self-contained unit. It's tied to a specific version or release of your product. It defines exactly what a certified user must be able to do — not what they watched, not what they attended, but what they can demonstrate. It uses hands-on labs, knowledge assessments, scenario-based problems, and some form of evaluation — programmatic, human, or increasingly agentic — to determine whether that bar has been met.
That is a fundamentally different infrastructure than a content delivery system. And it's infrastructure that justifies a fee.
The commercial logic is straightforward: you're not charging someone to learn. You're charging them to prove it. Those are different transactions, and customers understand the difference intuitively. Nobody expects a university to charge for studying. They do expect to pay for the diploma.
The Career Angle Few Are Playing
Here's where most customer education teams leave significant value on the table.
A product certification that only matters inside your product ecosystem has a ceiling. It's useful to the customer as long as they're using your product. The moment they churn, switch jobs, or move to a different tool, the credential becomes a line item on a resume that nobody outside your user base understands.
That's not nothing — but it's not much either…
Now consider what happens when you align that certification to something the participant already cares about professionally.
- Continuing education credits.
- Project management professional hours.
- Legal or compliance requirements.
- Industry association memberships that require documented learning.
These aren't niche concerns — for a significant portion of your user base, maintaining professional credentials may be a real, recurring obligation.
(They have to get those hours somewhere…)
If your certification satisfies that requirement, you've just changed the nature of the relationship. You're no longer selling access to your product's knowledge base. You're contributing to someone's professional standing. That's a different kind of stickiness — one that survives product switches, org changes, and budget cuts in a way that a product-specific credential never could.
Getting there requires work. Submitting certifications to professional boards for review, maintaining compliance with continuing education standards, documenting hours in formats that external bodies accept.
But it's overhead that transforms a certification from an internal metric into an externally recognized credential. And externally recognized credentials command a real market price.
The companies that figure this out first won't just have a training revenue line. They'll have built something their competitors can't replicate quickly — a certification infrastructure that's credentialed, versioned, and tied to the professional identities of the people who use their product.
That is a moat.
The Cost Argument Works in Your Favor
The most common objection to this model is cost. Labs are expensive. Grading takes time. Credentialing infrastructure doesn't build itself. Board submissions, compliance reviews, versioning certifications against product releases — none of that is free.
That's true. And it's actually the point.
The reason certification justifies a fee is precisely because it costs something real to deliver. Unlike a video that gets produced once and served ten thousand times, a certification infrastructure requires ongoing investment — in the assessment environment, in the evaluation process, in the credentialing relationships. That ongoing investment is what makes the credential meaningful. And meaningful credentials command meaningful prices.
Compare that to the content side of the equation. AI is already compressing the cost of content production. Teams that once required a videographer, an instructional designer, a narrator, and an animator can now produce comparable output with a fraction of that headcount. That's not a criticism — it's a reality. But it means the cost argument for charging premium prices on content is getting harder to make every quarter.
Certification moves in the opposite direction. The more rigorous the assessment, the more credentialed the outcome, the more infrastructure behind the evaluation — the stronger the justification for the fee. You are building toward a higher-value product at the same time content is trending toward commodity.
For leadership conversations, this reframe matters. A training function that says "we need budget to produce more content" is defending a cost center. A training function that says "we have a certification product that is partially self-funding and on a path to profitability" is having a completely different conversation. One is asking for investment with soft ROI. The other is presenting a business.
Even partial self-funding changes the dynamic. Full profitability — which is achievable with the right certification infrastructure and credentialing strategy — changes the conversation at the board level. Not because investors care deeply about training revenue as a line item, but because a training operation that pays for itself signals something about the maturity and intentionality of the customer success function overall.
Proficiency Is the Most Important Thing You Can Build Right Now
There is one more reason this model matters — and it has nothing to do with revenue.
As AI takes on more of the work that humans used to do inside your product, the humans who remain in the loop need to be more capable, not less.
- The person who used to run a report manually is now reviewing what an agent generated.
- The person who used to configure a workflow is now auditing whether the automated version is doing it correctly.
- The person who used to troubleshoot an integration is now the one a machine escalates to when it doesn't know what to do next.
In every one of those scenarios, the human's value is entirely dependent on their depth of understanding.
A surface-level user — someone who completed a course and got a completion badge — is not equipped for that role. A certified practitioner who has demonstrated the ability to solve real problems under real conditions is.
This means the second-order effects of a well-designed certification program are no longer just nice metrics to report.
Reduced support tickets, higher product utilization, stronger word-of-mouth — those have always been the downstream benefits of a capable user base. But in an agentic world, those outcomes become load-bearing. The quality of your certified users determines the quality of the human oversight layer on top of your AI-assisted product.
And someone has to train the agents, too.
The people best positioned to define what good looks like — to create the examples, evaluate the outputs, and course-correct when the machine gets it wrong — are the ones who have demonstrated proficiency themselves. You cannot outsource that to someone who watched a video.
This is why decoupling content from certification isn't just a revenue strategy. It's an infrastructure decision about what kind of user base you're building.
Free content gets people in the door. Rigorous certification builds the kind of customers who can actually grow with your product as it evolves — and who become more valuable to you, not less, as automation takes on more of the routine work.
The teams that understand this now will have a significant advantage over the ones who figure it out later.
This article was originally published on Scaling Trust on Substack.
Founder, CEO
Matt Tidwell is a strategist, creator, and founder of ThinkThru, where he helps teams build education-led customer experiences that scale trust and unlock product value. He also co-founded Care Transformation Studio, a platform reshaping how healthcare organizations access expertise and intelligence.