Factory Accelerator

Get your dev team ready for agentic engineering

A workshop format, hands on with your whole team: product managers, Scrum Masters, developers, QA engineers and support. Together we configure your real repo for agentic engineering, with context files, skills, slash commands and guardrails. Then we prove the setup on real stories from your own backlog, so your team sees it work on its own code before we leave.

Book a call

Days to weeks, depending on team size and project complexity. We scope your case in the call.

  • ◆ 30+ yrs in software
  • ◆ 5,000+ hrs of gen AI coding
  • ◆ 12+ teams shipped

We're an accelerator focused on AI productivity,
laying the groundwork for AI-first transformation.

Why this matters

When agents fail, it's usually the context that failed, not the model.

01

AI is no longer optional

Teams that don't move now fall behind on shipping speed and quality. The gap compounds every quarter you wait.

02

Most teams are stuck on tab-completion

They use AI like autocomplete, never reach agentic engineering, and slide back into old habits within weeks.

03

An unconfigured repo fights the agent

Agents stall when they can't see your context: conventions, architecture, guardrails. Write that down once and the same model starts shipping work you trust.

What's in the Factory Accelerator

Training, assessment, implementation, and application. Hands on with your team.

  1. 01

    The mindset shift: how to work with agents, what to hand off, what to keep

  2. 02

    Your repo configured for agents: CLAUDE.md and AGENTS.md, your project context written down

  3. 03

    Reusable skills and slash commands for the workflows your team repeats

  4. 04

    Guardrails and quality gates, so speed doesn't cost you review time

  5. 05

    Real stories from your backlog run through the setup, so you see it work on your own code

  6. 06

    Your team leaves knowing how to run and extend the setup

  7. 07

    A final report for your leadership: where the team was, where it is now, what it owns, and the KPI baseline

What you walk away with

Three things that are true when we leave.

✓

Your repo is configured

Context, skills, and guardrails live in your repo, versioned in your own pull requests. Yours to keep and extend.

↑

Your team works agentic

Developers hand off scoped work to agents and review the output, instead of typing every line.

✓

Proven on your backlog

We run real user stories from your backlog through the setup during the workshop, so you see it work before we leave.

"One of the best tech talks I've been to in recent times. Very inspiring. You certainly rattled some people."
Michael CTO, $100M Health Startup
Book a call

Days to weeks, depending on team size and project complexity. We scope your case in the call.

Who it's for

Engineering leaders who want agentic engineering to stick.

This isn't a lecture for converts or a pitch for skeptics. It's for the leader whose team has the tools, but hasn't turned them into a way of working yet.

  • ✓

    You lead a team of 5 to 30 developers.

  • ✓

    Your devs have the AI tools but still use them like autocomplete.

  • ✓

    You have an AI task force, or someone ready to own adoption. After the workshop they track the KPIs and drive it forward.

  • ✓

    You report on velocity and quality. You want a configured repo, not a pep talk.

  • ✓

    Your stack is TypeScript, Python, Java, C#, Go, or similar. Greenfield or 10-year-old codebase, both work.

Juri Kühn
Your trainer

Juri Kuehn

Hi, I'm Juri. I've been building software for over 30 years, and more than 5,000 of my hours have gone into building it with AI. These days I set up engineering teams for agentic work and ship with them on their own code.

I founded Codeligence and dev-agents.ai, and I still write production code with agents every single day.

30+
Years in software
12+
Teams shipped
Daily
Production code with agents
"AI requires a new mindset and new workflows. Letting go of old habits and accumulated knowledge is not always easy. I take it to heart to make the transition as smooth as possible and show a bright perspective on using AI in the new software development era."
What teams say

After the Factory Accelerator, the new way of working sticks.

"We were using Claude Code but treating each session as a one-off, with no shared conventions across the team. Now we approach it as an orchestration model, not a coding assistant. The goal shifted from AI helps us code faster to AI handles implementation while we supervise architecture and outcomes."
Bryan Scown

Bryan Scown

Director of Software Engineering, Valant

"There is a lot of AI hype out there. As a B2B SaaS company we evaluate every angle, but speed alone is not enough, we want a product that stays maintainable. Juri's session moved us forward with concrete value for our developers, close to our day-to-day coding."
Dr. Alexander Zimmerhofer

Dr. Alexander Zimmerhofer

Digital Solution, ITB Consulting GmbH

"One of the best tech talks I've been to in recent times. Very inspiring. You certainly rattled some people."
Michael

Michael

CTO, $100M Health Startup

"Working with Codeligence was completely uncomplicated. We were able to evaluate and start using AI quickly and with minimal effort. They made getting started effortless."
Tobias D. Kern

Tobias D. Kern

Managing Director, Atelier für Mediengestaltung

Format & logistics

What to expect on the day.

Duration
Days to weeks
Format
Live, remote or onsite
Attendees
Your whole team
Language
English
Prep
One repo, access ready
You keep
Repo config + final report
After the workshop

It doesn't end when we leave.

The workshop gets your team agentic-ready and your repo configured. What keeps it that way is rhythm: models and tools change every few months, and a setup nobody tunes goes stale. That's why most teams book a cadence.

You are here 01

Factory Accelerator

Workshop, days to weeks

Hands-on workshop. We configure your repo for agents and prove it on stories from your backlog. Your team owns the setup.

02

Optimization sessions

Weekly, monthly, or quarterly

We come back on a rhythm you pick: look at how the team actually works with agents, tune context and skills, and pick up what the newest models make possible.

03

The next teams

When you're ready

The setup that works for one team becomes the playbook for the rest. We help you roll it out, team by team.

FAQ

Questions leaders ask before booking.

Who should attend?

Your core dev team plus the lead (Tech Lead, CTO, or VP Engineering), and the roles the factory touches: product managers, Scrum Masters, QA engineers, and support. This is hands-on work on your repo, so the people who write the code should be in the room.

Will it work on our codebase?

Yes for mainstream stacks like TypeScript, Python, Java, C#, and Go. Works on both greenfield projects and decade-old codebases.

Do you need access to our code?

Yes. The whole point is to configure your real repo, so we work on it together during the workshop sessions. Read and write access for the engagement, scoped however your security team wants it.

What if my team is skeptical of AI?

That is the most common case. We start by shifting the mindset, then prove it on your own backlog, which converts skeptics faster than any demo.

Remote or onsite?

Default is remote. Onsite is possible, we can discuss on the intro call.

What does it cost?

Every engagement is scoped to your team, your repo, and your priorities. We scope your case in a call. Book a time and a senior engineer picks it up.

Ready to launch

After the Factory Accelerator,
your team is agentic-ready.

Hands on with your team, days to weeks depending on team size and project complexity. Pick a time and we'll start with a 20-minute intro call to confirm fit and scope.

Book a call

Days to weeks, depending on team size and project complexity. We scope your case in the call.