Partner

Add controlled learning capacity without expanding permanent payroll. The work ships under your brand, on your templates, inside your review cycle.

You hold the client relationship, the contract, and the commercial terms. IETERNUS produces the work behind you, under your name.

The capacity problem

The work is won. The scope is signed, the dates are fixed, and the production load lands in a quarter that is already committed.

The available moves are all expensive. Hiring adds permanent cost and takes longer than the delivery window allows. Freelancers vary in standard and have to be managed artifact by artifact. Moving the deadline costs credibility with a client you have only just started with. Absorbing the load internally means senior people building screens at night, and quality drifting in the places nobody has time to check.

This is not a planning failure. Production demand in learning arrives in blocks and does not match a permanent headcount curve. What is actually needed is capacity that can be turned on for a defined scope and turned off without a redundancy conversation.

White-label means white-label

This is the core of the arrangement, so it is stated precisely rather than implied.

• IETERNUS is not named to the end client. Not in the storyboard footer, not in document properties, not in the SCORM manifest or package metadata, not in course credits, not in a handover pack.
• No direct contact with your client. All client-facing communication runs through you. If you want production presence on a review call, that is arranged in writing beforehand and joins as part of your team, under your naming.
• Nothing is published or shown as IETERNUS work without your written permission. No portfolio use, no screenshots, no naming you as a partner, no logo use, no anonymised sample that would be recognisable to anyone in your market.
• Confidentiality is signed before files move, and covers your client’s content, your templates, your rates, and the existence of the arrangement itself.
• You receive editable source files, not only the published output — project files, scripts, asset libraries, and the storyboard of record — so nothing about the deliverable depends on continued involvement.
• Content is returned and removed on request. Retention is agreed in the work package, not left open.

For the same reason, no other organisation’s material is shown as evidence of standard. Craft is demonstrated on your own work, on a paid pilot, in your own templates.

Work packages available

• Curriculum maps — objectives, sequence, audience and role mapping, assessment strategy, and what belongs in each format.
• Storyboards — screen-level or module-level, in your storyboard format, written to be built from without interpretation.
• Scripts — narration, video, scenario dialogue, and knowledge-check items with answer rationale.
• eLearning production — build in your authoring tool, on your template, to your interaction and media standards.
• Accessibility QA — structured review against agreed standards, with an issue log and remediation notes. This supports accessibility improvement and alignment with agreed standards. It is not a legal certification and is never presented as one.
• LMS packaging — packaging, completion and tracking rules, upload testing in the target environment, and a defect list with reproduction steps.
• Deadline recovery — triage of a project already in trouble: what is salvageable, what is rebuilt, what is cut, and the sequence that gets the date back.

These packages draw on the same production capability offered directly — including the White-label Learning Pod, Learning Content Rescue, and the Accessible Learning Review — scoped so you can buy one artifact set at a time. The full list sits on the services pages.

Fitting inside your process

Your process stays. Ours runs underneath it.

That means your templates, your style guide, your file and version naming convention, your storyboard format, your review tool, your stage gates, and your definition of done. Nothing here asks you to adopt an IETERNUS format, learn an IETERNUS tool, or explain a new workflow to a client who already agreed to yours. Where an internal sequence is used to structure the work — discover, architect, build, validate, improve — it is mapped onto your stage gates rather than added alongside them.

Where your standard exists but is undocumented, it is captured once at the start from existing examples and confirmed with you, so the second package does not repeat the first conversation.

Review, versioning, and acceptance

The point of subcontracting is fewer things to manage, not a second project to run. These controls are agreed in writing before work starts.

• Review rounds are stated per artifact — how many, on what, and by when — as part of the work package, not negotiated mid-build.
• Feedback is consolidated. One file, one owner on your side, one deadline. Conflicting comments are resolved by your owner before the round closes.
• Every artifact carries a version and a change log stating what changed and which comment it answers. Superseded versions are retained, not overwritten.
• Acceptance is explicit. Acceptance criteria are written at package start, and sign-off is recorded against a stated version.
• Change beyond the agreed rounds is raised as change — scoped and quoted before it is done, not absorbed quietly and argued about at invoice.
• One point of contact on each side for the duration of the package.

Two routes in

1. A paid pilot work package. One bounded artifact set on real work — a curriculum map, a storyboard, one module built to your template. Fixed scope, written acceptance criteria, a defined number of review rounds. You judge the craft on the output rather than on claims about it.
2. Reserved monthly capacity. After a pilot, a block of production capacity is reserved each month with an agreed booking window, a defined intake format, and a rolling schedule you can plan pitches against. How unused capacity is treated is agreed in the arrangement, in writing.

The order matters. Reserved capacity is a commitment on both sides and should follow evidence, not precede it.

Where this fits — and where it does not

A good fit if: you are an agency or consultancy that has won work and lacks production capacity; you are an internal L&D team needing overflow delivery against a fixed deadline; you have templates and quality standards you want followed exactly; you will consolidate client feedback rather than forward it raw; and you are willing to start with a paid pilot.

Not a fit if: the decision rests only on unit cost per slide; you want bulk machine-generated content passed off as bespoke; you want the production partner to take over the client relationship; you need unlimited revisions or open-ended support; you want an LMS platform, a course marketplace, or general software development; or you need a guarantee of legal or regulatory compliance. IETERNUS is not an LMS vendor, is not a regulator or law firm, and does not issue compliance sign-off.

Starting

The way in is a capability and craft conversation — your formats, your standards, the work in front of you, and what a first package would cover. Then a pilot package on live work, judged on the artifact.

That conversation is the ask on this page. The Learning Systems Review is a diagnostic of an organisation’s own learning estate — it asks for platform access, the person accountable for the training outcome, and the delivery calendar, none of which an agency buying production capacity would be supplying. If what you actually have is a client whose learning estate needs reviewing, the Review is the right instrument and can be run under your name.