Skip to content
ENDE
 Book a pilot

Pilot

Six weeks. One team. One repo. Real stories.

You watch kanman work on your backlog, under your rules, with evidence for every change. At the end you decide with results, not with a demo.

Fixed price from €5,000 for 6 weeks

Book a pilot What's included

The six weeks

What happens, week by week

  1. Week 1

    Setup

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

  2. Weeks 2-3

    First stories

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

  3. Weeks 4-5

    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. Week 6

    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 cost plus 15%

What we bring

  • Setup in a joint session with your team
  • The acceptance manifest pull request for your repo
  • A 30-minute review with you every week
  • 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

INV-41 Export invoices as CSV

Outcome gate passed

Acceptance criteria

  • The export button downloads a .csv file passed
  • One row per invoice in the selected range passed
  • Amounts use the shared money formatter passed
  • An empty range shows a message and no file passed
Spec
.kanman/acceptance/INV-41/export.spec.ts
Written
at intake, red before Ready
Ran on
clean checkout of 4e1c9a7
Duration
41.6 s
Run cost
€0.84
Trace thumbnail: the invoices page with the Export CSV button pressed and the downloaded file listed.
Illustration A capture from the demo sandbox replaces it.

The flow

What every story goes through

  1. 1. Intake

    Paste a requirement or tag kanman in Slack. You get 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. Handoff

    A pull request 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 week one, 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 pilot sandbox: a Docker Compose app with Playwright specs. {KEY} is replaced with the story key.

Book a pilot

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. The pilot 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 the pilot

What does it cost to run, and how do budgets work?
The Team plan is a flat price per AI team, listed in the pricing section. Model usage comes on top, on your own keys or at 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)
Does kanman take part in our Slack or Microsoft Teams conversations?
Only where you add it. It answers questions about the team's work with links and sources, and turns requests into story drafts that a lead approves before anything reaches the board. By default it speaks only when mentioned. Per channel you can let it speak up, with a daily cap, quiet hours and a stop button on every unprompted reply. Read the docs (opens in a new tab)
Can it merge to main on its own?
Only if your policy says so. By default a person reviews and merges. You can allow automatic merges for small changes: every gate green and the diff under a line limit you set. While main is red, kanman holds them. Read the docs (opens in a new tab)
Where is our code processed and stored? What do model providers see?
kanman runs in the EU. Coding happens in sandboxes in Frankfurt, and every run gets a fresh sandbox that is thrown away afterwards. Model providers see the prompts and code context a run needs, under your own contract if you bring your keys. With the self-hosted runner, code execution stays in your network. Read the docs (opens in a new tab)