Contact

For teams that work with code

Set up Claude Code for your team

We set up Claude Code for your codebase, with rules, skills, connections and hooks that fit the way you work.

  • Claude Code, MCP, Agent SDK
  • Set up in your repository
  • Hands-on with your team
Request a call

Who it's for

For teams with their own codebase who want Claude Code to become part of their daily work.

What you get

  • Rules files (CLAUDE.md) that capture your conventions
  • Skills and hooks for tasks that keep coming back
  • MCP connections to the tools your team already uses

How it works

  1. 1We look at your codebase and how your team works.
  2. 2We set up the rules, skills, connections and hooks.
  3. 3We work through the first real tasks from your backlog with your team.

What we work with

  • Claude Code
  • CLAUDE.md, skills, hooks
  • MCP
  • Agent SDK

Work

Where we've done this before.

Two examples, contributions to someone else's open-source project and an in-house system built with Claude Code, rules files, skills and hooks.

  • Open source

    Claude Code for teams

    Norman Finance MCP server

    Four pull requests to Norman Finance's open-source MCP server, all reviewed and merged by the project's maintainers.

    New tools for suppliers, bills and attachments, plus fixes to input validation and to the published package.

    What it shows

    Code that holds up in someone else's codebase.

    The pull requests on GitHub(external site, opens in a new tab)
  • In-house system

    Automation · Claude Code for teams

    Daily briefing

    The briefing we run our own business on. Every morning, one email with everything that needs attention.

    The system reads several mailboxes, queries platforms through their APIs and captures invoices with text recognition. A language model sorts and summarises it all. Built with Claude Code, rules files, skills and hooks.

    What it shows

    Many sources become one overview, with nobody lifting a finger.

    More on automation

Working together

How we work.

  1. Fixed price or day rate, agreed upfront

    Before any work starts, we agree together what will be delivered.

  2. Remote, or on site in and around Munich

    Most of the work happens remotely, in English or German, on Munich time. For the kick-off or the handover we can also come to you in and around Munich.

  3. Your code, your accounts

    We work in your repository and your accounts. We don't keep access to your production systems once the project ends.

  4. After handover, it runs without us

    You get a written description of how everything fits together. With the code, the accounts and that description, someone else can carry on if we're ever unavailable.

Contact

Tell us what you're planning.

A few sentences are enough.

What happens next

  1. 1Tim Leonsteyn reads your message himself and replies within two working days.
  2. 2If useful, we follow up with a short call about goals and scope, not a sales pitch.

Or directly

We use your details only to answer your enquiry. Details in our privacy policy.