Findings & Fixes
A Shingo finding is a complete execution package. It tells your engineers what broke, why it matters, and how to fix it, all in one place.
Anatomy of a finding
Every finding includes these components:
Unique identifier for tracking and reference
Based on revenue impact and confidence score
The specific technical issue that caused the revenue impact
Exact file and line where the issue originates
Annualized dollar amount at risk
Number of user sessions impacted during the analysis window
How certain Shingo is that this cause produced the effect
Chronological sequence from cause to detection
Engineer-ready fix with code context
Example finding
cause: checkout.tsx:142 — JS lib v2.4.0 broke mobile validation
impact: $1.8M/yr · 12,847 sessions
cohort: mobile users, top-LTV (18% drop-off)
fix: revert to v2.3.1
→ Slack #eng-revenue · GitHub issue #2847 created
Delivery channels
Findings are delivered where your team already works:
GitHub Issues
Auto-created issues with priority labels, revenue impact tags, file references, and suggested fix. Your team reviews and ships.
Linear Tickets
Tickets created with priority, project assignment, and full finding context. Integrates with your existing sprint workflow.
Slack
Real-time notifications to your eng-revenue or eng-alerts channel with a summary and link to the full finding.
REST API
Programmatic access to all findings for custom integrations, dashboards, or internal tools.
Regression timeline
Each finding includes a timeline showing the chain of events from cause to detection. This helps your team understand the full story: