Skip to main content
NordsCode

Service 06

Training and Enablement

Workshops, pairing weeks and documentation that move operational knowledge into your team, measured by how rarely you need to call us afterwards.

Request a quoteAll services
Timeline
4 to 10 weeks
Investment
Fixed-scope engagements from EUR 9,000
Delivered by
2 engineers, embedded with yours
Ends with
Documented handover

Overview

Your engineers own the platform. Not a vendor.

A platform your team cannot operate is a dependency, not an asset. We have seen companies inherit excellent infrastructure from a previous agency and be unable to change any of it, which is a worse position than having built something simpler themselves.

Enablement is the deliberate transfer of that knowledge. It is taught against your own systems, using your own incidents and your own deployment history, because generic cloud training does not survive contact with a real production environment.

This is for you if

  • You inherited infrastructure from an agency and nobody internally is confident changing it.
  • One engineer answers every infrastructure question in the company.
  • On-call is technically a rotation but practically one person's phone.
  • You are ending an outsourcing arrangement and need the knowledge to come back in-house.

What we provide

Everything below is in the written scope before the engagement starts.

If something you need is missing from this list, it is a conversation during the proposal rather than a change request halfway through the build.

  • Skills assessment

    An honest read of what your team can do today and what it needs to be able to do, per person, so training targets real gaps rather than a standard syllabus.

  • Workshops on your systems

    Hands-on sessions using your repositories, your pipelines and your cloud accounts, so what people learn on Tuesday is directly usable on Wednesday.

  • Pairing weeks

    Our engineers working alongside yours on real backlog items, with your engineers holding the keyboard and making the decisions.

  • Internal documentation

    Architecture notes, runbooks and decision records written into your own wiki or repository, in a structure your team can keep current.

  • On-call readiness

    A rotation your team can actually staff, with rehearsed incident scenarios and an escalation path that does not end at one person's phone.

  • Office hours

    A scheduled weekly session for eight weeks after the engagement, so questions that surface later have somewhere to go.

Typical engagement timeline

A 4 to 10 weeks engagement, phase by phase.

Enablement runs four to ten weeks and is often attached to the end of another engagement. It can also stand alone when a team has inherited infrastructure it did not build.

  1. 01

    Assessment

    Week 1

    Interviews and a practical exercise per engineer to establish the real starting point, plus agreement with you on what independent operation should mean in practice.

  2. 02

    Core workshops

    Weeks 2 to 4

    Structured sessions covering infrastructure as code, the deployment pipeline, observability and incident response, all taught against your live systems.

  3. 03

    Pairing

    Weeks 4 to 8

    Real platform tickets worked jointly, with our engineers steadily reducing involvement until your team is delivering the changes unaided.

  4. 04

    Independent operation

    Weeks 8 to 10

    Your team runs the platform while we observe and correct rather than intervene, followed by eight weeks of scheduled office hours.

Key benefits

What changes for your team once this is in place.

These are the outcomes clients tell us mattered most six months after the engagement ended, rather than the ones that sound best in a proposal.

Knowledge stays in the company

Documented, taught practices survive the departure of any one engineer, including ours.

Lower ongoing cost

Routine platform work handled internally is dramatically cheaper than routine platform work bought by the hour.

Faster response to your own incidents

A team that understands its platform resolves problems in minutes rather than waiting for an external engineer to read the environment.

A credible on-call rotation

Enough engineers competent to hold the pager means the rotation is sustainable rather than nominally shared and actually held by one person.

Questions we are asked

Three things people ask before committing.

If your question is not here, ask it on the introductory call. We would rather answer it before a proposal than after one.

Who should attend?

The engineers who will operate the platform, which for most of our clients means the whole backend team rather than a designated infrastructure person. Sessions work best with four to eight people. Where a technical founder or CTO is still hands-on, they usually get the most out of the incident response and cost sessions.

Is the training remote or on-site?

Remote by default, in sessions of two to three hours so people can still do their jobs that week. We travel for the initial workshop block where a team strongly prefers it, and that is quoted separately at cost with no margin added.

What if our team changes afterwards?

That is exactly why the documentation is written into your own repositories and wiki rather than delivered as slides. New engineers can follow the same material, and the workshop recordings stay yours. Where a team turns over substantially, a short refresher engagement is usually a few days rather than a repeat of the full programme.

Request a quote

Fixed-scope engagements from EUR 9,000. 4 to 10 weeks.

Other services

Ready to scope Training and Enablement?

Send us the shape of the problem and we will come back with a written scope, a timeline with dates, and a fixed price. The introductory call is free.

Request a quoteSee all services
hello@nordscode.com+47 21 09 44 30