Live KPI proof

100% needs one real customer journey, not more demo rows

This run sheet defines the live evidence needed to prove Flow from lead to conversation to booking/proposal to paid or signed outcome.

KPI targetsPilot caseExport run sheet

Decision state

Ready to measure live traffic

The product and reporting surfaces are ready. Final KPI proof stays pending until a real tenant generates live lead, booking/proposal and paid/signature evidence.

5

proof steps

5

KPI metrics

98%

funnel target

Proof chain

Evidence required from the pilot tenant

Step 1

First live lead

Evidence: widget event, source/channel, tenant id, consent state and created ticket/conversation

Pass: Lead is attributed and visible in support/analytics without manual repair.

Step 2

First qualified conversation

Evidence: agent assignment, read/delivery state, response SLA and next intent

Pass: Conversation can be followed from visitor intent to owned team action.

Step 3

First booking or proposal

Evidence: booking/proposal id, selected service, availability state and owner

Pass: Booking or proposal is created from the same customer journey.

Step 4

First paid or signed outcome

Evidence: Kustom/payment reference or e-sign audit trail plus invoice/proposal state

Pass: Revenue outcome is linked back to the original lead and source.

Step 5

Weekly completeness review

Evidence: funnel completeness, attribution gaps, connector replay and anomaly review

Pass: Lead to booking to paid completeness is >= 98% for the pilot window.

Scorecard

Metrics that decide the claim

  • Funnel completeness: >= 98% · Revenue Ops
  • First response SLA: < 45s for live chat/callback · Support Ops
  • Booking/proposal continuity: 100% linked from source lead · Commercial Ops
  • Paid/signature traceability: 100% linked outcome for pilot case · Finance Ops
  • Connector replay success: >= 99% after provider credentials · Integrations

Rules

No fake KPI green

  • No KPI can turn green from seeded/demo-only rows.
  • Pilot evidence must include tenant id, timestamp, owner and source/channel.
  • Manual repair is allowed only when repair reason and before/after state are archived.
  • Sensitive customer data must be redacted from export packs.
  • A weekly KPI review must explain both pass and fail lanes.