It scans the market daily and pushes you only the few worth answering

Source, deduplicate, score, draft per channel, push to your phone. A lead that fails a step is never marked done, so it does not quietly disappear.

$ gig-radar demo

Scored leads (demo fixtures):
   92  ai-integration  [Hiring] Build a support chatbot grounded in our product docs (RAG)
   84  automation      [Hiring] Automate weekly ops reporting from Airtable and Slack
   76  ai-video        [Hiring] AI-generated product demo video for our launch
   28  other           [Hiring] Senior ML engineer, Toptal-vetted only
   12  other           [Hiring] Fix the fonts on my WordPress theme

(demo run: 5 ingested, 5 scored, 3 drafted, 3 would be pushed)
Real output from gig-radar demo, running on bundled fixtures with no network and no keys. Look at the last two rows: a Toptal-only ML role scores 28, a WordPress font fix scores 12, and neither gets pushed. The time saved is there, not in volume. This is the scoring section of the output, the drafting section is left out.

Why more listings is not the answer

Public hiring posts are not scarce. Filtering them is. Out of dozens a day, two or three actually match you. The rest have the wrong budget or are not your line of work.

The problem with filtering by hand is not speed, it is gaps. Two busy days and the window to reply has closed. A machine's value is that it does not have busy days.

So what it optimises for is no misses and no repeats. Each lead is pushed once, a failed push is retried, and a lead that clears the bar on a busy day waits in the queue and surfaces on a quieter one.

Every step leaves a trace

01

Source and deduplicate

Several public sources, each pulled for new items and checked against everything already seen. Re-running never hands you the same lead twice.

02

Score

Each lead is judged against your positioning: fit, budget signal, and whether the poster looks like a real client. The score and the reason are both kept.

03

Draft

Only the top few get written, and the wording changes by channel. A forum reply, a cold email and a platform bid are not the same register.

04

Push to you

Pushed to Telegram with the score, the reason, the original link and the draft. Whether it goes out, and in what form, is your call.

State lives in a local database. A lead that fails scoring is not persisted and gets fetched and scored again next run. One whose push fails is not marked pushed and stays in the queue. A failed draft does not swallow the lead, it arrives labelled draft failed, write manually. pytest reports 61 passing, run on 2026-08-31.

Where it gets things wrong

  • The score comes from a model, and models misread. That is why it pushes scores to you and never sends on your behalf. The judgement stays with the person at the last step.
  • The sources are public, so anyone can reach them. It wins on speed and coverage, not exclusivity. Anyone promising a private lead pool is making a claim worth checking.
  • A draft is a draft. Read it before it goes out under your name. The smoother it reads, the more that matters.

What each side brings

You bring

  • Your positioning: what you do, what you want, what you turn down
  • The sources to watch, or let us propose a set for your trade
  • A Telegram account to receive the pushes

We bring

  • A pipeline on your own server, running daily unattended
  • Persisted state, so a lead that fails is never marked done and comes back in the queue
  • Scoring rules and draft templates as configuration you can edit

Not this

  • Sending under someone else's name, or bidding as another identity
  • Blasting. One letter with the name swapped, sent to a hundred firms, reads as exactly that