Terra Technologies Let’s talk

Academy

Your team, your toolchain, your examples.

Any course in the catalog can be run for your organisation alone. Most clients find that is the version worth paying for. [Draft copy]

Why in-house

Public courses teach a general case. In-house courses teach yours — your pipeline, your estate, your obligation, your actual code. The exercises use your repositories rather than a sample project, so what people learn on the Thursday is applicable on the Monday.

A public course teaches the pattern. An in-house course teaches the pattern on your estate, which is the only version anyone remembers.

How it works

  1. We read your context first

    A short call and access to whatever you can share — the pipeline, the architecture, the finding that prompted this. Usually an hour.

  2. We adapt the material

    Examples and exercises rebuilt around your stack. This is the part that makes it worth doing and the part most providers skip.

  3. We deliver it, and we stay reachable

    The trainer is one of the people who does the delivery work, so the questions that come up afterwards land with someone who can answer them.

  4. You get the material

    Slides, exercises and the worked examples, yours to re-run for people who join later.

Cohort and format

Detail, and typical
DetailTypical
Cohort size8 to 16. Smaller loses the discussion, larger loses the hands-on.
FormatIn-person at your site, or your office plus remote for distributed teams.
DurationOne to three days, depending on the course.
PrerequisitesStated per course. We would rather move someone to a different course than have them sit through the wrong one.

[Draft copy] — confirm cohort sizes and delivery formats with the principals.

Cost and HRDF

Priced per cohort rather than per seat, which is usually cheaper once you are past about six people. Claimable against your HRDF levy on the same basis as the public courses.

[Client to supply] — per-cohort pricing. See also §17.2 on whether indicative ranges are published.

Tell us what you are being asked to prove.

Tell us what your team needs to be able to do, and how many of them there are.

Start a conversation