01
You reach out
An email or a short booked call is enough. Tell me where you're at and what you're wrestling with — I reply within a business day.
Going AI Native
From first contact to tailored workshop and follow-up. You pay for the time we spend together — not for a template.
How it goes
-
- 02
Scoping call
We spend 20–30 minutes on who should attend, what you want to be able to do after the workshop, and which parts of the AI landscape matter most to you.
- 03
Tailored workshop
Half-day or full day, on-site or remote. The content is assembled from the themes below based on what you need — no canned deck forced on you.
TDD with AI agents
- Red → Green → Refactor
- Tests as contract, not bureaucracy
- Evidence over trust
- Slash commands encode the loop
Multi-agent workflows
- 4–6 agents in parallel
- Steering, not typing
- Human in the loop
- The middle-manager mindset
The AI toolkit
- Claude Code, Codex
- MCP servers & Skills
- ADR Link, Borgmästare, Gas Town
- Workflow > tool
Quality & verification
- Screenshots > assertions
- Video as proof
- Tests survive refactors
- Captions in tests
Communicating with AI
- Voice all day
- AI as editor, not author
- Push back > nod along
- Show me, don't tell me
Personas & onboarding
- Builders, Craftsmen, Navigators, Strategists
- Onboarding ≠ tutorial
- Different rails for different riders
- Meet them where they are
Task vs Personal Conflict
- Separate the TASK from the PERSON
- AI amplifies team dynamics 10x
- Push back > silence
- Healthy friction = better output
Security
- AI-generated = dangerous by default
- Prompt injection
- Don't trust randos
- Skills can be Pirate Bay
- 04
Follow-up
Two weeks after the workshop we check in: what stuck, what didn't, what needs more time. Any continuation is decided then — no subscription.