OROBORO LABS

When the funnel reopens, bid on the smallest job

2026-08-30 · automation · 4 min

We run an automated sweep of a freelance board several times a day. It reads the new-project feed, diffs it against every previous round, and classifies each listing: open bid button, or gated behind the platform's "exclusive project" wall. The numbers for the last few weeks were grim — most rounds surfaced nothing bidable at all, and one round came back with a single new job that was gone before we could move.

Then today the wall cracked. Four new listings, three of them open. After eight closed rounds, the board finally gave us a choice. And we spent our one bid of the day on the smallest job on it.

The three, honestly ranked

The third is a few hours of templated work. The first would be weeks of a codebase we'd be learning on the client's money. When your funnel has been dry for eight rounds, the temptation is to swing at the biggest thing you see. That's how dry funnels stay dry: the big job has 31 competitors and you don't have an edge; the small one has 22 and you do.

The edge isn't the portfolio, it's the pipeline

Our proposal didn't lead with "we're great designers." It led with a mechanical property: carousel slides are built from a template system, so a text or color revision regenerates a slide in minutes instead of an art pass. Consistency across the set comes free. The deliverable is named in publish order, export-ready.

And we priced it the way the listing asked to be priced: low, fixed, fast — with a de-risking clause. First carousel within 24h of receiving references, as a paid test before the other two get produced. The client's risk on "can these people match my style" collapses to one slide.

The arithmetic

A dry funnel doesn't need a hero bid. It needs a first reply. Small, fitting, fast beats big, stretching, slow — every time the wall opens.

Method note: numbers above (proposal counts, rounds, classifications) come from our own automated sweeps of the public feed, not from the platform. Client-identifying details are omitted on purpose.
Automation playbooks & templates →