Skip to content
ENDE
 Try it free

Guided onboarding

We set kanman up with your team.

Most teams start on their own with the 14-day trial. If you would rather have us there, we connect your tracker and repo with you, add the acceptance manifest and tune the rules until kanman fits how your team works.

Price on request, with any paid plan

Ask about onboarding What's included Or start the 14-day trial on your own

The onboarding

What happens, step by step

  1. Step 1

    Setup

    We connect your tracker and repo together, pick the Trial preset, and kanman opens the pull request with your acceptance manifest.

  2. Step 2

    First stories

    kanman takes real stories from your backlog. Every pull request comes with an evidence pack. You review as usual.

  3. Step 3

    Your rules

    We tune the policy with you. What kanman may touch, the budgets, which calls come to you. Most teams move to Balanced here.

  4. Step 4

    Results

    A written summary of what shipped, what needed rework, what it cost and what we would change. You keep all of it.

What your team brings

  • A repo on GitHub or GitLab, with GitHub Issues, Jira or GitLab as the tracker
  • One tech lead who reviews kanman's pull requests, about two hours a week
  • A CI pipeline that runs your tests. If it is thin, we help.
  • Model access, either your own keys or usage through kanman at provider cost plus 15%

What we bring

  • Setup in a joint session with your team
  • The acceptance manifest pull request for your repo
  • Regular reviews of runs, decisions and cost with you
  • The written summary at the end

What you get on every pull request

The evidence pack

Acceptance criteria, the spec that checked them, where it ran and what it cost. Attached to the pull request and the story.

Evidence pack of a finished run: 3 of 3 acceptance criteria passed, the acceptance spec passed in a clean environment, 14 tests and CI passed, cost and duration

The flow

What every story goes through

  1. 1. Tell kanman

    Describe the work in the app, in Slack or in Microsoft Teams. kanman asks what is unclear and drafts stories with acceptance criteria and a way to demonstrate each one.

  2. 2. Rules

    Your policy decides what kanman may touch, spend and merge. Big calls come to you with a recommendation.

  3. 3. Work

    Claude Code or Codex does the coding in a sandbox. kanman picks the model by complexity, so trivial fixes stay cheap.

  4. 4. Proof

    Before anything reaches review, an acceptance spec runs against a fresh environment. No spec, no Ready. No green run, no review.

  5. 5. Hear back

    kanman tells you the pull request is ready, with the evidence attached. Your people review and merge, or your policy does.

One new file

Your repo gets an acceptance manifest

It tells kanman how to start your app and run a story's spec on a clean checkout. kanman opens the pull request for it in the first step, and you review it like any other change.

.kanman/acceptance.json 
{
  "version": 1,
  "provision": {
    "type": "docker_compose",
    "file": "docker-compose.acceptance.yml"
  },
  "ready_url": "http://localhost:3000/api/invoices",
  "ready_timeout_seconds": 120,
  "setup": "npm ci && npx playwright install --with-deps chromium",
  "run": {
    "command": "npx playwright test",
    "spec_arg": ".kanman/acceptance/{KEY}/",
    "env": { "BASE_URL": "http://localhost:3000" }
  },
  "spec_dir": ".kanman/acceptance/{KEY}",
  "artifacts": ["test-results/**/trace.zip", "test-results/**/*.png"]
}

Example from the kanman sandbox: a Docker Compose app with Playwright specs. {KEY} is replaced with the story key.

Ask about onboarding

Tell us about your team

We reply within two working days and suggest a 30-minute call. No slides, just your backlog and our questions. You get an offer for your setup. Onboarding runs on a short order form under our Terms of Service, with our data processing agreement signed before any code is touched.

Or pick a time on cal.com (opens in a new tab)

We use your details only to answer this request. More in our Privacy Policy.

FAQ

Questions about getting started

Can we try it before we pay?
Yes. Every new team gets the Team plan free for 14 days, no card needed. When the trial ends, cloud runs pause until you pick a plan; your board and the free Local plan keep working. If you would like us to set kanman up with your team, guided onboarding is available on request.
Our repo has no acceptance tests. Can we still start?
Yes. The Trial preset works without specs and says so plainly in every evidence pack. In the first week kanman opens one pull request that adds an acceptance manifest. From then on every story gets a spec. Read the docs (opens in a new tab)
What does it cost to run, and how do budgets work?
Every plan is a flat price per AI team, never per seat, listed in the pricing section. Local is free, Starter and Team are billed monthly, Enterprise is contracted for the number of teams you need. Model usage comes on top, on your own keys or at provider cost plus 15%. You set budgets per run, per day and per month with hard stops. Incident work is never blocked by a budget. Read the docs (opens in a new tab)
Which models and agents does it use? Can we use our own contracts?
The coding runs through Claude Code or Codex. You can bring your own keys for Anthropic, OpenAI, Azure OpenAI or AWS Bedrock, or your company's OpenAI-compatible AI gateway, or let kanman pass usage through at cost plus 15%. kanman picks the model by complexity, so small fixes stay cheap. Read the docs (opens in a new tab)