Claude Training & Enablement
Two live cohort programs — three sessions for business teams, six for technical teams. Taught by Claude Certified Architects who ship production systems every week.
Curriculum Map
two tracks · one cohort model
A team playbook your manager can approve
An agent, an eval harness, and a costed run rate
Outcome
Proficient people who keep working this way after we leave. The capability is the deliverable — CTES issues no certificate.
The Gap
Four patterns show up in almost every rollout we are called into. None of them are licensing problems.
Seats go out, a handful of enthusiasts explore, and everyone else returns to the old way of working. Adoption stalls at the people who were already curious.
Untrained users ask Claude to tidy an email. Trained users hand over a five-step process, then review the result like a manager. The gap between those two is training, not licensing.
Without evaluation, guardrails, and cost design, the first agent looks excellent in a meeting and falls over on real inputs in week three.
Teams need a clear line on client data, PII, and what always needs a human decision — set before the unofficial usage starts, not after.
Two Programs
Both run as small live cohorts, and both use your own work as the material. Business teams build fluency in Claude and Claude Cowork. Technical teams build the AI engineering and agentic AI skills that take a system to production.
Operations, finance, HR, marketing, legal, and executive teams. No technical background needed.
What You Build
Working proficiency in Claude and Claude Cowork, and a written playbook for how your department uses both.
Engineers, data teams, and technical leads. Comfortable in a codebase and on a command line.
What You Build
AI engineering and agentic AI skills — API, Claude Code, MCP servers, agents, evaluation, and production economics.
Program 01
Three sessions. Non-technical teams. Your real work as the material.
What Claude does well, where it fails, and how to brief it like a capable colleague.
You Leave With
Five briefs for tasks you personally do every week, written and tested in the session.
Moving from single questions to multi-step work you hand over and review.
You Leave With
One live workflow from your own team, delegated and reviewed start to finish.
Turning individual skill into how the department actually works.
You Leave With
A written team playbook: three standard workflows, the briefs that run them, and a usage policy your manager can approve.
Program 02
Six sessions. AI engineering and agentic AI, taught against your own repositories and systems.
The API surface, and the design decisions that come before any code.
You Leave With
A working service that calls Claude and returns validated, structured output.
Making Claude Code a force multiplier for a team, not a liability.
You Leave With
Your own repository configured, conventions committed, and a first task shipped through review.
Connecting Claude to the systems your business actually runs on.
You Leave With
A running MCP server that exposes one internal data source to Claude, safely.
The difference between an agent that demos and an agent that runs.
You Leave With
A single-purpose agent that owns one workflow end to end, with escalation designed in.
Proving the system works, and knowing the moment it stops working.
You Leave With
An eval harness and a passing baseline for the agent you built in session 04.
What it takes to run this every day, at a price the business accepts.
You Leave With
A design review of your own build and a costed run rate you can take to a budget conversation.
Tell us the size and shape of your team and we will come back with a quotation and the next available cohort dates.
How It Runs
Format
Live online, or on-site at your office in Metro Manila
Cohort size
8 to 15 participants, so everyone gets reviewed
Cadence
One session per week — three weeks or six weeks
Session length
3 hours, including the lab
Between sessions
A short assignment on your own work, plus async questions to the instructor
Close-out
Each participant presents what they built, and keeps every artifact from the sessions
CTES is a training and enablement program. It is not a certification program, and it does not issue a credential.
Enrollment
Private Cohort
Open Cohort
Who
Private Cohort
One company, one department
Open Cohort
Individuals from several companies
Size
Private Cohort
Up to 15 seats
Open Cohort
Up to 15 seats
Labs
Private Cohort
Built on your own workflows and repositories
Open Cohort
Built on realistic sample material
Schedule
Private Cohort
Set with you
Open Cohort
Published intake dates
Cohorts are quoted individually — by program, seats, and how much of the lab material we rebuild around your work. Tell us what your team looks like and we will send a quotation.
Request a QuotationWho It's For
Operations, finance, HR, marketing, and legal teams doing document-heavy, repeatable work. Program 01.
Teams that will own the agents, the MCP servers, and the evals after we hand over. Program 02.
Enterprise IT & EngineeringTeam leads and QA supervisors who need their people supervising AI-assisted work, not competing with it.
BPO & Shared ServicesBanks, fintechs, and insurers where the governance and audit half of the curriculum matters as much as the tooling half.
FinTech & RegulatedWhy Learn From Us
Among the first Philippine companies admitted, with direct platform access and an escalation path to Anthropic.
Across software engineering, cloud infrastructure, and machine learning — the three perspectives an agent needs at the design table.
Over 200 professionals trained across more than 20 cohorts. We know how to run a room, not just a demo.
Every instructor ships production Claude systems. The exercises are drawn from work that shipped, including the parts that went wrong.
Wawi del Mundo — Claude Certified Architect and AWS Certified Generative AI Developer – Professional — reviews the curriculum and teaches on the technical program.
How It Fits
Most clients end up doing both. A trained team makes a Build sprint faster, because the conversation starts past the basics. And after we hand a system over, it is your team that extends it.
Training & Enablement
Professional Services
What it produces
Training & Enablement
Proficient people — individuals who can do the work themselves after we leave
Professional Services
Decisions and a system — a prioritized use case backlog, then architecture and a live agent
Unit sold
Training & Enablement
A cohort, sized by seats
Professional Services
An engagement, scoped to your use cases
Shape
Training & Enablement
Curriculum, fixed sessions, recurring intake
Professional Services
Consulting sprint, 2 to 12 weeks, project team
Who attends
Training & Enablement
Anyone whose job changes because of Claude
Professional Services
Decision makers and the project team
Ends with
Training & Enablement
A capability you keep
Professional Services
A deliverable we hand over
Common Questions
Not for Claude for Business Professionals — it is written for people who have never opened a terminal. Claude for Technical Professionals assumes you write code and work in a repository daily.
Yes. Participants train on the accounts they will use afterwards, so the habits transfer. We will help you work out which plan fits before the cohort starts.
Yes. Private cohorts are the common case: the labs are built on your workflows, your documents, and your repositories.
No. CTES is training and enablement. What participants take away is the ability to do the work, plus everything they built in the sessions — briefs, playbooks, an MCP server, an agent, an eval harness. We do not issue credentials.
The session structure stays fixed; the labs and examples are rebuilt around your work. For a BPO the document work is tickets and QA; for a law firm it is contracts and case files.
Every cohort is quoted on its own — the number depends on program, seats, delivery, and how much of the lab material we rebuild around your work. Tell us the shape of your team and we will come back with a quotation.
Some teams stop there. Others move into a CPS Build sprint with a much clearer brief, or a retainer where we keep coaching while the systems grow.
Explore
Flagship Program
Enable, Architect, Build. From a prioritized use case backlog to a live agent in 6 to 12 weeks.
See the full programBuild With Us
Custom Claude agents and MCP servers, built and operated by our team.
Explore the practiceEnterprise IT
Rolling Claude Code out across an engineering organization, with the conventions that make it stick.
Learn moreLet's Work Together
A 45-minute conversation mapping your top use cases against the Enable, Architect, Build framework. You leave with a point of view on where AI is worth your investment — and where it is not.
cloud@apper.ph · Metro Manila, Philippines
