Artist Discovery System
4 KPIs
Measured from the end of the 30-day post-launch tuning window onward. The tuning window is not subject to KPI measurement.
Pipeline Uptime
System completes its scheduled daily scan cycle without critical failure. Measured over any rolling 7-day window by pipeline execution logs. Scheduled maintenance windows (communicated 24 hours in advance) are excluded from the calculation. A scan that completes with warnings but produces output counts as successful.
Platform Coverage
Each scan cycle queries all configured platforms. A platform counts as "covered" if the API or scraper returned data or returned a valid empty result. Platform-side outages (API down, rate-limited by provider, endpoint rotation) are logged as "platform unavailable" and excluded — they do not constitute a miss. Node will communicate known platform outages within 24 hours of detection.
Classification Accuracy
Node and AB6 jointly review a random sample of 20 candidates per month. Each candidate is checked for correct signed/unsigned classification and label attribution. Disagreements resolved by checking the primary source (Deezer or Spotify label data, whichever is available). Accuracy = correct classifications / total sample.
Candidate Delivery Latency
Qualifying candidates appear in the dashboard within 4 hours of scan completion. Measured by timestamp delta between scan-complete log entry and candidate record creation in UI. Measured on candidates that pass all filters. Rolling 7-day average.
Exclusions
Candidate volume (how many artists the system surfaces per day) is a function of market activity across monitored platforms and genres, not system performance. The Discovery KPIs measure operational reliability — that the pipeline runs, scans, classifies, and delivers correctly. Periods of low candidate volume reflect genre and platform activity, not system failure, and do not constitute a KPI miss.
LeadGenOS
4 KPIs
Measured from first campaign send onward. The 2–4 week infrastructure warmup period is not subject to KPI measurement.
Sending Volume
System sends at or above 85% of the agreed daily target volume. Target volume set jointly at kickoff based on AB6's campaign scope and domain capacity. Measured as a rolling 7-day average via Instantly sending analytics. Pauses requested by AB6 (campaign hold, list swap, offer revision) are excluded from the calculation.
Bounce Rate
Hard bounces as a percentage of total emails sent. Measured over any rolling 7-day window via Instantly deliverability dashboard. Soft bounces (recipient mailbox full, temporary server issues) are excluded. Bounces caused by AB6-provided contact lists (if AB6 supplies their own lists outside of Node's enrichment pipeline) are excluded.
Spam Complaint Rate
Spam complaints as a percentage of total emails delivered. Measured over any rolling 7-day window via Instantly and Google Postmaster Tools (where available). Complaints resulting from AB6 manually sending emails outside of the LeadGenOS system using the same domains are excluded.
Reply Routing Latency
Inbound replies surface in AB6's Instantly unified inbox within 2 hours of receipt by the sending infrastructure. Measured by timestamp delta. Rolling 7-day average. Platform-side delays (Instantly outages, email provider delays) are logged and excluded.
Exclusions
LeadGenOS KPIs measure the outreach engine's mechanical performance — sending reliability, list hygiene, deliverability health, and reply routing speed. Open rates, response rates, meeting conversion, sponsorship outcomes, and deal revenue depend on AB6's offer positioning, reply handling, sales execution, and market timing, and are explicitly excluded from KPI measurement per SOW Section 4.1.
Protocol
Measurement & Review
KPI Review Cadence
Node provides AB6 with a written KPI status report at each milestone payment trigger and at each monthly monitoring check-in. Reports include raw metrics, rolling averages, and any excluded events with explanations. Both parties review and acknowledge the report within 5 business days.
Dispute Resolution
If AB6 disputes a KPI measurement, both parties will review the underlying data source together within 5 business days of the dispute. The data source defined in each KPI's measurement protocol (system logs, Instantly dashboard, Postmaster Tools, or joint sample review) is the authoritative record. If the data source is ambiguous or unavailable, the KPI is deemed met for that measurement period.
Exit Clause Trigger
Per SOW Section 4: an exit clause is triggered only when 3 or more KPIs within the same system miss their thresholds simultaneously in the same measurement period. A single KPI miss, or misses across different systems, does not trigger an exit. AB6 must provide written notice citing the specific KPIs missed and the measurement data supporting the claim.