Build a prospect list

The insight: a list's quality is set by its worst validation gate, not its best source — and a count ask is the standing temptation to skip the gates. "Get me 50" tempts every builder to pad: widen the filters silently, keep the departed, keep the adjacent-but-wrong titles. The searches are recall engines — they hand back companies outside the size band you asked for and people who left the company months ago, without erroring. So the deliverable is defined by what survives validation: 38 validated rows beat 50 padded ones, and when the honest count falls short you say so and offer the widening levers (looser geo, adjacent titles, wider size band) — the user chooses, never the skill silently.

Declared inputs

Nothing here ships with a value. Each one is the installer's, not the author's: ask for it, never substitute a plausible default, and where an answer does not exist say which step becomes unavailable rather than guessing. Where a default IS defensible it is named below, and using it means saying so in the output.