Every Signal. One Honest Report.
Focus pulls activity from your time tracker, repositories, issue tracker and CI/CD pipeline, then turns it into a single scheduled report your managers actually read — with context, not just numbers.
Balanced week overall. Low commit counts on two profiles are support-heavy contributions, not underperformance. One account has no data in any source — likely a coverage gap, not a result.
One report, every source
Focus connects to the tools your team already uses and reads them — nothing more. Every connector is read-only, and every report shows exactly which sources were reachable.
Time & activity tracking
Productive hours and efficiency, averaged only across days actually worked — weekends and time off never dilute the score.
Code repositories
Commits, changed files and repositories touched across every Git provider you use — aggregated per person, never per keystroke.
Issue tracker
Resolved items, logged effort and issue-type breakdown so a support-heavy week reads as support, not as silence.
CI/CD pipelines
Human-triggered builds and deployments are counted separately from scheduled automation, so nobody gets credit for a cron job.
Tool & seat usage
See which paid seats are actually being used and what they cost — reported as a licence-optimisation signal, never as a performance score.
Source health panel
Every report opens with a coverage table: which integrations responded, what period was scanned, and where data is missing.
Anatomy of a Focus report
Delivered to your inbox on the schedule you choose. Skimmable in 30 seconds, drillable when you need the detail.
Headline metrics
Team size, total commits, resolved items, deployments and active tool seats — the whole period in a single glance.
AI executive summary
A short written narrative that explains the week: who carried which type of load, what stands out, and what looks like a data artefact rather than a result.
Per-person breakdown
One row per team member: productive hours, efficiency, commits, files and repos touched, deployments, resolved items, logged effort and issue-type mix.
Unmatched identity list
Commits and tickets from aliases that don't map to a known person are surfaced instead of silently dropped — so real contribution never disappears.
Suggested actions
Concrete follow-ups a manager can act on, each clearly labelled as a suggestion. Focus never changes anything on its own.
| Person | Hrs | Eff. | Commits | Resolved | Effort |
|---|---|---|---|---|---|
| Member A | 41.7 | 96% | high | 15 | 23.9 |
| Member B | 45.2 | 93% | med | 18 | 6.3 |
| Member C | 35.4 | 94% | low | 12 | 29.0 |
| Member D | 38.6 | 88% | med | 8 | 23.0 |
| Member E | — | — | — | — | — |
Highlighted row: low commit count paired with high logged effort. Focus flags this as a different contribution type (support, analysis, operations) — not as underperformance.
Built so the numbers can't lie
Raw metrics mislead. Focus ships guardrails that keep automated reporting honest — and keeps humans in charge of the conclusion.
Contribution type over volume
Low commits with high resolved items and effort is read as a support or operations profile. The report says so in writing, right next to the row.
Missing data ≠ low performance
When a person has no signal in any source, Focus labels it a coverage gap and prompts you to check leave or account mapping first.
Noise-aware code metrics
Huge line counts from generated code, formatting or vendored dependencies are marked as raw indicators, not achievements.
Read-only by design
Focus never writes to your repositories, tickets or pipelines. Every integration uses least-privilege, read-only credentials.
Decision stays human
Every report carries the same footer: automated support only. Recommendations are labelled as not applied, and the final call belongs to the manager.
Fair efficiency maths
Efficiency averages only the days someone actually worked. Weekends, holidays and approved leave never drag the percentage down.
Reports that arrive before you ask for them
Set the cadence once. Focus builds the report, writes the summary and delivers it — no dashboard visit required.
Daily, weekly, monthly or custom periods — with the exact date range printed on every report.
Scoped audiences — a squad lead sees their squad, a director sees the roll-up, HR sees only what policy allows.
Email, Slack or Teams delivery — plus PDF, CSV and Excel export for anything that needs to leave the platform.
Custom metric sets — pick the columns that matter to your team and hide the ones that don't.
Full REST API — pipe the same dataset into your BI stack or data warehouse.
If an integration is unreachable, the report still ships — with the gap stated up front instead of silently skewing the numbers.
The same data, framed for each reader
One pipeline, different lenses — so nobody has to build a spreadsheet on Monday morning.
Engineering managers
Spot blocked work, uneven load and quiet weeks early — with enough context to open a useful 1:1 instead of an awkward one.
- ·Load distribution across the squad
- ·Delivery vs. support split
- ·Deployment ownership
Executives
A written summary and five headline numbers per period — enough to steer without reading a single dashboard.
- ·Period-over-period trends
- ·Tooling spend vs. usage
- ·Capacity and risk signals
HR & operations
Evidence-based inputs for reviews and workload conversations, with the fairness notes attached so numbers aren't quoted out of context.
- ·Sustained-overload warnings
- ·Contribution-type profiles
- ·Policy-scoped visibility
Get your first report this week
Connect your tools in minutes. Focus takes care of the rest — and tells you honestly when it can't.
No credit card required · 14-day free trial