Claude Code setup for engineering teams

Your team pays for Claude Code.
I make it part of how they ship.

Most teams use a fraction of what they pay for. Across 1,000+ companies, median AI adoption is 74% while median AI-assisted code is 27% (Jellyfish, 2026). I set up the shared config, guardrails and tool connections that close that gap. Fixed price. Two weeks.

Team Setup $3,500 flat. Or start with a $750 audit.

Where are you now?

Pick the one that sounds like your team.

  1. Seats paid for. Barely used.

    A few people tried it, got lost, and went back to the old way.

    Team Setup →
  2. Two power users. Everyone else stuck.

    Every developer has a different setup, and nobody shares what works.

    Team Setup + Monthly Care →
  3. Claude needs your internal tools.

    It writes the code but cannot see your data, your admin or your tracker.

    MCP Server →

Packages

Published prices. Fixed scope.

The price is agreed before work starts and does not move.

Harness Audit

$750 one-time

Credited in full toward Team Setup

You want to know what is wrong before you commit.

  • Review of your CLAUDE.md files, hooks, permissions and MCP setup
  • A walkthrough call with your lead
  • A written, ranked fix list your team can execute

Team Setup

$3,500 flat

Two weeks · up to 15 developers

Seats are paid for. Usage is not.

  • A shared CLAUDE.md per repo that encodes your conventions
  • Hooks and permissions: guardrails that run every time, not when someone remembers
  • Skills for the work your team repeats
  • 1–2 existing MCP servers connected (GitHub, Linear, your database)
  • Cost controls, so the bill does not surprise finance
  • A hands-on session on your real codebase
  • A check-in at day 30

MCP Server

$2,500 flat per server

Up to 7 tools · +$350 per additional tool

Claude can write the code but cannot see your systems.

  • One internal system (database, API or SaaS) connected to Claude
  • Read-only first; write access earns its way in
  • Tool descriptions written for the model, not for humans
  • Tests, docs and deployment
  • The source code is yours

Monthly Care

$1,500 per month

Month to month · 10 hours of work included

Claude Code changes monthly. Your setup should keep up.

  • Your setup kept current as Claude Code changes
  • New skills, hooks or tools within the 10 hours
  • Answers within one business day
  • Work beyond 10 hours is quoted at the flat prices above

Proof

Inspect the harness.

Buyer's guides tell you to ask a consultant for a real CLAUDE.md, a real hooks config and a real MCP integration. Here are mine, with private paths and client details removed.

The rules · CLAUDE.md (excerpt)

## Prohibited actions
- If something that should work with real data isn't working,
  fix it with real data. No mock, stubbed or simulated data
  unless explicitly requested.
- Never write TODO tasks in the code itself.
- Validate that all tests pass before marking a task complete.
- Never mark a task complete without the user's approval.

## Modes
EXPLORE → PLAN → IMPLEMENT.
No files change in EXPLORE. Plans need explicit approval.
Silence is not approval.
Standing rules the agent reads on every session. They are the reason it asks before it builds.

The guardrails · ~/.claude/settings.json (excerpt)

"hooks": {
  "UserPromptSubmit": [{ "hooks": [{
    "type": "command",
    "command": "python3 ~/.claude/scripts/wake_up.py --file",
    "timeout": 5000 }] }],
  "Stop": [{ "hooks": [{
    "type": "command",
    "command": "python3 ~/.claude/scripts/session_close.py",
    "timeout": 5000 }] }],
  "PreToolUse": [{ "matcher": "*", "hooks": [{
    "type": "command",
    "command": "node monitor/hook-handler.js PreToolUse" }] }]
}
Memory that survives resets: one hook loads context on the first prompt, another writes it back at the end. A monitor sees every tool call, on all eight hook events.

The integration · ad-operations MCP server (excerpt)

@mcp.tool
@tool_with_telemetry(category="campaign-management")
async def get_campaign(campaign_id: str, ctx: Context = None) -> dict:
    """Campaign ID → full config: paths, cost model,
    traffic source, country, URL.

    Use when: pre-launch verification → confirm path
      structure and offer assignment.
    Use when: diagnosing path issues → inspect default
      and conditional paths.
    Use when: updating a campaign → fetch the full entity
      first (the API requires all fields on PUT).
    """
    return await tracker.get(f"/campaign/{campaign_id}")

@mcp.tool
@tool_with_telemetry(category="campaign-management", is_write=True)
async def create_campaign(...): ...
From a paying client's ad-operations server: 43 tools, 18 of them flagged as writes. Descriptions tell the model when to call a tool, not only what it does. Every call is recorded with its outcome and latency.

Running in public

@agentjeanclaude is a disclosed AI agent that posts and talks with other agent builders on X. It runs on the harness above.

Try one before we talk

ContextOverflow is my public MCP server: a library of thinking techniques you and your AI share. Free, no login.

claude mcp add --transport http contextoverflow https://contextoverflow.org/mcp

How it works

The Two-Week Setup

  1. Book a 15-minute call

    Tell me what your team runs. You leave knowing which package fits, or that you do not need one.

  2. Get a fixed quote

    Scope and price in writing, agreed before any work starts.

  3. I build in your repos

    Config, hooks, skills and connections, on your real codebase.

  4. Handoff and day-30 check

    Your team owns it. We check usage a month later.

The terms

The Fixed-Price Agreement

Questions

Before you book

What does it cost?

Harness Audit $750, credited toward Setup. Team Setup $3,500 flat for up to 15 developers. MCP Server $2,500 for up to 7 tools, plus $350 per additional tool. Monthly Care $1,500 per month with 10 hours of work included.

Why not do it ourselves?

You can; the docs are good. What you pay for is skipping the trial and error: which hooks earn their keep, how to scope MCP permissions, how to keep 15 setups from drifting apart. If your team has the time, the audit gives you the fix list and you execute it.

Is our code safe?

I work inside your repos under your access controls. Tools start read-only. Anything that writes, spends or touches customers goes behind a human approval step.

Which stacks?

Claude Code works on any language. MCP servers in TypeScript or Python, local or remote: Cloudflare Workers or your own infrastructure.

What happens when Claude Code changes?

It will, often. Monthly Care exists for that.

Who is behind this? Tal Onn Sella, the Agentsmith. The story →

Fifteen minutes. A fixed price.

Tell me what your team runs. You'll leave knowing which package fits and what it costs, or hearing that you don't need one.

Book a 15-minute scoping call

No prep. No pitch.

Not sure there's anything worth a call? Sixty seconds will tell you →