For engineering teams

Help your engineers use AI properly

Most of my work now is with founders whose apps were built by AI. This is the other half of the practice: teams that already have engineers and want them getting real value out of these tools.

Team workshops

In person or remote · half-day to two days

Hands-on sessions using your own codebase, not toy examples. Your engineers leave with working patterns for AI-assisted development rather than a set of slides.

  • Working sessions on your real repositories
  • Prompting patterns that survive code review
  • Where AI helps, and where it reliably doesn't
  • Testing and review habits for AI-written code

Custom internal tooling

Scoped per project

The internal tools your team keeps saying somebody should build, built this time, then deployed and documented well enough to outlive the engagement.

  • Internal assistants over your own documentation and data
  • Code generation fitted to your conventions
  • Integrations with the systems you already run
  • Handover documentation, so it isn't ours to maintain

Workflow automation

Scoped per project

Finding the repeated manual work in your engineering process and taking it away: review triage, release notes, test scaffolding, on-call routine.

  • An audit of where your team's hours are going
  • Automation for the highest-frequency work first
  • CI and review pipeline improvements
  • Measurement, so you know whether it worked

Ongoing support

Monthly retainer

For teams that want an experienced pair of hands on call while their AI practice finds its feet, without hiring a head for it.

  • Regular working sessions with your engineers
  • Architecture and tooling guidance
  • Async support when the team is stuck
  • Periodic review as your practice matures

Let's talk about your team

Tell me how big the team is and what you have already tried, and I'll tell you whether this is something I can help with.

Book a callMessage