Weaver The Engineering Intelligence Platform We Built to See Our Own Delivery Clearly. Background We run projects across six tools — Cursor, Jira, GitHub, Google Workspace, Figma, and Slack — each holding one slice of the truth about how a project, or a person, is actually doing. Getting a straight answer to “how is the team doing?” meant manually cross-referencing all six, usually after a deadline had already slipped. We built Weaver to remove that manual step, for ourselves first. Problem Statement Sprint velocity and ticket quality lived in Jira. Code activity lived in GitHub. AI tool usage and spend lived in a separate admin console. Design progress lived in Figma. Meeting load and communication patterns lived in Google Workspace and Slack. None of it talked to each other, so status updates were built by hand, and risk — an overloaded developer, a stalled branch, a quality regression — usually surfaced in a meeting, not before one. Solution Weaver syncs all six sources into one database every night, on demand, and via historical backfill, then computes the same metrics the same way for everyone. It presents them through gamified leaderboards, per-member scorecards, and project health dashboards. A built-in AI assistant answers plain-language questions about the data directly, and an automated risk-alerting engine flags problems before they become delivery issues.

251

Rob Maclean

Developing award-winning apps. Deploying AI-native engineers