How to Reasonably Raise Course or Consulting Prices Without Losing Users When Content Production Costs Rise
On a Thursday evening in November 2024, I was reviewing accounts at a co-working space in Nanshan, Shenzhen, and discovered that for the same recorded course "From Topic Selection to Finished Video," the per-person delivery cost had risen from about 186 RMB in early 2023 to nearly 310 RMB. It wasn't one big expense, but a string of small holes: outsourced editing went from 45 RMB/min to 70; material licensing changed from annual packages to per-project; customer service went from part-time to full-time; and the extra 2 hours of Q&A in the community each week, which I used to handle myself, now required paying someone 120 RMB/hour.
The course was still priced at 999. On paper it still looked profitable, but when I factored in "my own time" at 200 RMB/hour, the margin had thinned to the point where I dared not promise "lifetime updates." That day I wrote two notes in Excel:
- Keep bearing it = chronic blood loss
- A straight 30% increase = might lose the loudest users overnight, and also lose reputation
Over the next three months, I implemented a step-by-step price increase. The result: recorded course from 999 to 1299, 1v1 consulting from 800/session to 1200/session; old users could renew once at the old price within 90 days; new public-channel customers paid the new price. Three months later: net paying user loss was about 6%, average ticket price rose about 24%, and margin went from "barely sustainable" back to a range where "content can continue to be made." What follows is not theory, but a breakdown of that operation and the practices I now routinely reuse.
Part 1: First Get the Numbers Straight — What Are You Really Passing On
Many people jump straight to an announcement: "Due to rising costs, the course price increases by XX." When users read this, their brains translate it as: "Your problem, my bill."
I prefer to first break costs into four pieces, and only pass on to pricing and value adjustments the portion directly related to delivery quality:
| Cost Item | Early 2023 (approx) | Late 2024 (approx) | Can Users Perceive It? |
|---|---|---|---|
| Finished video (editing/subtitles/packaging) | 80 RMB/course | 135 RMB/course | Yes (quality, update pace) |
| Materials and tool subscriptions | 30 RMB/person shared | 55 RMB/person shared | Weak |
| Delivery and Q&A labor | 40 RMB/person shared | 85 RMB/person shared | Yes (response speed, frequency) |
| Customer acquisition and platform fees | Variable | Higher | No (don't use this as the main reason) |
My view is clear: customer acquisition getting more expensive should not be the main narrative for raising prices on existing users. Acquisition is your business problem; users buy results and experience. What can go into the notification letter can only be changes they can feel: "content is more complete," "Q&A is more timely," "delivery is more defined." The cost table is for you; what users see is a value table.
Another harder lesson:
Not raising prices but secretly cutting delivery (fewer updates, fewer Q&A sessions, template-basedperfunctory) hurts trust more than a public price increase. In 2023 I tried "keeping the price but switching from weekly to bi-weekly updates," and negative reviews and refund intentions went up instead. From then on I decided: better to raise the price and clearly define boundaries than to disguise reduced delivery as "still the same price."
Part 2: 14 Days Before the Increase — Do Only Three Things, Don't Rush the Announcement
### 1. Segment, Don't Do "One Price Fits All"
I split users into four categories (you can adapt based on your CRM or spreadsheet):
- **A High-loyalty old customers**: bought 2+ times or consulting repeat buyers; sensitive to results, relatively insensitive to price
- **B Single-course satisfied but not repurchased**: price-sensitive, need "transition benefits"
- **C Price-sensitive and active in community price-comparing**: most likely to lead the noise in groups
- **D Non-converted leads**: only see the public price, just use the new price
Different groups can have different increase amounts and messaging, but the underlying price rules must be unified, otherwise things get chaotic internally. My final rules were:
- Public page: always new price
- A/B old customers: within 90 days of announcement date, can repurchase/upgrade once at old price
- Already purchased recording: rights unchanged, no retroactive price adjustment
- Consulting: unfinished old packages honored at old price; new contracts from a certain date at new price
Cases from service industries show that segmented communication can keep churn to single digits while lifting profits; my experience matches — the problem isn't the price, it's that "who gets what price" isn't clear.
### 2. Test Willingness First, Don't Ask "Can You Accept a 20% Increase?"
A direct survey almost always fails. When faced with "are you willing to pay more," customers instinctively say no; stated willingness and actual orders are far apart.
I used dirtier but more real methods:
- **Change price only for new customers for 2 weeks** (landing page A/B: 999 vs 1199), old customer page unchanged
- **Add a "standard tier + upgraded tier with extras"**, upgraded tier 25% more expensive, see if conversion collapses
- **Raise consulting price first, course later** — consulting has a shorter decision chain, faster feedback
Two weeks of data (small sample, but directional):
- New customer page 999 → 1199: conversion dropped from 4.8% to 4.1%, but revenue per visitor rose about 8%
- Upgraded tier accounted for about 22%, showing some people were paying for "one extra review + template pack"
- Consulting from 800 to 1000 test: bookings dropped about 15%, total revenue still about 6% higher
The conclusion was enough for me: it's not that you can't raise prices, it's that you can't jump from a "friendly price" to a "scary price" in one step, and you must give choices.
### 3. Add Perceivable Value First, Then Ask for Money
10 days before the price increase announcement, I first launched three "visible" things:
- Added 2 sessions of "2024 Platform Rule Updates" to the course
- Changed Q&A from "irregular" to "every Wednesday 20:00–21:00 fixed session"
- Changed consulting delivery from verbal agreement to a one-page PDF (pre-call questionnaire + 48-hour post-call summary)
Costs did go up a little more, but what users perceived was "service is upgrading." When the price increase was later announced, the narrative became: rules upgraded, price aligned — not "I'm poor, you pay."
Part 3: Step-by-Step Price Increase — My Actual 45-Day Timeline
The table below is the template I later standardized; adjust numbers by your category, but I suggest keeping the rhythm.
| Phase | Time | Action | Scope/Target | Goal |
|---|---|---|---|---|
| Day 0–7 | Preparation | Cost calculation, segmentation, prepare old/new benefits comparison | — | Internal alignment |
| Day 8–21 | Pilot | New customer page/new consulting tier micro-adjustment | +10%~15% | Test conversion and objections |
| Day 22 | Internal finalization | Finalize public price and old-customer window | Course +30% max; consulting tiered | Avoid repeated price changes |
| Day 23 | Announcement | Email + community pin + individual message to A class | **21–30 days** advance notice | Reduce shock |
| Day 23–Effective date | Transition | Old-price window, Q&A FAQ, one-on-onesoothe C class | No "private discount backtracking" | Control sentiment |
| 30 days after effective | Review | Churn, complaints, refunds, new customer structure | — | Decide if second adjustment needed |
On magnitude, my personal standards:
- Cumulative public price increase within one year: **try to keep within 15%–30%**; beyond 30% must be accompanied by product form changes (more modules, new deliverables, new service boundaries), otherwise it feels like "the same product suddenly became expensive."
- Consulting is more suitable for "big steps" than courses: because it's selling time, a price increase essentially filters people.
- Always keep an **entry-level priced product** (short course, basic recording, single light consultation) so price-sensitive users have a step, instead of only "either expensive or leave."
Experiences from coaching and service industries have validated similar pacing: about 30 days advance notice, honestly explain the reason, emphasize the value they have received and will receive — most customers who understand the rules stay. I found 21 days also sufficient, but don't go under 14 — otherwise it feels like a surprise attack.
Part 4: Communication Strategy — What to Say, What Not to Say, How to Give Choices
### 1. Notification Structure (Feel Free to Adapt Numbers)
Subject: Notice Regarding Course and Consulting Price Adjustment (Effective Date: January 15, 2025)
Body Outline:
- **One-sentence conclusion**: From [date], XX course public price adjusted from 999 to 1299; 1v1 consulting standard tier from 800 to 1200.
- **Why the change (only what users can perceive)**: Over the past 12 months we added N session updates, Q&A changed to fixed schedule, consulting added post-call summaries; production and delivery costs have risen, the old price can no longer support the same standard.
- **What it means for you**: Already purchased course rights unchanged; already scheduled unfinished consulting honored at original terms.
- **Transition plan**: Orders/completions before January 14 still at old price; old students get one old-price renewal within 90 days.
- **Choice, not ultimatum**: Basic recording 1299; advanced version with assignment review 1599; tight budget? Buy "single module 199."
- **Thanks + inquiry channel**: Fixed email/WeCom account, reply within 48 hours.
Sentences I deliberately removed:
- "Raw materials, inflation, the overall environment..." (users struggle too)
- "The whole industry is raising..." (irrelevant to me)
- "If you don't accept it, you can leave the group" (too aggressive)
### 2. How to Handle Objections (Condensed from Real Conversations)
"Are you exploiting old users?"
→ "Already purchased will never be retroactively charged. Old users have a 90-day old-price window — this is a reward for trust, not a forced purchase."
"You raised 30%, did content increase by 30%?"
→ "Not a one-to-one percentage match. What we promise is: maintaining weekly-level content calibration + fixed Q&A + standardized consulting delivery. If we only maintained 2023's delivery depth, the price could stay the same — but that's not the product I want to make."
"Others are cheaper."
→ "Cheaper options exist — that's normal. Our difference lies in delivery boundaries and update density. If you prioritize low-cost trial, the basic short course is still available."
"Can you give me a discount only?"
→ "Within the window, yes. Outside the window, no more private pricing — otherwise it's unfair to those who paid by the rules." — This line must be held. I once gave a private old price to a connection, and within a week three people came to compare prices, and community trust cracked directly.
### 3. Channel Rhythm
- **Day 1**: Email + public account/community long post (full version)
- **Day 1–3**: Community pinned short version + FAQ
- **For A class**: Voice or 1-minute call — ten times more useful than group messages
- **For C class**: Don't debate pricing in the big group; private message options, publicly only repeat the rules
Private messages cool fires, public communication maintains stability — this is a conclusion I paid tuition for.
Part 5: Three Product Moves That Make a Price Increase Not Feel Like One
Simply changing 999 to 1299 is a hard psychological sell. I pair it with at least one structural change:
### Option A: Value Bundle (Raise More, but Include Low-Cost Benefits)
For example, price +20%, include: one assignment review, template pack, or 30-day community access. Controllable cost, high perceived value. Some small businesses tested "straight +12%" vs "+20% with small add-ons" and found the latter had better acceptance — provided the add-ons were genuinely useful, not junk.
### Option B: Tiered Packages (Turn "Stay or Leave" into "Which Tier")
- Basic: pure recording
- Standard: recording + monthly Q&A
- Premium: recording + Q&A + 1 light consultation
The user's focus shifts from "why are you raising prices" to "which tier do I need." This is what I consider the most stable price increase container in knowledge commerce.
### Option C: Raise Only for New Customers and New Cycles, Lock Old Cycles
Subscription and bootcamp models especially suit this. Cohort 1: 1999, Cohort 2: 2399; returning students get "early-bird old price for 7 days." Raises unit price while preserving face for loyalty.
Part 6: Pitfalls I Stepped Into (I Suggest You Skip Them Directly)
- **Announcing on the day of the increase**
Feels like price-gouging. At least 14 days advance notice, ideally 21–30.
- **Only citing "costs" as the reason**
Costs are your problem. Users buy results. Explain the money as "to continue maintaining X delivery."
- **A uniform spike across the board with no entry-level option**
You'll offend both price-sensitive users and those who "want to try before buying deep." Keep a low-price path.
- **Extending the window indefinitely**
"One more week" said three times, and the rule is dead. I now set a hard deadline, calendar reminder, automatic price switch at expiry.
- **Delivery can't keep up after the increase**
This is the biggest credit suicide. The 60 days after the effective date are the inspection period. Late Q&A, missed updates — refunds and bad reviews come back multiplied.
- **Using fear to create FOMO**
"Buy now or it's gone forever" can work, but don't act it. Fake scarcity gets screenshotted.
Part 7: A Checklist I Now Regularly Execute
Before the increase:
- Calculate per-person delivery cost clearly (including your own time)
- Segment: export A/B/C/D lists
- New customer pilot ≥ 14 days, with conversion and complaint records
- Launch at least 1 perceivable delivery upgrade
- Write: old/new price comparison, benefits comparison, FAQ, email draft
- Set in stone: effective date, old-price window, exception terms
During the increase:
- Consistent information across all channels (page, group,customer service script)
- A-class one-on-one outreach
- In public, don't argue; repeat the rules
- No secret permanent discounts
30 days after the increase:
- Statistics: number of transactions, ticket price, refunds, group departures, NPS/simple survey
- If churn > 15% and revenue still drops: check whether the issue is the increase amount or communication/delivery
- If revenue rises but complaints focus on one clause: fix the clause, don't rush toreduce prices
Part 8: My Personal Position, Made Clear
A price increase is not passing incompetence on to users; it's refusing to pretend generosity at a loss.
The content industry has a bad habit: using loss-leader pricing early for reputation, then afraid to raise prices and afraid to reduce quality, until creators burn out and the product deteriorates. I respect a different relationship: you pay a price that can cover quality delivery; I complete the work by the checklist, and when the cost structure changes, I renegotiate the terms with you in advance, clearly, and with options.
On the day the January 2025 price adjustment took effect, I watched the orders in the backend. The first two hours had only a trickle of orders, and my palms were sweaty. That evening, a student who had been following since 2022 messaged: "Raise it if you must, just keep the weekly Q&A stable."
That one sentence was worth more than any growth curve.
Costs will rise again. Platforms will change rules again. The only things you can control are three: get the numbers straight, break the steps down, speak human language. Price is the result; trust is the prerequisite — reverse this order, and any increase will feel like robbery; get the order right, and a reasonable price increase can be the beginning of a long-term partnership.