Is it running well?

The daily scan has never run yet.

The 20 most recent

Latest emails found

All origins combined (signals, Google Maps, referral...) - the section above only covers prospects that came from a market signal.

No email found recently.

The keywords we anchor on

One keyword per line, per market. actif = searched every day, disabled = kept for reference, never searched. Click a keyword to enable or disable it, "✕" to delete it for good. News (press) search only - the job titles for hiring are just below, in their own block.

The job titles that trigger a search

Same mechanism as above, applied to job postings (JobSpy search, LinkedIn + Indeed) rather than press. A studio hiring on one of these titles has an approved budget - the art outsourcing window opens shortly after the role goes live. This only affects job posting search - ICP qualification by engagement (leads already identified on LinkedIn) is judged separately and does not read this table.

Is this keyword bringing back good things?

Read-only search on a single keyword/region, never creates a real signal or prospect - judge a keyword before enabling it (Configuration section), or understand why an already active keyword brings nothing back. Same mechanism as "Run the scan": the request is handled by a script on the server within the next 10-15 minutes (DDG/GDELT do not run in this container).

Recent results

No test run yet.

What works best

Sorted by the average score of the prospects created (pipeline/scoring.py - referral, signal strength, company size and freshness already combined), not by volume - the signal count stays shown next to it: a score based on 1 signal does not carry the same reliability as one based on 10. Based on keyword/region → signal attribution, tracked only since 2026-07-31: older signals do not appear here. The average score remains a PREDICTION made when the prospect was created - "real replies" next to it measures what actually happened afterwards (same definition as the conversion funnel: replied, has a meeting, or won).

By keyword

By region (Southeast Asia)

By source

Objectively checks whether the new sources (RSS feeds, government registries) really produce better prospects, rather than assuming it from the weight declared in advance (pipeline/scoring.py::SOURCE_STRENGTH_OVERRIDE).

What the current configuration can produce

Not a promise nor a real historical extrapolation - too few real signals since automation started (2026-08-16 13:33:32) for that. A ceiling of capacity derived from the current configuration, next to what was actually observed over the last 7 days.

231 signals detecteds in total since the start, of which 0 devenus a real prospect in the pipeline. The ceiling assumes one region scanned per day (full cycle over 4 days) and up to 10 results per search - reality depends on what the press and job boards actually publish, often well below the ceiling.

Leads derived from current data

231 signals awaiting manual review (status 'new') - normally close to 0, automation handles the rest by itself. A growing backlog can mean a market has lost its approved sequence.

1 market(s) with no active keyword - will never produce a signal as long as no keyword is enabled (Configuration section) : dedicated (dedicated).

Signals per market, from least to most covered - still early (automation from 2026-08-16 13:33:32) to tell a market in trouble apart from a market that simply has not had a lucky break yet.