“We’ll help after launch” sounds generous in an overseas course proposal. It also sounds harmless until the client asks for a platform fix, a new lesson, weekly office hours, learner replies and a report three months later.
Chinese course-construction documents make the hidden expansion visible. A Zhaoqing University smart-course production project lists resource support, platform maintenance, consultation, user training and after-sales work. A Southwestern University of Finance and Economics online-course construction procurement describes a running course, promotion, Q&A or assistant work and technical response. These are specified project scopes, not universal contract rules. They are useful because they show how many different jobs can sit beside “course production.”
The commercial decision is simple: define support as a bounded scope before the build begins.
The phrase “course build” is doing too much
A course build can include content design, recording, editing, translation, platform setup, testing and handoff. It may not include ongoing maintenance, learner support, platform operations or promotion. If those are included, they should be named as separate work.
The Zhaoqing project’s published scope is a good reminder that maintenance, consultation, training and after-sales are not the same action. The Southwestern University document similarly places course operation, promotion, Q&A or assistant support and technical response beside the course itself.
The sources do not say that every buyer needs all these services. They do not establish a support period, response time, price or qualification for an overseas expert. They show only that a specified project may distinguish them.
Four lanes for a clear offer
Build
What is created? Curriculum, scripts, videos, exercises, translated assets, course pages or a content package? Define the accepted artifacts. “A complete course” is not an artifact until the number, format and review point are clear.
Launch and handoff
Who uploads, configures, tests and accepts the course? Is the handoff a file transfer, an operating platform, a live orientation or a signed internal receipt? A launch can be part of a build or a separate phase; the offer should state which.
Limited support
If support is included, define its boundary: a fixed number of review sessions, a stated support window, a named channel, or correction of specified defects. Avoid importing legal or SLA language unless the responsible contract process has approved it. This article is a scope-writing method, not contract advice.
Excluded ongoing operations
List what is not included: new modules, content updates, continuous moderation, learner counselling, platform administration, promotion, new integrations, analytics reports or emergency response. Exclusions are not an apology. They protect the reader from interpreting “support” as unlimited availability.
A scene: the one-time build that became a team
An expert quotes a six-week course build. The client supplies a platform and asks for “a little help after launch.” During week eight, learners report confusing instructions. The client asks the expert to rewrite two lessons, answer questions every Friday, check the platform and provide a monthly performance report.
None of those requests is unreasonable in isolation. Together they are a new operating service. The original offer did not say who owned the platform, how long support lasted or which artifacts were included. The ambiguity is now being settled by urgency rather than by a clear decision.
The scenario is a constructed example, not a customer case. Its purpose is to show why the support boundary belongs in the initial scope.
What the sources can and cannot do for pricing
A public course project can reveal that maintenance, consultation, training, technical response or promotion were listed as project work. It cannot establish a normal price for those services. A total project amount, where published, is not a per-lesson, per-hour or per-support benchmark.
Do not copy a university’s support language into a sales page as if it were a market standard. Do not infer that a foreign expert can offer the same technical service. Use the source to ask: “Which work did this specified buyer choose to name?” Then design the smallest scope your own delivery can honestly support.
The support window is not a guarantee of outcome
A bounded support period can clarify availability. It cannot guarantee that learners will finish, that the platform will remain unchanged, or that the course will produce a business result. If the client wants a measured learning or operational result, define a separate test and evidence path.
For example, “two review calls during the first 30 days” is a support scope. “The course will become effective within 30 days” is an outcome claim. The first describes a service activity; the second needs evidence and careful definition.
A counterexample: when no support is correct
If a client already has a platform team, editor and learner-support channel, a content-only handoff may be the best fit. The course build can end at approved files and a transfer note. Adding a support retainer would create work the buyer does not need.
Similarly, a one-hour expert talk may have one completion point and no course operations. Do not force a full support matrix onto a narrow engagement.
The five questions before accepting the build
- What exact artifacts are delivered at build completion?
- Who owns platform setup and acceptance?
- What support is included, for how long and through which channel?
- Which requests are new work rather than corrections?
- What ongoing operations are explicitly excluded?
If the proposal cannot answer the third and fourth questions, “support” is still a promise-shaped blank space.
The same discipline applies when the buyer asks for a small courtesy after launch. One clarification call, a correction to supplied copy, and a new lesson design are different units of work. Listing them separately keeps a friendly handover from becoming an unpriced second project, while still leaving room for a deliberately scoped support option.
The sentence worth carrying forward is: support is a scope decision, not a kindness that can remain undefined.
If you need to separate course production, handoff and bounded support for a China-facing offer, request a China validation review. Bring the intended artifacts and the post-launch assumptions separately.
Related reading
- A China Training Procurement Brief Is a Service Scope, Not a Course
- A China-Facing Live Cohort Has Three Surfaces
- Product Portability Audit
- The End-to-End Access, Payment and Delivery Test Script
Sources and evidence boundary
- Zhaoqing University smart-course production service result, checked 2026-08-23. Shows one project’s support, maintenance, consultation, training and after-sales scope; does not establish universal service terms.
- Southwestern University of Finance and Economics online-course construction procurement, checked 2026-08-23. Shows one project’s operation, promotion, Q&A/assistant and technical-response requirements; does not establish a standard package or SLA.
Image brief: Contract-free editorial scope map with build, launch, limited support and excluded ongoing operations as four lanes. No legal language, SLA promises, prices or vendor logos. Alt text: “A course build scope separated from a bounded support period and explicit exclusions.”