Five signals · one action · Slack or email

Know how your team is delivering before standup, without opening Jira.

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

Gabel APP 09:00

📊 Weekly Engineering Brief — Helio Orbital

2026-06-02 🔴 CRITICAL

🎯 To Do

Unblock aging WIP first — likely driving cycle time drift: HELIO-113, HELIO-112, HELIO-111 (+6 more). Hold new intake until WIP drops below 8.

🐌 Slowest:


⏱️ Cycle time drift

7.1 days (P85)
🔴 worsened (6.2 days → 7.1 days)

P85 cycle time is 7.1 days vs a 4.9-day baseline (+44.9%). The drift started around 2026-06.

▃▃▄▄▆ 4.5 days → 7.1 days (5 briefs)

👉 Next: Target P85 cycle time back to 4.9 days (currently 7.1). Review WIP intake and items stalling in review.


🔀 PR merge lag

3.59 calendar days avg
🔴 worsened (3.49d → 3.59d)

Average PR merge time is 3.59 calendar days (open → merge) across 8 merged PRs. 5 PRs had no review within 24h.

▃▄▅▅▅ 2.1d → 3.59d (5 briefs)

👉 Next: Route review requests — 4 PRs waited 24h+ for a first review. Prioritize merge reviews (4.4d avg vs 2d target).


📥 WIP spike

14 active work items
⚠️ still above target

Team has 14 active work items (1.75× the team size of 8). 9 items have been active for more than 5 days.

▃▃▄▆▆ 10 items → 14 items (5 briefs)

👉 Next: Unblock the 9 stuck items; consider pulling nothing new until WIP drops below 8.


✅ On track

📊 Velocity variance 31% CoV 🟢 improved (36% → 31%)

Target: ≤35% CoV


🐛 Bug ratio 18% 🟢 improved (22% → 18%)

Target: ≤25% of throughput


How it works

Replaces the weekly Jira sweep, not your stack.

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.

What you do today

  • Open Jira and scroll the active sprint and backlog.
  • Wonder whether cycle time or bug volume is worse than last time you checked.
  • Check the pull request queue — or skip it altogether.
  • Walk into standup without a reliable view of what changed.

What Gabel will do for you

  • Five signals with clear thresholds and the week-over-week change.
  • Direct links to affected Jira stories and PRs when reviews fall behind.
  • One prioritized action for you to focus on this week.
  • A flag when last week’s fix didn’t actually move the number.

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

Predictable rules. Transparent thresholds.

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.

  • What we read — Jira issue metadata, sprint fields, status transitions, and pull request open / merge / review timestamps. Read-only API access.
  • What we never store — source code, ticket descriptions, attachments, or any customer PII.
  • When a signal fires — the 85th-percentile cycle time drifts more than 20% from its 4-week baseline; work in progress exceeds 1.5× team size; bugs exceed 25% of completed work; sprint-to-sprint velocity varies by more than 35%; average pull request merge time exceeds 2 calendar days (plus the count of PRs waiting 24+ hours for a first review).
  • How it arrives — Slack incoming webhook or HTML email. Optional 12-week trend page on a secret URL, no login required.
    • Optional mid-week alert — covers work-in-progress and pull request lag only, silent when both are within target

Pricing

EUR 49 · USD 55 · CHF 49 per team, per month.

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

Five thresholds. Linked issues when they fire.

All five are computed from Jira board metadata and pull request history. Read-only access; Jira stays the system of record.

> 20% vs 4-week average

Cycle time drift

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.

> 1.5× team size

Too much work in flight

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.

> 25% of completed work

Bug ratio rising

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.

Variance > 35%

Velocity inconsistency

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.

> 2 calendar days

Pull request merge lag

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.

Cross-signal

To Do

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

Async setup. First real brief within a week.

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.

1

Share your name and email

We follow up to confirm your Jira site, board, team size, and git host. No credentials in this form.

2

Secure credential handoff

We send a short setup guide. You share read-only API access on a secure channel, and we provision your workspace.

3

First brief in your channel

The first brief arrives on your desired weekday and time. After that, weekly on the same schedule.

FAQ

Frequently asked questions

Is this an AI copilot or agent platform?

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.

What makes this different from LinearB or Swarmia?

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.

Do you require Jira?

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.

Does this work with GitHub or only Bitbucket?

Both. One git provider per subscription: a GitHub organization or a Bitbucket workspace.

Do we need to create a Slack bot?

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.

Is the trial free? What happens after?

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.

What data leaves our environment?

Issue metadata, sprint fields, and pull request metadata only. Read-only access. We never read source code or ticket bodies.

Can we see a sample shaped to our board before committing?

Yes. After a short conversation about your setup, we can send a redacted sample brief before you provision any API access.

Free trial

Leave your email. We’ll do the rest.

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.

  • Four weeks free, no credit card.
  • After the trial: EUR 49 / USD 55 / CHF 49 per team, per month — opt-in only.
  • No dashboard and charts to learn. No bot to install.

We’ll reach out within one business day to set things up. By submitting, you agree that we process your details as described in our privacy policy.