Skip to content
Ahmet Eren Lapanta
TürkçeLet's talk
Menu
Let's talk

The English site is still catching up with the Turkish one, so a few pages and links are Turkish for now.

Let's talk

Everyone on your team can get a demo out of AI. Together we get it to production.

When an agent writes the code, review needs rules the whole team shares. If they aren't written down, every PR gets judged by whoever happens to read it. We put those rules in place with your team, in your company's own code. The first step is a 2-hour session.

This way of working took shape in the companies and teams I've worked with. Some of those teams use Claude Code with TeamHandbook today.

See the formats

The call is free and there are no slides. By the end you know which format fits and roughly how long it takes.

The agent's code gets stuck on the way to production

  • Someone built a demo with AI and everyone liked it, but nobody thought about permissions or what happens under load.
  • The agent's code reaches review. No one knows what to look for, so the PR waits or goes in unread.
  • The agent wrote the code and the tests, and the tests are green. Nobody on the team is sure that means much.
  • The team's rules aren't written down, so the agent makes the same mistake in every session.

Together we write the team's rules, and what the agent may touch, into the repo the agent works in every day. A new hire and the agent read the rules from the same place.

Formats and how long they take

The easiest start is the 2-hour session. We decide what comes after once the team has shipped its first piece of work.

If you're not sure which format to start with, take the 8-question team test (in Turkish).

  • Free30 min

    Intro call

    Who it's for
    The person who decides for the team
    What stays with the team
    Which format you start with and roughly how long it takes
    Book a call 
  • Start here2 hours

    Live session with the team

    Who it's for
    A team that writes code, up to 6 people
    What stays with the team
    Everyone's first real piece of work done with the agent, the team's rules in the repo, and the session report
    See a sample report 
  • 1 day

    Workshop

    Who it's for
    A team or a department
    What stays with the team
    Real tasks picked from your backlog get finished. The team's first skills come out of that work.
    Talk about scope 
  • 2 to 4 weeks

    Team skill repo

    Who it's for
    A team that wants the setup to stick
    What stays with the team
    A shared skill repo built with TeamHandbook. The team's recurring tasks run the same way in everyone's agent.
    See TeamHandbook 
  • Project

    Idea to product

    Who it's for
    A business with an idea and no product yet
    What stays with the team
    A first version that's live and in use
    Tell me your idea 

What you have after the session

After every session I send the team a written report. The one below is a sample and doesn't belong to any real team.

Sample

2-hour session with the team

A backend team of 5

Before the session
The team ships changes with the agent, but none of its rules are written down. Nobody trusts the agent's code in review.
After the session
Everyone on the team finished a small change from their own work with the agent. Each change went through review by someone on the team.
What the team keeps
  • The team's rules in the repo, meaning CLAUDE.md and the agent's permission settings
  • The team's first two draft skills
  • A written list of where we got stuck in the session
  • A suggestion for the next 30 days
Next step
The 1-day workshop or the team skill repo. We read the report together and pick one.

How the two hours go

Everyone works on their own computer, on their own task. When someone gets stuck, I sit down with them and show them what to tell the agent.

  1. 10 min

    Opening

    What gets finished today

  2. 15 min

    Setup

    Repo and Claude Code ready on every machine

  3. 20 min

    Telling the agent what to do

    The agent writes the plan, the person reads and fixes it

  4. 45 min

    Working with the agent

    The agent writes the test first, then the code, and opens the PR

  5. 20 min

    Review and merge

    Someone on the team reads the PR, whoever has merge rights merges it

  6. 10 min

    Wrap-up

    Where the agent got it wrong

I plan the session around your team's repo. It starts with a 30-minute call.

How I work

  1. 01

    The code stays in your company

    The agent runs on your team's computers through your company's Claude account. I keep no copy of the code. In the first call we write down together what the agent may touch.

  2. 02

    Every job ends with something in writing

    You get a written report after every session, with what got finished and what's next. It links to the PRs and quotes no code.

  3. 03

    Scope is written before we start

    The proposal after the intro call says what's included. What's left out is written in the same place.

  4. 04

    If it isn't a fit, I say so in the first call

    What you need might not be training, or I might not be the right person. Then you get a short email instead of a proposal.

Questions teams ask

Do we work in our own code? Where does it go?

Yes, wherever possible, in your team's own repo, and the code stays there. The agent sends the parts it works on through your company's Claude account, so that account's data rules apply. I keep no copy. For a sensitive repo we use a template repo instead.

Does everyone need Claude Code?

Yes. Everyone joining the session needs a Claude subscription or a company account. If access isn't set up yet, we schedule the session for after it is.

What does the price depend on?

On the format, how many people join and for how long. After the intro call I send you a written proposal with the number in it.

Why a team session when there's a free guide?

The free guide is for one person putting their own app online from a template repo. In a team the hard part is a grown codebase and people reading each other's PRs, so wherever possible we work in your team's own repo.

What happens after the session?

The team gets a written report with where we got stuck and my suggestion for the next 30 days. If you want to keep going, we carry on with the workshop or the skill repo.

Let's talk

We start with a 30-minute call and I bring the questions. The first two are how big the team is and which repo you work in. The rest of the time goes to where things get stuck.

If the calendar doesn't suit you, write to me on LinkedIn or fill in the form.

I use your details only to reply to this request. Data protection notice (in Turkish)