New Research Research: 167K PRs analyzed Read Report
Engineering Delivery Visibility

See how your team is actually delivering.

Track cycle time, review load, PR flow, and whether AI-related signals move with better outcomes. Connect GitHub without reading source code.

Built for 15-75 dev teams
Free during Alpha
5 min setup
No code access

Questions that show up too late

The delivery problems most leaders feel before they can prove them.

"Why did cycle time jump this sprint?"

Work is still shipping, but something slowed down. You need to know whether the delay is coding, review, or merge time.

"Which repos are creating review bottlenecks?"

A few pull requests can consume the whole review queue. Without repo-level visibility, every slowdown looks random.

"Is AI helping delivery or just creating more review work?"

AI can speed up coding, but it can also increase review load. You need the delivery metrics next to the signal, not another opinion.

Tformance connects to GitHub and shows the flow behind those answers.

Platform Features

What you get

Delivery visibility, review load, and team trends in one dashboard.

Loading preview...

Use arrow keys to navigate between features

How It Works

Three steps. Five minutes. No code changes.

1

Connect

One click to connect:

  • GitHub (repos, PRs)
  • Jira (tickets, status) Soon
  • Slack (surveys) Soon

No agents. No code changes. Just OAuth.

2

We Track

We collect metrics automatically:

  • PR size, cycle time, reviews
  • AI-related signals alongside direct delivery metrics
  • Jira correlation Soon

Daily sync. No manual work.

3

You See

Dashboard with clear answers:

  • Cycle time and review bottlenecks by repo
  • Trend changes across teams and pull requests
  • Review load distribution without leaderboards

See what changed, where work is stuck, and where to look first.

See what's slowing your team. Know what to fix.

Dashboards with context, not raw CSV exports.

Delivery Comparison

Compare delivery outcomes side by side, then use AI-related signals as one lens for interpretation.

Cycle time
Signal: 2.1 days Baseline: 3.4 days
Review rounds
Signal: 1.3 Baseline: 2.1
Lines changed
Signal: 142 Baseline: 89

Review Load View

See where review load is concentrated before the queue becomes the team's bottleneck.

API
Heavy queue
Web
Balanced
Infra
Needs attention

Trend Charts

Week-over-week delivery trends. Track whether outcomes improve as your process changes.

4 weeks ago This week

Weekly Slack Digest

Coming Soon

Automated summary in your Slack channel. A weekly view of flow, review load, and changes worth discussing.

t

Weekly Delivery Brief

This week: cycle time improved 18% while review load stayed flat.

We Never See Your Code

Seriously. Not a single line. Here's exactly what we access.

What We Collect

  • + PR metadata (title, size, timestamps)
  • + Review counts and cycle times
  • + File paths and change counts
  • + Author and reviewer info

What We NEVER Touch

  • - NO source code content
  • - NO file diffs or patches
  • - NO commit message bodies
  • - NO private messages

Your code stays in GitHub. We only see metadata.

What We Actually Request

Our GitHub GraphQL query and a real response

github-api.graphql
pullRequests(first: 100, states: [MERGED, OPEN, CLOSED]) {
  nodes {
    number
    title
    body
    state
    createdAt
    mergedAt
    additions
    deletions
    isDraft

    author { login }
    labels { nodes { name, color } }
    milestone { title, number, dueOn }
    assignees { nodes { login } }
    closingIssuesReferences { nodes { number, title } }

    reviews {
      nodes {
        state        # APPROVED, CHANGES_REQUESTED, COMMENTED
        body
        submittedAt
        author { login }
      }
    }

    commits {
      nodes {
        commit {
          oid          # Git SHA
          message
          additions
          deletions
          author { date, user { login } }
        }
      }
    }

    files {
      nodes {
        path           # File path only
        additions
        deletions
        changeType     # ADDED, MODIFIED, DELETED
      }
    }
  }
}
response.json
{
  "number": 2420,
  "title": "Inertia migration: Settings",
  "state": "MERGED",
  "createdAt": "2025-11-13T16:00:00Z",
  "mergedAt": "2025-12-24T15:12:10Z",
  "additions": 1700,
  "deletions": 1611,
  "isDraft": false,
  "author": { "login": "pradumnkumar" },
  "labels": { "nodes": [] },
  "reviews": {
    "nodes": [
      {
        "state": "APPROVED",
        "submittedAt": "2025-12-24T15:09:44Z",
        "author": { "login": "cousinemmanuel" }
      }
    ]
  },
  "commits": {
    "nodes": [
      {
        "commit": {
          "oid": "b6cc8f045814...",
          "message": "fix: linter issues",
          "additions": 1,
          "deletions": 2
        }
      }
    ]
  },
  "files": {
    "nodes": [
      {
        "path": "app/controllers/settings/base_controller.rb",
        "additions": 16,
        "deletions": 0,
        "changeType": "ADDED"
      }
    ]
  }
}

Notice: No source code content, no diffs, no secrets. Just metadata about your PRs.

You're In Control

Minimal access. No lock-in. Your data, your rules.

Minimal Permissions

Read-only access to PRs. No write permissions, no admin access, no repo settings.

Delete Anytime

Revoke access in one click. All your data is wiped—no questions, no lock-in.

Private by Default

Only your team sees your metrics. No public dashboards, no shared leaderboards.

Honest Answers

Questions you might have before trying another tool.

Verify it quickly. Connect GitHub, inspect the raw pull-request data, and decide whether the trends match what your team already feels. The product should earn trust from the data, not from a pitch.

Very focused. Tformance is built around GitHub-first delivery visibility: cycle time, review load, PR flow, trends, and AI-related signals as a secondary lens. We keep the scope narrow so setup stays fast and the metrics stay legible.

If you need heavy workflow automation or enterprise finance reporting, use the tool built for that. If you want delivery visibility for a 15-75 developer team without enterprise sprawl, Tformance is a much faster way to get answers.

Straight feedback on whether the metrics help you act. Which views clarify delivery? Which charts are noise? What should be simpler? That is the feedback that improves the product fastest.

We treat AI-related metrics as directional signals, not perfect truth. The direct metrics are cycle time, review time, PR flow, and throughput. AI-related signals help you test whether those outcomes improve or worsen as usage changes.

Live now: GitHub integration, pull-request metrics, cycle time, review load, team-level trends, and public benchmarks. Coming next: Jira context, Slack summaries, and deeper team health signals.

See what is slowing delivery before it becomes a status meeting

Connect GitHub and get cycle time, review load, PR flow, and trend visibility in minutes.

Free during Alpha. No credit card required.

Start Free