Weekly KPI targets
Last 6% is measured, not designed
Flow has strong product and runtime surfaces. These KPI targets keep the final production claim honest: they require CI ring proof, real connector replay evidence and live funnel completeness.
Decision
Targets are wired, live proof remains
This is not a development blocker. It is the scorecard we use before saying Flow is 100% proven in production against competitors.
5
KPI targets
3
external proof lanes
387/402 (96.3%)
current TODO progress
Target cockpit
What must turn green before the 100% claim
Ultimate gate pass rate
Target: 100% in staging and production
Run release ultimate gate per ring after CI auth secrets are configured.
Owner: Platform/DevOps
Control-plane success rate
Target: >= 0.95
Archive control-plane verification output and compare against the weekly target.
Owner: Platform Ops
Ring gate p95 duration
Target: <= configured threshold
Use release-ring evidence to track p95 duration across planned runs.
Owner: Release Owner
Connector replay success
Target: >= 99%
Run webhook replay against first-class connectors and archive pass/fail counts.
Owner: Integrations
Funnel completeness
Target: >= 98%
Measure lead to booking to paid attribution completeness from live customer traffic.
Owner: Revenue Ops
External blockers
Not product-development blockers
- Staging/production CI auth secrets are still external infra pending.
- Connector replay proof needs real provider credentials for at least one first-class connector family.
- Funnel completeness needs live customer traffic with attribution, booking and payment events.
- Control-plane and ring p95 can be measured now, but final target pass requires the production CI ring.
Next action
Run weekly target review after each release
Use this cockpit as the single source for the last production proof loop. When each KPI has archived evidence, the remaining open TODO rows can be closed without turning the roadmap into wishful thinking.