@sellable/mcp 0.1.123 → 0.1.124

package/agents/source-scout-linkedin-engagement.md

@@ -50,6 +50,8 @@ currentStep: "signal-discovery" })` before sampling so the watched Signal
 7. Compute capacity before recommending the source: target good-fit leads
    (default 500 unless the parent supplies a target), reachable engagers,
    sampled ICP-fit rate as `n/N` plus an easy percentage/range, expected usable
+   leads per 100 engagers before and after a conservative dedupe/cleanup
+   factor, average reachable engagers per right-content post, expected usable
    leads per right-content post after dedupe/cleanup, and posts needed to hit
    the target.
 8. Select/promote enough right-content posts to plausibly hit the target. If the
@@ -65,8 +67,10 @@ Return a concise structured result with:
 - `selected_posts` with URL/title, author/topic, age, engager count, sampled engagers, good fits as n/N, estimated usable prospects per post, use/discard
 - `sample_leads`, if any
 - `approval_math` with eligible posts, target good-fit leads, sampled engagers,
-  ICP-fit rate as `n/N` plus percentage/range, posts needed for target, selected
-  post count, expected usable lead range, and scale fallback
+  ICP-fit rate as `n/N` plus percentage/range, good-fit prospects per 100
+  engagers, average reachable engagers per post, expected usable prospects per
+  post after cleanup, posts needed for target, selected post count, expected
+  usable lead range, and scale fallback
 - `estimated_good_fit_range`
 - `message_context_strength`, directional and source-specific
 - `false_positive_patterns`
@@ -82,7 +86,9 @@ Evidence standards:
   GTM/outbound/buyer pain, workflow, or role context that makes the campaign
   relevant.
 - Do not make the user infer capacity. Say, plainly, how many eligible posts
-  exist, what percent of sampled engagers looked in-ICP, how many posts are
-  needed for 500+ good-fit leads, and which posts you would use.
+  exist, how many sampled engagers looked in-ICP, how many good-fit prospects
+  that implies per 100 engagers, how many usable prospects one right-content
+  post should yield after cleanup, how many posts are needed for 500+ good-fit
+  leads, and which posts you would use.
 - If `fetch_post_engagers` is unavailable or fails, report that explicitly and mark the estimate lower-confidence.
 - Keep LinkedIn Engagement viable when selected posts can produce roughly 150+ ICP-fit warm prospects before final filtering, even if Sales Nav is more scalable.

package/agents/source-scout-sales-nav.md

@@ -26,8 +26,16 @@ Process:
 2. Preserve target role names with `CURRENT_TITLE` lookups; do not rely on seniority alone when the brief names concrete roles.
 3. When `lookup_sales_nav_filter` returns multiple title options, choose the closest semantic title match instead of the first result.
 4. Build a broad-but-reasonable baseline from role/title, geography, company size, industry/account context, and recent LinkedIn activity when relevant.
-5. Run the baseline plus 1-2 refinements if the first pass is noisy or under-scaled.
-6. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
+5. Check scale against the target good-fit lead count (default 500 unless the
+   parent supplies a target). If raw preview volume or projected usable volume
+   is below target, do not present the tiny result as the scale fallback yet.
+   Loosen nonessential filters in order: remove recent-activity first, widen
+   adjacent title variants, widen geography/company-size constraints, and only
+   keep hard ICP requirements from the brief.
+6. Run the baseline plus 1-2 refinements or loosening passes if the first pass
+   is noisy or under-scaled. Label the final pool as constrained if it still
+   cannot plausibly reach the target after loosening.
+7. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
 
 Return a concise structured result with:
 
@@ -36,6 +44,11 @@ Return a concise structured result with:
 - `exact_filter_recipe`
 - `lookup_ids_used`
 - `raw_result_count`
+- `scale_check` with target good-fit lead count, preview/raw volume, sampled
+  good fits as n/N, projected usable count, and whether the pool can reach the
+  target
+- `loosening_attempts` with what was removed or widened when the pool was too
+  tight
 - `sampled_people` and good fits as n/N
 - `estimated_good_fit_range_after_cleanup`
 - `expected_acceptance_rate_range`, directional if inferred
@@ -49,5 +62,9 @@ Evidence standards:
 
 - Optimize for a useful prospect pool, not max volume at any cost.
 - Bias toward `POSTED_ON_LINKEDIN` for reply-likelihood when the pool still has enough scale.
+- Do not over-tighten fallback filters into a pool that cannot be meaningfully
+  larger than the warm-post path. If Sales Nav is offered for scale, it should
+  either project to the target good-fit count or clearly say it is too tight and
+  name the next broadening/Prospeo option.
 - Do not hand-wave missing filter IDs.
 - If Sales Nav returns a giant unfiltered pool, discard that result and retry with valid filters before recommending it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.123",
+  "version": "0.1.124",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/SKILL.md

@@ -826,7 +826,9 @@ Required behavior:
   2. If Signals does not have enough recent, relevant, ICP-looking engagers,
      switch to Sales Nav with recent activity when the target can be expressed
      as title/persona/company filters. Run preview filters, inspect preview rows,
-     validate the filters applied, and estimate scalable-fit volume.
+     validate the filters applied, and estimate scalable-fit volume. If the
+     preview/projected usable pool is below the target good-fit count, loosen
+     nonessential filters before presenting Sales Nav as the scale fallback.
   3. If recent-activity Sales Nav is too small or noisy, broaden to normal Sales
      Nav title + company filters and call out the weaker activity context.
   4. Use Prospeo Contact only when the campaign has a domain/account path, the
@@ -1025,8 +1027,9 @@ not a research memo. It must include only:
   activity filters. For Signals, name the selected post set. For Prospeo, name
   the account/domain and title recipe.
 - `Math:` with these labels and values:
-  `Eligible posts`, `Sample`, `ICP-fit`, `Target`, `Posts needed`, `Selected`,
-  `Expected good-fit leads`, and `Scale option`.
+  `Eligible posts`, `Sample`, `ICP-fit`, `Good-fit / 100 engagers`,
+  `Avg engagers/post`, `Good-fit / post`, `Target`, `Posts needed`,
+  `Selected`, `Expected good-fit leads`, and `Scale option`.
 - `Why this source:` with at most two bullets.
 - `Watch link: {watchUrl}` only when the campaign shell exists and the host
   needs a handoff link.
@@ -1036,14 +1039,20 @@ Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead
 lists, or long tradeoff prose in the default approval packet. Keep those details
 in `lead-review.md` or campaign/source decision state. The math block is the
 bottom-line arithmetic that makes the recommendation obvious. For example:
-`Eligible posts: 8 outbound + Claude posts. Sample: 120 engagers. ICP-fit: 52/120
-(~43%, directional). Target: 500 good-fit leads. Posts needed: about 8-10 at
-this fit rate. Selected: 8 posts. Expected good-fit leads: ~420-560 after
-dedupe/cleanup. Scale option: Sales Nav gives more rows but loses the engaged
-with this content message hook.` For Sales Nav/Prospeo alternatives, include
-preview/raw volume, sampled usable rows as `n/N` plus percentage/range,
-estimated usable range, and the warmth or context tradeoff. Do not use
-percent-only fit rates or unsupported reply-rate claims.
+`Eligible posts: 18 outbound + Claude posts. Sample: 31/125 ICP fits. ICP-fit:
+~25%, directional. Good-fit / 100 engagers: ~25 before cleanup, ~15-18 after
+dedupe/cleanup. Avg engagers/post: ~480 reachable. Good-fit / post: ~72-86
+usable. Target: 500 good-fit leads. Posts needed: about 6-7 right-content posts.
+Selected: 7 posts. Expected good-fit leads: ~500-600 after dedupe/cleanup. Scale
+option: Sales Nav can broaden to founder/GTM/RevOps filters if you want colder
+scale, but loses the engaged-with-this-content message hook.` If the selected
+posts only support the 15-row review batch or a smaller warm pilot, say that
+plainly and do not imply the lane can hit 500. For Sales Nav/Prospeo
+alternatives, include preview/raw volume, sampled usable rows as `n/N` plus
+percentage/range, estimated usable range, and the warmth or context tradeoff.
+If Sales Nav preview volume is too tight, broaden nonessential filters before
+using it as the scale option, or label it constrained and name the next fallback.
+Do not use percent-only fit rates or unsupported reply-rate claims.
 
 The first sentence of the visible decision must make the actual choice clear:
 `I recommend {primary source} using {exact filter/source recipe}. The runner-up
@@ -1091,12 +1100,14 @@ For Signals, default to a quick capacity test before final recommendation. Pick
 a narrow first sample of fresh, high-density posts, and in campaign-attached
 watch runs promote those posts with `select_promising_posts` before sampling so
 the user sees which posts are being tested. Then sample engagers, show ICP-fit
-rate as `n/N` plus percentage/range, calculate how many right-content posts are
-needed to reach the target good-fit lead count, and select/promote enough
-right-content posts if the lane can hit the target. If the first sample is good
-but volume is low, say how many more posts would be needed and offer the Sales
-Nav/Prospeo scale alternative instead of recommending an under-sized source as
-if it can produce 500+ leads.
+rate as `n/N` plus percentage/range, convert that to good-fit prospects per 100
+engagers, estimate average reachable engagers per right-content post, apply a
+conservative dedupe/cleanup factor, calculate good-fit prospects per post, then
+calculate how many right-content posts are needed to reach the target good-fit
+lead count. Select/promote enough right-content posts if the lane can hit the
+target. If the first sample is good but volume is low, say how many more posts
+would be needed and offer the Sales Nav/Prospeo scale alternative instead of
+recommending an under-sized source as if it can produce 500+ leads.
 
 Keep discarded paths and full sample rows in the campaign/source decision
 context. In explicit debug/UAT runs they may also be copied into

package/skills/create-campaign-v2/core/flow.v2.json

@@ -525,7 +525,7 @@
           "suppliedProfilesOrCsv": "supplied-list",
           "explicitCompare": "compare-requested-sources"
         },
-        "quickViabilityRule": "Run only enough of the current lane to decide whether it can supply relevant, reachable ICP-looking leads. For Signals, viability requires sampled ICP-fit rate plus posts-needed math against the target good-fit lead count, not raw post count. Stop on the first viable source unless the user asked for comparison.",
+        "quickViabilityRule": "Run only enough of the current lane to decide whether it can supply relevant, reachable ICP-looking leads. For Signals, viability requires sampled ICP-fit rate normalized to good-fit prospects per 100 engagers, average reachable engagers per right-content post, projected good-fit prospects per post after cleanup, and posts-needed math against the target good-fit lead count, not raw post count. Stop on the first viable source unless the user asked for comparison.",
         "parallelAllowedOnlyWhen": [
           "user explicitly requested source comparison",
           "resuming already-started parallel scouts",
@@ -568,7 +568,7 @@
           },
           "when": "after_source_selection_checkpoint_before_first_source_attempt",
           "requiresPriorVisibleStep": "pick-provider",
-          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Only run this after the Pick Provider source-selection checkpoint has been made visible and explained in chat/watchNarration. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, make it clear this is a viability path before lead import: generate intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role, not broad anchor-only lanes. For Claude/GTM campaigns, prefer lanes like Claude outbound, Claude Code LinkedIn outreach, AI SDR Claude, GTM automation Claude, and founder-led sales Claude over generic Claude Code, MCP, AI agents, or agentic coding. If the first pass is broad, retarget around the campaign wedge before selecting posts. Promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the target lead count. Before final source approval, compute eligible posts, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
+          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Only run this after the Pick Provider source-selection checkpoint has been made visible and explained in chat/watchNarration. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, make it clear this is a viability path before lead import: generate intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role, not broad anchor-only lanes. For Claude/GTM campaigns, prefer lanes like Claude outbound, Claude Code LinkedIn outreach, AI SDR Claude, GTM automation Claude, and founder-led sales Claude over generic Claude Code, MCP, AI agents, or agentic coding. If the first pass is broad, retarget around the campaign wedge before selecting posts. Promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the target lead count. Before final source approval, compute eligible posts, sampled ICP-fit rate, good-fit prospects per 100 engagers, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
         },
         {
           "action": "run_first_campaign_attached_source_search",
@@ -617,7 +617,7 @@
           "action": "run_subskill",
           "target": "find-leads",
           "mode": "campaign-attached-required",
-          "sourceScoutRule": "Shell-first flow requires the CampaignOffer campaignId from durable state. Pass campaignId as campaignOfferId into every provider prompt/search that can persist source state (`get_provider_prompt({ provider, campaignOfferId, confirmed: true })`, `search_signals`, `search_sales_nav`, `search_prospeo`) and include currentStep for tools that accept it so the user can watch the selected source inside the campaign. Use the default sequential source viability funnel when the user did not specify a source: Signal Discovery first, then Sales Nav with recent activity, then general Sales Nav, then Prospeo only as fallback. For Signal Discovery, use intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role; broad anchor-only lanes are fallback inventory, not selectable source lanes while narrower wedge lanes exist. Do not recommend from raw post count; sample engagers, calculate ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. Stop on the first viable source unless the user explicitly asked to compare. If the user names hiring signals, domains/accounts, supplied lists, posts/comments, or title/persona filters, start with the matching source instead. Parallel source scouts only when the user requested comparison, an existing parallel run is being resumed, or the first viable source is borderline and one cheap fallback check is needed. The later import_leads call must use the same campaignOfferId. Do not import, confirm, enrich, queue, or start leads during source discovery."
+          "sourceScoutRule": "Shell-first flow requires the CampaignOffer campaignId from durable state. Pass campaignId as campaignOfferId into every provider prompt/search that can persist source state (`get_provider_prompt({ provider, campaignOfferId, confirmed: true })`, `search_signals`, `search_sales_nav`, `search_prospeo`) and include currentStep for tools that accept it so the user can watch the selected source inside the campaign. Use the default sequential source viability funnel when the user did not specify a source: Signal Discovery first, then Sales Nav with recent activity, then general Sales Nav, then Prospeo only as fallback. For Signal Discovery, use intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role; broad anchor-only lanes are fallback inventory, not selectable source lanes while narrower wedge lanes exist. Do not recommend from raw post count; sample engagers, calculate ICP-fit rate, good-fit prospects per 100 engagers, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. For Sales Nav fallback, do not over-tighten filters into a tiny pool; if preview/projected usable volume is below the target, loosen nonessential filters before presenting Sales Nav as the scale option and label it constrained if it still cannot reach the target. Stop on the first viable source unless the user explicitly asked to compare. If the user names hiring signals, domains/accounts, supplied lists, posts/comments, or title/persona filters, start with the matching source instead. Parallel source scouts only when the user requested comparison, an existing parallel run is being resumed, or the first viable source is borderline and one cheap fallback check is needed. The later import_leads call must use the same campaignOfferId. Do not import, confirm, enrich, queue, or start leads during source discovery."
         },
         {
           "action": "optional_debug_artifacts",
@@ -720,6 +720,9 @@
             "Eligible posts",
             "Sample",
             "ICP-fit",
+            "Good-fit / 100 engagers",
+            "Avg engagers/post",
+            "Good-fit / post",
             "Target",
             "Posts needed",
             "Selected",
@@ -764,6 +767,10 @@
             "reachable engagers count",
             "sampled engagers count",
             "sampled ICP fits as n/N plus percentage or range",
+            "good-fit prospects per 100 engagers",
+            "average reachable engagers per post",
+            "expected good-fit prospects per post after cleanup",
+            "dedupe or cleanup factor",
             "target good-fit lead count",
             "posts needed for target",
             "selected posts count",
@@ -771,6 +778,7 @@
             "scale alternative source",
             "scale alternative raw or preview volume",
             "scale alternative sampled usable rows as n/N plus percentage or range",
+            "Sales Nav broadening or loosening attempts when fallback volume is too tight",
             "warmth or message-context tradeoff",
             "what to choose if the user wants more volume"
           ],
@@ -794,7 +802,7 @@
           "doNotCompressToSummaryOnly": false,
           "doNotRenderArtifactLinksOnly": true,
           "sourceRecommendationReadyWatchRule": "When the source recommendation decision card is ready in chat with counts and sample quality, and before asking for source approval, call update_campaign with leadSourceType `new`, leadSourceProvider set to the recommended primary provider, currentStep set to that provider lane (`sales-nav`, `signal-discovery`, or `prospeo`), and find-leads watchNarration. If the recommendation changed from the lane last sampled, switch the watched provider page to the recommended lane first so the user can inspect what they are approving. Use a headline like `Review the source in Codex`, body copy that says the browser is showing the evaluated source/results, and nextAction like `Approve in Codex`. Do not keep future-tense copy like `I'll show a source recommendation` after the decision is visible. Include a safety note that no leads import until the user approves the source.",
-          "chatRenderRule": "Show a compact rendered-Markdown decision card only, never a fenced code block. The first sentence must make the decision explicit: 'I recommend {primary source} using {exact filter/source recipe}. The runner-up is {source} because {reason}.' Use only these sections: Lead source decision, Source recommendation, Math, Why this source, and the concrete approval question. The Math section must include labeled lines for Eligible posts, Sample, ICP-fit, Target, Posts needed, Selected, Expected good-fit leads, and Scale option. Show fit as n/N plus an easy percentage or range, never percent-only. Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead lists, or long tradeoff prose in the default approval packet; keep those details in lead-review.md or campaign/source decision state. Do not forecast connection acceptance rates, reply rates, meetings, pipeline, revenue, or ROI unless the user supplied verified benchmark data for this exact workspace/sender. For Signals, do not recommend from raw post count. Compute eligible right-content posts, reachable engagers, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the user wants more volume than the warm post-engagement estimate, explicitly say which Sales Nav or Prospeo alternative provides that volume and what message-context warmth is lost. If no engagers could be fetched, say that explicitly and lower confidence. Do not show plain filesystem paths unless links cannot be created."
+          "chatRenderRule": "Show a compact rendered-Markdown decision card only, never a fenced code block. The first sentence must make the decision explicit: 'I recommend {primary source} using {exact filter/source recipe}. The runner-up is {source} because {reason}.' Use only these sections: Lead source decision, Source recommendation, Math, Why this source, and the concrete approval question. The Math section must include labeled lines for Eligible posts, Sample, ICP-fit, Good-fit / 100 engagers, Avg engagers/post, Good-fit / post, Target, Posts needed, Selected, Expected good-fit leads, and Scale option. Show fit as n/N plus an easy percentage or range, never percent-only. Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead lists, or long tradeoff prose in the default approval packet; keep those details in lead-review.md or campaign/source decision state. Do not forecast connection acceptance rates, reply rates, meetings, pipeline, revenue, or ROI unless the user supplied verified benchmark data for this exact workspace/sender. For Signals, do not recommend from raw post count. Compute eligible right-content posts, reachable engagers, sampled ICP-fit rate, good-fit prospects per 100 engagers, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the selected warm posts only support a review batch or smaller pilot, say they do not hit 500 instead of calling them scalable. If the user wants more volume than the warm post-engagement estimate, explicitly say which Sales Nav or Prospeo alternative provides that volume and what message-context warmth is lost; Sales Nav must be broadened/loosened before it is presented as the scale option if the initial filter pool is too tight. If no engagers could be fetched, say that explicitly and lower confidence. Do not show plain filesystem paths unless links cannot be created."
         },
         {
           "action": "render_post_lead_parallel_progress",
@@ -816,7 +824,7 @@
         {
           "action": "ask_continue_revise_or_confirm_only_if_needed",
           "approvalQuestionRule": "If asking the user, the question and options must name the concrete decision. Prefer: 'Approve Sales Nav with {filters}, or use warmer Signals instead?' over 'Approve this lead source?' Option labels must name the source choice, such as 'Approve Sales Nav filters', 'Use warmer Signals posts', 'Try Prospeo/account search', and 'Revise source'.",
-          "approvalMathRule": "Immediately above the approval question, render the compact Math block: given this many eligible relevant posts, this many reachable engagers, this sampled ICP fit as n/N plus percentage/range, this target good-fit lead count, and this many posts needed, we expect this usable lead range from the selected posts; if the user wants more volume, name the Sales Nav or Prospeo alternative, its preview/sample math, and the colder/weaker-context tradeoff. Do not ask the approval question until this math is visible.",
+          "approvalMathRule": "Immediately above the approval question, render the compact Math block: given this many eligible relevant posts, this many reachable engagers, this sampled ICP fit as n/N plus percentage/range, this many good-fit prospects per 100 engagers, this average reachable engagers per post, this expected good-fit prospects per post after cleanup, this target good-fit lead count, and this many posts needed, we expect this usable lead range from the selected posts; if the user wants more volume, name the Sales Nav or Prospeo alternative, its preview/sample math, any Sales Nav loosening used to avoid an over-tight pool, and the colder/weaker-context tradeoff. Do not ask the approval question until this math is visible.",
           "autoContinueWhen": {
             "status": "confirmed",
             "confidenceIn": [

package/skills/providers/signal-discovery.md

@@ -89,6 +89,16 @@ You must estimate:
   - how many sampled people matched the rough headline rubric
 - `passRate`
   - sampled pass rate used for extrapolation
+- `goodFitPer100Engagers`
+  - normalized fit rate as good-fit prospects per 100 engagers, before and
+    after a conservative dedupe/cleanup factor
+- `avgReachableEngagersPerPost`
+  - average reachable engagers per right-content post used for capacity math
+- `goodFitProspectsPerPost`
+  - expected good-fit prospects per right-content post after dedupe/cleanup
+- `postsNeededForTarget`
+  - number of right-content posts needed to reach the target good-fit lead
+    count, defaulting to 500 unless the campaign says otherwise
 - `projectedRange`
   - the conservative range implied by the observed sample
 
@@ -112,7 +122,7 @@ Use conservative logic:
    - stale posts
    - adjacent communities that are not actual buyers
 4. Explain the pass-through briefly and explicitly:
-   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `avgUsableEngagersPerStrongPost`: 20-40, `projectedRange`: 210-600"
+   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 before cleanup / ~13-16 after cleanup, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~31-38, `postsNeededForTarget`: ~14-17, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `projectedRange`: 210-600"
    - fallback: "I could not fetch engagers, so this is inferred from post and author quality only"
 5. If the evidence is too weak, say so and return a low-confidence estimate instead of pretending precision.
 6. Do not manually enumerate dozens of engagers in the final answer. Summarize the sample by `sampledCount`, `passCount`, `passRate`, `projectedRange`, and 3-6 representative examples.
@@ -368,6 +378,8 @@ recommendation, estimate source capacity from real sample math:
 - eligible right-content posts by lane/content type
 - reachable engagers from those posts
 - sampled ICP-fit rate as `n/N` plus an easy percentage/range
+- good-fit prospects per 100 engagers before and after conservative cleanup
+- average reachable engagers per right-content post
 - expected good-fit leads per selected post after dedupe/cleanup
 - posts needed to reach the target