DeliveryCompass gives engineering managers team-level PR metrics without the staff-meeting spreadsheet. Merge throughput, PR lead time and review health sit on one dashboard, on definitions every team shares.
It connects to GitHub with read-only access, and setup takes four steps. It’s built by Insurgency Labs and free during Early Access, with no credit card.
DeliveryCompass · Team delivery metrics
Table of Contents
- What you get
- The spreadsheet it replaces
- How to set it up in four steps
- What it doesn’t measure
- Who should try it
- What works in Early Access today
- FAQ
- Try it
What you get
DeliveryCompass reads your GitHub organization with read-only access. It turns pull request and review activity into team-level KPIs on a shared dashboard:
- Merge throughput shows how much each team is shipping.
- PR lead time shows how long work sits in the pipeline.
- Review responsiveness shows where review lag is slowing teams down.
- Weekly summaries flag who moved up or down vs the prior period, ready for leadership reviews.
- Contributor signals give you evidence for coaching conversations, on the same definitions your directors see.
You map repositories to teams once. After that, everyone compares teams on the same metrics instead of five different spreadsheet tabs.
The spreadsheet it replaces
Every engineering manager I talk to has the same ritual. Export something from GitHub, paste it into a spreadsheet, and argue about definitions. Then rebuild the deck the night before the staff meeting.
By the time everyone agrees what “lead time” means, the meeting is over. DeliveryCompass is what I wished existed instead: engineering intelligence for GitHub PR delivery, built for managers who run recurring delivery reviews.
The product site has a deeper walkthrough of using these metrics in staff meetings: GitHub metrics for engineering managers.
How to set it up in four steps
- Create an account at dc.insurgencylabs.com.
- Connect a read-only GitHub PAT (
read:org,repo). - Finish onboarding. Repo and team import runs on the worker in the background.
- Assign repos to teams, then open the dashboard.
There’s no sales call. It’s free during Early Access, with no credit card. More detail is in how it works.
What it doesn’t measure
I’m opinionated about scope. DeliveryCompass is not:
- A Jira or Linear replacement.
- Full deploy-based DORA. It needs no CI/CD or incident pipelines.
- Source-code surveillance. We import PR metadata and statistics only, not diffs or file contents.
Asking “are we deploying safely and how often?” needs pipeline data. Asking “how is PR flow and review health across my teams?” is the question DeliveryCompass answers. See limitations for the full Early Access scope.
Who should try it
- Engineering managers preparing staff meetings.
- Directors and VPs who want comparable team baselines.
- CTOs at startups scaling past “one spreadsheet for the whole org”.
If you run a small company and want help deciding what to measure in the first place, start elsewhere. The fractional CTO guide and the technical due diligence checklist cover that side.
What works in Early Access today
DeliveryCompass is in an Early Access pilot. The core loop works: GitHub import, team KPIs, charts, weekly summary and snapshots.
We’re iterating in the open, with a public roadmap, the limitations page, and a Discord community for pilot feedback.
It follows the same builder pattern as other things I’ve shipped, like the internal hackathon platform. This one is aimed at a problem I kept hearing from engineering leaders on GitHub.
FAQ
What is DeliveryCompass?
DeliveryCompass is engineering intelligence for GitHub PR delivery. It gives engineering managers team-level dashboards for merge throughput, PR lead time and review responsiveness. It uses read-only GitHub metadata, so staff meetings run on shared definitions instead of rebuilt spreadsheets.
Does DeliveryCompass replace Jira or track deploy frequency?
No. It is not a Jira or Linear replacement, and it does not measure deploy-based DORA metrics. It answers PR flow and review health questions from GitHub pull request data only. Deploy frequency and incident metrics require CI/CD or incident tooling.
Is DeliveryCompass free during Early Access?
Yes. You can start a self-serve trial at dc.insurgencylabs.com/app/onboarding with no credit card during Early Access. Scope and limitations are documented on the product site.
What GitHub access does DeliveryCompass need?
A read-only GitHub PAT with read:org and repo. It imports PR metadata and statistics only, not diffs or file contents.
Try it
If you’re an EM on GitHub and the spreadsheet ritual sounds familiar:
- Start free trial: self-serve onboarding, read-only GitHub.
- GitHub metrics for engineering managers: the longer guide on the product site.
DeliveryCompass is built by Insurgency Labs. Questions are welcome: schedule a call or reach out on LinkedIn.