New: Calculate your AI development ROI in minutes Try the calculator →
Engineering Health

Workflow Analytics

See exactly where pull requests lose time — from the moment code is written to the moment it ships. Eliminate bottlenecks at every stage of your delivery pipeline.

4

Pipeline Stages

Coding, Pickup, Review, Merge

PR-level

Granularity

Drill into any metric, any PR

Real-time

Bottleneck Detection

Know what's stuck before it's a problem

Industry

Benchmarks

Compare to 50th, 75th, 90th percentile

Cycle Time BreakdownLast 8 weeks · 75th Percentile

Coding

18m

↓ 71%

Elite

Pickup

5m

↓ 18%

Elite

Review

1d 6h

↑ 12%

Focus

Merge

22m

↓ 9%

Elite

Metric

Avg Value

Industry Avg

Pickup Time

5m

≤ 1 hr

Review Time

1d 6h

≤ 4 hrs

Merge Rate

94%

≥ 90%

Pipeline Visibility

Find the bottleneck. Fix it. Measure the improvement.

Most teams know their overall cycle time is too long — but not why. Signals breaks every pull request into four precise stages: coding, pickup, review, and merge. You'll instantly see which stage is responsible for your slowest deliveries and by how much.

  • Per-stage time measured to the minute — not averaged across vague "cycle time" buckets
  • Elite / High / Medium / Focus ratings benchmarked against industry peers at your chosen percentile
  • Period-over-period trend on every stage so you know if you're improving or regressing
  • Click any stage to see the individual PRs contributing to its average — with author and status

Pickup & Review Time

Know exactly how long reviewers take to jump in.

Pickup time is the silent killer of developer flow. A PR sitting unreviewed for hours blocks the author, stalls the team, and inflates cycle time — without anyone noticing until it's too late. Signals tracks pickup and review time separately, surfaces patterns over weeks, and benchmarks them against what great looks like.

  • Pickup time: measured from PR open to first review activity
  • Review time: measured from first comment or approval to merge-ready state
  • Weekly trend charts reveal whether review delays are getting worse — before they become cultural debt
  • Filter by team or repo to pinpoint whether it's a specific group or a systemic issue
Pickup & Review Time — Trend8-week window

Pickup Time

5m

Elite

8 wks ago

Now

Review Time

1d 6h

Needs Focus

8 wks ago

Trending up ↑

Industry average review time at the 75th percentile is ≤ 4 hours. Your team is currently 7× above that threshold.

Merge Rate & PR ThroughputLast 8 weeks

Merge Rate

97%

Elite

PRs Reviewed

142

↑ 24%

Avg PR Size

+87

lines changed

PR Title

Cycle Time

Status

feat: add OAuth2 token refresh logic

12m

merged

fix: resolve race condition in queue processor

2h 4m

merged

chore: update CI pipeline configuration

8m

merged

Click any row to see pickup, review, and merge stage timing for that PR

Merge Rate & Throughput

A high merge rate isn't luck — it's a process signal.

Merge rate tells you how much of your team's work actually makes it to production. A dip in merge rate is often the first signal of blocked PRs, unresolved review cycles, or a code quality problem — weeks before it shows up in delivery velocity. Signals tracks it continuously so you catch it early.

  • Merge rate tracked over time — not just as a point-in-time snapshot
  • PRs reviewed count reveals actual reviewer throughput, not just open/close velocity
  • Drill into any PR to see exactly how long each stage of its lifecycle took
  • Filter by team, repo, or author to isolate where merge rate degradation is coming from

What You Get

Every stage of your pipeline — measured, benchmarked, and improvable.

Stop guessing where time goes. Signals makes every minute of your delivery pipeline visible so you can act on facts, not instinct.

Pickup Time

Measure the gap between when a PR is opened and when a reviewer first engages. Reduce developer idle time and keep code flowing through the pipeline.

Review Time

Track how long code spends under active review. Identify teams spending too long in review cycles and surface the patterns driving that delay.

Merge Rate

Track the percentage of PRs that successfully reach merge. A declining merge rate is an early warning signal for blocked workflows or review overload.

Cycle Time Variance

A low average cycle time hides a high variance. Signals exposes the spread between your fastest and slowest PRs so you can achieve consistent, predictable delivery.

PR-Level Drill-Down

Click into any metric to see the exact pull requests behind it — with per-PR stage timing, author, and status. Go from team-wide average to a specific PR in two clicks.

Industry Benchmarks

Compare pickup time, review time, and merge rate against the 50th, 75th, and 90th industry percentiles. Know whether you're fast — or just fast compared to yourself.

How It Works

Measure. Identify. Fix. Repeat.

01

Connect your repositories

Link GitHub, GitLab, or Bitbucket in minutes. Signals immediately starts measuring every PR event — open, review, approve, merge — with no agents or code changes required.

02

See your pipeline in detail

Every pull request is broken into Coding, Pickup, Review, and Merge stages. Signals calculates averages, trends, and variance for each — across every team and repo.

03

Identify the real bottleneck

Elite, High, Medium, and Focus ratings benchmarked against industry percentiles surface exactly which stage is pulling your cycle time up — and by how much.

04

Measure the improvement

After your team makes a change, compare periods to see the actual impact. From review SLAs to reviewer assignments — validate your fixes with real data, not anecdote.

Stop coordinating. Start shipping.

Imagine engineers spending time building instead of chasing status. See what that looks like for your team.

Quick start · Real impact