Business Impact & ROI

Overview

The Business Impact & ROI feature connects engineering work to business outcomes. By tagging pull requests with value categories, you can answer questions that engineering dashboards alone cannot: Which work drove revenue? How much delivery capacity is technical debt consuming? What is the return on the last quarter of engineering investment?

This is the data VPs of Engineering and CTOs need for quarterly reviews and OKR check-ins — without building a custom spreadsheet every time.

---

Value Tagging

Every merged pull request can carry one or more business value tags. Tagging happens in two ways:

Method	How it works
GitHub PR labels	Apply a label matching a Koalr value tag to the PR before merge. Koalr syncs labels automatically during the next GitHub sync.
Manual tagging in Koalr	Open any PR in the Pull Requests view and assign a tag from the dropdown. Useful for retroactively categorizing past work.

Supported Value Tags

Tag	Typical use case
Revenue	Features that directly drive new ARR or expansion revenue
Cost Reduction	Infrastructure changes, automation, or efficiency work that lowers OpEx
Risk Mitigation	Security patches, compliance work, dependency upgrades
Developer Experience	Tooling improvements, CI speed, local dev quality of life
Technical Debt Paydown	Refactors, deprecations, test coverage improvements
Compliance	Regulatory or audit-driven work (SOC 2, GDPR, etc.)

---

The ROI Dashboard (/roi)

The main ROI dashboard gives a full-quarter view of how engineering time was allocated across value categories.

Section	What it shows
KPI row	Total PRs tagged this period, estimated value delivered, tech debt cost per sprint
Work-by-tag donut	Percentage breakdown of merged PRs by business value tag
90-day trend	Week-by-week stacked area chart of PR volume by tag — shows whether the mix is shifting over time

The date range picker at the top of the page controls all three sections. The default view is the trailing 90 days.

---

Technical Debt Cost Estimation (/technical-debt)

Koalr estimates the delivery drag caused by deferred technical debt using three signals:

1. Rework rate — percentage of lines changed in a PR that touch code modified within the previous 30 days (a proxy for churn driven by brittle code)
2. P75 cycle time delta — the difference in P75 PR cycle time between PRs tagged Technical Debt Paydown vs. Revenue feature PRs (debt work tends to take longer)
3. Delivery capacity drag — extrapolated estimate of sprint capacity consumed by debt-related slowdowns, expressed in engineer-hours per sprint

These three signals are combined into a cost estimate displayed on the /technical-debt page. The estimate is directional, not a precise accounting figure — it is intended to make the conversation about debt prioritization quantitative rather than anecdotal.

---

Who It Is For

Role	How they use it
VP of Engineering	Quarterly business reviews, headcount justification, OKR reporting
CTO	Board-level engineering ROI narrative, debt prioritization decisions
Engineering Manager	Sprint retrospectives, demonstrating team impact beyond velocity

---

Limitations and Best Practices

The accuracy of the ROI view is directly proportional to your tagging coverage. A team tagging 20% of PRs will see an incomplete picture; a team tagging 80% or more will see reliable trend data.

To get the most value:

• Aim to tag at least 50% of merged PRs. Koalr surfaces an untagged PRs list on the Business Impact page to make bulk-tagging easy.
• Use GitHub labels as your primary tagging method — it adds zero friction to existing PR workflows.
• Tag consistently. A PR that adds a feature and pays down debt can carry two tags.
• Run the ROI dashboard export (PDF) at the end of each quarter before your engineering all-hands.

---

Related Docs

• Custom Metrics — define your own KPIs alongside the built-in value tags
• DORA Metrics — delivery performance data that contextualizes ROI trends
• Reports — schedule automated ROI and DORA summary reports to stakeholders