# Source acquisition cost scenarios

Generated: 2026-05-20T02:31:32.902Z

No-spend scenario estimates for choosing a small local max-spend cap. This does not enable provider spend.

Recommendation: DataForSEO first; Apify only after a named post-pilot gap.

## Guardrails
- Scenario estimates are not approval and do not unlock spend.
- DataForSEO payload remains empty until ASINs are confirmed.
- Apify remains blocked until DataForSEO review selects run_apify_gapfill and names a gap.
- Use these rows to fill source-acquisition-cost-plan.json; then rerun cost, approval, preflight, and spend gates.

## Scenarios
- DataForSEO Stage 1 / standard_queue_exact_9_asin_depth_10: 10 ASIN tasks x 1 ten-review block x $0.00075 => estimate $0.0075; suggested local cap reference $1. Status: blocked_until_asins_budget_cost_plan_approval_preflight.
- DataForSEO Stage 1 / priority_queue_reference_only: 10 ASIN tasks x 1 ten-review block x $0.0015 => estimate $0.015; suggested local cap reference $1. Status: not_recommended_without_explicit_speed_need.
- DataForSEO Stage 1 / depth_safety_rule: depth 10 stays at 1 ten-review block; depth 11 would round to 2 blocks => estimate $0.0075; suggested local cap reference $1. Status: keep_depth_10.
- Apify Stage 2 / one_actor_first_3_targets_reference_cap: 1 actor run x first 3 targets x 3 requests/brand; CU cost depends on actual run => estimate $0; suggested local cap reference $5. Status: blocked_until_dataforseo_review_names_gap.
- Apify Stage 2 / compute_unit_reference: $0.2 per CU; exact CU = memory x runtime plus platform usage => estimate $0; suggested local cap reference $5. Status: reference_only.

## Next use
- Keep spend blocked until ASINs/payload are ready.
- If choosing to subscribe later, fill `data/sources/budgets/source-acquisition-cost-plan.json` from these scenarios and current account pricing, then rerun all gates.