Freelance proposal pipeline

What it is

Freelance platforms reward speed, which is exactly why most proposals are bad. This pipeline goes the other way: it reads everything, keeps almost nothing and spends the platform's limited connects only on jobs that pass a client-quality gate and rank high on expected value.

Proposals get drafted against the actual posting and submitted through the platform's own flows. A Postgres ledger tracks every API call against rate limits. A circuit breaker backs off the moment the platform signals a restriction.

Under the hood

• A pipeline with opinions: classify, gate, enrich, rank, draft, submit. The gate is loud about what it rejects and why.
• Expected value per connect: jobs ranked by what the connect is actually likely to return.
• Rate-limit discipline: a Postgres ledger for every API call and a circuit breaker for restrictions. The account never looks like a bot even though it is one.
• Drafted, not templated: proposals are written against the posting text.
• A documented pivot: the original strategy qualified many jobs, the current one ranks few. The write-up says why.

What was hard

Staying inside the platform's tolerance. The pipeline does everything a careful freelancer does, just faster. The design that keeps it welcome is boring on purpose: paced calls, a ledger, an honest backoff. The strategy pivot came from the same discipline: fewer, better proposals beat more, worse ones. The funnel data said so.

Stack