dlivrd-GCS · Language training
A language-learning platform owned by dlivrd-GCS. Trains the team in English today, Spanish for the US team next, and becomes the base for every course the company runs after that.
The problem
The promise on the site is "top bilingual professionals who deliver from day one". That adjective is what makes a professional placeable in a client-facing role — and today the company's ability to produce it depends entirely on one instructor's calendar.
The opportunity
Colombia has a deep pool of capable, qualified professionals — that is the whole premise of the GCS model. What most of them don't yet have is the language level a client-facing role demands.
Training language systematically turns a hiring constraint into a hiring advantage — and widens the supply of the exact thing GCS sells.
Why the current setup can't fix it
The platform
Courses run on a main path with side lessons for the work situations the team actually deals with. Nothing unlocks because time passed — it unlocks when a learner passes.
Deployed once per audience. English for the Colombia team now, Spanish for the US team later, company onboarding after that — same software, separate installs, separate branding.
Feature · Content authoring
This is the part LearnDash gets wrong and the reason the current library never made it onto the platform.
Existing material is reused, not rebuilt. Authoring stays with the instructor, not with the development team — which is what makes the platform grow without adding cost.
Feature · Automatic assessment
Speaking is scored sound by sound against a reference, then explained in plain language. Written answers get instant feedback. Every word carries a native recording and its phonetic transcription, pulled automatically.
This is the capability nothing on the market gives the company today, and the one that removes the human bottleneck from practice.
Feature · Teaching operations
Who's moving, who's stalled, what's waiting for review. Reminders go out on their own. Courses get assigned to a whole team instead of one person at a time.
Live sessions stay exactly as they are — but the instructor walks in already knowing what to work on, instead of spending the hour diagnosing.
Feature set · Version 1
Feature set · Deliberately later
None of this changes what gets built now. Each one waits on a decision or on the first version proving itself.
What it solves for dlivrd-GCS
What it solves for the teaching side
Same method, same sessions, many more people reached.
Cost
| Line | Per year |
|---|---|
| Hosting, database, email | $60 |
| File storage | $0 |
| Speech assessment | $0–30 |
| Automatic written feedback | $1–10 |
| LearnDash licence today | $400 |
| Running the platform | $61–100 |
The real cost
Infrastructure is not the number that matters. The cost is time: development, and the instructor's hours designing the course path and the placement test. That is the figure worth agreeing on up front.
If it doesn't work
Two learners, one course. Nothing currently running is switched off, and every existing system stays exactly where it is.
To start
The course path — a first sketch of one level
The main line, plus two or three side lessons hanging off it. Without a map there is nothing to build.
The placement test
Ten or fifteen questions is enough to start. Questions are data, not code — they can be replaced later without touching the application.
Two pilot learners, at different levels
Two, not ten. A small group keeps the first version honest and fixable.
The pronunciation standard
Speech scoring measures against a native speaker, so a perfectly intelligible Colombian speaker can score 70. If the goal is being understood on a client call rather than sounding American, the bar is set differently. That decision belongs to the instructor, not to the software.