Back to Action Plan

NAVIRA — SCORING CONFIGURATOR

Outreach Scoring Engine

Configure scoring for each of the five outreach segments. Work through Steps 1–5, one at a time. The ⛳ checkpoint after Step 2 is where you Save and Re-score — Steps 3–5 work off whatever version is saved and scored there, and the checkpoint always shows both version numbers.

Loading…
Checking mode…
Loading pipeline status…

Apollo enrichment doesn't run in dry_run mode. Once Evan turns on production mode the run / re-run button enables here — note that each enrichment run spends Apollo credits.

After you re-score: the updated tiers don't appear instantly. Re-scored segments land on the Review Queue roughly 10–15 minutes after the run finishes. The Review Queue shows which config version it's displaying and flags itself if it's still behind this page.

Per-segment setup
Steps 1–2 run one segment at a time (pick → define); Steps 3–4 cover every segment (verify its copy → wire it); Step 5 hands off to the next pages.
Step 1 of 5

Choose or create a segment

Pick a segment to configure its Steps 2–5, or add / duplicate / archive below. You're not locked to five.

Each brand is enrolled in only its best-match segment — never emailed twice. Archiving hides a segment from outreach but keeps its data.

Step 2 of 5

Define the segment —

Describe the segment the way you talk about it: each signal is a Must have (required — outside the band = suppressed for this segment) or Nice to have (ranks brands higher), with a value band ("between X and Y"; leave an end blank for no min / no max). Passing the must-haves scores 50; nice-to-haves carry a brand from 50 to 100. Presets come from the Jun 11 meeting. Two power tools live at the bottom of this step: ➕ Add a signal (measures not in this definition yet — new ones land there first) and ⭐ Calibrate by example (search any pulled brand — clients included — and back-solve bands from brands you know).

Loading a live brand sample for the charts…

Calibrate by example — pick brands you know belong in this segment (they turn gold on the charts), then back-solve: each band snaps to cover your picks.
searches the full pulled cohort — every non-suppressed brand, plus suppressed ones tagged ⛔ (a current client is still a fine calibration example)
picks are test-safe (browser only); back-solve changes bands — Undo restores them, and nothing re-scores until the Re-score button is pressed
⛳ Checkpoint

Make it official — save, then re-score

Step 3 of 5

Verify the sequence copy

A segment's emails are written for its definition — when the definition is final, read that segment's sequence and confirm the copy still matches who you're targeting. Wiring in Step 4 unlocks per segment only after its sequence is verified. Editing a segment's definition automatically un-verifies it (the audience changed, so the copy needs another look).

Step 4 of 5

Wire segments → Smartlead

One Smartlead campaign per segment. Score a segment first, then Wire it — we create the campaign (paused) in Smartlead so the name always matches, with no copy-paste. Archiving a segment detaches & pauses its campaign automatically. Suppressed brands are never enrolled.

⚠ Wiring creates a paused campaign. It won't send until you load the sequence copy and activate it in Smartlead. Already made the campaign yourself? A “link existing” picker appears next to Wire once your Smartlead account has campaigns to choose from.

Step 5 of 5

Next: enrich contacts, then work the queue

Scoring decides who; the rest of the flow gets you someone to email and a decision per brand:

1 · Enrichment ↗

Apollo finds the decision-maker contacts for scored brands (tiers + roles set in the Global panel above). Runs once Evan flips enrichment to production after you approve the scored cohort.

2 · Review Queue ↗

Every non-suppressed brand with its score, segment, and contact — approve, hold, or reject each one (keyboard: j/k to move, a/h/x to decide). Approved brands are what campaigns enroll.

The order that keeps everyone confident: define (2) → verify copy (3) → wire (4) → enrich → review → campaigns go live. Each page hands off to the next.

Global settings
Set once — these apply across every segment, not per-segment. Edits here commit with the same ⛳ checkpoint above Step 3 (or the toolbar up top) — one Save covers the whole page.
Global

Score thresholds

One set of thresholds for every segment. Under the criteria model a brand that passes every must-have starts at 50, and nice-to-haves carry it toward 100 — so a threshold is "how many of the nice-to-haves does Hot require?" Hot at 75 means at least half the known nice-to-haves hit. Edits apply to all segments; the preview re-buckets live.

Quick set:

Hot — immediate priority, highest-touch sequence.

Warm — strong prospect, standard sequence.

Cold — worth a light touch, lowest-intensity sequence.

Suppressed — failed a must-have, hit a deal-breaker, or caught by a global gate (revenue floor/ceiling, excluded category, HubSpot relationship). Every qualifying brand scores at least 50, so a Cold line below 50 never suppresses on its own.

Too many Hot brands? Raise the Hot threshold. Want a bigger Cold pool? Lower the Cold threshold. Tune until the sample brands in the preview land where you'd expect them.

Global

Scoring rules & targets

Applied to every segment: trajectory basis, target categories (for Category fit), and the disqualifiers that skip a brand before scoring.

Growth signalshow growth enters the scoring

The criteria model reads YoY growth and MoM growth as two separate signals — band either (or both) per segment in Step 2, no global switch needed. Both are always visible per brand in the Review Queue’s ⓘ popup. (The old global “growth basis” toggle only steered the retired weight-slider variable, so it was removed rather than left as a switch that does nothing.)

Target categoriesevery category is targeted by default — untick the few NAVIRA doesn't want; brands in unticked categories are suppressed across all segments
Loading categories…
0 excluded

Pulled from the actual categories in the cohort, so they always match. With nothing unticked (the default) category plays no role. Takes effect on the next re-score.

Universal disqualifiers

These rules run before scoring on every segment. Any brand matching an enabled rule is skipped entirely — not enriched, not enrolled.

Finished your segments? Click Save config above. Evan’s pipeline uses the latest saved version automatically — nothing to send, nothing to email.

Need to revise later? Come back, make edits, hit Save again. Each save is versioned — the last 10 are kept.

Global

Apollo contact enrichment

After scoring, Apollo pulls one decision-maker per matched brand. Choose which tiers to enrich, which roles to target, and whether a verified email is required.

Which tiers to enrich

Only brands in an enabled tier are sent to Apollo. Suppressed brands are never enriched. All tiers on = enrich every matched brand (current behavior).

Email quality & contact gate

Require a verified email to keep only confirmed addresses. Optionally suppress brands where Apollo finds no decision-maker contact at all.

Decision-maker roles to target

Apollo searches for these roles, ranked by seniority and title match. The single best contact per brand is kept.

Default: all tiers on so nothing changes silently on the next run. Turn Cold off to focus Apollo spend on Hot + Warm only. Changes save with the rest of the config; the pipeline reads them on the next run.

Global

HubSpot suppression — never email a relationship

At the start of every re-score, the pipeline reads NAVIRA's HubSpot and suppresses brands with evidence of a relationship — never just "we emailed them once." Your ~5,000 past-outreach leads stay fair game; active clients, open deals, and live conversations are protected. Rules below are read from the saved config; if HubSpot is unreachable the re-score proceeds on the last-synced list (clients stay protected either way).

Checking last sync…

Always on (not configurable): contacts who unsubscribed are suppressed permanently — that one is legal, not strategic. Suppressed brands leave the Review Queue on the next re-score.

Definition —

The definition driving scores. Updates live as you adjust bands in Step 2.

Your brands, scored live — sample per segment

How a brand gets scored
Every brand is scored against every segment and lands in the one it fits best. A segment is a definition: must-haves, nice-to-haves, and value bands you set in Step 2. A brand outside any must-have band is suppressed for that segment. Passing every must-have scores 50; nice-to-haves carry it from 50 to 100 (each known nice-to-have hit adds an equal share). A brand only competes on signals it has data for — missing ones are reported as unknown, never guessed as zero. The tier (Hot / Warm / Cold) is where that score lands against your Step-3 thresholds. Suppressed means removed at scoring — fails a must-have everywhere, hits a deal-breaker, or sits in an excluded category — i.e. “don’t contact,” not merely a low score.

Real brands from the last run, re-scored in your browser against the definition on screen. Flagship = textbook fit · borderline = first to move when a band shifts · suppressed = scored but not contacted. Click any brand for its full breakdown. With unsaved edits, these scores will differ from the Review Queue until you Save and re-score.

Add email sequence?

Creates blank placeholder steps on the Sequences page for Jeremy to fill in. No copy is generated — just the scaffolding.