Technical enablement · AI & developer platforms
I build the technical curriculum your GTM teams run on.
Courses, hands-on labs, demos, and facilitator guides for AI and developer-platform companies — built against your real APIs, and maintainable after I hand them over.
// The prompt never asks for JSON. The schema is attached to // the request and the API is constrained to it. const TriageSchema = z.object({ category: z.enum(CATEGORIES), urgency: z.enum(["low","normal","high","urgent"]), requires_human: z.boolean(), escalation_reason: z.string().nullable(), confidence: z.number().min(0).max(1), });
Facilitator note
Stop here. Ask the room what happens when
confidence
comes back at 0.4. Most people say “retry”. The answer
the schema is arguing for is route it to a person.
That distinction is the whole lab. Budget 8–10 minutes; it is where the group either gets structured outputs or doesn’t.
Not a mockup. That is lab 2 of a course that is live, and the link runs it.
The difference
Working labs and demos against real APIs. Slides about them.
Things you can open right now
Most enablement portfolios are screenshots.
These are running. No signup, no key, no sales call first — open one and use it the way an engineer in your field org would on day one.
A Claude API course, end to end
Ten labs from first call to an eval harness with an LLM judge, built around one support-triage service you can read start to finish. Instructor guide, run-of-show, and an auto-scored assessment included.
Course10 labsFacilitator guide northwind.mlynn.devThe scenario, made real
The fictional company the course is about, as a working shop. File a support ticket and watch a live model classify your own words, then try to talk it out of its instructions in the injection playground.
Live demoReal inference~60 secondsHow the work is shaped
Start small. The audit is the door.
Most teams begin with a fixed-fee audit, because it produces something useful whether or not we work together again.
Curriculum audit & roadmap
I go through what you already have, map it against your product surfaces, and find where the gaps actually are — usually not where the backlog says.
Build sprints
Courses, labs, demos, and decks, built and shipped against your real APIs. Written to be maintained by your team, not just delivered to it.
Fractional enablement lead
A set number of days a week, owning one product surface's curriculum end to end alongside your enablement, DevRel, and PMM leads.
Workshops & developer days
Hackathon-in-a-box and Developer Day design, live delivery, and train-the-trainer so your own people can run it next time.
Background
I have built this program before, at scale.
Twenty-five years across software engineering, infrastructure, enterprise architecture, and developer platforms — the last decade of it at MongoDB, building the enablement that field teams actually used.
Years across engineering, enterprise architecture, and developer platforms.
At MongoDB — Principal Staff Developer Advocate and Manager, Strategic Developer Relations.
Designed the Developer Day program delivered worldwide to drive hands-on adoption.
Episodes hosting the MongoDB Podcast, plus a decade of conference stages.
Next step
Bring me the backlog you keep deferring.
Thirty minutes. Tell me what your field org is struggling to teach, and I will tell you whether it is an audit, a sprint, or something you should just build in-house. If it is the last one, I will say so.