The need is written in a post, not in a tender
Before talking to three agencies, a founder asks their network. One sentence, posted on a Tuesday morning: "Does anyone know a reliable agency to rebuild our website?" Twenty comments within the hour, two recommendations shortlisted, a meeting booked. By the time the request reaches a tender platform — if it ever does — the decision has been made.
These posts have three flaws for anyone prospecting. They live for a few hours: by the next day, all that remains is other people's comments. The feed shows only a fraction of them: the algorithm picks a small share of what your network publishes, and nothing of what gets published beyond it. And searching by hand does not last: typing the same queries three times a day, sorting the noise, remembering what you have already seen — nobody keeps that up for more than a week.
Prosko does exactly that, continuously, inside your browser. You describe what you no longer want to miss; the extension reads the feed while you browse and queries the LinkedIn search in the background. When a post contains your words, you receive the author's name, their job title, the excerpt where the word appears and the direct link to the post.
The rule that catches these posts
A rule is a topic, words that trigger an alert, and words that block it. For a web agency, it looks like this:
Trigger words are phrases the way people actually write them, not search-engine keywords. Nobody posts "B2B web development services"; people write "does anyone know", "I'm looking for", "recommendations welcome". That is the difference between a rule that surfaces three real requests a week and one that surfaces forty blog articles. A multi-word trigger fires as soon as all of its words appear in the post, in any order: "looking for an agency" also catches "we've been looking for two weeks for an agency". Case, accents and hyphens are ignored.
Ignored words cut the noise your triggers attract despite themselves. "Looking for an agency" also catches internship offers and training ads; "we are hiring" and "internship" discard them before they bother you. Start broad, let it run for a few days, then add exclusions based on what wasted your time. A detector also flags overly generic terms as you type, before you suffer their noise.
What it catches
Two posts like the ones a rule of this kind surfaces in an ordinary week. The names are made up; the phrasing is not.
"Does anyone know a reliable agency to rebuild our marketing website? Budget approved, kick-off in March."
"Our mobile app is no longer maintained, the previous agency shut down. Recommendations welcome for a freelancer or a small team able to take over a React Native codebase."
The first post comes from the LinkedIn search — that is, from beyond your network. The second went through your feed while you were reading something else. In both cases, the window for a useful reply is measured in hours.
The alert you receive
"Does anyone know a reliable agency to rebuild our marketing website? Budget approved, kick-off in March."
No automatic summary, no score: the person, what they do, what they wrote, and the link to the post. "Checked by the assistant" means the AI assistant re-read the post and confirmed it is someone actually looking, not a post that merely discusses the topic — a job ad and an article on "how to choose your agency" contain the same words. You describe your intent in one sentence; it discards the rest. The analysis is included in the subscription, within a monthly quota shown in the extension.
Reply fast, but reply well
The alert gives you the head start; what you do with it decides the rest. A few common-sense rules, in four lines.
Reply within the hour, publicly first. A useful comment — a precise question about the need, an example of a comparable project — beats a cold private message. The author sees you have read the post, and so do the other readers. The private message comes afterwards, short, referring to the comment.
Do not pitch. The person did not ask for a presentation, they asked for a name. Give yours, one sentence about the closest thing you have done, and let them come to you. Three-paragraph replies end up at the bottom of the list.
Keep a record. Finds stay in the extension — the last five hundred — with the date and the link. A request you did not answer last month is still a relevant contact this month: the need does not vanish because the post got older.
Expect the right volume. A well-tuned rule for a specific line of work surfaces a few posts a day, not fifty. If you receive fifty, the rule is too broad, and you will stop reading them before the week is out. Tighten the triggers or add exclusions.
What to know before you start
- Your LinkedIn account is enough. Free or Premium, Prosko reads the feed and the search exactly as your account displays them. Sales Navigator is not required.
- It does nothing on your behalf. No messages sent, no connection requests, no automatic comments. Prosko tells you, you reply — and your account stays yours, with no automation putting it at risk.
- Everything runs in your browser. No server, no account on our side: your keywords and finds never leave your machine. In return, monitoring works while Chrome is open.
- It reads posts. That is where requests get written. The comments, where they get discussed, are one click away from the alert.
Frequently asked questions
Do I need a Sales Navigator account?
No. Prosko reads the LinkedIn feed and search exactly as your account displays them, free or paid. Sales Navigator changes nothing about what the extension sees.
How many alerts a day should I expect?
It depends entirely on your words. A rule with four or five precise triggers, for a specific line of work, usually surfaces a few posts a day. If you receive many more, it is your triggers that need tightening, not the tool.
Does it work in French, or in several languages?
Yes. The watched words are the ones you write, in whatever language you want. A single rule can contain both "looking for an agency" and "cherche un prestataire".
Are my keywords and finds sent anywhere?
No. There is no server on our side, no account, no telemetry. Your rules, your finds and your webhook address stay in your browser's local storage. The only outside destinations are the ones you configure yourself: your Slack, your Discord.
Can several salespeople share the alerts?
Yes, by sending alerts to a shared Slack or Discord channel. Each person running the extension needs their own licence; the channel is shared by everyone who reads it.
Page updated on .