EUR 49
USD 55 · CHF 49
Per team, per month · flat
Five signals · one action · Slack or email
Every week, Gabel checks your Jira board and repos against five delivery health thresholds. If something is off, you get the number, what changed week-over-week, and one specific action — posted to Slack or email.
EUR 49
USD 55 · CHF 49
Per team, per month · flat
5 signals
1 action
1 board per team
Delivered
Slack or email
On your schedule
Sample brief
How it works
Most engineering managers and tech leads already do an informal pass over Jira and pull requests before standup. Gabel runs that pass for you and posts the result — same data, on schedule.
Jira and one git host (Bitbucket or GitHub) stay where they are. EUR 49 / USD 55 / CHF 49 per team, per month. Team-level signals only — never used for individual developer scorecards.
Methodology
No black-box scoring. Each signal is a simple threshold on data you already have, and the narrative is templated from which signals fired and how the numbers moved week-over-week.
Pricing
Flat per team — not per developer seat. Covers one Jira board, the repositories you connect, and any delivery destinations (Slack channel, email address). A second team or board is a second subscription.
The five signals
All five are computed from Jira board metadata and pull request history. Read-only access; Jira stays the system of record.
85th-percentile cycle time pulling away from the 4-week baseline. Names when the drift began and the change from last week.
Next: pull cycle time back to baseline — review intake and items stalling in review.
Active work in progress exceeds 1.5× team size. Linked Jira keys for any item sitting 5+ days.
Next: unblock the named items and pause new intake until work in progress drops below team size.
Share of bugs in completed work, plus the rework rate from issues that regressed out of Done.
Next: inspect regressions from Done — rework may be driving the number more than new defects.
Sprint-over-sprint delivery is swinging. Names the outlier sprints and shows delivered-vs-committed counts.
Next: set the next sprint commitment to a median number that the team can more confidently deliver.
Average open-to-merge time, slowest repos, count of PRs waiting 24+ hours for a first review, and the slowest merges.
Next: route review requests in the repo where merges are stalling.
When several signals fire at once, Gabel picks the one to tackle first — with deep links to the slowest PRs when review lag is the bottleneck.
Role: tells you what to fix first when the board is noisy.
Getting started
Leave your name and work email. We reply within one business day to confirm your Jira site, stack, and delivery channel, send the setup steps, and share a sample shaped to your board before the first scheduled run to ensure it fits your team.
We follow up to confirm your Jira site, board, team size, and git host. No credentials in this form.
We send a short setup guide. You share read-only API access on a secure channel, and we provision your workspace.
The first brief arrives on your desired weekday and time. After that, weekly on the same schedule.
FAQ
No. Gabel runs fixed thresholds and deterministic rules over Jira and git metadata. The narrative is templated from which signals fired and how the numbers moved — no open-ended chat, no autonomous agent. You read one brief, not a new workspace.
Those are dashboards you log into, usually priced per seat. Gabel is a single weekly brief pushed to your channel with one prioritized action — no charts to interpret, no per-seat math, no weekly login habit to build.
Yes. All five signals are board-driven, so Jira Cloud or Jira Server with API access is required. Linear and Shortcut are not supported yet.
Both. One git provider per subscription: a GitHub organization or a Bitbucket workspace.
No. Trials use a standard Slack incoming webhook to your channel. If webhooks are restricted in your workspace, email delivery works just as well. No OAuth app to build or approve.
Four weeks free, no credit card. After the trial, EUR 49 / USD 55 / CHF 49 per team, per month if you opt in. Nothing converts automatically.
Issue metadata, sprint fields, and pull request metadata only. Read-only access. We never read source code or ticket bodies.
Yes. After a short conversation about your setup, we can send a redacted sample brief before you provision any API access.
Free trial
Drop your name and work email. We’ll reach out within one business day to learn your setup and get a real brief running on your own board.