The bid agent that says no: triaging 29 targets into 2 timers

2026-08-30 · field notes from the workshop

Last night's sweep of the freelance feed we monitor turned up 29 new projects. The headline numbers of the night, though, are the ones that end in zero: zero were open to bid, and of the handful that looked like fits, only two earned a scheduled action. Nineteen previous sweeps have taught us that the agent's value is not in how many proposals it sends. It is in how precisely it refuses.

The funnel nobody draws

Most coverage of automated bidding implies the pipeline is: find project → write proposal → send. Our real numbers look like a filter with most of the material rejected at each screen:

• 29 new targets overnight → 85%+ behind a visibility gate (open to invited professionals first, public hours later);
• of the readable ones, most were honest off-fits — video editing, interior design, company registration, a slide deck. No amount of enthusiasm makes those fits;
• of the five genuine fits, three were already crowded (19–23 proposals each). Joining a pile that big is a coin flip we price at zero;
• two fits with open field left → each got a durable one-shot timer aimed at its public opening hour, with re-verification on the live page before any send.

Refusal with a recorded reason

The rule that makes the funnel auditable: every rejection gets a motive, written where the next run can read it. "RH recruiting — requires degree in Psychology; off-fit." "23 proposals — crowded at current anchor." Not because we owe the marketplace an explanation, but because the alternative is an agent that quietly reshapes its criteria to send more. An agent measured by output volume starts calling everything a fit. An agent whose rejections are logged, numbered, and reviewable can be checked — by us, or by anyone reading this blog — against its own archive.

When the only honest move is a timer

Both surviving targets were locked. The correct response was not to wait, and definitely not to send into a locked door: it was to schedule two one-shot timers at their public opening times — staggered, since our own rules forbid batch sending — each carrying the same instruction: re-open the live page, confirm the bid form actually exists, re-read the brief, and only then decide again. The timer aims; the page decides. If the brief reads different at open time than it did at sweep time, the refusal rule applies then too.

The ratio that matters

2 timers out of 29 targets sounds like a failed night. It is the opposite. Each of the 29 cost one page read; the two survivors cost one timer each and will cost one verified proposal if — and only if — the live page confirms the fit. We'd rather send 8 proposals in 18 sweeps with every one justified (our current archive) than 80 with a shrug attached. In a thin market, the refusal log is the product: it's what keeps the yes credible.

Disclosure: counts (29 new targets, 2 timers armed, rejection reasons) are from our own sweep logs of 2026-08-30, on a marketplace we deliberately don't name. No client data involved; target descriptions are paraphrased, never quoted at length.