Tuning Your Book

Tune from real accounts, not assumptions. Run for a day or two, look at the actual rows the orchestrator delivered, then adjust one thing in the Audience at a time.

"The accounts are not a good fit"

Almost always an Audience problem. In order of impact:

1. Tighten Fit. Industries too broad, or no exclusions. See Fit.
2. Sharpen Path roles. Too many target titles dilutes lead warmth across the book.
3. Narrow Self competitors and keywords. Loose lists drive noisy competitor_engagement and keyword_buzz signals.

Open Audience, change one thing, give it one tick to re-evaluate. Don't change five things at once — you won't know which fixed it.

"I'm barely getting accounts"

The opposite problem: Audience so tight that nothing clears Fit, or all signals are disabled.

1. Loosen one Fit dimension (add a headcount bucket, add a country).
2. Turn on more signals — at minimum, funding + job_change + hiring + ICP search should be on.
3. Check your Path roles aren't typos; LinkedIn job titles need to be exact text-matches in spirit.

Hiring signal looks off

Most common cause: Replaces roles is empty or has the wrong titles in it.

Hiring catches companies opening reqs that match your replacesRoles — the roles your product scales or replaces, NOT the roles you sell to.

• If you sell to Heads of Sales and your replacesRoles is "Head of Sales" — that defeats the signal. A company hiring a Head of Sales is not a buying trigger for sales tooling; it's a leadership gap.
• Put "SDR", "BDR", "Sales Operations Manager" in replacesRoles if you sell SDR tooling. That's the function whose scale-up is the buying trigger.

See Path for the full breakdown.

Why some accounts never appear

By design:

• Already-delivered accounts don't re-land. Each company shows up once for this Product.
• Dismissed accounts won't resurface unless a strong fresh signal lands.
• Companies whose employees match your competitor domains are filtered before the book.
• Companies that fail the verification step are dropped pre-save and audited in the drops table (see Settings → Tuning).

None of these count against your lead allowance.

Compute budget pacing

Each plan has a compute budget — 70% of your plan price, as a hard cap that auto-pauses the pipeline. You'll see a warning at 50% spend and a pacing notification at 50% / 70% lead consumption ("at this pace you'll hit cap on day X"). At the 70% hard cap, the pipeline auto-pauses and a manual review is required to restart.

In normal use, you won't get near this. If you do, a Fit dimension is too broad, a keyword set is too generic, or competitor domains are too many. Tighten one and the cost normalises.

See Limits and Quotas.