About
solo · public beta · ships every Friday

I built Upwatcher because I was tired of being candidate #20 on every Upwork brief.

Hi — I'm Danylo. I freelance on Upwork from Lviv, Ukraine. Upwatcher is a tool I made for myself first, because the gap between a brief going live and forty-seven proposals landing on it had gotten too short to win by refreshing the search tab.

The problem I had

A queue forms in three minutes.

Every Upwork search tab I kept open was the same story. Eight in the morning, decent client, a brief that read like it was written for me. By the time I read it, opened the proposal, pasted my voice, edited the rate, attached a sample — there were forty proposals on it. Not because mine was bad. Because mine was forty-first.

I tried the usual fixes. Email digests are too slow. The mobile app pings you on the wrong kind of jobs. Auto-bidders log in as you and click Apply on every brief they find — that's a TOS violation by construction and gets accounts flagged. Nothing existed that just told me a job was up the moment it was up and let me decide whether to act.

What I built

An editorial tape, not an auto-bidder.

Upwatcher reads public Upwork postings on its own infrastructure — it never logs in as you, never auto-bids, never runs anything in your browser. When a new posting matches the search URL you paste in, you get a Telegram, Discord or Slack ping within seconds, with a fit score against your profile and three proposal drafts ready to edit and send. You stay in the loop. Your Upwork account stays clean.

That TOS-safe posture is the entire design constraint. Everything Upwatcher does is something a careful freelancer could do manually — just instant, parallel across niches, and with the boring parts (draft scaffolding, rate benchmarks, profile gaps) handled for them.

How it ships

Built in public. Weekly cadence.

Upwatcher is solo. One developer (me), one product, one roadmap visible from the public changelog. There's no team, no investors, no "let me check with marketing." The tradeoff is honest: feature velocity is what one careful person can ship in a week, and every public-beta user gets to see exactly what's landing on Friday.

I run on a build-in-public cadence — Threads, LinkedIn, X. The reason isn't theatre, it's accountability: when the week's ship is visible the day it lands, the work has to be real.

What it isn't

Four things Upwatcher will never become.

  • Not an auto-bidder. No version of the product, paid or free, will ever submit a proposal on your behalf. The draft is yours; the send button is yours.
  • Not a scraper of your account. We never ask for Upwork credentials, never run a browser session as you, never read your inbox. Everything is sourced from public job pages on our infrastructure.
  • Not a content mill. The market and guides pages are built from the same scrape that powers the alerts — real medians, real percentiles, real 30-day samples. If the data is thin, the page says so.
  • Not eternally free. A paid tier is coming. The free watcher stays free. Founding-tier pricing locks in for anyone who signs up before paid ships.
The operator

One developer, Lviv, Ukraine.

Upwatcher is operated by Danylo Vyslotskyi, an individual based in Lviv. The product, the website, the scraper, the LLM pipeline, this page — all of it is one person's work, and the company behind it is a sole proprietorship registered in Ukraine.

Reach me at hello@upwatcher.io. Bugs, feedback, feature requests, "why doesn't your scraper read X" — I read everything and try to reply inside two business days.

Try it
the only honest test is your own niche

Two minutes to your first watcher.

Free, no card, one Upwork search URL. From the next posting onward, you read briefs while the client is still online — not after the queue closes.