Custom-scoped program

Developer Education Series

Teach a defined workflow with your product.

We plan practical tutorials and expert-led explanations around the tasks developers need to complete. Your technical team reviews the examples, versions, and claims so each release has a clear scope and an agreed next step.

BUYING SITUATIONS

When this helps

  • Developers need a visual explanation of a setup, integration, or operating workflow.
  • Documentation and webinars exist, and the team has identified a specific teaching gap.
  • A release introduces tasks that need updated guidance.
  • Developer relations has subject expertise and a recurring topic list, with a need for production support.

Readiness. Bring the intended developer audience, prerequisites, supported product version, a usable example environment, and a technical reviewer.

CUSTOM SCOPED

What we can scope

Each proposal defines the audience, subjects, formats, quantities, review rounds, responsibilities, schedule, and usage rights. We agree on original pieces, shorter edits, and format versions separately.

Audience/task map and episode plan
Define the intended skill level, prerequisites, tasks, and learning objectives
Recording and demonstration briefs
Prepare examples and identify what viewers should be able to follow
Expert-led tutorials or explanatory episodes
Teach the approved task with visible steps and relevant context
Technical review and version labeling
Record supported versions, tested examples, review date, and client approval
Transcripts, chaptering, and useful links
Help viewers find the relevant step and continue into official documentation
Shorter topic edits and channel versions
Support discovery or answer individual developer questions
Release plan
Coordinate publication with the client team and approved destinations
REVIEW AND DELIVERY

How the work is reviewed

  1. Identify developer tasks and inspect existing learning material.
  2. Agree on the series scope, prerequisites, examples, and release sequence.
  3. Prepare scripts or outlines with a designated client expert.
  4. Record, edit, and complete the agreed technical review.
  5. Publish or hand over the episodes according to the agreed responsibilities.
CLIENT RESPONSIBILITIES

What your team provides

  • Product access and official documentation
  • Example permissions and subject experts
  • Technical validation, including who tests code or commands and on which versions
SEPARATELY SCOPED

Scope boundaries

  • Keep secrets and production credentials out of all examples.
  • Tutorials should state material prerequisites and limitations.
  • Repositories, full courses, certification, interactive labs, developer support, and continuing updates require separate scopes.
  • Software engineering and security review remain assigned to qualified owners.
  • A later product update may require a separately scoped content revision or a maintenance pilot.
ILLUSTRATIVE MATERIAL

Illustrative brief — not a client case study

A developer-tool company has identified a gap between setup documentation and a production workflow. A series follows an approved example through setup, execution, review, and troubleshooting. Each episode records its prerequisites and product version, with code and commands checked by the client's technical owner.

PLANNING THE PROJECT

Buying questions

Can you work with our developer-relations team?

Yes. We can provide planning, interviewing, recording, editing, and publication support around your team's expertise and technical review.

Who checks the code and technical instructions?

The proposal names the qualified technical owner and validation process. We coordinate the production and review record around that responsibility.

Can the series use an existing webinar or documentation?

Yes, subject to usage rights and a review of what needs to change for the intended task and audience. New explanations, recording, and existing-footage edits are scoped separately.

Are future product updates included?

Ongoing updates require an explicit agreement. The initial scope identifies the versions covered and the release responsibilities. A Technical Content Maintenance pilot can be discussed separately.

TECHNICAL PROGRAMS

Related programs

Custom-scoped program

Developer Education Series

Share the developer task, existing material, product version, and the expert who can review the work.