Octo reads the search results you already have open. It flags clients who rarely hire, hides "$5 to $25" bait posts, and remembers every job you've opened. All before you click.
Everything runs on the page you already loaded. Your thresholds, your words, your history.
The moment you open a job, Octo reads the client's posting history and flags the ones who collect proposals but never hire. A client with 73 posts and a 20% hire rate gets a red edge before you spend a connect.
You set $25/hr. Upwork still shows "$5–$25" posts. Octo hides any job whose posted minimum sits more than 20% under your filter, leaving a thin one-line bar you can tap to peek. The little green * next to Upwork's Min field explains it, right where you'd look.
"Commission only", "crypto", "rockstar". Whatever wastes your time, add it to your list and matching posts never render again.
Members pool the client stats their own browsers already displayed. So a warning can appear on a job you never clicked, because someone else did.
Octo never talks to Upwork's servers. Not one request. It reorganizes the information your browser already rendered for you, the same way an ad blocker or password manager works. Nothing to detect, nothing to abuse.
No dashboard to learn. Octo annotates Upwork's own controls, like the asterisk on the hourly rate filter, and stays quiet everywhere else.
Upwork sells connects whether or not a client ever hires. The risk is all yours, and nobody upstream loses sleep over it. Octo is the layer that's on your side: built in the open, steered by the freelancers who use it, powered by what we all see anyway. Protection, pooled.
Bid averages, proposal counts, hiring activity: the numbers Upwork reveals only after you've paid to apply. Once one member applies, every member sees them.
"Client ghosted after 3 interviews." Leave it on the job; the next freelancer reads it before spending a connect.
Connect the dots between a client's posts over time, so their real history follows them, not just the stats on today's listing.
Your proposals this week, in the navbar, next to the community's pace. A little friendly pressure, plus a leaderboard email for the competitive.
The roadmap is steered by members, not decreed. The best ideas so far came from people describing their worst week. Suggest a feature in our community →