Automation and integrations decision
Esferas.io
A capable developer can build a usable LinkedIn outreach tool from open-source components, but reproducing the commercial product's polish, account-safety features, and scaling/delivery guarantees is non-trivial, so keeping the paid product may make sense for full production use.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off70 h to build
$0/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Discover LinkedIn profiles, queue outreach actions, execute messages/connection requests via an automated browser, and record results/status.
What it still won’t have
- Polished, battle-tested UI and onboarding flows
- Built-in multi-account rotation and sophisticated evasion heuristics
- Commercial support and SLA
- Any closed-source analytics, integrations, or proprietary deliverability tuning
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Esferas.io does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal LinkedIn outreach automation service using FastAPI (Python) backend, Playwright for headless-browser automation, Postgres for storage, Redis for queueing, and a small React admin UI. In scope: 1) crawler to collect profiles from search pages and store leads in Postgres; 2) a Playwright-based worker that logs into LinkedIn accounts and performs connection requests and templated messages with throttling; 3) a Redis queue with retry/backoff and scheduled campaign execution; 4) REST API endpoints to create campaigns, view lead statuses, and pause/resume workers; 5) basic auth for the admin UI, logging of all outbound actions, and unit tests for critical flows. Out of scope: advanced multi-account rotation dashboards, paid analytics, training ML models, and any attempts to circumvent platform terms of service. Include error handling, retries, and automated tests for the API and worker logic.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productEsferas - LinkedIn Automation That Works
Integrity checks
What held up, and what did not.
