Pricing & scoping
One business day to a fixed price. Not a quote range. Not a call.
Send a representative sample of your training material and the languages you need. Within one business day you receive a fixed, itemised statement of work: modules, runtime, languages, assessments, revision rounds, timeline, and one price. For orientation while you wait, the published market rates are below — cited, not ours.
Market benchmarks
What custom e-learning costs, according to vendors who publish.
Most production houses publish nothing, so the few published figures matter. Normalized to US dollars per finished minute of course video, the public 2024–2026 numbers look like this:
Two further published reference points: project minimums at Clutch-listed e-learning shops commonly run $10,000–50,000, and Indonesian local-market vendors have quoted roughly Rp 30–50 million per learning hour (anecdote-grade, the only figure here without a published source). The full table, with citations and the cost drivers behind the spread, lives in the cost guide and the downloadable buyer's benchmark.
Cost drivers
Four variables decide most of any quote.
Finished runtime
The strongest driver everywhere in the market — costs scale with finished minutes, not source-page count. Good scripting usually compresses seat time substantially, which is why scoping starts from your material, not your agenda.
Interactivity & assessment
Knowledge checks, scenario branching, and completion gating add design and QA work. Market data shows interactivity level is what separates the $83 floor from $250+ rates far more than video polish does.
Languages
Each language version prices as a fraction of the master — adaptation, narration, re-fitting, re-testing. The fraction is itemised per language in the SOW so staged rollouts have known unit costs.
Review cycles
Script-stage review is effectively free; post-production change is not. SOWs state included revision rounds explicitly, and projects that invest reviewer attention at the script gate consistently land cheaper and faster.
Pricing — questions
Asked often. Answered directly.
Why is there no rate card on this page?
Because a rate card would be less honest than it looks. Custom course cost is driven by variables a card can't see — source material condition, interactivity, languages, review cycles — so published tiers either pad every job or get renegotiated on contact. Instead you get the market's published numbers above for orientation, and a fixed, itemised SOW for your actual project within one business day.
Is the SOW really fixed, or an estimate?
Fixed. The SOW itemises modules, runtime, languages, assessments, and revision rounds with one price. If you change scope mid-project, the change is priced the same way — itemised, agreed before work continues. No hourly meters.
Is there a project minimum?
A single module is a perfectly good first project — most relationships start with one as a pilot. There is no artificial minimum designed to filter small engagements.
How does pricing work across languages?
Each language version is itemised separately in the SOW, priced as a fraction of the master because structure, presenter, graphics, and assessments carry over. This makes staged rollouts easy to plan: launch the master plus two languages now, add four more next quarter at known unit cost.
What are your payment terms?
Stated in the SOW; typically a deposit on signature with the balance on delivery for first engagements, and invoicing arrangements for established clients. Procurement and vendor-onboarding processes are accommodated as standard.
Stop estimating.
Get the actual number.
One representative document and your language list is enough. Within one business day: a fixed, itemised statement of work — price, timeline, deliverables. No discovery call required.
Request a proposal or write to hello@voctus.studio