Skip to content
Jordan Hudgens
Project 07 · Developer education

Encapsa: Customer AI Training & Internal Developer Enablement

I teach customer engineering and operations teams during every Encapsa deployment, provide ongoing training outside deployments and build internal training and usage tools. This work runs alongside hands-on production AI engineering and daily use of Claude Code CLI, Codex CLI, a custom Goose harness and Mistral.

Role
Co-founder & CTO
Organization
Encapsa
Period
Current enablement work
Program launch date not specified
Type
Ongoing program
Jordan Hudgens 07
Encapsa / Customer & internal enablement Ship the system. Teach the team. Customer engineers and operations teams. Teaching tied to current production work.
Every
deployment
Customer engineering + operations Daily coding tools Claude Code CLI · Codex CLI · custom Goose harness · Mistral
  • During delivery Instruction for customer teams
  • Beyond deployment Ongoing customer training
  • Inside the organization Internal training and usage tooling
jordanhudgens.com Portfolio summary · Oct 2026 record
AI delivery and enablement in the same role. A scope summary of customer instruction during every deployment, ongoing training and internal training and usage tools. It presents confirmed activities, not invented adoption or time-to-productivity metrics.

Who receives the customer AI instruction?

I teach customer engineering and operations teams as part of every Encapsa deployment. The scope continues beyond initial delivery through ongoing customer training and internal training and usage tooling. This combines instruction for the people using the systems with the hands-on development of production AI workflows.

The stated scope is an activity and responsibility: teaching during every deployment. It is not an invented customer adoption rate, number of people trained or time-to-productivity improvement. Customer implementation outcomes are documented in their own case studies, not assigned to the training program without evidence.

How does Jordan connect engineering and enablement?

I work on the AI systems and teach the teams using them. My current role combines production engineering, customer-facing technical instruction, ongoing training and internal developer enablement. Daily tools include Claude Code CLI, Codex CLI, custom Goose harness, and Mistral, alongside end-to-end AI workflows for product development, internal training and usage.

This is current practice at Encapsa, where I lead eight full-time team members as Co-founder & CTO. The training responsibilities do not replace the engineering remit; the same role spans both. No specific model version, tool certification or time-saving percentage is inferred from the daily tool list.

What happens during and after a deployment?

During deployment, instruction serves customer engineers and operations staff. Outside deployments, the work continues through ongoing customer training. Inside the organization, I build training and usage tooling. The visual separates these three confirmed scopes rather than inventing a curriculum calendar, standardized lesson plan or customer-success metric.

The platform itself includes closed-circuit LLM systems, multi-model orchestration, agents, MCP, retrieval and self-hosted inference. The enablement work is connected to that production practice. The public record does not establish that every customer receives instruction on every capability or that all deployments use the same architecture.

  • During delivery: customer engineering and operations instruction
  • Beyond deployment: ongoing customer training
  • Inside the organization: internal training and usage tooling

What earlier education leadership supports this work?

At Bottega University, I owned required instructor onboarding, teaching observations, dry runs, a formal cleared-to-teach rubric and ongoing development. I also owned instructor hiring, performance reviews and contract renewals. That earlier education-leadership record provides context for current customer enablement, while remaining a distinct program and role.

The connection is between confirmed instructional responsibility and current engineering practice. It is not a claim that Bottega’s clearance rubric is used for Encapsa customers, that the programs share a credential or that a measured Bottega outcome carries over to the current training work.

What does the record show?

Figures and responsibilities from the approved record, with the scope each one carries.
Customer instructionEvery deploymentCustomer engineering and operations teams
Ongoing trainingOutside deploymentsContinues after initial delivery
Internal enablementTraining and usage toolingBuilt inside the organization
Daily coding toolsClaude Code CLI, Codex CLI, custom Goose harness, and MistralCurrent practice
Team8 full-timeLed as Co-founder & CTO

Which skills does this project demonstrate?

  • Technical TrainingInstruction for customer engineering and operations teams.
  • Customer EducationTraining during every deployment and ongoing training beyond it.
  • Developer EnablementInternal training and usage tools tied to current engineering work.
  • Generative AIDaily coding tools and hands-on production AI systems.
  • Workflow AutomationEnd-to-end workflows for product development and internal use.

What does this case study not claim?

  • The confirmed scope is instruction during every customer deployment, ongoing training and internal tooling.
  • No adoption, onboarding-time, pass-rate or time-to-productivity metric is invented.
  • The Bottega instructor program is historical supporting experience, not a claimed Encapsa curriculum or credential.

Where is the supporting evidence?

All projects
  1. Production AI Ongoing program

    Encapsa: Enterprise AI Platform & Engineering Leadership

    Jordan Hudgens leads Encapsa’s production AI platform: 300+ deployments, agents, retrieval, self-hosted inference and customer training.

Teaching at scale. Building in production.

Curricula used by 250,000+ learners across platforms and schools.

300+ live enterprise deployments across seven verticals.