Customer Education

When software shipped as a box, the vendor taught each customer in person. After the contract was signed, someone drove to the customer's office, gathered everyone in a conference room, and spent a day or two walking through the product. Questions after that came in by phone. With twenty customers each paying tens of thousands of dollars, the arithmetic worked. Teaching never got its own name because it was just one of the steps that came attached to selling.

Subscription pricing broke that arrangement. What a single customer pays dropped to tens of dollars a month, and the number of customers climbed from dozens into the thousands. The time a vendor can spend on one account fell from two days to a few minutes. The amount there is to learn did not fall with it. If anything it grew, because a product that changes every few weeks is never learned once and then done.

Pagedeck went through exactly this. With ten customers, Sofia shared her screen with each new team for thirty minutes and walked them through setup. At three hundred customers there were not enough hours in the day. The inbox carried the same question forty times a month — how do you split permissions across a team — and Sofia wrote the answer forty separate times. Hiring one more person only moves the wall: at six hundred customers the team is back where it started. Any approach that scales explainers in step with accounts stops working at some point. What gives out is the ratio. Thirty minutes per new team is manageable when four teams sign in a week; at forty signings a week the same promise needs twenty hours before anyone answers a single question.

The harder problem is that customers who never learn the product leave without saying anything. A customer who complains at least tells you what is wrong. A customer who uses half the features because nobody showed them the other half says nothing at all. They get half the value, and at renewal they close the account with one sentence about not using it as much as they expected. When Pagedeck went back through its first year of lost accounts, more of them had left because they did not know a feature existed than because a feature was missing.

Customer education answers both problems the same way: take the explanation out of a person's head and put it into documents, recordings, and courses. One good piece of guidance stops hundreds of identical questions from ever reaching the queue, and the share of questions resolved that way — solved by the customer, never filed — gets counted on its own as ticket deflection. Those unfiled tickets save the customer's time as much as the vendor's, since a two-hour wait for a reply turns into a thirty-second search.

Customer success splits the post-sale world into seven strands: roles, lifecycle, health, support, retention, metrics, and education. The first six decide where a person's attention goes. Education reduces how much attention is needed at all. That is also why it pays back late. Writing twenty articles this month does not lower this month's ticket count; it shows up two or three months later as a question that stops arriving.

Education is densest during customer onboarding, the first few weeks spent getting a new account to a working state. It does not end there. Even after the product settles into daily work — the stage called adoption — the admin quits, a new hire joins the team, a neighboring department starts using the tool, and the product itself keeps shipping features. Someone is always learning it for the first time, which makes education less a project with an end date than a piece of machinery that has to keep running.

Four terms sit under customer education, and all four belong to one strand: format. They differ not in what gets taught but in what the teaching is packaged in. Two questions separate them. Does the teacher have to be present, and how many people does one unit of effort reach?

1. Training session — a scheduled lesson run live by a person. The customer joins at an agreed time, watches a screen, and asks questions on the spot. It is the most expensive format of the four, and in exchange it is the only one that adapts. Ask what the customer plans to use the product for, build the examples out of that workflow, and comprehension arrives much faster. Its limits are that reach stops at whoever showed up and nothing survives the call, so teams save it for the first weeks of a contract and for the launch of something large.
2. Help document — written instructions for one feature. The customer searches at the moment of need, reads, and leaves, so nobody has to be present. One article keeps working for years until the feature changes, and it costs the same whether ten people or ten thousand read it. A handful of articles can circulate as links; several hundred create a finding problem of their own, which is why teams put them behind categories and search in a knowledge base. The catch is upkeep. Publishing an article is cheap and keeping it true is not, and a library nobody prunes fills up with instructions for screens that no longer exist.
3. Release communication — telling existing customers what is new and what changed. The first two formats teach people who do not know yet; this one updates people who already did. It prevents two failures at once. One is a new feature nobody notices. The other is a button that was there yesterday and gone today, which sends a wave of tickets. When a release changes a screen, the announcement has to go out before the deploy. Reverse that order and customers conclude their own account is broken.
4. Certification — a course and an exam that formally recognize how well someone knows the product. Where the other three push knowledge from the vendor toward the customer, certification builds an expert inside the customer's own company. At an account with three hundred users, two certified admins absorb most of the questions before they ever reach the vendor. The cost is the steepest of the four: course material, exam questions, a passing bar, and a rewrite of all of it every time the product moves. Below a certain customer count that investment never comes back.

The four are not a menu of alternatives. They feed each other in a line. Questions that keep coming up in sessions become the list of articles to write, articles accumulate into the material a certification course teaches, and every release announcement sends someone back to revise those articles. Leave one link out and the next one spins. Pile up documents without release communication and customers find instructions that no longer match the screen; a customer burned once by a stale article stops searching and files a ticket instead.

Which format to build first is decided by customer count and by what one customer pays. A product with thousands of accounts at tens of dollars a month has no room for a person per account, so documents and announcements come first. A product with fifty accounts paying six figures a year can afford people in sessions and a certification track. A company with both kinds of customers, as Pagedeck has, splits the approach: free teams get articles and in-product guidance, enterprise accounts get sessions with a named person in the room.

"This question came in eleven times this month. Let's write the article instead of covering it in another session."

A question that repeats is a signal to move the answer out of a person and into a document.

"The permissions screen changes in next week's release, so the announcement goes out before the deploy. Flip that order and Monday is all tickets."

A request to treat education as a step ahead of shipping rather than cleanup behind it.

"This account has two certified admins, so we barely hear from them."

Move the teaching inside the customer's company and the questions stop there.

At Pagedeck the phrase comes up most in the quarterly education review. Sofia brings the twenty most common questions from the previous quarter's tickets and checks each one against existing guidance. Anything with no article goes on the writing list. Anything that has an article and still generates tickets gets handled differently: the problem there is not the explanation but the path to it, so instead of rewriting the article the team looks for where to surface it. Mia finds that spot in the product and hands it to Theo.

Last quarter six of the twenty were questions that already had articles. All six came from the same setup screen, and that screen had no link to help of any kind. After a single inline link was added, filings for those six questions fell by more than half the following quarter. Grace uses the meeting to test one tradeoff every time: another person on education versus another person on support. The answer comes from ticket volume that disappeared and the hours those tickets used to consume.

The most common mistake is treating customer education as document production. Articles are the visible output, and article count is an easy number to report progress against. An article nobody reads is the same as no article. When the moment a customer gets stuck and the place the explanation lives are far apart, the customer files a ticket rather than searching. Left alone, this produces a library of four hundred articles alongside a ticket count that has not moved, and an education budget that is hard to defend the next time it comes up. The number worth tracking is not articles written but people who read one and did not write in. That number is harder to collect, since it counts an event that failed to happen, which is exactly why teams fall back on the easy one.

The second mistake is thinking education belongs to the first few weeks. Learning sounds like a beginner's activity, and the heaviest lifting really does happen right after signing. But new beginners keep appearing inside the customer's company. Admins leave, new hires arrive, an adjacent team picks up the tool. The product does not hold still either — six months is enough to change several screens. Teach once at the start and walk away and a second-year account ends up using a year-old version of the product. That surfaces at renewal. When a customer says they only use a few features for the price, the underlying fact is often that nobody told them about anything shipped in the last twelve months.