Implement the logic that scores and buckets brands based on the agreed-upon criteria, automatically assigning them to prospect segments. Each brand runs as its own trigger.dev task — if one fails, only that brand retries, not the whole pipeline.
✅ Built + deployed — the criteria & bands model is LIVE. Following the June 11 working session, the weight sliders were replaced by the "criteria & bands" model the team aligned on: each segment is defined by must-haves, nice-to-haves, value bands, and deal-breakers, in plain language (e.g. Segment D's locked decision: 4–10 third-party sellers as the sweet spot, eligible to 20). The definitions from the meeting were saved and re-scored on the new engine (config v20, June 17), and the cohort has grown to ~43,981 brands after onboarding ~8,100 previously-missed 1P / Vendor-Central brands (they have no Amazon storefront, so the original ingest skipped them). What's in the Review Queue now is the criteria model, end to end, with ~29,100 non-suppressed brands. Live signals: annual revenue, YoY & MoM growth, 3P sellers per listing (+ the sweet-spot band), catalog size, Prime-coverage gap, Vendor Central dominance (now measured by dominant-seller coverage — the literal "Amazon owns X% of the brand" number), and Brand/page score (covers ~72% of brands while the product backfill finishes). The Scoring page's Step 2 draws every band over a live sample of real brands (drag the band directly on the chart), can back-solve bands from example brands you name, and re-scores real companies in the preview as you adjust — including the now-live Segment F — 1P in Decline, which targets Vendor-Central brands Amazon dominates (~1,300 brands land in it). ⏳ Still open — the calibration pass: the first criteria run was deliberately wide; Nick's June 17 pass began tightening it (Hot is now ~17,300, down from ~24,000 — Segment E's growth gate still captures most of it), so Hot keeps narrowing. Nick's remaining pass: tighten Segment E further (ad-spend/TACoS data is confirmed available to make "growth + margin pressure" measurable), nudge score thresholds, close Segment A's three open bands, untick excluded categories, and wire each segment (now including F) to its Smartlead campaign — see "What I Need from Your Team."
| Task | Hours |
|---|
✅ segment-leads trigger.dev task — wired, deployed to production | 2 |
| ✅ Scoring Configurator UI — criteria & bands model in two phases (define → re-score → act), live preview of real companies per segment that re-score as you tune (expand any brand for its breakdown), live bucket totals that show how many brands land Hot/Warm/Cold per segment as you move the thresholds, cloud save → D1 (pipeline reads config directly, no file transfer needed) | 8 |
| ✅ Build scoring rules — multi-signal engine (revenue, growth, seller mix, Prime/Vendor presence, lifecycle, catalog size, Product Page Score gap, category fit); 5 mutually-exclusive segments. Product backfill complete — Product Page Score gap now scored | 10 |
| ✅ Implement 1P vs. 3P seller classification | 4 |
| ✅ Bucketing logic — auto-assign brands to hot / warm / cold / suppress; categoryFit inert until allow-list set | 4 |
| ✅ Conditional chaining — hot/warm brands automatically trigger enrichment task | 2 |
| ⏳ Backtest scoring against the 47 existing partners — ready to run now that the full scored cohort is live in D1 | 4 |
| ⏳ Unit testing & validation against known brand examples (Phase 7) | 4 |