GitHub Copilot

Do you have a GitHub handle?
Enter it to personalise your report, or skip if you don't have one.
What's your first name?
So we can tailor the report to you.
What's your work email?
We'll use the domain to suggest your company — pick it, or type it yourself if we get it wrong.
Please fill in your first name, work email, and company.

Live
Before you start

The four stages of GitHub Copilot adoption.

Your report benchmarks your team against these four stages, using GitHub's own Copilot usage data across roughly 10,600 licensed developers (14 Jul to 10 Aug 2026).

STAGE 0

Passive

Licensed for GitHub Copilot, but not yet part of the regular development workflow.

4.9 days

median PR merge time

STAGE 1

Code-first

Licensed and using code completions or inline chat inside the IDE.

1.9 days

median PR merge time

STAGE 2

Agent-first

Working with one coding agent, such as the CLI, the coding agent, or code review.

2.2 hours

median PR merge time

STAGE 3

Multi-agent

Comfortable running two or more agents as part of everyday workflows.

1.3 hours

median PR merge time

How it works

Output preview

    Frequently asked

    We use public GitHub signals only, and only if you offer a handle. No private repository access required.

    Add 3 quick details to sharpen your signal.

    This helps estimate team impact, AI tool sprawl, and the most relevant GitHub Copilot opportunity.

    All three questions are required.

    Generating your AI Development Cost Signals

    0%
    Reviewing public GitHub activity signals
    Estimating engineering productivity patterns
    Checking potential AI tool sprawl
    Mapping GitHub Copilot fit
    Building your cost control recommendation
    Comparing throughput against adoption benchmarks
    Request received

    Signal interrupted

    We couldn't generate your signals.

    Something went wrong on our side. Your inputs weren't lost — try again in a moment.