The campaign engine is easy to describe: a lead list, message templates, a daily cap and a reply inbox. What no build can supply is LinkedIn itself. Omentir sends invites and messages from your own account through a provider, and its open-source repo needs Firebase, an AI key and a Unipile account, whose entry price is about as much as the $49 subscription. That provider works by reverse engineering LinkedIn, and LinkedIn's user agreement restricts bots and scraping, so an account can be restricted whoever wrote the code. What you can build and keep is the desk around it: leads, scoring, drafted notes you send yourself and reply sorting.
Before you buildOmentir has no free hosted plan. Self-hosting its MIT-licensed code needs Firebase, an AI key and a Unipile account (from about €49 a month), so it isn't a cheaper route.
Build me a LinkedIn prospecting desk that I operate by hand, covering the part of Omentir I can build without automating LinkedIn. Requirements: - Node.js 22 + TypeScript: Fastify with htmx pages on http://127.0.0.1:4910; storage in better-sqlite3 at ./data/prospects.db. - Leads: import a CSV (papaparse) with name, title, company, company size, location, profile URL and a free-text "recent activity" column; dedupe by profile URL; add tags and notes. - ICP: a settings page where I describe my ideal customer (titles, industries, company sizes, exclusions). Score each lead 0-100 with an OpenAI-compatible model (OPENAI_BASE_URL, OPENAI_API_KEY and MODEL in .env), as JSON with a one-line reason checked by zod, and cache the result per lead. - Drafts: for a chosen lead, write a connection note within a limit set in .env (default 200 characters, because LinkedIn's limit varies by account type) and one follow-up, using my offer text and the lead's row only. Show the character count and never invent facts that aren't in the row. - Queue: a Today page listing up to N leads to contact (N in .env, default 20), each with an "Open profile" link, a copy button for the note, and buttons sent, skip and replied. I send everything myself inside LinkedIn. - Replies: paste a reply into a lead's page; the model labels it interested, not now, wrong person or stop and drafts a response I can edit; "stop" adds the lead to a do-not-contact list. - Pipeline: stages new, invited, connected, replied, meeting and lost, a weekly count per stage, and CSV export of everything. - No accounts, no telemetry, local-first: only the model call leaves the machine, and the README says what lead text is sent. - Out of scope: any automated sending, scraping or browser automation on LinkedIn, lead search, cold email. - README: the .env keys, LinkedIn's rules against automated activity and why this tool never touches the site, and GDPR basics for storing other people's data.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Omentir.
Add a weekly review page to the prospecting desk in this folder. Requirements: - Per ISO week, counts of leads added, notes marked sent, replies, meetings and losses, with the conversion between each stage. - Break replies down by the label the model gave them, and by the tag or ICP score band of the lead, so I can see whether high scores really reply more. - A table of leads stuck in a stage for more than 10 days. - Export the review as Markdown. Update the README.
Add company research notes to the prospecting desk in this folder. Requirements: - On a company page, a text box where I paste an About page or recent post; the model returns 3 short hooks that quote only that text, shown for my approval before they're saved. - Drafts for any lead at that company can use the approved hooks, and the draft shows which hook it used. - Never fetch pages automatically; every piece of text is pasted by me. - Update the README.
Add note templates with results to the prospecting desk in this folder.
Requirements:
- Save named templates with variables like {{firstName}} and {{company}}, and let me pick one
as the base for a draft; keep a version history.
- Record which template each sent note used, and show sent, accepted and replied counts per
template once a template has been used at least 20 times.
- Say "too few to compare" below that number; never show a percentage without the count.
- Update the README.Founders pay $49 to skip hiring an SDR and stitching a lead database, a sequencer and an inbox together, and the refund guarantee lowers the cost of trying. Omentir says it paces sending at a human rate with limits you set, but its own FAQ and help pages say LinkedIn's rules still apply and automation carries account risk.
Estimate · Runs on your machine. LLM tokens are the only running cost, nothing with a local model. This covers the desk, not automated sending. The build is token usage on your agent plan.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Pro | $49 | — | 1 user, 1 LinkedIn account, unlimited AI agents, leads and campaigns, AI-automated campaigns, API access, email support. Carries a booking guarantee: 3 bookings a week or a refund. |
| Enterprise | custom | — | Unlimited users and LinkedIn accounts, SSO, dedicated onboarding, priority support, managed campaigns. |
No free hosted plan. The code is MIT-licensed and can be self-hosted, but it needs Firebase, Unipile and an AI provider, which cost money.
Not really. Founders pay $49 to skip hiring an SDR and stitching a lead database, a sequencer and an inbox together, and the refund guarantee lowers the cost of trying. Omentir says it paces sending at a human rate with limits you set, but its own FAQ and help pages say LinkedIn's rules still apply and automation carries account risk. The prompt on this page builds the closest honest substitute.
About $49 a month on the Pro plan, $588 a year (checked 2026-10-19).
Invites and follow-ups sent for you on a schedule from your LinkedIn account; Lead search against LinkedIn with fit scoring; Targeting of people who comment on competitors' posts; A live inbox of LinkedIn replies and the MCP and REST API for Claude, ChatGPT and Cursor; The three-bookings-a-week guarantee. If any of those matter to you, keep paying.
Yes: Omentir (self-hosted) (open source), Linki (free).