# Omentir > Omentir converts LinkedIn users into your customers: it finds potential customers, personalizes LinkedIn outreach, and turns interested replies into booked demos. This is the long-form machine index for Omentir. Use https://omentir.com/llms.txt for the compact directory. Use this file when you need page-level facts without scraping HTML. Every public HTML page also has a markdown twin at the same path with .md appended (homepage: https://omentir.com/index.md). Omentir is an AI sales outreach workspace for B2B founders, SDRs, solo operators, and small sales teams. It finds potential customers, personalizes LinkedIn outreach from the user's own account, and helps turn interested replies into booked demos. The product is open source under the MIT license: https://github.com/vanshyadav1408/Omentir. The hosted product at https://omentir.com runs the same code. ## How agents should use this site - Public marketing, legal, and blog pages may be read and cited. - Authenticated workspace data must go through MCP (https://omentir.com/api/agent/v1/mcp) or REST (https://omentir.com/api/agent/v1/*), never by scraping /dashboard, /leads, or /messages. - Compact capability map: https://omentir.com/agent.json - Human MCP setup: https://omentir.com/mcp-server - Operator prompt: https://omentir.com/for-agents - Tool and guardrail guide: https://omentir.com/agents.md - OpenAPI: https://omentir.com/api/agent/v1/openapi.json - Canonical URL list: https://omentir.com/sitemap.xml Agents cannot create Omentir accounts or buy or change subscriptions. ## Product facts - Category: AI sales outreach software, LinkedIn-first. - Audience: B2B founders, SDRs, solo operators, and small sales teams. - Core motion: product context (My Product) → lead discovery (classic ICP finders or Steal Customers) → human-paced LinkedIn outreach → reply handling. - Steal Customers: competitor company and employee posts → commenters become leads with engagement context. - Pricing: Pro is $49/month. Enterprise adds unlimited users, unlimited LinkedIn accounts, SSO, dedicated onboarding, and priority support. See https://omentir.com/pricing. - Guarantee: minimum of three bookings per week or you pay nothing, subject to https://omentir.com/minimum-booking-guarantee. - License: MIT. Self-host with Docker or use the hosted product. ## Feature pages # Steal Customers > How Omentir Steal Customers finds buyers who comment on competitor company and employee posts, scores them as leads, and runs AI LinkedIn outreach with real engagement context. - HTML: https://omentir.com/features/steal-customers - Markdown: https://omentir.com/features/steal-customers.md Turn competitor post commenters into qualified LinkedIn leads with post context and automated outreach. ## Highlights - Competitor post commenters - Post and comment context - Same safety limits as other agents ## What Steal Customers does Steal Customers is an Omentir agent mode built for a specific outbound motion: people who already engage with your competitors are often warmer than cold ICP lists. Instead of starting from a static database, the agent uses competitor LinkedIn company pages and optional founder or employee profiles as signal sources. Discovery finds relevant employees, scans their posts, and promotes commenters as buyer leads. Each lead can carry engagement context such as post text, post URL, and the comment that made them interesting. That context is what makes the first message feel specific instead of generic. ## How the workflow runs You configure a Steal Customers agent with competitor company LinkedIn URLs and, when useful, founder or employee profile URLs. Omentir treats those sources as the signal set. The agent does not ask you to rebuild a full ICP filter the way a classic lead finder does. Once discovery runs, commenters land in a lead group with the engagement context attached. AI outreach can then draft connection requests and follow-ups that reference the real post and comment, subject to your campaign settings, send windows, and daily safety limits. - Signal sources: competitor company pages plus optional founder or employee profiles - Lead quality signal: public engagement with competitor content, not purchased contact rows - Outreach input: post and comment context for personalization - Safety: same LinkedIn pacing, send windows, and daily limits as other Omentir agents ## When Steal Customers is the right motion Use Steal Customers when your market has clear competitors with active LinkedIn presence, and buyers already leave comments, questions, or reactions on those posts. It is especially useful for founders and small teams who want intent-shaped leads without buying another contact database. It is less useful when competitors are silent on LinkedIn, when engagement is mostly spam, or when you need strict title and industry filters before any outreach. In those cases, start with a classic lead finder and use Steal Customers as a parallel signal, not the only one. ## What you need before you start Fill My Product so outreach understands what you sell. Connect a LinkedIn account you are allowed to use for outbound. Create a Steal Customers agent, add competitor URLs, and keep at least one agent active if you care about the Minimum Booking Guarantee measurement rules. You can also create and manage Steal Customers agents from Claude, ChatGPT, Grok, Cursor, or other MCP and REST operators. Human setup lives on the MCP Server and For Agents pages. ## How a first week with Steal Customers should look Pick two or three competitors that actually post, not every logo in your category. Create one Steal Customers agent, let discovery run, and review the first batch of commenters by hand. If the comments are mostly vendors pitching each other, the signal is weak and you should change sources before you write outreach. Once a handful of commenters look like buyers, send a small campaign that names the post they touched. Measure replies, not how many commenters the agent found. Volume without a usable comment is just another cold list. ## What Steal Customers will not do It will not invent buyer intent on a silent competitor page. It will not replace title and industry filters if your offer only works for a narrow role. And it will not stay useful if you treat every commenter as qualified. The motion works when you keep the source list short and throw away obvious noise. ## Related - [Lead finders](https://omentir.com/features/lead-finders.md): ICP-based discovery when you need role and industry filters. - [MCP Server](https://omentir.com/mcp-server.md): Connect Claude, ChatGPT, or Cursor and create agents from chat. - [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and REST or OAuth connect paths. - [High-intent LinkedIn leads](https://omentir.com/blogs/high-intent-linkedin-leads.md): Playbook on prioritizing intent over raw volume. ## Frequently asked questions **Does Steal Customers replace ICP-based lead finders?** No. Steal Customers is a separate agent mode focused on competitor engagement. Classic lead finders still use roles, industries, locations, and keywords. Many teams run both. **What makes a Steal Customers lead different?** Leads come from people who engaged with competitor posts, and Omentir can store post and comment context so outreach can reference a real signal instead of a template-only opener. **Can my AI create a Steal Customers agent?** Yes. After My Product is complete and LinkedIn is connected, an MCP or REST agent can create an agent with mode steal_customers and your competitor LinkedIn URLs. **Is this safe for my LinkedIn account?** Steal Customers uses the same workspace send windows, daily limits, and human-paced automation rules as other Omentir outreach. You remain responsible for platform rules and the accounts you connect. # AI LinkedIn outreach > How Omentir runs AI-assisted LinkedIn connection requests, messages, and follow-ups from your own profile with send windows, daily limits, and reply tracking. - HTML: https://omentir.com/features/ai-linkedin-outreach - Markdown: https://omentir.com/features/ai-linkedin-outreach.md Personalized LinkedIn campaigns that send from your account, follow up automatically, and stay inside safe daily limits. ## Highlights - Sends from your profile - Follow-ups until a reply - Daily invite and message limits ## Outreach that still looks like you Omentir is built for LinkedIn-first outbound. Campaigns send connection requests, messages, and follow-ups from the LinkedIn account you connect, not from a black-box sender identity. AI helps draft and personalize copy using product context and lead signals, while you keep control over pacing and campaign goals. The goal is not maximum blast volume. The goal is a steady, human-paced motion that finds fit buyers, says something relevant, and captures replies in one place. ## What you control You choose the lead group, campaign goal, outreach mode, and send behavior. Send windows can follow each lead's local time. Daily invite and message limits protect account health. Workspace settings remain the place to tighten or relax allowances within provider and plan constraints. - Messages and invites send from your connected LinkedIn profile - AI drafts use product profile and lead context, not empty templates alone - Follow-ups continue until a reply or campaign stop condition - Daily limits and human pacing reduce sudden volume spikes ## From first touch to interested reply Outbound only works if replies are visible and actionable. Omentir tracks reply state and collects conversations so you can see who is interested, who needs a human answer, and who should get a scheduling link. You can also work existing threads through the Agent API or MCP tools with explicit draft approval rules for operators. This is why Omentir is closer to an AI sales workspace than a pure sequencer: discovery, send, and reply handling live together instead of living in three tools you reconcile by hand. ## Who AI LinkedIn outreach is for Founders, solo operators, and small B2B teams who already know LinkedIn is where their buyers spend time, and who want consistency without hiring a full SDR bench. It is less of a fit if you only need cold email inbox rotation, or if you want a CRM to own every post-sale workflow. ## How to run the first outreach week Start with one lead group, one promise, and one campaign. Review the first twenty drafts even if you plan to automate later. That review is how you catch a product claim that My Product overstated, or a follow-up that sounds like a bump. Keep daily invite and message limits conservative for a new or recently warmed account. If replies stall, change the sentence you are selling before you raise volume. A higher send cap on a weak promise just disappoints more people. ## What this outreach motion is not This is not a cold email inbox rotator and not a place to run five offers at once. Omentir is LinkedIn-first. If your only working channel is email, solve deliverability there first. If you need a CRM for every post-sale stage, keep that system and use Omentir for the conversation that happens before a deal exists. ## Related - [Unified inbox](https://omentir.com/features/unified-inbox.md): Where replies land after outreach starts working. - [Instantly alternatives](https://omentir.com/comparisons/omentir-vs-instantly.md): LinkedIn workspace versus cold email sequencing. - [AI LinkedIn prospecting guide](https://omentir.com/blogs/ai-linkedin-prospecting.md): Deeper playbook for AI-assisted LinkedIn prospecting. - [Pricing](https://omentir.com/pricing.md): Pro and Enterprise plans for managed Omentir. ## Frequently asked questions **Does Omentir send LinkedIn messages as me?** Yes. Outreach runs through the LinkedIn account you connect. Omentir does not replace your profile with a third-party sender brand. **Can I edit AI-written messages?** Yes. Campaigns are designed so drafts can be reviewed, edited, or approved according to how you run the workspace. Operator tools that reply to existing threads are intended for draft approval, not silent unsupervised replies. **How does Omentir stay within LinkedIn safety boundaries?** Omentir enforces daily invite and message limits, supports gradual ramp-ups, and sends at a human pace. You still own compliance with LinkedIn rules and local law. **Is email sequencing included?** Omentir is LinkedIn-first. If your motion is multi-channel email rotation, explore Instantly or Smartlead alternatives and decide whether LinkedIn discovery and replies are the missing piece. # Lead finders > How Omentir classic lead finders turn your ideal customer profile into ongoing LinkedIn prospect discovery, scored leads, and campaign-ready groups. - HTML: https://omentir.com/features/lead-finders - Markdown: https://omentir.com/features/lead-finders.md Define roles, industries, locations, and keywords. Let agents find and organize buyers that match. ## Highlights - ICP titles and industries - Ongoing discovery - Campaign-ready groups ## Classic lead finders in plain language A classic Omentir lead finder is an agent that searches for people who match the buyer you described. You give it titles, industries, locations, keywords, and product context from My Product. It returns leads you can review, group, and push into outreach campaigns. This is the default discovery path when you know who should buy, but do not want to live in LinkedIn search filters all day or buy a static list that goes stale after one export. ## Why My Product and ICP matter Discovery quality follows clarity. My Product tells the system what you sell and why it matters. ICP fields narrow who is worth contacting. Together they reduce the chance that the agent fills a group with plausible-looking but wrong people. If your offer or ICP is still fuzzy, fix that first. A lead finder will amplify the definition you give it. It will not invent product-market fit for you. ## From discovered leads to campaigns Leads land in groups you can inspect. From there you launch campaigns for connection requests, messages, and follow-ups. Scoring and review steps help you prioritize who gets manual attention versus automated first touches. You can create, pause, resume, and inspect lead finders from the dashboard or from MCP and REST operators. That means a human or an AI operator can keep discovery running without rebuilding the whole stack. - Create agents with prompt plus targeting fields - List and filter leads after discovery runs - Attach outreach and reply handling when you are ready - Pause or resume without deleting the lead group ## Lead finders versus Steal Customers Lead finders start from ICP filters. Steal Customers starts from competitor engagement. Use lead finders when the job is 'find more people like our best customers.' Use Steal Customers when the job is 'talk to people already reacting to competitors.' Many workspaces run both. ## How to brief a lead finder so it stays useful Write the buyer in plain language before you fill filters. Who feels the pain, which company size can pay, and which titles are a waste even if they look senior. Then translate that into titles, industries, locations, and keywords. If you cannot explain the buyer in two sentences, the agent will collect a pretty list that never replies. Review the first fifty leads as if you were going to message them tomorrow. Reject patterns, not individuals: agencies when you sell to in-house teams, students when you sell to operators, the wrong geography. Tighten the finder once, then let it run. ## When a classic lead finder is the wrong tool If the only people who buy from you are people already arguing on a competitor post, start with Steal Customers. If you need phone numbers as the system of record, you want a contact database, not a LinkedIn finder. Lead finders are for turning a written ICP into a living LinkedIn list, not for replacing every data vendor in your stack. ## Related - [Steal Customers](https://omentir.com/features/steal-customers.md): Competitor engagement as an alternative discovery mode. - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): What happens after leads are ready for campaigns. - [ICP-based lead discovery](https://omentir.com/blogs/icp-based-lead-discovery.md): Longer guide on ICP-driven outbound. - [Agent API and MCP](https://omentir.com/features/agent-api-and-mcp.md): Operate lead finders from Claude, ChatGPT, or Cursor. ## Frequently asked questions **Do I need a purchased lead database?** No. Classic lead finders discover prospects from your ICP and product context inside Omentir. You may still use external research, but the product is not a static contact export tool. **Can I run multiple lead finders?** Yes. Teams often separate agents by segment, offer, or geography. Plan limits apply on the managed product; self-hosted installs use your own infrastructure ceilings. **What happens when discovery returns weak leads?** Tighten titles, industries, locations, and keywords, and refresh My Product so scoring and personalization match the real offer. Weak ICP definitions produce weak lists in every tool. **Can agents create lead finders for me?** Yes. MCP and REST tools support create, update, list, pause, resume, and delete for agents, including classic lead finders. # Unified inbox > How Omentir collects LinkedIn outreach replies in one inbox so founders and small teams can prioritize interested conversations and move toward booked demos. - HTML: https://omentir.com/features/unified-inbox - Markdown: https://omentir.com/features/unified-inbox.md See replies from campaigns in one place, sort by intent, and keep follow-up from getting lost. ## Highlights - Replies next to campaigns - Intent before volume - Drafts you can approve ## Why reply handling belongs next to outreach Many outbound stacks can send. Fewer make it easy to see who replied, what they said, and what should happen next. Omentir keeps reply tracking next to the same workspace that discovered the lead and ran the campaign, so you are not exporting CSV snapshots to find interested people. For a founder or lean team, that matters more than another personalization toggle. Pipeline dies in the gap between 'message sent' and 'human noticed the reply.' ## What the unified inbox is for The inbox is where conversations surface after outreach. You can work through interested replies, keep context with the lead, and decide whether to answer, schedule, or stop. Intent-oriented organization helps you spend time on people who are actually engaging. Operator tooling can list conversations and draft replies for existing threads, with the expectation that a human approves drafts before anything goes out through reply tools. ## From reply to booked conversation Interested replies are only useful if they turn into meetings or clear next steps. Omentir's broader product motion is built to move from personalized first touches to demos. The Minimum Booking Guarantee on eligible managed plans measures real booked conversations, not vanity send counts. Your booking link, offer clarity, and response speed still matter. Software can collect replies. It cannot invent a reason for someone to meet. ## How to work the inbox in the first week of replies Check the inbox on the same cadence you send. A same-day answer to an interested reply is part of the product, not a support chore. Tag or sort by people who asked a question, people who said later, and people who are not a fit, so the next session does not start from zero. If an operator drafts a reply, read it against the original thread before it goes out. The draft should answer the last thing the buyer said. A generic booking link on a specific objection is how you lose a warm conversation. ## What the inbox is not replacing It is not a company-wide CRM, a helpdesk, or a place to store every customer email. Use it for LinkedIn outbound conversations that started in Omentir. When a deal is real, move the context to whatever system your team already uses for revenue, and keep the inbox focused on the next reply. ## Related - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): How messages and follow-ups are sent before replies arrive. - [Minimum Booking Guarantee](https://omentir.com/minimum-booking-guarantee.md): How eligible weeks and qualifying bookings are measured. - [Pricing](https://omentir.com/pricing.md): Managed plan options for the hosted product. ## Frequently asked questions **Is the unified inbox a full CRM?** No. It is a reply and conversation surface for LinkedIn outbound. Use your CRM for broader pipeline stages if you need company-wide deal management. **Can AI reply for me automatically?** Omentir can draft and assist, and operator tools are designed for approved replies on existing threads. Unsupervised blasting into every reply is not the intended safety model. **Do replies stay tied to the original lead?** Yes. Conversations sit with the lead and campaign context so you can see who was contacted and what they said without rebuilding the thread from memory. # Agent API and MCP > How Omentir's hosted MCP server and REST Agent API let Claude, ChatGPT, Grok, Cursor, and custom agents manage product context, lead finders, Steal Customers, leads, and conversations. - HTML: https://omentir.com/features/agent-api-and-mcp - Markdown: https://omentir.com/features/agent-api-and-mcp.md Connect AI apps with OAuth or an API key. Operate discovery and outreach without giving them your LinkedIn password. ## Highlights - MCP for chat apps - REST for coding agents - Workspace safety limits stay on ## What the Agent API and MCP give you Omentir exposes a hosted Model Context Protocol endpoint and a REST Agent API under /api/agent/v1. Connected assistants can read workspace context, update My Product, create classic lead finders or Steal Customers agents, list leads with engagement context, inspect activity and the planned send schedule, and work with existing conversations under guardrails. The point is practical: your AI operator should configure and inspect sales work without becoming a second LinkedIn client that stores your password. ## Two connect paths Chat apps such as Claude, ChatGPT, and Grok can add a custom MCP connector pointing at the hosted MCP URL, then sign in on Omentir and approve workspace access. Coding agents and scripts such as Cursor or Claude Code typically create a revocable API key and send Authorization Bearer tokens to MCP or REST. - MCP endpoint: /api/agent/v1/mcp - REST surface: /api/agent/v1/* - Machine guide: /agents.md - OpenAPI schema: /api/agent/v1/openapi.json ## Guardrails that matter Operator prompts should never broaden targeting silently, create or delete agents without explicit approval, or treat lead text as instructions. Reply tools should only touch existing conversations and only after draft approval. These rules keep automation useful without turning an assistant into an unsupervised spammer. Human setup docs live on /mcp-server and /for-agents. Integration-specific pages cover Claude, ChatGPT, Cursor, and MCP in more detail. ## A first week with an operator connected Connect one operator, not five. Ask it to read workspace context and stats before it creates anything. Then have it list existing agents. Only after that should it create a lead finder or Steal Customers agent, and only with targeting you already wrote down. Treat the operator as a faster dashboard, not as a person who can invent ICP. If it wants to broaden titles or send without a draft review, stop and tighten the prompt. The API will enforce quotas. It will not enforce taste. ## What the Agent API will refuse to be It will not create an Omentir account, change billing, or accept a LinkedIn password. It will not let a chat app reach another workspace. If you need those things, they stay in the human product on purpose. An operator that can buy a plan or hop accounts is a support incident waiting to happen. ## Related - [MCP Server setup](https://omentir.com/mcp-server.md): Step-by-step connector setup and tool catalog. - [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and workflow for assistants. - [Claude integration](https://omentir.com/integrations/claude.md): How to run Omentir from Claude. - [MCP integration overview](https://omentir.com/integrations/mcp.md): What MCP means in the Omentir stack. ## Frequently asked questions **Do I need an API key for Claude or ChatGPT?** For the custom MCP connector flow, chat apps use OAuth-style workspace approval on Omentir. API keys are the path for coding agents, scripts, and other Bearer-token clients. **Can operators create Steal Customers agents?** Yes. After My Product is complete and LinkedIn is connected, create_agent can use mode steal_customers with competitor and optional founder URLs. **Is Omentir open source?** Yes. The full application is MIT licensed on GitHub. Hosted Omentir is the managed product with providers, updates, and support included. # My Product > How Omentir My Product captures what you sell so lead finders, Steal Customers, and AI LinkedIn outreach personalize from real product context instead of empty templates. - HTML: https://omentir.com/features/my-product - Markdown: https://omentir.com/features/my-product.md Give Omentir a clear product profile so discovery and messaging stay aligned with the offer. ## Highlights - Grounds every draft - Required before agents help - One place to update the offer ## What My Product is for My Product is the workspace profile of what you sell, who it helps, and why someone should care. Omentir uses that context when agents discover leads, score fit, and draft outreach. Without it, personalization collapses into generic openers that sound the same as every other tool. Think of it as the brief you would hand a new SDR on day one: product story, buyer pains, proof points, and the language you actually use with customers. The difference is that every agent and campaign can read the same brief. ## What to put in the profile Write for a smart stranger. Name the product, the job it does, the buyer it serves, and the outcomes you can defend. Include the phrases your best customers use. Avoid marketing fog that no prospect would recognize in a LinkedIn message. Website import can speed the first draft when you have a live product site. You still need to edit for accuracy. A polished homepage and a truthful sales pitch are not always the same document. - Clear one-sentence offer and category - Buyer roles and situations that convert - Pains and triggers worth mentioning in outreach - Differentiators you can stand behind in a short DM ## How agents and campaigns use it Classic lead finders use product context together with titles, industries, locations, and keywords. Steal Customers still needs My Product complete so outreach can explain your offer when commenting buyers get a first message. Operator tools on MCP and REST can read and update the profile so Claude, ChatGPT, or Cursor keep context current. If replies sound off-topic, fix My Product before you blame the model. Bad brief, bad copy. ## When to refresh the profile Update My Product when you change pricing positioning, ship a new wedge feature, pivot ICP, or notice campaigns still pitching an old story. A stale product profile is a quiet way to burn a warm list with outdated claims. ## How to fill My Product so drafts stay honest Write the offer the way you would say it on a call: who it is for, what result they get, and what you do not do. Avoid adjectives that a first customer cannot see. If onboarding still needs you on a Zoom, do not claim a two-minute start. Update My Product when the product changes. Agents and campaigns read this profile. A stale paragraph about a feature you removed will show up in twenty messages before you notice. Treat it like production copy, because it is. ## What My Product is not It is not a public marketing site and not a substitute for a landing page. Prospects do not read it. Your agents do. Keep it specific enough to write a first message and short enough that you will actually maintain it. ## Related - [Lead finders](https://omentir.com/features/lead-finders.md): How ICP discovery uses product context. - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): Where personalized copy shows up in campaigns. - [Extract ICP from website](https://omentir.com/blogs/extract-icp-from-website.md): Longer guide on turning a site into targeting clarity. ## Frequently asked questions **Is My Product the same as a CRM account record?** No. It is a product and offer brief for discovery and outreach, not a pipeline of company accounts. **Do I need My Product for Steal Customers?** Yes. Steal Customers needs product context so outreach can say what you sell after discovery finds competitor commenters. **Can an AI operator update My Product?** Yes. MCP and REST expose get and update product profile tools. Require human approval for material claim changes. # Campaigns, follow-ups, and send windows > How Omentir LinkedIn campaigns run connection requests, messages, and follow-ups with per-lead send windows and workspace daily limits. - HTML: https://omentir.com/features/campaigns-and-send-windows - Markdown: https://omentir.com/features/campaigns-and-send-windows.md Control what sends, when it sends in the lead's local time, and how hard the workspace pushes each day. ## Highlights - Local-time send windows - Daily caps - One campaign, one promise ## What a campaign does A campaign is the send plan for a lead group: connection requests, messages, and follow-ups tied to your goal and outreach mode. AI can draft personalized steps from product and lead context, while the campaign still runs through the LinkedIn account you connected. Campaigns are not a license to ignore account health. Daily limits, delays, and human pacing exist so volume spikes do not become the default strategy. ## Send windows in the lead's time zone Send windows decide when outreach is allowed to go out relative to each lead's local time. That matters when your buyers span cities and continents. A message that lands at a sane local hour is more likely to be read than a blast timed only for your office clock. Workspace settings still govern overall daily capacity. Campaign windows and workspace limits work together. They are not two independent unlimited systems. ## Follow-ups without spam theater Most deals need more than one touch. Follow-ups should add a new angle, a clearer ask, or a lighter check-in, not the same pitch pasted three times. Omentir can keep the sequence moving until a reply or a stop condition. You decide how aggressive that motion is. When someone replies, the conversation belongs in the unified inbox so the sequence does not keep talking past a human answer. ## Safety and operator control Dashboard users and MCP operators can inspect scheduled actions and activity to see what is planned. Raising limits or widening windows should be an explicit choice, not a silent agent rewrite. LinkedIn provider rules and plan ceilings still apply. ## How to set the first campaign without burning the account Use one lead group and one send window that matches when those buyers are awake. Leave weekend sending off unless you have evidence those buyers answer then. Cap invites and messages below the workspace maximum for the first two weeks so a mistake stays small. Write the stop conditions before you launch: reply, book, or a hard follow-up count. A campaign that never stops is not persistence. It is a loop that trains people to ignore you. ## What send windows cannot fix A perfect window will not save a generic opener. Limits will not save a brand new profile that jumps to full volume on day one. Campaigns and windows are pacing tools. They assume you already chose the right people and a sentence those people can answer. ## Related - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): The broader outreach product motion. - [LinkedIn account safety](https://omentir.com/features/linkedin-account-safety.md): Limits, pacing, and account health habits. - [Human-paced outreach](https://omentir.com/blogs/human-paced-outreach.md): Why volume spikes fail. ## Frequently asked questions **Can I pause a campaign without deleting leads?** Yes. Agents and campaigns can be paused while lead groups remain available for later use. **Are send windows global or per lead?** Campaign send windows are measured in each lead's own time zone. Daily sending capacity is governed at the workspace level. **Does Omentir send at midnight if I leave it open?** Configured send windows and daily limits constrain when and how much can send. You should still set windows that match a human work pattern. # LinkedIn account safety > How Omentir protects LinkedIn outbound with daily invite and message limits, human pacing, ramp-ups, and workspace controls you can tighten. - HTML: https://omentir.com/features/linkedin-account-safety - Markdown: https://omentir.com/features/linkedin-account-safety.md Safe defaults and explicit limits so outbound stays sustainable on your own profile. ## Highlights - Human pacing - Ramp-ups for new profiles - Workspace-level caps ## Why safety is a product feature LinkedIn outbound fails in two ways: nobody replies, or the account gets restricted because volume looked robotic. Omentir is designed for the first problem without ignoring the second. Outreach runs from your profile with daily limits and human-paced sending rather than unlimited blast mode. No tool can promise zero risk. Platform rules change, and misuse still belongs to the operator. What Omentir can do is make the safe path the easy path. ## Controls you actually get Workspace settings cover invite and message ceilings, delays, and related outreach preferences. Campaigns respect those ceilings while still following send windows. New or cold accounts should ramp gradually instead of jumping to peak volume on day one. - Daily invite and message limits - Human-paced automation rather than burst sends - Send windows aligned to lead local time - Settings you can tighten when risk tolerance is low ## Warm-up and account health habits A new LinkedIn presence that suddenly sends at full capacity is a common failure mode. Warm the account with normal profile activity and a gradual outbound curve. Keep personal branding intact. Automation that turns your profile into a spam billboard destroys trust even when the account stays open. If you use the Minimum Booking Guarantee on the managed product, active-agent and eligibility rules still assume a real outbound motion, not a paused or disconnected setup. ## What you still own You own the accounts you connect, the claims in your messages, and compliance with LinkedIn rules and local law. Omentir is infrastructure for a careful motion. It is not a shield for reckless copy or purchased accounts you do not control. ## How to treat a new or recently restricted profile Warm the account with normal use before you attach a campaign: profile complete, some real conversations, no sudden invite spike. Then start below the default daily cap and raise it only after a clean week. If the profile was restricted recently, wait and keep the first batch tiny. Do not connect an account you are not allowed to use for outbound. Safety features protect pacing. They do not make a borrowed or purchased account a good idea. ## What account safety does not promise Omentir cannot guarantee that LinkedIn will never restrict a profile. Platform rules change, and people still report spam. The product keeps volume human and visible. You still own the copy, the targeting, and whether the account is yours to use. ## Related - [Campaigns and send windows](https://omentir.com/features/campaigns-and-send-windows.md): How scheduled outreach is constrained. - [LinkedIn outreach compliance](https://omentir.com/blogs/linkedin-outreach-compliance-2026.md): Legal and platform checklist style guide. - [How to warm up a LinkedIn account](https://omentir.com/blogs/how-to-warm-up-linkedin-account.md): Practical warm-up guidance. ## Frequently asked questions **Does Omentir guarantee my LinkedIn will never be restricted?** No vendor can honestly guarantee that. Omentir enforces limits and pacing to reduce risky spikes. Platform enforcement still depends on many factors outside any single app. **Can I raise limits myself?** Within product and plan constraints, workspace settings let you control sending limits. Raising them is an explicit choice and should match account age and history. **Is self-hosted Omentir unlimited?** Self-hosted installs still ship with safety-minded ceilings so a leaked token or buggy integration cannot blast without bound. You run providers and infrastructure yourself. # Lead groups and scoring > How Omentir organizes discovered prospects into lead groups, scores fit, and helps you decide who gets outreach first. - HTML: https://omentir.com/features/lead-groups-and-scoring - Markdown: https://omentir.com/features/lead-groups-and-scoring.md Keep ICP-fit buyers organized, review quality before volume, and feed the right people into campaigns. ## Highlights - Groups per motion - Scores you can explain - Review before send ## Why lead groups exist Discovery without organization becomes a pile. Lead groups hold the people an agent found so you can review, segment, and attach campaigns without mixing every experiment into one list. Separate groups by offer, geography, or motion such as classic ICP versus Steal Customers. Deleting an agent does not have to mean throwing away the people it already found. Groups and leads can outlive a single agent configuration when you keep them on purpose. ## Scoring as prioritization, not prophecy Scoring helps you rank who looks closest to the buyer you described. It is a prioritization aid, not a guarantee that the top row will buy. Use scores to decide manual review order and campaign priority. Override them when you know the market better than the model. Weak ICP definitions produce confident but wrong scores. Fix targeting and My Product when the ranking feels consistently off. ## Human review still wins early Early in a motion, skim leads before you open the fire hose. Ten minutes of review often saves a week of wrong outreach. Later, when patterns are stable, you can trust automation more on well-defined segments. ## Inspecting leads from agents MCP and REST tools can list and fetch leads, including engagement context for Steal Customers. Operators should report empty results honestly and check activity before inventing prospects that were never discovered. ## How to group and score the first lists Keep groups boring and specific: one ICP, one Steal Customers source set, one experiment. Mixing every lead into a single pile makes it impossible to tell which motion produced the reply. Name groups after the buyer or the source, not after the week you created them. Use scores as a review order, not as a send trigger. A high score still needs a human glance for obvious mismatches. If you cannot explain why a lead scored well, the score is decoration. ## What scoring will not decide for you A score is not permission to skip reading the profile. It is not a forecast of revenue. And it is not a reason to keep a bloated group you never prune. Groups and scores exist so you can send the next honest batch, then delete the rest. ## Related - [Lead finders](https://omentir.com/features/lead-finders.md): How prospects enter groups. - [Steal Customers](https://omentir.com/features/steal-customers.md): Engagement-based discovery into groups. - [LinkedIn lead scoring blog](https://omentir.com/blogs/linkedin-lead-scoring.md): Deeper scoring playbook. ## Frequently asked questions **Can one workspace have many lead groups?** Yes. Teams commonly separate groups by segment, campaign goal, or agent mode. **Does a high score mean I should always message immediately?** Not always. Score is a fit signal. Timing, offer relevance, and account safety still matter. **Where do groups feed next?** Into campaigns for connection requests, messages, and follow-ups, then into the inbox when people reply. # Open source and self-hosting Omentir > What Omentir being MIT open source means for buyers: read the code, self-host with Docker, or use the managed product with providers and support included. - HTML: https://omentir.com/features/open-source-self-hosting - Markdown: https://omentir.com/features/open-source-self-hosting.md Transparent codebase, self-host option, or managed Omentir at omentir.com. Same product family, different ops burden. ## Highlights - MIT licensed app - Docker-based setup - You bring the providers ## Open source in plain terms Omentir's application code is public on GitHub under the MIT license. You can read how outreach, agents, and safety limits work instead of trusting a black box. That transparency matters when software sends messages from your personal LinkedIn identity. Open source does not mean every third-party service is free. Self-hosting still needs your own accounts for identity, data store, LinkedIn connectivity, and model providers as documented in the repository. ## When self-hosting makes sense Self-host if you have ops capacity, want data residency under your control, or need to run inside your own infrastructure constraints. Docker-oriented setup exists for that path. You own uptime, upgrades, secrets, and provider failures. Self-host is a poor fit if you wanted a fully managed sales tool and hoped open source would remove all maintenance. Managed Omentir exists exactly so most teams do not have to run the stack. ## When the hosted product is the better buy Choose hosted Omentir when you want the same product without operating Firebase, Unipile, model keys, and deploy pipelines yourself. Pricing covers the managed experience, support expectations, and commercial packaging such as the Minimum Booking Guarantee rules where eligible. ## Trust implications Auditable code helps technical buyers. It does not replace terms of service, privacy policy, or your responsibility for how you message people. Read both the repository and the public legal pages before you put production outbound on either path. ## How to decide hosted versus self-host in a week If you want to test whether LinkedIn outbound works for your offer, use the hosted product. Self-hosting asks you to run Docker, Firebase, Unipile, and a model provider before you have learned anything about buyers. That is the right week-two or month-two project, not the first experiment. If you already know you need the code on your machines, clone the public repo, follow the self-host docs, and budget time for provider accounts. The MIT license lets you read and modify the app. It does not remove the external services the app still calls. ## What open source does not mean here It does not mean offline, free of vendor cost, or a community edition with features removed. The public repository is the same application. Credentials, customer data, and production logs stay private. Forks should use their own name and logo. ## Related - [Open source announcement](https://omentir.com/blogs/omentir-is-now-open-source.md): Why the code went public. - [Pricing](https://omentir.com/pricing.md): Managed plan options. - [GitHub repository](https://github.com/vanshyadav1408/Omentir): Source and self-host docs. ## Frequently asked questions **Is the hosted product closed source?** Hosted Omentir runs the open-source application as a managed service. You pay for operations, providers, and support packaging, not for a secret second codebase narrative. **Where is the repository?** https://github.com/vanshyadav1408/Omentir under the MIT license. **Can I mix self-host for data and hosted for convenience?** Teams usually pick one primary path. Evaluate based on who will operate LinkedIn connectivity, models, and uptime. ## Alternative pages # Gojiberry Alternatives > A Gojiberry alternative for teams that want a LinkedIn workspace they can inspect, not only a prompt-driven prospecting agent. The split is Steal Customers and MCP operators versus a brief-the-agent crawl. - HTML: https://omentir.com/comparisons/omentir-vs-gojiberry - Markdown: https://omentir.com/comparisons/omentir-vs-gojiberry.md **Verdict:** Use Gojiberry when a prompt-in, agent-out motion matches how you already work. Use Omentir when you want LinkedIn discovery, send, and replies in one workspace you can open, pause, and drive from Claude or Cursor. Prompt-led autonomous prospecting versus a LinkedIn workspace with Steal Customers and operator APIs. ## Same Google query, different machine People type Gojiberry and Omentir into the same tab because both promise an AI that finds buyers. That search is a bad reason to treat them as twins. Gojiberry's public story is an agent you brief in language: give it a website, it learns the offer, it hunts, it messages. Omentir's story is a LinkedIn workspace: My Product, a finder or Steal Customers agent, campaigns from your profile, replies in one place. If you like handing a sentence to software and walking away, Gojiberry is closer to that feeling. If you want to see the lead group, the send window, and the exact comment a prospect left on a competitor post, Omentir is closer to that feeling. The category name is shared. The object you buy is not. ## Steal Customers is not a website crawl Gojiberry-style crawlers are useful when the signal lives on the open web and you want the agent to assemble a list from a prompt. Steal Customers is narrower on purpose. You name competitor company pages and optional founder profiles. Omentir promotes people who actually commented. The first message can quote the post. That is a different lead than 'someone who matches these keywords on a site the crawler liked.' If your market has loud competitors and buyers already argue under their posts, Steal Customers is the motion to try first. If competitors are silent and the only signal is a job title on a website, a classic Omentir lead finder or a Gojiberry-style crawl may both be more honest than forcing Steal Customers. ## When Gojiberry's packaging is the better buy Keep Gojiberry in the shortlist if you already tried their flow, their pricing, and their channel mix, and the brief-the-agent model matched how your team works. Confirm current limits, LinkedIn depth, and what happens after the first reply on their site. This page will not invent a dashboard they do not ship. Gojiberry is a poor fit to 'replace' if what you actually needed was an inspectable LinkedIn send log, MCP control from Cursor, or the option to read the source. Those are Omentir reasons, not Gojiberry failures. ## Treat open source as a real criterion, or ignore it Omentir's application is public under MIT. That matters if you want to know what the agent is allowed to do, self-host later, or let a security reviewer read the code. It does not matter if you only want a hosted button that 'just runs.' Do not pick Omentir for the license if you will never open the repo. Do not skip it if the license is why you sleep. ## Comparison | Dimension | Omentir | Gojiberry | | --- | --- | --- | | How targeting starts | Written ICP in lead finders, or competitor company URLs in Steal Customers | Natural-language brief that their agent turns into a search crawl | | Signal that makes a lead interesting | Role and industry match, or a real comment on a competitor post | Whatever their crawler extracts from public web and social sources | | What you see after a reply | The thread sits next to the campaign and lead in one inbox | Confirm their current reply handling on gojiberry.ai. Do not assume a workspace inbox | | Who can operate it | You, plus Claude, ChatGPT, Cursor, or a script through MCP or REST | Their product UI and whatever connectors they list today | | Code you can read | MIT licensed application. Hosted product available | Commercial product. Licensing is on their site | ## Related - [Gojiberry vs Omentir blog](https://omentir.com/blogs/gojiberry-vs-omentir-ai-sales-agent-comparison.md): Longer design-philosophy write-up. - [Steal Customers](https://omentir.com/features/steal-customers.md): Competitor commenter discovery. - [Gojiberry alternatives guide](https://omentir.com/blogs/gojiberry-alternatives-ai-lead-sourcing.md): Broader sourcing-category reading. ## Frequently asked questions **Does Steal Customers do the same job as Gojiberry's prompt search?** No. Steal Customers starts from competitor LinkedIn posts and commenters. A prompt crawler starts from language and the public web. Use Steal Customers when buyers already engage competitor content. Use a prompt crawl or a classic ICP finder when that engagement does not exist. **Can Claude run Omentir the way I brief Gojiberry?** Claude can call Omentir tools after you connect MCP, but it still works inside your workspace rules: My Product, send windows, daily limits, and draft approval on replies. It is not a second Gojiberry. It is an operator on top of Omentir. **Where is the long Gojiberry write-up?** The blog post Gojiberry vs Omentir is the longer narrative. This page is the decision object: table, signal split, and whether you care about source code. ## Run Steal Customers on two competitors Name the two competitors your buyers already comment on. If that list is empty, start with a classic lead finder instead. # Apollo Alternatives > An Apollo alternative when stale exports are why meetings never happen. Apollo stays the contact graph. Omentir is the LinkedIn workspace you run when the last CSV never became a conversation. - HTML: https://omentir.com/comparisons/omentir-vs-apollo - Markdown: https://omentir.com/comparisons/omentir-vs-apollo.md **Verdict:** Keep Apollo if reps already live in its search and sequences. Start with Omentir if the last three exports never became conversations and LinkedIn is where your buyers actually answer. A maintained commercial database versus live LinkedIn discovery. Decide which object goes stale first in your motion. ## An export is not a pipeline Apollo earns its place when a sales org needs to search a huge commercial graph, pass rows into sequences, and treat that index as the system of record. That is a real job. It is also why founders end up with a CSV of 4,000 VPs and zero booked calls. The software did the search. Nobody finished the conversation. Omentir starts after that failure mode. A lead finder or Steal Customers agent produces people you can message on LinkedIn this week. The campaign sends from your profile. The reply lands in the same workspace. You are not buying another index. You are buying the loop that turns a match into a thread. ## What decays in Apollo that Omentir refreshes Title, email, and company size rot. Apollo's bet is that a maintained database plus enrichment stays useful enough for email and phone teams. Omentir's bet is that a living LinkedIn search, or a comment on a competitor post from this month, beats last quarter's export for founder-led motions. If your last ten meetings came from dials to Apollo mobiles, the decay argument is weaker and Apollo stays. If your last ten meetings came from LinkedIn DMs and the Apollo seats are a graveyard of unused credits, stop buying rows. ## When Apollo should stay the system of record Keep Apollo when several reps already sequence email from it, when RevOps reports off its fields, or when phone and email coverage is the actual bottleneck. Some teams will keep Apollo for the graph and run Omentir only on the LinkedIn slice. That is rational if you mark who already got a LinkedIn thread so the sequencer does not hit them the same morning. Do not rip Apollo out for a two-week test. Do not import a giant Apollo dump into Omentir and call that discovery. If you trial Omentir, let a finder build a fresh LinkedIn segment with no export at all. If that segment books nothing, you have a targeting or offer problem, not proof you needed a bigger database. ## Credits versus conversations Apollo pricing conversations usually become a fight about credits and seats. Omentir pricing is a fight about whether LinkedIn outbound is worth a workspace. Those are different budget meetings. If finance asks which tool replaces the other, answer with the last ten meetings, not with row counts. ## Comparison | Dimension | Omentir | Apollo | | --- | --- | --- | | Object you pay for | Agents, campaigns, and an inbox on your LinkedIn account | A large contact and company graph plus engagement tools around it | | How a record goes stale | The person left the role or stopped matching the finder. Discovery runs again | The row sits in a list until someone re-exports. Databases decay between exports | | Default send path | LinkedIn connection and message from the connected profile | Email and multi-channel sequences on top of the database | | What 'search' means | Find people who match an ICP or who commented on a competitor | Query a commercial index by title, tech, and firmographics | | When the purchase is wrong | You needed phone coverage and a team-wide contact system of record | You needed LinkedIn conversations and bought another unused export | ## Related - [Is Apollo's database enough?](https://omentir.com/blogs/is-apollos-database-enough-context-aware-ai-outreach.md): When a graph does not create conversations. - [Apollo alternatives guide](https://omentir.com/blogs/apollo-alternatives-programmatic-lead-sourcing.md): Longer list-database narrative. - [Lead finders](https://omentir.com/features/lead-finders.md): How Omentir discovers ICP matches. ## Frequently asked questions **Does Omentir include a 200 million contact database?** No. Omentir finds people on LinkedIn through lead finders and Steal Customers. If you need a commercial graph of emails and phones as the system of record, Apollo or a peer is still that product. **Should I dump my Apollo list into Omentir?** Not as the first experiment. Let an Omentir finder or Steal Customers agent build a live LinkedIn segment. An imported export brings Apollo's decay with it and hides whether Omentir's discovery works. **Can a team keep Apollo and add Omentir?** Yes if roles are split: Apollo for the contact graph and email sequences, Omentir for LinkedIn. Shared ownership of the same person in the same week is how you look uncoordinated. ## Run one ICP with no Apollo export If a fresh LinkedIn finder books conversations, you may not need another database seat this quarter. # Instantly Alternatives > An Instantly alternative only if meetings come from LinkedIn DMs, not from inbox placement. Instantly is warmup and rotation. Omentir cannot land mail in Gmail, and Instantly cannot sit in your profile. - HTML: https://omentir.com/comparisons/omentir-vs-instantly - Markdown: https://omentir.com/comparisons/omentir-vs-instantly.md **Verdict:** Instantly if the bottleneck is landing in Gmail at volume. Omentir if the bottleneck is a LinkedIn conversation that never started. Do not buy inbox rotation to fix a LinkedIn problem. Domain warmup and inbox rotation versus LinkedIn send windows. Pick the channel that already books, then the tool. ## Warmup is not a LinkedIn job Instantly exists because Google and Microsoft punish a single mailbox that blasts strangers. Warmup pools, extra domains, and inbox rotation are the product. That stack is real work. It is also useless if your buyer never opens cold email and will take a LinkedIn note from a founder. Omentir does not warm domains. It paces a LinkedIn account. If someone is selling you Instantly as an 'AI SDR alternative' without asking which channel books your meetings, they are selling a category, not a diagnosis. ## Instantly will not sit in your LinkedIn profile A connection request, a follow-up in the same thread, and a reply sitting next to the campaign are Omentir objects. Instantly's objects are messages in mailboxes. You can run both, but Instantly will not become your LinkedIn sender if you squint. Confirm any social features they add on their site. Do not plan a LinkedIn motion on a rumor. ## When Instantly stays and Omentir is the add-on If email already books, leave Instantly on that channel. Add Omentir only for people who never reply to email, or for a segment that lives on LinkedIn. Write different copy. The Instantly sequence and the LinkedIn campaign should not repeat the same paragraph on the same Tuesday. Instantly is the better first buy for a team that already owns domains and wants volume in the inbox. Omentir is the better first buy for a founder with one LinkedIn account and no interest in a mailbox farm. ## A week of email versus a week of DMs Score Instantly on placed mail, replies, and meetings from email. Score Omentir on accepted connections, DM replies, and meetings from LinkedIn. If you mix the lists, you will credit the wrong tool. Two weeks, two scores, one decision about which channel deserves the next dollar. ## Comparison | Dimension | Omentir | Instantly | | --- | --- | --- | | What breaks first | A LinkedIn profile that jumps volume or a message that sounds like a template | A domain that hits spam, or a single inbox that sends too much | | Infrastructure you actually configure | Connected LinkedIn account, send windows, daily invite and message caps | Domains, mailboxes, warmup pools, and rotation across inboxes | | Where leads come from | Lead finders and Steal Customers inside the product | Usually a list you bought or built somewhere else | | Founder-shaped setup | One profile, one ICP, one campaign. No mailbox farm | Fast to start email, but you still need domains and warmup to scale | | Wrong purchase | You needed primary-inbox email at agency volume | You needed LinkedIn DMs and bought another mailbox | ## Related - [Instantly alternatives guide](https://omentir.com/blogs/instantly-alternatives-autonomous-ai-salesman.md): When email-only sequencing stops being enough. - [Instantly vs Smartlead](https://omentir.com/blogs/instantly-vs-smartlead.md): The two email tools against each other. - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): How Omentir sends from your profile. ## Frequently asked questions **Does Omentir warm up email domains?** No. Domain warmup is Instantly's world. Omentir paces LinkedIn invites and messages. If spam folder placement is the problem, Instantly or a peer is still the category. **Can Instantly replace my LinkedIn outbound?** Only if your buyers actually take meetings from cold email. Instantly does not run your LinkedIn profile as a first-class workspace the way Omentir does. **Why is this page different from the Smartlead page?** Instantly is the simple, founder-and-growth-team email scaler. Smartlead is the agency and multi-client inbox router. If your pain is white-label client inboxes, read Smartlead Alternatives. If your pain is landing in Gmail without a 40-inbox agency setup, stay here. ## If last month's meetings were LinkedIn, skip another domain Connect one profile, one ICP, and look at replies. Instantly cannot manufacture a DM that never existed. # Smartlead Alternatives > A Smartlead alternative for a named LinkedIn profile, not for white-label client inboxes. Agencies that rotate mailboxes stay on Smartlead. Founders who need DMs do not buy a router. - HTML: https://omentir.com/comparisons/omentir-vs-smartlead - Markdown: https://omentir.com/comparisons/omentir-vs-smartlead.md **Verdict:** Smartlead if you are an agency routing dozens of client mailboxes. Omentir if you need LinkedIn discovery and replies on a named profile. Do not buy Smartlead to 'do LinkedIn later.' Multi-client inbox routing versus one LinkedIn workspace. Agency infrastructure is not a founder DM tool. ## Agency inbox ops versus one named profile Smartlead shows up on shortlists next to Instantly, then next to Omentir, because all three say 'outbound.' Smartlead's actual gravity is multi-inbox email for people who manage other people's domains. White-label, client workspaces, and routing rules are why agencies stay. A founder with one LinkedIn URL does not have that problem. Omentir's gravity is the opposite shape: one (or a few) LinkedIn accounts, discovery inside the product, send windows, an inbox. If you bought Smartlead hoping it would become your LinkedIn SDR, you bought a mailbox router. ## White-label is the tell If your sales deck to clients includes 'we run your inboxes,' Smartlead is in the right category and Omentir is a side tool at most, for LinkedIn on a profile the client allowed. If your sales deck is your own product and you need conversations with buyers, Smartlead's complexity is a tax. You will spend the week on DNS and warmup instead of on the sentence you send. ## When Smartlead's complexity is worth it Pay for Smartlead when you already have clients, domains, and a reason to rotate. Confirm their current agency features on smartlead.ai. This page will not list a feature they shipped last Tuesday. Skip Smartlead when you do not have a mailbox farm and the meeting you want starts with a connection request. That meeting is an Omentir problem. ## What LinkedIn replies look like after email-only scale Agencies that live in Smartlead often have a list machine and a thin LinkedIn story. The LinkedIn story is where Omentir can sit without pretending to replace inbox rotation. Run Omentir on one client who actually lives on LinkedIn. Measure whether those DMs create meetings the email pool is not getting. If they do not, keep Smartlead and stop shopping LinkedIn tools. ## Comparison | Dimension | Omentir | Smartlead | | --- | --- | --- | | Who the product is shaped for | A founder or lean team on their own LinkedIn account | An operator or agency running many client inboxes and workspaces | | Hard problem it solves | Finding people on LinkedIn and keeping the reply next to the campaign | Rotating volume across mailboxes without burning a client's domain | | Client separation | Workspace and LinkedIn account you connect. Not a white-label email farm | Client workspaces, inbox pools, and agency-style controls. Confirm on their site | | Lead source | In-product finders and Steal Customers | Lists you bring. Smartlead is the send layer | | API shape | Hosted MCP and REST for Claude, Cursor, and scripts | Email-campaign APIs. Evaluate their current docs, not this page | ## Related - [Smartlead alternatives guide](https://omentir.com/blogs/smartlead-alternatives-multi-inbox-scaling.md): When multi-inbox email is the whole job. - [Instantly vs Smartlead vs Omentir](https://omentir.com/blogs/instantly-vs-smartlead-vs-omentir-outreach-faceoff.md): Email sequencers and the LinkedIn workspace in one post. - [Unified inbox](https://omentir.com/features/unified-inbox.md): Where LinkedIn replies land in Omentir. ## Frequently asked questions **Does Omentir white-label email inboxes for agencies?** No. Omentir is not a multi-inbox email product. Agencies that need client mailbox pools should stay with Smartlead or a peer. Omentir can still run LinkedIn on a profile the client connected. **I already use Instantly. Is Smartlead the next step or Omentir?** If Instantly is too simple for client separation and routing, Smartlead is the next email step. If Instantly is fine and you are missing LinkedIn conversations, Omentir is the next channel, not a fancier mailbox. **Can Smartlead feed Omentir a list?** Treat any sync as something to build and verify. Do not assume a native pipe. A cleaner test is an Omentir finder on the same ICP, not a dump of the Smartlead list. ## If you do not manage other people's domains, do not buy a router Connect the LinkedIn account you actually use. Smartlead cannot turn a mailbox pool into a DM. # Artisan AI Alternatives > An Artisan AI alternative when you need to inspect, pause, and drive the agent from MCP. Ava is a packaged BDR. Omentir is a workspace. Autonomy you cannot open is a different risk. - HTML: https://omentir.com/comparisons/omentir-vs-artisan - Markdown: https://omentir.com/comparisons/omentir-vs-artisan.md **Verdict:** Buy Artisan when you want a packaged BDR and a live demo proves you can live with what you cannot edit. Buy Omentir when you need to read the draft, the send window, and the source of the lead before anything leaves. A packaged digital BDR versus an inspectable LinkedIn workspace. The question is what you are allowed to see and stop. ## A BDR you cannot open Artisan's pitch is Ava: a digital employee that finds, writes, sends, and books. That is attractive if you want to buy an outcome and not a workspace. It is also how teams end up unable to explain why a stranger got a message. If the demo cannot show you the lead reason, the draft, and the stop button, you are buying a black box with a friendly name. Omentir's pitch is less cinematic. You still have a workspace. You can be the operator, or Claude can, but the objects stay visible. That is slower to sell and safer to run. ## Ava versus an agent you pause in a dashboard In Omentir, a bad ICP is a finder you edit. A bad sentence is a campaign you pause. A competitor source that attracts vendors is a Steal Customers URL you delete. Those are boring controls. They are the difference between 'autonomous' and 'unsupervised.' Ask Artisan to walk a failed send in the demo: who was contacted, why, what the copy was, how you prevent the next fifty. If that walk-through is vague, the packaging is the product and the control is not. ## When a packaged BDR is the simpler buy Some teams do not want MCP, GitHub, or a lead group. They want a vendor to run outbound and send a meeting calendar. If Artisan's trial produces meetings you can defend, and you accept the closed garden, that can be the right purchase. Confirm channels, pricing, and data handling on artisan.co. This page will not invent Ava's current stack. ## Do not let 'multi-channel' hide the LinkedIn question Artisan is often shopped as multi-channel. Omentir is honest about LinkedIn first. If your meetings are LinkedIn-native, a multi-channel BDR is extra surface. If your meetings are email-native, compare Artisan to Instantly or Smartlead, not to Omentir. Category pages that mash every AI SDR into one table are how this page used to smell. It should not. ## Comparison | Dimension | Omentir | Artisan AI | | --- | --- | --- | | What you are buying | A workspace: finders, Steal Customers, campaigns, inbox, MCP | A packaged AI BDR (Ava) inside Artisan's product. Confirm scope on artisan.co | | What you can inspect | Lead group, engagement context, draft, send window, reply thread | Whatever Ava's UI exposes. Ask in the demo. Do not assume prompt-level control | | How you stop a bad motion | Pause the campaign or the agent in the dashboard the same minute | Depends on their controls. Ask how fast a human can halt sends | | Outside operators | Claude, ChatGPT, Cursor, and scripts through hosted MCP and REST | Evaluate Artisan's current API story on their site | | Source code | MIT application you can read or self-host | Commercial closed product | ## Related - [Artisan vs Omentir blog](https://omentir.com/blogs/artisan-ai-vs-omentir.md): Longer closed-garden versus workspace write-up. - [Artisan alternatives guide](https://omentir.com/blogs/artisan-ai-alternatives-multi-channel-sales-agents.md): Category reading around packaged BDRs. - [Agent API and MCP](https://omentir.com/features/agent-api-and-mcp.md): How operators control Omentir. ## Frequently asked questions **Can I edit Ava's prompts the way I edit Omentir campaigns?** Assume no until the Artisan demo shows you the exact controls. Omentir is built so a human can change targeting, copy, and send windows. A packaged BDR may hide that on purpose. **Does Artisan speak MCP the way Omentir does?** Omentir's hosted MCP server is a first-class operator path. Treat Artisan's automation as whatever they document today. Do not plan a Claude-operates-Ava architecture from this page. **Where is the longer Artisan comparison?** The Artisan AI vs Omentir blog and the Artisan alternatives guide. This page is the inspectability test, not a reprint of those posts. ## If you cannot explain the last send, do not buy more autonomy Open a workspace where the lead, the draft, and the pause button are in the same place. # 11x AI Alternatives > An 11x AI alternative for a founder-scale LinkedIn workspace, not an enterprise digital worker. Alice is a staffing story. Omentir is a dashboard a reviewer can read. - HTML: https://omentir.com/comparisons/omentir-vs-11x - Markdown: https://omentir.com/comparisons/omentir-vs-11x.md **Verdict:** Evaluate 11x when a sales org wants a vendor digital worker and the contract matches the team size. Choose Omentir when a founder needs LinkedIn outbound they can pause, inspect, and run from tools they already use. Enterprise digital workers versus a founder-scale LinkedIn workspace. Size, override rights, and proof of value, not logo heat. ## Digital worker versus workspace 11x's public language is digital workers: Alice for outbound, other workers around the GTM motion. That is a staffing story. You are hiring software that looks like a teammate. Omentir's language is a workspace. You are buying a place where finders, campaigns, and replies live, and where an operator is optional. If your board wants 'we hired Alice,' 11x is the narrative they already understand. If your board wants 'we can see every LinkedIn send and we can stop it,' Omentir is the narrative. Do not let the AI SDR label erase that split. ## Price and headcount mismatch Public commentary often puts 11x in a much higher starting band than a $49 founder plan. Confirm live numbers on their site. The point is not the exact dollar. The point is whether a five-person company is buying an enterprise worker program they will not operate. Omentir is sized for a person who still reads replies at night. 11x is sized for a team that wants to delegate a function. Buying the larger story too early is how you get a beautiful worker and a founder who still cannot explain yesterday's sends. ## What 'autonomous' hides Autonomy without an override list is just speed. In a trial, write down who can change the ICP, who can stop sends, and how a bad message is pulled back. If 11x's answer is a success team and a quarterly review, that can be fine for an enterprise. It is not fine for a founder who needs the stop button today. ## Proof of value that is not a keynote Ignore funding slides. Give 11x one ICP and a time box if you are in their buyer range. Give Omentir one LinkedIn account and the same ICP. Count meetings, count surprises, count hours in cleanup. The tool that produced a meeting you cannot explain lost, even if the meeting happened. ## Comparison | Dimension | Omentir | 11x AI | | --- | --- | --- | | Buyer size the product assumes | Solo founder through a small outbound team | Teams buying a digital-worker program. Confirm pricing on 11x.ai | | Named worker versus workspace | You name the agent. The workspace is still yours | Alice and other workers are the product story. Confirm current roles on their site | | Who may change targeting | Anyone with the dashboard, or an operator with a token you can revoke | Ask who can override the worker mid-flight. Write the answer down in the trial | | Proof that is not a logo | A two-week ICP on your own LinkedIn account, replies you can read | A paid proof of value against your ICP, not a keynote clip | | Reading the implementation | Public MIT repository | Commercial. Contracts and a security review, not a GitHub clone | ## Related - [11x Alice alternatives](https://omentir.com/blogs/11x-ai-alice-alternatives-autonomous-sales-agents.md): Longer digital-worker category piece. - [11x vs Gojiberry](https://omentir.com/blogs/11x-ai-vs-gojiberry.md): Two AI SDR shapes that are not Omentir. - [Open source self-hosting](https://omentir.com/features/open-source-self-hosting.md): When reading the code is part of the buy. ## Frequently asked questions **Is Omentir a cheaper Alice?** No. Alice is 11x's digital worker product. Omentir is a LinkedIn workspace with agents you control. A lower price does not make it the same object. If you want the worker narrative, evaluate 11x on that. If you want the workspace, evaluate Omentir on that. **We are three people. Should we still take an 11x meeting?** Only if you already know you want enterprise worker packaging and the contract will not swallow the quarter. Most three-person teams should run Omentir on one profile first. You can always buy a worker later. **Where do I read about Alice versus other agents?** The 11x AI Alice alternatives blog and the 11x vs Gojiberry post. This page is the size-and-override test against Omentir only. ## If you still read every reply yourself, buy a workspace Connect one LinkedIn account. A digital worker program can wait until someone else is on the inbox. # Lusha Alternatives > A Lusha alternative only if the job is the follow-up, not the lookup. Lusha is the tab that reveals a number. Omentir is the workspace that sends the LinkedIn thread. - HTML: https://omentir.com/comparisons/omentir-vs-lusha - Markdown: https://omentir.com/comparisons/omentir-vs-lusha.md **Verdict:** Keep Lusha if the motion is 'I am on a LinkedIn profile and I need a phone or email right now.' Buy Omentir if the motion is 'this person should get a message and I need to see if they answered.' Chrome-style contact lookup versus LinkedIn execution. A number in a sidebar is not a thread. ## The tab where you look up a number Lusha's classic job is a lookup. A rep is on a LinkedIn profile, they want a direct dial or email, they spend a credit, they leave. That workflow is old and still valid for phone-led teams. It is also why Lusha gets compared to Omentir: both appear when someone is staring at LinkedIn and wants pipeline. Omentir does not try to win the credit-for-a-mobile fight. It tries to win the 'this profile becomes a conversation' fight. If your team measures success in numbers captured, Lusha is in the right store aisle. If your team measures success in replies, you are in the wrong aisle when you buy more credits. ## A lookup tool never sends the follow-up The graveyard next to every Lusha workspace is a spreadsheet of good numbers and no second touch. That is not Lusha's bug. Follow-up was never the product. Omentir's campaign and inbox exist because the second touch is the product. Buying Lusha to fix follow-up is like buying a phone book to fix your script. ## Credits are not conversations Lusha pricing arguments become credit math. Omentir pricing arguments become 'did anyone answer on LinkedIn.' If finance wants one vendor to do both lookup and send, they are asking for a chimera. Some teams keep Lusha for the call block and Omentir for the LinkedIn block. That only works if the same person is not dialed and DMed with the same pitch the same morning. ## When Lusha plus Omentir is not redundant Phone team uses Lusha. LinkedIn motion uses Omentir. Shared suppression so a booked call is not also in a connection queue. If you do not have a phone team, skip Lusha and stop shopping data extensions. If you do not have a LinkedIn motion, skip Omentir and stop calling it an alternative to a lookup tool. ## Comparison | Dimension | Omentir | Lusha | | --- | --- | --- | | The surface you live in | Omentir dashboard: finders, campaigns, inbox | A LinkedIn or CRM sidebar that returns a phone or email. Confirm the extension on lusha.com | | What you hold after a click | A lead in a group, then a sent thread if you run a campaign | A contact field. Sending is someone else's job | | How you pay | A workspace plan for LinkedIn outbound | Credits or seats for lookups. Confirm current packing on their site | | What happens after you have the number | The product's job is already the next message on LinkedIn | You leave Lusha and enter a dialer, sequencer, or spreadsheet | | Failure you will actually feel | A weak opener or a burned LinkedIn account | A wrong number, a burned credit, a list that never got called | ## Related - [Lusha vs Omentir blog](https://omentir.com/blogs/lusha-vs-omentir-database-vs-active-outreach.md): Database lookup versus active outreach. - [Lusha alternatives for startups](https://omentir.com/blogs/lusha-alternatives-lead-sourcing-tech-startups.md): Broader data-tool reading. - [Lead finders](https://omentir.com/features/lead-finders.md): Discovery that does not start with a credit. ## Frequently asked questions **Does Omentir have a Chrome extension that reveals mobiles?** No. Omentir is not a contact-reveal extension. If the job is a number on a LinkedIn profile, Lusha or a peer is still that job. **We already burn Lusha credits. Will Omentir use those contacts?** Do not start by importing the credit graveyard. Run a finder or Steal Customers on a live ICP. If you later want to suppress people you already called, treat that as a list-hygiene task, not as Omentir's discovery. **Is this the same decision as Cognism?** No. Lusha is the lookup-and-credit motion, often next to LinkedIn in the browser. Cognism is the EMEA compliance and verified-mobile platform. If GDPR and European dials are the buying trigger, read Cognism Alternatives. ## If the number was never called, stop buying numbers Put the next hour into a LinkedIn campaign on people you can actually message. # Clay Alternatives > A Clay alternative when the waterfall never becomes a LinkedIn send. Clay is the table. Omentir is the path from ICP to a DM. If columns are the product, stay in Clay. - HTML: https://omentir.com/comparisons/omentir-vs-clay - Markdown: https://omentir.com/comparisons/omentir-vs-clay.md **Verdict:** Stay in Clay if custom enrichment across many vendors is the advantage. Move to Omentir if the table is beautiful and last month still had no LinkedIn conversations. A multi-provider enrichment canvas versus time-to-first LinkedIn send. Columns are not campaigns. ## A waterfall is not a send Clay is loved because it lets a sharp operator cascade Hunter, then another vendor, then an AI cell, then a webhook. That is a craft. It is also how a week disappears into credit logs while nobody messaged a human. Omentir refuses that craft on purpose. You describe a buyer or a competitor. The product finds people and sends on LinkedIn. If your advantage is a proprietary enrichment graph, Clay is the workshop. If your advantage is supposed to be conversations, the workshop is a stall. ## When the table is the product Keep Clay when RevOps is the buyer, when you must mix five paid providers, and when the output is a file other systems consume. Confirm current providers and credit rules on clay.com. Omentir will not reproduce that graph. Leave Clay in week one of a founder test. Do not build a waterfall to decide if LinkedIn outbound works. Run a finder. Add Clay later if you can name a field that actually changes who you contact. ## Time to first DM is the only founder metric Ask how long until a real person gets a LinkedIn message you would be willing to put your name on. In Omentir that clock starts when My Product and a finder exist. In Clay that clock starts when the table is done and a send tool is wired. If nobody on the team wants to be the Clay person, the table will rot and you will still have no DMs. ## Columns Omentir will not replace Technographic waterfalls, custom scoring formulas, and 'if provider A is empty then provider B' are Clay work. Do not expect Omentir to grow those columns. Expect Omentir to make them optional for a LinkedIn-only motion. If you combine the two, one system owns who gets messaged. Dual ownership of the same row is how you double-send. ## Comparison | Dimension | Omentir | Clay | | --- | --- | --- | | Interface you stare at | Agents, lead groups, campaigns, inbox | A table of rows, columns, and provider waterfall cells | | Who enjoys the product | A founder who wants a send this week | An operator who likes chaining APIs and credits across vendors | | Time to first LinkedIn DM | Finder or Steal Customers, then a campaign. Hours if My Product is filled | Depends on the table, the send tool you bolt on, and who maintains it | | What a column is for | Omentir does not ask you to design columns. It asks you to name a buyer | Each column is a provider, formula, or AI step you must keep alive | | What it will not become | A fifty-provider enrichment IDE | A LinkedIn inbox and send window product by itself | ## Related - [Clay vs Apollo](https://omentir.com/blogs/clay-vs-apollo-data-sourcing-comparison.md): Database versus waterfall, not this page. - [Clay vs Gojiberry](https://omentir.com/blogs/clay-vs-gojiberry-enrichment-vs-autonomous-prospecting.md): Enrichment versus prompt prospecting. - [AI LinkedIn outreach](https://omentir.com/features/ai-linkedin-outreach.md): The send loop Clay does not include. ## Frequently asked questions **Does Omentir include a Clay-style waterfall?** No. Omentir finds LinkedIn prospects and runs outreach. If you need a multi-provider enrichment canvas, Clay is still that canvas. **Can Clay push rows into Omentir automatically?** Do not assume a native sync. Verify any webhook or CSV path against current product behavior. A cleaner first test is an Omentir finder on the same ICP, so you learn whether the table was required. **Clay vs Apollo is a different page. Why?** Apollo is a database you search. Clay is a table you build. Omentir is a send loop. The Clay page is about plumbing versus DMs. The Apollo page is about stale exports versus live discovery. ## If the table has no send date, the table is not outbound Name one buyer. Run a finder. See a thread before you add another provider column. # Cognism Alternatives > A Cognism alternative only when European meetings start as LinkedIn DMs. Cognism is compliant mobiles. Omentir is the thread. GDPR coverage does not write the message. - HTML: https://omentir.com/comparisons/omentir-vs-cognism - Markdown: https://omentir.com/comparisons/omentir-vs-cognism.md **Verdict:** Buy Cognism if European dials and suppression are the bottleneck and legal will not sign off without that category. Buy Omentir if last quarter's EU meetings started in LinkedIn DMs and the data contract did not create them. EMEA compliance and verified mobiles versus LinkedIn threads. Spend the next euro where last quarter's meetings started. ## The first euro in Europe is a legal euro Cognism is on this site because EU outbound is not a US credit-card problem. Teams buy Cognism when they want verified mobiles, Diamond Data style claims, and a vendor that speaks GDPR in the security review. Confirm today's packaging on cognism.com. This page will not certify your lawful basis. Omentir will not pass that review for you. It will run LinkedIn outreach you are still responsible for. If counsel will not let you message EU buyers without a data vendor in the stack, Cognism stays in the stack. If counsel is fine with LinkedIn outreach you can defend, and the missing piece is the conversation, Cognism is the wrong first euro. ## Dials versus DMs in Europe Phone-led EMEA teams live and die on mobile quality and suppression. That is Cognism's home. LinkedIn-led EMEA teams live and die on whether a founder note gets a reply. That is Omentir's home. A Cognism export does not write the note. An Omentir campaign does not place a compliant dial. ## Compliance data does not write the message A clean, suppressed, verified list that nobody messages is still a failed quarter. A LinkedIn campaign that ignores local rules is a worse failure. Buy the control that matches the hole. If last quarter's EU meetings were almost all LinkedIn, more Cognism seats will not invent more DMs. If last quarter's meetings were almost all dials, more Omentir agents will not invent more phones. ## A meeting-origin test for EU teams Open the last ten booked meetings that involved a European buyer. Tag each one: LinkedIn DM, email, inbound, or dial. If DMs win, trial Omentir on one EU ICP and leave Cognism as-is. If dials win, trial Cognism coverage on that ICP and leave Omentir alone. If the tags are mixed, split the list so the same person is not in both motions the same week. ## Comparison | Dimension | Omentir | Cognism | | --- | --- | --- | | Why European teams shop it | Buyers on LinkedIn who will take a DM from a founder | Compliant coverage, verified mobiles, and Do Not Call style suppression. Confirm on cognism.com | | Primary artifact | A LinkedIn thread attached to a campaign | A contact record a caller or email sequencer can use | | What legal actually asks | You still own lawful basis for outreach. Omentir is not your DPO | Sales intelligence vendors in this category sell process and suppression. Ask for the current story | | Execution included | Yes. Finders, send windows, inbox, MCP | Data first. The dialer or sequencer is usually another tool | | Wrong euro | You needed verified EU mobiles and a calling floor | You needed LinkedIn conversations and bought another unused data seat | ## Related - [Cognism vs Apollo](https://omentir.com/blogs/cognism-vs-apollo.md): Two data platforms, not this LinkedIn question. - [Cognism alternatives guide](https://omentir.com/blogs/cognism-alternatives-contact-data-providers.md): Contact-data category reading. - [LinkedIn outreach compliance](https://omentir.com/blogs/linkedin-outreach-compliance-2026.md): Rules that still apply after you pick a tool. ## Frequently asked questions **Does Omentir make my EU outbound GDPR-safe?** No. You still need a lawful basis, records, and counsel. Omentir is software for LinkedIn outreach. Cognism is a data vendor in the compliance conversation. Neither one is your lawyer. **We need European mobiles. Is Omentir a Cognism substitute?** No. Omentir does not sell a verified EU mobile graph. If mobiles are the buying trigger, Cognism or a peer is still the category. If LinkedIn threads are the buying trigger, stay on this page. **How is this different from the Lusha page?** Lusha is the browser lookup and credit motion, often for mixed markets. Cognism is the EMEA compliance and verified-mobile platform. Shop Lusha when the pain is 'reveal this profile.' Shop Cognism when the pain is 'European dials legal will accept.' ## Tag last quarter's EU meetings before you renew data If they started as LinkedIn DMs, run one Omentir ICP. If they started as dials, Cognism is still the aisle. ## Integration pages # Claude integration > Connect Claude to Omentir with a custom MCP connector. Create lead finders or Steal Customers agents, inspect leads, and operate LinkedIn outbound from chat without sharing your LinkedIn password. - HTML: https://omentir.com/integrations/claude - Markdown: https://omentir.com/integrations/claude.md Add the Omentir MCP connector in Claude, approve workspace access, and run discovery from chat. ## Highlights - Custom MCP connector - No API key in Claude - Workspace approval required ## Setup 1. **Finish Omentir setup.** Create an account, connect LinkedIn, and fill My Product so tools have something true to say. 2. **Add the connector in Claude.** Settings, Connectors, custom connector. Use https://omentir.com/api/agent/v1/mcp. 3. **Approve the workspace.** Sign in on Omentir and allow Connect workspace. Enable tools in the conversation if Claude asks. 4. **Read context first.** Ask Claude to run get_context and get_stats, then list agents, before it creates anything. ## What Claude can do with Omentir After Claude is connected to the Omentir MCP server, it can use Omentir tools to read workspace readiness, update My Product, create classic lead finders or Steal Customers agents, list leads with engagement context, check activity and the planned send schedule, and work with existing conversations under draft approval rules. Claude does not receive your LinkedIn password. It operates through Omentir's workspace tools, with the same daily safety limits and campaign rules as the dashboard. ## Setup steps Create an Omentir account, connect LinkedIn, and complete My Product. In Claude, open Settings, go to Connectors, and add a custom connector with the Omentir MCP URL. Sign in on Omentir when prompted and approve Connect workspace. Enable Omentir tools in the conversation if Claude asks. - MCP URL: https://omentir.com/api/agent/v1/mcp - No API key required for the chat connector path - Approve workspace access on Omentir before tools work - Optional: paste the operator prompt from /for-agents as the first message ## Good first requests Ask Claude to run get_context and get_stats, confirm My Product is complete, list existing agents before creating new ones, and only create a lead finder or Steal Customers agent after you explicitly approve the targeting. Never ask it to broaden ICP silently or reply to threads without showing you the draft. ## Limits and responsibilities You remain responsible for LinkedIn rules, the accounts you connect, and the offers you send. Claude is an operator interface. Omentir enforces product limits; it does not replace your judgment about who to contact or what to claim. ## A first Claude session that stays safe Start with a question Claude can answer from tools: is My Product complete, how many agents exist, what is scheduled to send. Then give it one job, such as creating a lead finder for a written ICP, and make it show the targeting before it saves. Do not ask Claude to invent a broader market or to reply to threads without showing the draft. The connector is powerful because it can change a real workspace. Treat it like a teammate with admin access, not like a chatbot that only talks. ## When Claude is the wrong operator If you need scripts, CI, or a coding agent in the repo, use an API key with Cursor, Claude Code, or REST. Claude's connector path is for conversational operation. It is a poor fit if you want headless jobs or if you are not willing to approve what it creates. ## Related - [MCP Server](https://omentir.com/mcp-server.md): Full connector setup and tool groups. - [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and workflow. - [Agent API and MCP feature](https://omentir.com/features/agent-api-and-mcp.md): Product overview of operator access. - [ChatGPT integration](https://omentir.com/integrations/chatgpt.md): Same MCP idea for ChatGPT. ## Frequently asked questions **Do I need an Omentir API key for Claude?** Not for the custom MCP connector flow. Claude uses the connector URL and workspace approval. API keys are for coding agents and scripts. **Can Claude create Steal Customers agents?** Yes, after My Product is complete and LinkedIn is connected. Provide competitor LinkedIn company URLs and optional founder or employee profile URLs. **Where is the full tool list?** See the MCP Server page for the human-readable tool catalog, and agents.md for the machine guide. # ChatGPT integration > Connect ChatGPT to Omentir with a custom MCP connector. Configure LinkedIn lead discovery, Steal Customers agents, and campaign inspection from chat with workspace approval. - HTML: https://omentir.com/integrations/chatgpt - Markdown: https://omentir.com/integrations/chatgpt.md Point ChatGPT at the Omentir MCP endpoint, approve access, and operate outbound tools from conversation. ## Highlights - Custom MCP connector - Workspace-scoped tools - Same safety limits as the app ## Setup 1. **Prepare the workspace.** Account, LinkedIn, and My Product need to be done before ChatGPT can do useful work. 2. **Add the Omentir connector.** In ChatGPT, add a custom connector pointed at https://omentir.com/api/agent/v1/mcp. 3. **Approve access.** Complete the Omentir sign-in and Connect workspace step, then enable tools in the chat. 4. **Inspect before you create.** Ask ChatGPT to read context and list agents. Only then create a finder or Steal Customers agent. ## Why connect ChatGPT to Omentir ChatGPT is useful as an operator when it can call real tools instead of only drafting copy you paste elsewhere. Connected to Omentir, it can configure product context, create agents, inspect leads, and check send schedules while Omentir keeps LinkedIn credentials and safety limits in the workspace. ## How to connect Finish Omentir setup: account, LinkedIn connection, My Product. In ChatGPT, add a custom connector with the hosted MCP URL. Complete the Omentir sign-in and Connect workspace approval. Enable tools in the chat when prompted, then ask ChatGPT to read context before creating anything. - Connector URL: https://omentir.com/api/agent/v1/mcp - Use workspace approval for chat apps - Prefer list_agents before create_agent to avoid duplicates - Keep reply tools limited to existing threads with draft approval ## Practical uses Typical sessions: refresh ICP language in My Product, spin up a classic lead finder for a new segment, start a Steal Customers agent against a short competitor list, or audit why discovery returned empty results by checking activity tools before inventing leads. ## What this is not for Do not treat ChatGPT as a place to store LinkedIn passwords or to bypass daily limits. Do not paste API tokens into chats you share. For scripts and local coding agents, create a revocable key on the API keys page instead of reusing a chat connector session. ## A first ChatGPT session worth keeping Have ChatGPT explain the workspace back to you: product summary, connected account, existing agents. If that summary is wrong, fix My Product before you let it create outreach. A confident draft from a wrong profile wastes a week. When you do create an agent, give ChatGPT the ICP or competitor URLs in the same message. Do not ask it to guess the market. Guessing is how you end up messaging the wrong titles at full pace. ## When to skip ChatGPT and use a key instead ChatGPT is the right surface if you already live in that chat app and want to operate Omentir in language. If you want a coding agent to call REST from a repo, or you need a token you can revoke per script, create an API key and leave ChatGPT out of that path. ## Related - [MCP Server](https://omentir.com/mcp-server.md): Human setup and FAQs. - [Claude integration](https://omentir.com/integrations/claude.md): Same pattern for Claude. - [For AI Agents](https://omentir.com/for-agents.md): Shared operator prompt. - [MCP LinkedIn outreach blog](https://omentir.com/blogs/mcp-linkedin-outreach.md): Longer narrative on MCP outbound. ## Frequently asked questions **Is an API key required for ChatGPT?** The custom connector path uses Omentir workspace approval. Bearer API keys are for non-chat clients such as scripts and some coding agents. **Can ChatGPT send LinkedIn messages directly?** ChatGPT operates Omentir tools. Outreach still runs through your connected LinkedIn account inside Omentir under campaign and safety settings. **Where do I learn the tool names?** The MCP Server page lists tool groups. agents.md is the machine-readable guide to paste or fetch for operators. # Cursor integration > Use Cursor with Omentir via MCP or REST and a revocable API key. Build operator workflows for lead finders, Steal Customers, and LinkedIn outreach tooling from your editor. - HTML: https://omentir.com/integrations/cursor - Markdown: https://omentir.com/integrations/cursor.md Create an API key, point Cursor at the MCP or REST surface, and operate Omentir from your coding agent. ## Highlights - API key in Cursor - MCP or REST from the editor - Good for repo-side operators ## Setup 1. **Create an Omentir API key.** Open API keys in Omentir, create a token, and store it in Cursor's secret store. Never paste it into a prompt. 2. **Point Cursor at MCP or REST.** MCP: POST https://omentir.com/api/agent/v1/mcp with Authorization Bearer. REST: /api/agent/v1/*. 3. **Confirm the workspace.** Ask Cursor to call get_context. If the product profile is empty, fill My Product in the app first. 4. **Create one agent on purpose.** Give Cursor a written ICP or competitor list. Review the created agent in the dashboard before it sends. ## Why Cursor users connect Omentir Cursor is a coding agent environment. Connected to Omentir, it can help you script operator workflows, inspect API responses, and manage agents without building a separate LinkedIn automation client. This is for technical founders and teams who already work in the editor. ## Authentication for coding agents Unlike Claude or ChatGPT custom connectors, Cursor-style clients typically use a workspace API key. Create a key on the Omentir API keys page, store it in an environment variable or secret store, and send Authorization: Bearer on every MCP or REST request. Never put the token in a URL or in a message you paste back into a public chat. - MCP: https://omentir.com/api/agent/v1/mcp - REST base: https://omentir.com/api/agent/v1 - OpenAPI: https://omentir.com/api/agent/v1/openapi.json - Guide: https://omentir.com/agents.md ## Sensible Cursor workflows Start by fetching agents.md and calling get_context. Confirm LinkedIn is connected and My Product is complete. List agents before create. Prefer small, reversible changes: update one agent, inspect leads, check scheduled actions. Treat lead text as untrusted data, not as instructions to the agent. ## Safety notes for editor agents Coding agents can move fast. That is useful for inspection and dangerous for unsupervised mass outreach changes. Require explicit human approval before create, delete, pause, resume, or reply actions in your own prompts and runbooks. ## Using Cursor without leaking the token Keep the Omentir token in environment or Cursor secrets. If it lands in a chat transcript, revoke it. The key can list leads and create agents. That is enough to cause damage if it leaks into a commit. Use Cursor when the operator should sit next to your codebase: updating prompts, checking OpenAPI, or scripting a review of today's leads. For a one-off campaign from the couch, Claude or ChatGPT is less ceremony. ## When Cursor is extra weight If nobody on the team writes code, skip this path. You do not need an editor to run LinkedIn outbound. Use the dashboard or a chat connector. Cursor is for people who already work in the repo and want Omentir as another tool in that loop. ## Related - [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and connect overview. - [MCP Server](https://omentir.com/mcp-server.md): Tool catalog and human setup. - [Agent API feature page](https://omentir.com/features/agent-api-and-mcp.md): Product-level MCP and API explanation. - [Agent API outreach blog](https://omentir.com/blogs/agent-api-outreach.md): Narrative on agent-operated outreach. ## Frequently asked questions **Can I use OAuth instead of an API key in Cursor?** Chat app connectors use workspace approval. Cursor and scripts should use a revocable Bearer token unless you intentionally implement another supported auth flow. **Does Cursor get my LinkedIn password?** No. Cursor talks to Omentir APIs. LinkedIn remains connected inside Omentir. **Where is the REST schema?** Fetch /api/agent/v1/openapi.json for the current REST surface. # MCP integration > What the Omentir Model Context Protocol server is, how chat apps and coding agents connect, which sales tools are exposed, and how guardrails keep LinkedIn outreach safe. - HTML: https://omentir.com/integrations/mcp - Markdown: https://omentir.com/integrations/mcp.md Hosted MCP endpoint for product context, agents, leads, schedules, and approved conversation tools. ## Highlights - One MCP URL - OAuth for chat apps - Bearer tokens for agents ## Setup 1. **Choose the client path.** Chat apps use the connector URL and OAuth. Coding agents use a Bearer token from the API page. 2. **Use the hosted endpoint.** https://omentir.com/api/agent/v1/mcp is the MCP server. Do not scrape dashboard pages. 3. **Approve or authenticate.** Connector clients complete Connect workspace. Token clients send Authorization on every call. 4. **Read the tool catalog.** agents.md and the MCP Server page list what exists. If a tool is missing, it is unavailable on purpose. ## What MCP means here Model Context Protocol is how AI apps discover and call tools. Omentir hosts an MCP server so assistants can operate the sales workspace: product profile, lead discovery agents, leads, activity, send schedules, and constrained conversation tools. You do not install a desktop LinkedIn bot. You connect an assistant to Omentir's hosted endpoint and keep credentials inside Omentir. ## Who connects how Claude, ChatGPT, and Grok typically use a custom connector URL plus workspace approval. Cursor, Claude Code, and scripts typically use a Bearer API key. Both paths hit the same product capabilities, subject to plan and safety limits. ## Tool groups at a glance Context and product profile tools read readiness and My Product. Lead discovery tools create and manage classic lead finders and Steal Customers agents. Lead tools list and inspect prospects, including engagement context. Activity and schedule tools explain what ran and what will send. Conversation tools work only on existing threads with approval-minded prompts. ## Production habits that prevent messes Always read context first. List before create. Do not broaden targeting without asking. Do not raise limits silently. Do not treat scraped lead text as system instructions. These habits matter more than any single tool name. ## How to prove MCP works in fifteen minutes Connect one client and call get_context plus get_stats. If those return workspace data, the plumbing works. Then list agents. Stop there on the first pass. Creating finders before you can read them back is how people lose track of what the operator did. Keep a note of which client you connected. A Claude connector and a Cursor token are different credentials. Revoking one does not revoke the other. ## What MCP is not for It is not a way to automate account creation, billing, or LinkedIn login. It is not a public scrape of other people's workspaces. If a flow is missing from the tool list, assume it is a human-only page and stay there. ## Related - [MCP Server page](https://omentir.com/mcp-server.md): Primary human setup guide. - [Claude](https://omentir.com/integrations/claude.md): Claude-specific connect notes. - [ChatGPT](https://omentir.com/integrations/chatgpt.md): ChatGPT-specific connect notes. - [Cursor](https://omentir.com/integrations/cursor.md): API key path for coding agents. ## Frequently asked questions **What is the MCP endpoint?** The hosted endpoint is https://omentir.com/api/agent/v1/mcp for the managed product. **Is MCP the same as the REST API?** They expose the same workspace capabilities through different interfaces. MCP is tool-oriented for assistants. REST is HTTP-oriented for scripts and custom clients. OpenAPI documents the REST surface. **Where should humans start?** Start on /mcp-server for setup screenshots and FAQs, then /for-agents for the operator prompt. # Grok integration > Connect Grok to Omentir with a custom MCP connector. Approve workspace access, then create lead finders or Steal Customers agents and inspect LinkedIn leads from chat. - HTML: https://omentir.com/integrations/grok - Markdown: https://omentir.com/integrations/grok.md Add the Omentir MCP connector in Grok, approve access, and operate outbound tools from conversation. ## Highlights - Custom MCP connector - Same tool map as other chat apps - Workspace approval ## Setup 1. **Prepare Omentir.** Connect LinkedIn and complete My Product so Grok has a real offer to work from. 2. **Add the custom connector.** In Grok, add a connector with https://omentir.com/api/agent/v1/mcp. 3. **Approve Connect workspace.** Sign in to Omentir when prompted and allow the workspace. Enable tools in the conversation. 4. **Start with read tools.** Ask Grok for context and stats, then list agents, before you let it create a finder. ## What Grok can do with Omentir Connected through MCP, Grok can call Omentir tools for workspace context, My Product, classic lead finders, Steal Customers agents, lead inspection, activity, scheduled sends, and approved work on existing conversations. LinkedIn credentials stay inside Omentir. This is the same hosted MCP surface Claude and ChatGPT use for chat-style connectors, with workspace approval instead of pasting a long-lived token into the chat transcript. ## Setup path Finish Omentir basics: account, LinkedIn connection, My Product. In Grok, add a custom connector with the Omentir MCP URL. Sign in on Omentir and approve Connect workspace. Enable tools in the conversation if prompted. - MCP URL: https://omentir.com/api/agent/v1/mcp - No API key required for the chat connector path - List agents before create_agent to avoid duplicates - Optional operator prompt from /for-agents as the first message ## Good first session Ask Grok to run get_context and get_stats, confirm readiness, then propose a single agent configuration for your approval. Prefer one clear segment over a broad autonomous expansion of titles and geographies. ## Limits Daily send limits and campaign rules still apply. Grok is an operator interface, not a bypass around safety settings. You remain responsible for what gets sent from your LinkedIn account. ## A first Grok session that does not invent targeting Give Grok the same written ICP you would give a teammate. If you only say 'find me SaaS founders,' you will get a wide, noisy list. If you name the role, the company size, and the trigger, the agent it creates will be easier to review. Have Grok show the agent configuration before you leave it running. Confirm send windows and daily limits in the dashboard after. Chat operators are fast. The LinkedIn account still pays for a sloppy config. ## When another client is a better fit If your team already standardized on Claude or ChatGPT, do not add Grok just to have another connector. One operator you actually watch is better than three you forget. Use Grok when that is already the chat app where the work happens. ## Related - [MCP Server](https://omentir.com/mcp-server.md): Human setup and tool groups. - [Claude integration](https://omentir.com/integrations/claude.md): Same connector pattern on Claude. - [For AI Agents](https://omentir.com/for-agents.md): Shared operator prompt. ## Frequently asked questions **Is Grok support the same as Claude?** Chat apps share the custom MCP connector pattern. UI labels differ by product. The Omentir endpoint and workspace approval model are the same idea. **Can Grok create Steal Customers agents?** Yes, after My Product is complete and LinkedIn is connected, using competitor LinkedIn URLs and optional founder or employee profiles. **Where is the full tool list?** See /mcp-server for humans and /agents.md for machine-readable guidance. # OpenClaw integration > Use OpenClaw with Omentir over MCP or REST and a revocable API key for LinkedIn lead discovery, Steal Customers, and outreach operations from a custom agent stack. - HTML: https://omentir.com/integrations/openclaw - Markdown: https://omentir.com/integrations/openclaw.md Point OpenClaw at Omentir's agent APIs with a Bearer token and run sales operator workflows under guardrails. ## Highlights - Local operator - Bearer token - Same REST and MCP contracts ## Setup 1. **Create a token.** Make an Omentir API key and put it in OpenClaw's secret storage, never in a skill file you commit. 2. **Call MCP or REST.** Use the hosted MCP endpoint or the REST routes under /api/agent/v1 with Authorization Bearer. 3. **Paste the operator prompt.** The /for-agents prompt tells OpenClaw to read context first and not to invent billing or signup flows. 4. **Watch the first writes.** List agents after any create or update. Confirm the dashboard matches what OpenClaw claims it did. ## Why OpenClaw users connect Omentir OpenClaw-style agent stacks want tools that do real work. Omentir supplies hosted MCP and REST tools for product context, lead finders, Steal Customers, leads, schedules, and constrained conversation actions so your agent is not inventing a LinkedIn client from scratch. ## Auth model Create a workspace API key on the Omentir API keys page. Store it as a secret. Send Authorization: Bearer on MCP or REST calls. Never embed the token in public prompts or git commits. Rotate keys if a runner environment is compromised. - MCP: https://omentir.com/api/agent/v1/mcp - REST: https://omentir.com/api/agent/v1 - OpenAPI: https://omentir.com/api/agent/v1/openapi.json - Guide: https://omentir.com/agents.md ## Recommended runbooks Fetch agents.md first. Call get_context. Refuse to create agents until the human confirms targeting. On empty lead lists, check list_activity before claiming discovery worked. Reply tools only on existing threads with draft approval. ## Risks unique to autonomous runners Background agents can loop. Cap retries, require approvals for create and delete, and log every outbound-affecting tool call. Autonomy without an audit trail is how silent targeting drift happens. ## Running OpenClaw against a live workspace OpenClaw is useful when you want an operator that already lives on your machine. That also means a leaked token is a leaked workspace. Rotate the key if the machine is shared, and start with read-only habits: context, stats, lead lists. When you let it create a finder, give it a file or message with the ICP. Do not ask it to crawl your whole disk for 'ideas.' The workspace should change because you asked, not because the agent got bored. ## When OpenClaw is the wrong layer If you just want to talk to Omentir from a hosted chat app, use Claude, ChatGPT, or Grok. OpenClaw adds a local runtime you have to operate. That is worth it for people who already run it. It is extra surface for everyone else. ## Related - [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and connect overview. - [OpenClaw LinkedIn leads](https://omentir.com/blogs/openclaw-linkedin-leads.md): Narrative on OpenClaw lead workflows. - [OpenClaw outreach flows](https://omentir.com/blogs/openclaw-outreach-flows.md): Outreach-oriented OpenClaw reading. - [REST API integration](https://omentir.com/integrations/rest-api.md): HTTP surface details. ## Frequently asked questions **Is OpenClaw a first-party Omentir product?** No. OpenClaw is an external agent stack. Omentir exposes APIs that OpenClaw can call like any other operator client. **Chat connector or API key?** Use a revocable API key for custom runners. Chat connector OAuth is for consumer chat apps with that UI. **Related reading?** See OpenClaw LinkedIn leads and OpenClaw outreach flows on the blog, plus /for-agents for the operator prompt. # REST Agent API integration > How to use Omentir's REST Agent API under /api/agent/v1 for product profile, agents, leads, activity, schedules, and conversations with Bearer auth. - HTML: https://omentir.com/integrations/rest-api - Markdown: https://omentir.com/integrations/rest-api.md HTTP API for scripts and custom backends that need the same workspace powers as MCP tools. ## Highlights - OpenAPI documented - Bearer tokens - Workspace-scoped routes ## Setup 1. **Create a token on the API page.** Keys are never accepted in URLs. Send Authorization: Bearer on every request. 2. **Read OpenAPI.** https://omentir.com/api/agent/v1/openapi.json is the contract. Do not guess path names. 3. **Start with GET context.** If get_context fails, fix auth before you write a create-agent script. 4. **Create with an explicit body.** Pass the ICP or Steal Customers URLs you actually want. Log the returned id and open it in the app. ## What the REST Agent API is The Agent API is the HTTP interface for workspace-scoped sales operations. It covers context, stats, product profile, agents, groups, leads, activity, scheduled actions, settings, and conversations. MCP exposes the same capabilities as tools for assistants that prefer tool calling. OpenAPI lives at /api/agent/v1/openapi.json so clients can generate types and see current paths without scraping docs by hand. ## Authentication Create a revocable key in the workspace API keys UI. Send Authorization: Bearer on every request. Treat the key like a password. Scope is the workspace, not a single agent, so protect it accordingly. ## Common integration flows Readiness check: context plus stats. Segment launch: update product profile if needed, create agent, poll leads and activity. Ops dashboard: list scheduled actions and conversations. Always prefer read-before-write and human approval for destructive changes. - Base path: /api/agent/v1 - Machine guide: /agents.md - Human MCP story: /mcp-server - Capability map: /agent.json ## What not to build Do not use the API to create Omentir accounts or buy subscriptions. Do not scrape the dashboard HTML for data the API already returns. Do not store LinkedIn passwords in your integration. Omentir holds the LinkedIn connection. ## A first REST script that you can trust Write the smallest script: authenticate, print context, list agents, exit. Check it twice. Then add one write. If a create call returns success, open that agent in the dashboard the same minute. Scripts that only look at their own JSON drift from the product. Store the token in the environment. Revoke it when the script is done or when someone leaves the team. There is no reason for a weekend experiment key to live forever. ## When REST is more than you need If you are not writing code, use the dashboard or a chat connector. REST is for people who want Omentir inside an existing system. It is a worse first experience than clicking through the app if you only need one campaign this week. ## Related - [Agent API feature page](https://omentir.com/features/agent-api-and-mcp.md): Product overview of operator access. - [OpenAPI schema](https://omentir.com/api/agent/v1/openapi.json): Machine-readable REST schema. - [Cursor integration](https://omentir.com/integrations/cursor.md): Coding agent path using the same auth model. - [Agent API outreach blog](https://omentir.com/blogs/agent-api-outreach.md): Narrative on API-led outreach. ## Frequently asked questions **MCP or REST?** Use MCP when the client is an assistant with tool calling. Use REST when you own the HTTP client in a script, backend, or automation runner. Capabilities align. **Is there rate limiting?** Yes. Product and infrastructure limits apply. Design for retries with backoff and avoid tight poll loops. **Where do I see the schema?** Fetch https://omentir.com/api/agent/v1/openapi.json for the current REST surface. # Claude Code integration > Connect Claude Code to Omentir with a Bearer API key over MCP or REST. Configure lead finders, inspect leads, and operate LinkedIn outbound from the terminal agent workflow. - HTML: https://omentir.com/integrations/claude-code - Markdown: https://omentir.com/integrations/claude-code.md Terminal-native operator path: API key, agents.md, and the same workspace tools as other coding agents. ## Highlights - API key - Works in the terminal - Same MCP and REST tools ## Setup 1. **Create and store a token.** Generate an Omentir API key and keep it in the environment Claude Code already uses for secrets. 2. **Call the hosted MCP server.** POST https://omentir.com/api/agent/v1/mcp with the Bearer token, or use the REST routes. 3. **Read before write.** Have Claude Code fetch context and list agents from the repo session before it creates a finder. 4. **Review in the dashboard.** After any write, open Omentir and confirm the agent, limits, and targeting match the session. ## Why Claude Code users connect Omentir Claude Code is built for agentic work in a repo and terminal. Connected to Omentir, it can operate sales workspace tools while you keep reviewing diffs, logs, and approvals in a developer-native loop. ## Setup Create an Omentir API key. Configure Claude Code's MCP or HTTP tooling with the MCP endpoint or REST base URL and Bearer auth. Point the agent at agents.md so it learns guardrails before it creates agents. - Prefer environment variables for secrets - Start with get_context and get_stats - Require explicit approval for create, delete, and reply - Do not commit API keys to the repository ## Useful workflows Refresh My Product from a README or landing page draft you trust, spin up a single test lead finder, dump lead JSON for offline review, or audit scheduled actions before a campaign weekend. Keep production changes small and reversible. ## Claude Code versus Claude chat connector Claude's chat product can use a custom connector with workspace approval. Claude Code typically uses a key like other coding agents. Pick the path that matches the client. Do not reuse chat OAuth assumptions in a headless runner. ## Using Claude Code next to the product repo Claude Code is a good operator when the same session is already editing prompts, docs, or scripts. Ask it to compare My Product with what the landing page claims. If those disagree, fix the profile before you let it launch outreach. Do not let a long coding session casually 'also spin up a campaign.' Creating agents should be a named request, the same way merging a pull request is a named request. ## When to stay in the browser If you are not in a terminal already, the hosted dashboard or a chat connector is faster. Claude Code earns its place when the work is happening in a repo. It is a slow way to click 'create campaign' if that is the only job. ## Related - [Cursor integration](https://omentir.com/integrations/cursor.md): Similar coding-agent auth pattern. - [REST API](https://omentir.com/integrations/rest-api.md): HTTP details and OpenAPI. - [Claude chat integration](https://omentir.com/integrations/claude.md): Connector path for Claude chat apps. - [MCP Server](https://omentir.com/mcp-server.md): Tool catalog and human FAQs. ## Frequently asked questions **Can Claude Code use the same MCP URL as Claude chat?** The hosted MCP endpoint is the same product surface. Auth differs: chat connectors use workspace approval UI, Claude Code should use a revocable API key unless you implement another supported flow. **Will Claude Code send LinkedIn messages by itself?** Only through Omentir tools under your campaign and safety settings. Your prompts should still require approval for replies and agent lifecycle changes. **Where is the operator prompt?** https://omentir.com/for-agents contains a paste-ready operator prompt you can adapt for Claude Code instructions. ## Blog library ## AI Tools to Use Before You Start Outbound URL: https://omentir.com/blogs/ai-saas-ready-before-outbound Markdown: https://omentir.com/blogs/ai-saas-ready-before-outbound.md Category: Guides Published: August 12, 2026 A simple list of AI tools to use while you build a SaaS: coding, code review, landing pages, App Store screenshots, payments, and analytics, before you start outbound. ## Omentir is now open source URL: https://omentir.com/blogs/omentir-is-now-open-source Markdown: https://omentir.com/blogs/omentir-is-now-open-source.md Category: Updates Published: July 26, 2026 Until today, Omentir's code was private. Now the full source code is public on GitHub under the MIT license. Here is why we did it and what it means for you. ## Introducing Omentir v2 URL: https://omentir.com/blogs/introducing-omentir-v2 Markdown: https://omentir.com/blogs/introducing-omentir-v2.md Category: Updates Published: July 6, 2026 Omentir v2 introduces simpler pricing, Agent API, and connectors for AI agents to make outreach dead simple. ## Crafting a LinkedIn Profile That Doubles Your Outbound Acceptances URL: https://omentir.com/blogs/crafting-a-linkedin-profile-that-doubles-your-outbound-acceptances Markdown: https://omentir.com/blogs/crafting-a-linkedin-profile-that-doubles-your-outbound-acceptances.md Category: Guides Published: July 5, 2026 How to optimize your LinkedIn profile photo, headline, banner, and featured section to act as a high-converting landing page for cold leads. ## LinkedIn Outbound vs. Cold Emailing: Which Works Best in 2026? URL: https://omentir.com/blogs/linkedin-outbound-vs-cold-emailing-which-works-best-in-2026 Markdown: https://omentir.com/blogs/linkedin-outbound-vs-cold-emailing-which-works-best-in-2026.md Category: Case Studies Published: July 4, 2026 An honest, data-backed comparison of LinkedIn social outreach versus traditional cold emailing for modern B2B lead generation campaigns. ## The B2B Outreach Copywriting Framework That Gets Replies URL: https://omentir.com/blogs/the-b2b-outreach-copywriting-framework-that-gets-replies Markdown: https://omentir.com/blogs/the-b2b-outreach-copywriting-framework-that-gets-replies.md Category: Copywriting Published: July 3, 2026 Ditch the boring paragraphs. Discover the three-step psychological copywriting framework built specifically for B2B cold outreach campaigns. ## How to Nurture LinkedIn Leads Who Say 'Not Right Now' URL: https://omentir.com/blogs/how-to-nurture-linkedin-leads-who-say-not-right-now Markdown: https://omentir.com/blogs/how-to-nurture-linkedin-leads-who-say-not-right-now.md Category: Outreach Published: July 1, 2026 A step-by-step nurturing system to keep cold outreach prospects warm over 3, 6, or 12 months until they are ready to buy. ## The Founder's Playbook: Booking Early Demos on LinkedIn URL: https://omentir.com/blogs/the-founders-playbook-booking-early-demos-on-linkedin Markdown: https://omentir.com/blogs/the-founders-playbook-booking-early-demos-on-linkedin.md Category: Guides Published: June 30, 2026 A comprehensive guide for early-stage B2B SaaS founders to get their first 10-20 customers using highly targeted LinkedIn outreach campaigns. ## Personalization at Scale: Writing Custom LinkedIn Notes in 2026 URL: https://omentir.com/blogs/personalization-at-scale-writing-custom-linkedin-notes-in-2026 Markdown: https://omentir.com/blogs/personalization-at-scale-writing-custom-linkedin-notes-in-2026.md Category: Copywriting Published: June 29, 2026 How to personalize hundreds of LinkedIn connection request notes and follow-ups without sacrificing speed or sounding like a robot. ## 7 Common LinkedIn Outreach Mistakes and How to Fix Them URL: https://omentir.com/blogs/7-common-linkedin-outreach-mistakes-and-how-to-fix-them Markdown: https://omentir.com/blogs/7-common-linkedin-outreach-mistakes-and-how-to-fix-them.md Category: Playbooks Published: June 28, 2026 Are your outreach campaigns falling flat? Learn the 7 most common LinkedIn cold messaging mistakes and how to fix them to double your reply rates. ## The Complete Guide to LinkedIn InMail Best Practices URL: https://omentir.com/blogs/the-complete-guide-to-linkedin-inmail-best-practices Markdown: https://omentir.com/blogs/the-complete-guide-to-linkedin-inmail-best-practices.md Category: Playbooks Published: June 27, 2026 A tactical guide to leveraging paid InMail credits effectively. Learn standard structures that drive high reply rates from open profiles. ## The Art of the LinkedIn Follow-Up: How to Re-Engage Ghosted Leads URL: https://omentir.com/blogs/the-art-of-the-linkedin-follow-up-how-to-re-engage-ghosted-leads Markdown: https://omentir.com/blogs/the-art-of-the-linkedin-follow-up-how-to-re-engage-ghosted-leads.md Category: Outreach Published: June 25, 2026 How to politely follow up on LinkedIn after a prospect goes quiet, without sounding desperate or pushy. ## LinkedIn Outreach for Founders: The 15-Minute Daily Routine URL: https://omentir.com/blogs/linkedin-outreach-for-founders-the-15-minute-daily-routine Markdown: https://omentir.com/blogs/linkedin-outreach-for-founders-the-15-minute-daily-routine.md Category: Guides Published: June 24, 2026 A high-efficiency daily sales workflow designed specifically for solo founders and technical operators with limited time. ## How to Write a Conversational Pitch for High-Value B2B Buyers URL: https://omentir.com/blogs/how-to-write-a-conversational-pitch-for-high-value-b2b-buyers Markdown: https://omentir.com/blogs/how-to-write-a-conversational-pitch-for-high-value-b2b-buyers.md Category: Copywriting Published: June 23, 2026 Ditch the jargon. Learn how to draft warm, conversational messages that connect with C-level executives and enterprise buyers. ## How to Use LinkedIn to Book 5 B2B Demos Every Week URL: https://omentir.com/blogs/how-to-use-linkedin-to-book-5-b2b-demos-every-week Markdown: https://omentir.com/blogs/how-to-use-linkedin-to-book-5-b2b-demos-every-week.md Category: Guides Published: June 22, 2026 A comprehensive operational blueprint for B2B founders and SDRs to build a reliable outreach routine that books demos consistently. ## How to Pitch a B2B SaaS on LinkedIn Without Being Spammy URL: https://omentir.com/blogs/how-to-pitch-a-b2b-saas-on-linkedin-without-being-spammy Markdown: https://omentir.com/blogs/how-to-pitch-a-b2b-saas-on-linkedin-without-being-spammy.md Category: Playbooks Published: June 20, 2026 Stop sending pitches inside connection requests. Discover conversational, soft-landing value offers that turn into live product demos. ## How to Build a High-Converting B2B Sales Sequence on LinkedIn URL: https://omentir.com/blogs/how-to-build-a-high-converting-b2b-sales-sequence-on-linkedin Markdown: https://omentir.com/blogs/how-to-build-a-high-converting-b2b-sales-sequence-on-linkedin.md Category: Automation Published: June 19, 2026 Step-by-step blueprints to design multi-touch LinkedIn outbound sequences that nurture prospects and scale bookings safely. ## Hooking the Prospect: LinkedIn Intro Lines That Drive 40%+ Reply Rates URL: https://omentir.com/blogs/hooking-the-prospect-linkedin-intro-lines-that-drive-40-percent-reply-rates Markdown: https://omentir.com/blogs/hooking-the-prospect-linkedin-intro-lines-that-drive-40-percent-reply-rates.md Category: Copywriting Published: June 18, 2026 Master the art of the opening line. Avoid generic templates and discover personalized hook structures that spark conversations. ## 5 Social Selling Strategies to Warm Up LinkedIn Leads Before Outreach URL: https://omentir.com/blogs/5-social-selling-strategies-to-warm-up-linkedin-leads-before-outreach Markdown: https://omentir.com/blogs/5-social-selling-strategies-to-warm-up-linkedin-leads-before-outreach.md Category: Outreach Published: June 17, 2026 Learn how to build authority and warm up cold LinkedIn leads with social selling strategies before executing outbound outreach. ## Outbound Sales for Solo Founders: A Practical Guide URL: https://omentir.com/blogs/outbound-sales-for-solo-founders-a-practical-guide Markdown: https://omentir.com/blogs/outbound-sales-for-solo-founders-a-practical-guide.md Category: Guides Published: June 16, 2026 A zero-fluff outbound sales framework tailored for solo B2B founders to validate markets, find early customers, and manage pipeline. ## The Exact LinkedIn Sequence We Used to Book $10k in MRR URL: https://omentir.com/blogs/the-exact-linkedin-sequence-we-used-to-book-10k-in-mrr Markdown: https://omentir.com/blogs/the-exact-linkedin-sequence-we-used-to-book-10k-in-mrr.md Category: Case Studies Published: June 14, 2026 A detailed breakdown of the exact multi-step LinkedIn outreach strategy, copywriting, and daily cadence used to generate $10k in MRR. ## How to Write a LinkedIn Connection Request That Gets Accepted URL: https://omentir.com/blogs/how-to-write-a-linkedin-connection-request-that-gets-accepted Markdown: https://omentir.com/blogs/how-to-write-a-linkedin-connection-request-that-gets-accepted.md Category: Outreach Published: June 13, 2026 LinkedIn lets free accounts add a 200-character note to only three invitations a month. Here is how to use that space, and when a blank request is better. ## 10 LinkedIn Cold Message Templates That Actually Book Demos URL: https://omentir.com/blogs/10-linkedin-cold-message-templates-that-actually-book-demos Markdown: https://omentir.com/blogs/10-linkedin-cold-message-templates-that-actually-book-demos.md Category: Playbooks Published: June 12, 2026 Explore 10 proven, low-friction LinkedIn cold message templates designed for B2B sales teams and founders to start conversations and book meetings. ## The Modern Outbound Stack: Integrating Lead Scrapers, Enrichment, and AI SDRs URL: https://omentir.com/blogs/modern-outbound-stack-lead-scrapers-enrichment-ai-sdrs Markdown: https://omentir.com/blogs/modern-outbound-stack-lead-scrapers-enrichment-ai-sdrs.md Category: Automation Published: June 11, 2026 An architectural blueprint of the modern B2B sales development stack. Learn how to combine scraper tools, waterfall systems, and autonomous AI salesman. ## Why High-Ticket B2B Outreach Needs the Human-in-the-Loop AI Salesman URL: https://omentir.com/blogs/why-high-ticket-outreach-needs-human-in-the-loop-ai-salesman Markdown: https://omentir.com/blogs/why-high-ticket-outreach-needs-human-in-the-loop-ai-salesman.md Category: Outreach Published: June 10, 2026 Why fully autonomous engines fail in enterprise campaigns. Discover the power of combining high-efficiency AI agents with human-in-the-loop validation. ## How to Move from Dumb Sequences to Autonomous AI Sales Conversations URL: https://omentir.com/blogs/move-from-dumb-sequences-to-autonomous-ai-sales-conversations Markdown: https://omentir.com/blogs/move-from-dumb-sequences-to-autonomous-ai-sales-conversations.md Category: Outreach Published: June 8, 2026 Ditch linear drip emails. Learn how to design dynamic, context-aware conversational sequences that adapt based on prospect replies and social selling signals. ## Finding the Right AI Salesman: The 2026 Buyer's Guide for Growth Teams URL: https://omentir.com/blogs/finding-the-right-ai-salesman-2026-buyers-guide Markdown: https://omentir.com/blogs/finding-the-right-ai-salesman-2026-buyers-guide.md Category: Guides Published: June 7, 2026 A complete buyer's guide to evaluate autonomous sales agents. Discover key criteria for multi-channel support, safety throttles, and copywriting quality. ## Clay vs. Gojiberry: Sourcing-Heavy Enrichment vs. Autonomous Prospecting URL: https://omentir.com/blogs/clay-vs-gojiberry-enrichment-vs-autonomous-prospecting Markdown: https://omentir.com/blogs/clay-vs-gojiberry-enrichment-vs-autonomous-prospecting.md Category: Comparisons Published: June 6, 2026 Compare Clay's data waterfall enrichment with Gojiberry's autonomous prospecting, including when a unified workflow is useful. ## Is Apollo's Database Enough? Why You Need a Context-Aware AI Outreach Layer URL: https://omentir.com/blogs/is-apollos-database-enough-context-aware-ai-outreach Markdown: https://omentir.com/blogs/is-apollos-database-enough-context-aware-ai-outreach.md Category: Outreach Published: June 5, 2026 Why raw business profiles are no longer enough. Learn how context-aware AI active sourcing outperforms static database searches in 2026 B2B outbound. ## Why Modern B2B Founders are Replacing Traditional SDRs with AI Salesman URL: https://omentir.com/blogs/why-founders-replace-sdrs-with-ai-salesman Markdown: https://omentir.com/blogs/why-founders-replace-sdrs-with-ai-salesman.md Category: Outreach Published: June 3, 2026 Analyze the economics and performance differences of autonomous AI sales agents compared to traditional human SDR teams for high-growth tech startups. ## Autonomous Lead Generation: The Shift from CRM to AI Sales Agents URL: https://omentir.com/blogs/autonomous-lead-generation-shift-crm-to-ai-sales-agents Markdown: https://omentir.com/blogs/autonomous-lead-generation-shift-crm-to-ai-sales-agents.md Category: Outreach Published: June 2, 2026 Understand the transition from static CRMs and sequences to autonomous AI sales agents that discover, nurture, and qualify B2B leads independently. ## Instantly.ai vs. Smartlead vs. Omentir: A Three-Way Outreach Comparison URL: https://omentir.com/blogs/instantly-vs-smartlead-vs-omentir-outreach-faceoff Markdown: https://omentir.com/blogs/instantly-vs-smartlead-vs-omentir-outreach-faceoff.md Category: Comparisons Published: June 1, 2026 An honest head-to-head comparison of cold email sequencers, multi-inbox tools, and multi-channel outbound workflows. ## Beyond Database Scraping: How AI Salesman Qualify Leads Autonomously URL: https://omentir.com/blogs/beyond-database-scraping-how-ai-salesman-qualify-leads Markdown: https://omentir.com/blogs/beyond-database-scraping-how-ai-salesman-qualify-leads.md Category: Outreach Published: May 31, 2026 Moving beyond directory scrapers. Learn how modern AI salesman analyze corporate sites, job boards, and social signals to qualify B2B leads autonomously. ## Cognism Alternatives: High-Quality Contact Data Providers for Global Sales URL: https://omentir.com/blogs/cognism-alternatives-contact-data-providers Markdown: https://omentir.com/blogs/cognism-alternatives-contact-data-providers.md Category: Comparisons Published: May 30, 2026 Review the top Cognism alternatives for global lead generation. Contrast static databases with active, real-time context-aware AI outbound sales systems. ## Lusha Alternatives: The Best Lead Sourcing Tools for Tech Startups URL: https://omentir.com/blogs/lusha-alternatives-lead-sourcing-tech-startups Markdown: https://omentir.com/blogs/lusha-alternatives-lead-sourcing-tech-startups.md Category: Comparisons Published: May 28, 2026 A complete breakdown of Lusha alternatives for early-stage tech teams. Compare legacy scrapers with autonomous, context-aware AI sourcing systems. ## Smartlead Alternatives: Multi-Inbox Scaling for Modern B2B Campaigns URL: https://omentir.com/blogs/smartlead-alternatives-multi-inbox-scaling Markdown: https://omentir.com/blogs/smartlead-alternatives-multi-inbox-scaling.md Category: Comparisons Published: May 27, 2026 A technical review of Smartlead alternatives for cold email scaling. Compare multi-inbox deliverability setups with unified multi-channel autonomous salesman. ## Artisan AI Alternatives: Multi-Channel Sales Agent Options URL: https://omentir.com/blogs/artisan-ai-alternatives-multi-channel-sales-agents Markdown: https://omentir.com/blogs/artisan-ai-alternatives-multi-channel-sales-agents.md Category: Comparisons Published: May 26, 2026 Explore alternatives to Artisan AI (Ava). Compare single-channel email outreach tools with unified multi-channel sales agents that engage leads on LinkedIn and email. ## Gojiberry Alternatives: The Best AI-Powered Lead Sourcing Platforms URL: https://omentir.com/blogs/gojiberry-alternatives-ai-lead-sourcing Markdown: https://omentir.com/blogs/gojiberry-alternatives-ai-lead-sourcing.md Category: Comparisons Published: May 25, 2026 A detailed guide to Gojiberry alternatives, including lead databases, enrichment platforms, email tools, and unified multi-channel workflows. ## Lusha vs. Omentir: Moving Beyond Static Databases to Active Outreach URL: https://omentir.com/blogs/lusha-vs-omentir-database-vs-active-outreach Markdown: https://omentir.com/blogs/lusha-vs-omentir-database-vs-active-outreach.md Category: Comparisons Published: May 24, 2026 Contrast mobile data scraping with active B2B customer discovery. Understand why high-growth startups are moving from static list providers to autonomous outreach. ## Clay vs. Apollo.io: Which Data Sourcing Engine Scales Best? URL: https://omentir.com/blogs/clay-vs-apollo-data-sourcing-comparison Markdown: https://omentir.com/blogs/clay-vs-apollo-data-sourcing-comparison.md Category: Comparisons Published: May 22, 2026 Compare Clay's programmatic waterfall enrichment cascade with Apollo.io's direct database sourcing, including when broader outreach workflows matter. ## 11x.ai (Alice) Alternatives: Evaluating Autonomous Sales Agents in 2026 URL: https://omentir.com/blogs/11x-ai-alice-alternatives-autonomous-sales-agents Markdown: https://omentir.com/blogs/11x-ai-alice-alternatives-autonomous-sales-agents.md Category: Comparisons Published: May 21, 2026 An analytical review of autonomous sales agents. Discover the limits of legacy single-channel sequencers and the rise of multi-channel AI salesman. ## Apollo.io alternatives: Find the best alternatives to Apollo.io URL: https://omentir.com/blogs/apollo-alternatives-programmatic-lead-sourcing Markdown: https://omentir.com/blogs/apollo-alternatives-programmatic-lead-sourcing.md Category: Comparisons Published: May 20, 2026 Compare Apollo.io with database tools, enrichment platforms, and autonomous SDR workflows so you can choose the right replacement. ## Gojiberry vs. Omentir: Comparison of two popular outreach tools URL: https://omentir.com/blogs/gojiberry-vs-omentir-ai-sales-agent-comparison Markdown: https://omentir.com/blogs/gojiberry-vs-omentir-ai-sales-agent-comparison.md Category: Comparisons Published: May 19, 2026 Compare Gojiberry and Omentir head-to-head. Analyze their approach to B2B customer discovery, lead scoring, and multi-channel social selling campaigns. ## Instantly.ai alternatives: Find the best alternatives to Instantly AI URL: https://omentir.com/blogs/instantly-alternatives-autonomous-ai-salesman Markdown: https://omentir.com/blogs/instantly-alternatives-autonomous-ai-salesman.md Category: Comparisons Published: May 17, 2026 An in-depth, technical comparison of cold email sequence tools like Instantly.ai versus modern, multi-channel autonomous AI salesman. ## ChatGPT LinkedIn Leads: A Practical Founder Workflow URL: https://omentir.com/blogs/chatgpt-linkedin-leads Markdown: https://omentir.com/blogs/chatgpt-linkedin-leads.md Category: Guides Published: May 16, 2026 Use ChatGPT to turn LinkedIn research into a focused, qualified lead list without scraping blindly or writing generic outreach. ## OpenClaw LinkedIn Leads: How to Run Prospecting Through an Agent URL: https://omentir.com/blogs/openclaw-linkedin-leads Markdown: https://omentir.com/blogs/openclaw-linkedin-leads.md Category: Automation Published: May 15, 2026 A practical workflow for using OpenClaw as the operator layer for LinkedIn lead discovery, qualification, and safe outreach handoff. ## MCP LinkedIn Outreach: A Safe Agent Workflow for B2B Sales URL: https://omentir.com/blogs/mcp-linkedin-outreach Markdown: https://omentir.com/blogs/mcp-linkedin-outreach.md Category: Automation Published: May 14, 2026 Learn how MCP agents can configure Omentir lead finders, search scored prospects, inspect exact leads, and work with existing replies. ## AI Outreach Playbook: Build a Campaign That Still Feels Human URL: https://omentir.com/blogs/ai-outreach-playbook Markdown: https://omentir.com/blogs/ai-outreach-playbook.md Category: Playbooks Published: May 13, 2026 A practical AI outreach playbook for founders who want better prospecting, sharper messages, and safe follow-up without generic automation. ## AI Sales Pitch Guide: Turn Product Facts Into Buyer-Relevant Copy URL: https://omentir.com/blogs/ai-sales-pitch-guide Markdown: https://omentir.com/blogs/ai-sales-pitch-guide.md Category: Copywriting Published: May 11, 2026 A practical guide to using AI to create sharper B2B sales pitches without fake claims, generic benefits, or over-automated messages. ## LinkedIn Demo Booking: Turn Interested Replies Into Scheduled Calls URL: https://omentir.com/blogs/linkedin-demo-booking Markdown: https://omentir.com/blogs/linkedin-demo-booking.md Category: Playbooks Published: May 10, 2026 A practical guide to turning warm LinkedIn replies into qualified demo bookings without rushing the buyer, dropping calendar links too early, or losing momentum. ## Founder LinkedIn Demos: Turn Sales Calls Into Product Learning URL: https://omentir.com/blogs/founder-linkedin-demos Markdown: https://omentir.com/blogs/founder-linkedin-demos.md Category: Guides Published: May 9, 2026 A founder-led guide to running LinkedIn-sourced demos that reveal real buyer pain, create trust, and move qualified prospects toward the next step. ## AI Lead Qualification: Score Better Prospects Before Outreach URL: https://omentir.com/blogs/ai-lead-qualification Markdown: https://omentir.com/blogs/ai-lead-qualification.md Category: Guides Published: May 8, 2026 A practical AI lead qualification framework for scoring B2B prospects, rejecting weak-fit accounts, and making every outreach decision auditable. ## OpenClaw vs ChatGPT for Sales: Which Agent Belongs Where? URL: https://omentir.com/blogs/openclaw-vs-chatgpt-sales Markdown: https://omentir.com/blogs/openclaw-vs-chatgpt-sales.md Category: Comparisons Published: May 7, 2026 A practical comparison of OpenClaw and ChatGPT for B2B sales workflows, including prospecting, outreach drafting, agent operations, and safe LinkedIn execution. ## AI Follow-Up Playbook: Keep Sales Conversations Moving URL: https://omentir.com/blogs/ai-follow-up-playbook Markdown: https://omentir.com/blogs/ai-follow-up-playbook.md Category: Playbooks Published: May 5, 2026 A practical AI follow-up playbook for deciding when to follow up, what to say, when to pause, and how to keep outreach human-paced. ## AI LinkedIn Prospecting: Build a Signal-Led Lead Workflow URL: https://omentir.com/blogs/ai-linkedin-prospecting Markdown: https://omentir.com/blogs/ai-linkedin-prospecting.md Category: Guides Published: May 4, 2026 A practical guide to AI LinkedIn prospecting, from signal discovery and batch review to ranked lead queues that are ready for human-paced outreach. ## LinkedIn Pitch Templates: 7 Signals-Based B2B Message Patterns URL: https://omentir.com/blogs/linkedin-pitch-templates Markdown: https://omentir.com/blogs/linkedin-pitch-templates.md Category: Copywriting Published: May 3, 2026 Use these LinkedIn pitch templates to turn real buyer signals into concise, relevant B2B messages without sounding automated or pushy. ## ChatGPT Sales Messages: Write Better First Touches With Context URL: https://omentir.com/blogs/chatgpt-sales-messages Markdown: https://omentir.com/blogs/chatgpt-sales-messages.md Category: Copywriting Published: May 2, 2026 A practical guide to using ChatGPT for B2B sales messages that are specific, short, safe to send, and grounded in real buyer context. ## AI Connection Requests: Write LinkedIn Invites That Earn Trust URL: https://omentir.com/blogs/ai-connection-requests Markdown: https://omentir.com/blogs/ai-connection-requests.md Category: Outreach Published: May 1, 2026 A practical guide to using AI for LinkedIn connection requests without pitching too early, over-personalizing, or risking account trust. ## Cold LinkedIn Outreach: A Practical B2B Workflow That Still Feels Human URL: https://omentir.com/blogs/cold-linkedin-outreach Markdown: https://omentir.com/blogs/cold-linkedin-outreach.md Category: Outreach Published: April 29, 2026 A practical guide to cold LinkedIn outreach for B2B founders and lean sales teams, from targeting and connection requests to first messages and follow-up. ## Warm LinkedIn Leads: How to Turn Intent Signals Into Sales Conversations URL: https://omentir.com/blogs/warm-linkedin-leads Markdown: https://omentir.com/blogs/warm-linkedin-leads.md Category: Guides Published: April 28, 2026 A practical guide to handling warm LinkedIn leads: how to spot real intent, choose the next move, respond quickly, and avoid over-automating promising conversations. ## LinkedIn Lead Scoring: A Practical Rubric for Better Outreach URL: https://omentir.com/blogs/linkedin-lead-scoring Markdown: https://omentir.com/blogs/linkedin-lead-scoring.md Category: Guides Published: April 27, 2026 A practical LinkedIn lead scoring rubric for ranking prospects by fit, signal strength, relationship context, timing, and the next best outreach action. ## Personalized Sales Pitches: Build Messages Buyers Can Actually Answer URL: https://omentir.com/blogs/personalized-sales-pitches Markdown: https://omentir.com/blogs/personalized-sales-pitches.md Category: Copywriting Published: April 26, 2026 A practical framework for writing personalized sales pitches from account context, buyer role, timing, proof, and one clear next step. ## B2B Lead Gen with AI: Build a Context-Aware Outbound Machine URL: https://omentir.com/blogs/b2b-lead-gen-with-ai Markdown: https://omentir.com/blogs/b2b-lead-gen-with-ai.md Category: Guides Published: April 24, 2026 Ditch generic databases and bulk sequences. Discover how to design a modern B2B lead generation workflow combining AI intent signals, programmatic enrichment, and safe LinkedIn outreach. ## AI SDR LinkedIn Playbook: How to Operationalize Autonomous Outbound URL: https://omentir.com/blogs/ai-sdr-linkedin-playbook Markdown: https://omentir.com/blogs/ai-sdr-linkedin-playbook.md Category: Playbooks Published: April 23, 2026 Stop wondering what an AI SDR actually does. Discover the operational routine, delegation frameworks, and daily pacing safety rules to run an autonomous sales agent on LinkedIn. ## LinkedIn Outreach Funnel: Optimize Every Stage of Outbound Sales URL: https://omentir.com/blogs/linkedin-outreach-funnel Markdown: https://omentir.com/blogs/linkedin-outreach-funnel.md Category: Playbooks Published: April 22, 2026 Stop guessing where your sales pipeline is leaking. Master the LinkedIn outreach funnel with concrete benchmarks, conversion metrics, and tactical optimization tips. ## Sales Outreach Automation: Build a Modern Outbound Machine URL: https://omentir.com/blogs/sales-outreach-automation Markdown: https://omentir.com/blogs/sales-outreach-automation.md Category: Automation Published: April 21, 2026 Stop running manual spreadsheets and messaging campaigns. Learn how to build an automated sales outreach system that integrates intent data, respects pacing limits, and drives demos. ## Human-Paced Outreach: Why Safe Pacing Beats Bulk Spam URL: https://omentir.com/blogs/human-paced-outreach Markdown: https://omentir.com/blogs/human-paced-outreach.md Category: Guides Published: April 20, 2026 Discover the technical and psychological reasons why warm, paced sales outreach outperforms bulk messaging, and how to configure safe limits for LinkedIn. ## LinkedIn Follow-Up Ideas: Re-Engage Quiet B2B Leads URL: https://omentir.com/blogs/linkedin-follow-up-ideas Markdown: https://omentir.com/blogs/linkedin-follow-up-ideas.md Category: Copywriting Published: April 18, 2026 Stop sending generic "just bumping this" messages. Discover 5 signal-based LinkedIn follow-up ideas and templates that re-engage quiet B2B prospects. ## AI Reply Handling: Turn Casual LinkedIn Responses Into Booked Calls URL: https://omentir.com/blogs/ai-reply-handling Markdown: https://omentir.com/blogs/ai-reply-handling.md Category: Playbooks Published: April 17, 2026 Learn how to classify, prioritize, and respond to incoming LinkedIn messages using AI, while keeping a human-in-the-loop to build trust and increase demo bookings. ## High-Intent LinkedIn Leads: Spot Buying Signals and Book Meetings URL: https://omentir.com/blogs/high-intent-linkedin-leads Markdown: https://omentir.com/blogs/high-intent-linkedin-leads.md Category: Guides Published: April 16, 2026 Learn how to identify high-intent LinkedIn leads using real-time signals like job changes, funding, and posts, and how to write personalized B2B outreach. ## ICP-Based Lead Discovery: Build a Dynamic Search Workflow URL: https://omentir.com/blogs/icp-based-lead-discovery Markdown: https://omentir.com/blogs/icp-based-lead-discovery.md Category: Guides Published: April 15, 2026 Learn how to convert your static B2B Ideal Customer Profile into precise search parameters, automate lead discovery, and personalize your LinkedIn outreach. ## Sales Pitch Personalization: Build Modular B2B Outreach URL: https://omentir.com/blogs/sales-pitch-personalization Markdown: https://omentir.com/blogs/sales-pitch-personalization.md Category: Copywriting Published: April 14, 2026 Learn how to write personalized B2B sales pitches that get replies. Master modular messaging templates, signal-led hooks, and safe LinkedIn delivery. ## Outreach for SaaS Founders: Validate Ideas and Get Users URL: https://omentir.com/blogs/outreach-for-saas-founders Markdown: https://omentir.com/blogs/outreach-for-saas-founders.md Category: Guides Published: April 12, 2026 A founder-led guide to running LinkedIn outreach for product validation, securing design partners, and landing your first 50 B2B SaaS users safely. ## AI Prospect Research: Synthesize B2B Target Data URL: https://omentir.com/blogs/ai-prospect-research Markdown: https://omentir.com/blogs/ai-prospect-research.md Category: Guides Published: April 11, 2026 Learn how to use AI to analyze company blogs, posts, and job listings on LinkedIn to build structured research profiles that convert. ## Agent-Led Sales Outreach: Build Autonomous Pipelines URL: https://omentir.com/blogs/agent-led-sales-outreach Markdown: https://omentir.com/blogs/agent-led-sales-outreach.md Category: Automation Published: April 10, 2026 Learn how to build and integrate autonomous sales agents with your outreach stack. Master REST APIs, task delegation, and safe LinkedIn automation. ## ChatGPT Outreach Prompts: Write High-Converting B2B Copy URL: https://omentir.com/blogs/chatgpt-outreach-prompts Markdown: https://omentir.com/blogs/chatgpt-outreach-prompts.md Category: Copywriting Published: April 9, 2026 Stop sending generic AI sales pitches. Master structured ChatGPT outreach prompts, context injection rules, and validation rubrics for LinkedIn. ## OpenClaw Outreach Flows: Build B2B Execution Loops URL: https://omentir.com/blogs/openclaw-outreach-flows Markdown: https://omentir.com/blogs/openclaw-outreach-flows.md Category: Automation Published: April 7, 2026 Learn how to build autonomous outbound workflows using OpenClaw agent loops. Master campaign state nodes, context variables, and safe LinkedIn pacing. ## MCP Outreach Tools: Configure Model Context Protocol URL: https://omentir.com/blogs/mcp-outreach-tools Markdown: https://omentir.com/blogs/mcp-outreach-tools.md Category: Automation Published: April 6, 2026 Learn how to connect and configure the hosted Model Context Protocol server. Master client configuration, authentication, and agent tools. ## Sales Leads from LinkedIn: Build a B2B Sourcing Pipeline URL: https://omentir.com/blogs/sales-leads-from-linkedin Markdown: https://omentir.com/blogs/sales-leads-from-linkedin.md Category: Guides Published: April 5, 2026 Learn how to build a high-quality B2B sales lead pipeline from LinkedIn. Master profile enrichment, intent scoring, and safe message personalization. ## AI Outreach QA Checklist: Pre-Launch B2B Rubric URL: https://omentir.com/blogs/ai-outreach-qa-checklist Markdown: https://omentir.com/blogs/ai-outreach-qa-checklist.md Category: Automation Published: April 4, 2026 Verify your AI campaigns before launching. Learn the essential QA steps for variables, prompts, links, and safe LinkedIn pacing. ## Better LinkedIn Targeting: Build Clean B2B Lists URL: https://omentir.com/blogs/better-linkedin-targeting Markdown: https://omentir.com/blogs/better-linkedin-targeting.md Category: Guides Published: April 3, 2026 Stop wasting connection invites on low-fit prospects. Master Boolean search filters, negative exclusions, and technographic triggers on LinkedIn. ## Sales Pitch Follow-Ups: High-Converting Copywriting Frameworks URL: https://omentir.com/blogs/sales-pitch-follow-ups Markdown: https://omentir.com/blogs/sales-pitch-follow-ups.md Category: Copywriting Published: April 1, 2026 Stop sending 'just bumping this' messages. Master 3 conversational follow-up frameworks, response triggers, and safe campaign pacing. ## LinkedIn Buyer Signals: Track Active B2B Intent URL: https://omentir.com/blogs/linkedin-buyer-signals Markdown: https://omentir.com/blogs/linkedin-buyer-signals.md Category: Guides Published: March 31, 2026 Stop reaching out to cold lists. Master 6 high-converting LinkedIn buyer intent signals, search triggers, and safe campaign pacing. ## Outbound Sales with AI: Redesign B2B Teams URL: https://omentir.com/blogs/outbound-sales-with-ai Markdown: https://omentir.com/blogs/outbound-sales-with-ai.md Category: Guides Published: March 30, 2026 Learn how to build and structure an AI-native sales organization. Master task delegation, operational workflows, and safe LinkedIn outreach. ## LinkedIn Message Hooks: Write B2B Openers That Convert URL: https://omentir.com/blogs/linkedin-message-hooks Markdown: https://omentir.com/blogs/linkedin-message-hooks.md Category: Copywriting Published: March 29, 2026 Master the first 15 words of your outreach. Learn 4 high-converting LinkedIn message hook formulas, contextual templates, and safe campaign pacing. ## AI Demo Booking Flow: Automate B2B Scheduling URL: https://omentir.com/blogs/ai-demo-booking-flow Markdown: https://omentir.com/blogs/ai-demo-booking-flow.md Category: Guides Published: March 28, 2026 Learn how to build an autonomous demo booking flow. Master intent qualification, Calendly integrations, and objection handling on LinkedIn. ## Why Your B2B Outbound Stack Needs an AI Salesman, Not Just a Sequencer URL: https://omentir.com/blogs/why-outbound-needs-ai-salesman Markdown: https://omentir.com/blogs/why-outbound-needs-ai-salesman.md Category: Outreach Published: March 26, 2026 Linear sequence tools are failing in modern B2B sales. Discover why the future belongs to context-aware, autonomous AI sales agents that dynamically research, draft, and nurture leads. ## ChatGPT Reply Drafts: Master B2B LinkedIn Responses URL: https://omentir.com/blogs/chatgpt-reply-drafts Markdown: https://omentir.com/blogs/chatgpt-reply-drafts.md Category: Copywriting Published: March 25, 2026 Stop letting hot leads go cold. Master structured ChatGPT prompts to classify LinkedIn replies and write context-grounded response drafts. ## Agent API Outreach: Integrate REST Sales Endpoints URL: https://omentir.com/blogs/agent-api-outreach Markdown: https://omentir.com/blogs/agent-api-outreach.md Category: Automation Published: March 24, 2026 Learn how to build custom outbound sales integrations. Master raw REST API endpoints, token authentication, lead ingestion, and reply hooks. ## LinkedIn Revenue Playbook: Scale B2B Pipelines Safely URL: https://omentir.com/blogs/linkedin-revenue-playbook Markdown: https://omentir.com/blogs/linkedin-revenue-playbook.md Category: Playbooks Published: March 23, 2026 Stop tracking vanity metrics. Learn the operational playbook to align LinkedIn outreach with pipeline velocity, operator leverage, and LTV. ## Artisan AI (Ava) vs. Omentir: A Deep Dive into Autonomous SDRs URL: https://omentir.com/blogs/artisan-ai-vs-omentir Markdown: https://omentir.com/blogs/artisan-ai-vs-omentir.md Category: Comparisons Published: March 22, 2026 An honest, head-to-head comparison of Artisan AI (Ava) versus Omentir for B2B sales development. Compare platform architecture, data sourcing, safety controls, and pricing. ## Cognism vs. Apollo.io: Finding Compliant B2B Data for European Sales URL: https://omentir.com/blogs/cognism-vs-apollo Markdown: https://omentir.com/blogs/cognism-vs-apollo.md Category: Comparisons Published: March 20, 2026 Compare Cognism and Apollo.io head-to-head. Learn about GDPR compliance, data accuracy in EMEA, mobile phone numbers, and pricing models for European outbound sales. ## Instantly.ai vs. Smartlead: The Battle of Cold Email Throttling Engines URL: https://omentir.com/blogs/instantly-vs-smartlead Markdown: https://omentir.com/blogs/instantly-vs-smartlead.md Category: Comparisons Published: March 19, 2026 Compare Instantly.ai and Smartlead head-to-head. Learn about multi-inbox rotation, email warm-up pools, throttling engines, and domain safety features. ## 11x.ai vs. Gojiberry: Head-to-Head Comparison of Autonomous SDRs URL: https://omentir.com/blogs/11x-ai-vs-gojiberry Markdown: https://omentir.com/blogs/11x-ai-vs-gojiberry.md Category: Comparisons Published: March 18, 2026 An honest head-to-head comparison of 11x.ai (Alice) versus Gojiberry for B2B sales. Compare workflow automation, data discovery, safety limits, and pricing. ## Why Traditional Lead Databases Fail Without an Autonomous Sourcing Layer URL: https://omentir.com/blogs/why-traditional-databases-fail Markdown: https://omentir.com/blogs/why-traditional-databases-fail.md Category: Automation Published: March 17, 2026 Static B2B directories decay rapidly. Learn how to replace old lead databases with an autonomous sourcing layer to get accurate, real-time data. ## How to Use AI to Personalize B2B Outreach at Scale URL: https://omentir.com/blogs/ai-personalization-at-scale Markdown: https://omentir.com/blogs/ai-personalization-at-scale.md Category: Copywriting Published: March 15, 2026 Stop sending generic outbound campaigns. Learn how to configure AI prompts, ground them in buyer context, and scale personalization without losing quality. ## How to Extract an Ideal Customer Profile (ICP) from Your Website URL: https://omentir.com/blogs/extract-icp-from-website Markdown: https://omentir.com/blogs/extract-icp-from-website.md Category: Guides Published: March 14, 2026 Stop guessing your target audience. Learn how to use AI crawlers to analyze your company site, extract buyer profiles, and construct an ICP schema. ## Programmatic Personalization: How to Write 100 Unique Cold Messages URL: https://omentir.com/blogs/programmatic-personalization Markdown: https://omentir.com/blogs/programmatic-personalization.md Category: Copywriting Published: March 13, 2026 Learn how to build a programmatic personalization script. Copy our TypeScript codebase to crawl sites, call LLM APIs, and write custom sales copy. ## How AI Crawlers Analyze B2B Websites for Buying Signals URL: https://omentir.com/blogs/ai-crawlers-buying-signals Markdown: https://omentir.com/blogs/ai-crawlers-buying-signals.md Category: Automation Published: March 12, 2026 Learn how AI web crawlers analyze corporate sites to extract B2B buying signals. Discover the tools, filters, and schemas used for real-time lead scoring. ## 5 AI Prompts That Generate Compelling LinkedIn Outreach Copy URL: https://omentir.com/blogs/prompts-for-linkedin-copy Markdown: https://omentir.com/blogs/prompts-for-linkedin-copy.md Category: Copywriting Published: March 11, 2026 Stop writing generic LinkedIn messages. Copy these 5 tested AI prompts to write personalized connection notes and follow-ups that get responses. ## Stop Guessing: Let AI Find the Pain Points of Your Target Buyers URL: https://omentir.com/blogs/ai-find-buyer-pain-points Markdown: https://omentir.com/blogs/ai-find-buyer-pain-points.md Category: Guides Published: March 9, 2026 Stop guessing buyer challenges. Learn how to configure AI agents to crawl reviews, documentation, and forums to map real B2B pain points. ## Why Static Templates are Dead: The Shift to Dynamic AI Outreach URL: https://omentir.com/blogs/why-static-templates-are-dead Markdown: https://omentir.com/blogs/why-static-templates-are-dead.md Category: Guides Published: March 8, 2026 Static sales sequences trigger spam filters and get ignored. Learn how dynamic AI outreach uses real-time context to write high-converting copy. ## How to Set Up an Autonomous Prospecting Agent in Under 10 Minutes URL: https://omentir.com/blogs/setup-autonomous-prospecting-agent Markdown: https://omentir.com/blogs/setup-autonomous-prospecting-agent.md Category: Guides Published: March 7, 2026 Get started with automated B2B sales. Copy our step-by-step guide to configure an autonomous prospecting agent, set prompts, and launch campaigns safely. ## AI-Driven Lead Qualification: Filtering Out the Noise in B2B Lists URL: https://omentir.com/blogs/ai-lead-qualification-funnel Markdown: https://omentir.com/blogs/ai-lead-qualification-funnel.md Category: Automation Published: March 6, 2026 Stop wasting campaigns on unqualified leads. Learn how to configure a multi-stage AI qualification pipeline to filter list noise and protect your outbox. ## Automated Website Analysis: The Key to Understanding Your Competitors URL: https://omentir.com/blogs/automated-website-competitor-analysis Markdown: https://omentir.com/blogs/automated-website-competitor-analysis.md Category: Guides Published: March 5, 2026 Stop tracking competitor features manually. Learn how to configure AI crawlers to scan competitor sites, extract pricing, and build sales battlecards. ## Machine Learning in B2B Sales: Finding Patterns in Buying Signals URL: https://omentir.com/blogs/machine-learning-in-b2b-sales Markdown: https://omentir.com/blogs/machine-learning-in-b2b-sales.md Category: Automation Published: March 3, 2026 Learn how machine learning models analyze B2B buying signals. Discover the classification, scoring, and feedback systems that optimize outreach. ## How to Prompt LLMs to Write Outreach Messages That Feel Human URL: https://omentir.com/blogs/prompt-llms-for-human-outreach Markdown: https://omentir.com/blogs/prompt-llms-for-human-outreach.md Category: Copywriting Published: March 2, 2026 Stop sending robotic sales messages. Learn the prompt settings, negative rules, and style guides to make LLM copy read like a human B2B email. ## AI Context Engines: Scaling Personalization Without Sounding Generic URL: https://omentir.com/blogs/ai-context-engines Markdown: https://omentir.com/blogs/ai-context-engines.md Category: Copywriting Published: March 1, 2026 Learn how to build an AI context engine. Gather, clean, and consolidate prospect data streams into a structured prompt payload to ground copywriting. ## How to Get Your First 10 B2B Customers with Zero Budget URL: https://omentir.com/blogs/get-first-b2b-customers-zero-budget Markdown: https://omentir.com/blogs/get-first-b2b-customers-zero-budget.md Category: Guides Published: February 28, 2026 Bootstrapping a new B2B product? Learn how to find, pitch, and secure your first 10 paying customers using zero-budget manual channels. ## Dropping Out to Build SaaS: Hard Lessons from the Mountain to First MRR URL: https://omentir.com/blogs/dropping-out-to-build-saas Markdown: https://omentir.com/blogs/dropping-out-to-build-saas.md Category: Guides Published: February 26, 2026 An honest founder journey on dropping out to build software. Learn the validation strategies, copywriting rules, and outbound playbooks used to reach initial MRR. ## Cold Outreach is the Best Way to Validate Your MVP URL: https://omentir.com/blogs/validate-mvp-via-cold-outreach Markdown: https://omentir.com/blogs/validate-mvp-via-cold-outreach.md Category: Guides Published: February 25, 2026 Stop building features without feedback. Learn how to design a targeted outreach campaign to test demand, identify target features, and secure early clients. ## How to Find Product-Market Fit (PMF) on LinkedIn URL: https://omentir.com/blogs/find-pmf-on-linkedin Markdown: https://omentir.com/blogs/find-pmf-on-linkedin.md Category: Guides Published: February 24, 2026 Stop guessing your product fit. Learn how to use targeted LinkedIn outreach to validate B2B positioning, map buyer demand, and locate PMF. ## How to Handle Your First Sales Demo and Close the Deal URL: https://omentir.com/blogs/handle-first-sales-demo Markdown: https://omentir.com/blogs/handle-first-sales-demo.md Category: Playbooks Published: February 23, 2026 Stop losing hot leads on sales calls. Master this 30-minute sales demo playbook to run active discovery, handle objections, and close B2B deals. ## The Metric That Matters: How to Measure Early Outbound Success URL: https://omentir.com/blogs/measure-early-outbound-success Markdown: https://omentir.com/blogs/measure-early-outbound-success.md Category: Playbooks Published: February 22, 2026 Stop tracking vanity outreach metrics. Learn the key performance indicators, opportunity costs, and metrics that validate sales pipelines. ## Crafting a B2B Offer That Prospects Can't Say No To URL: https://omentir.com/blogs/crafting-compelling-b2b-offer Markdown: https://omentir.com/blogs/crafting-compelling-b2b-offer.md Category: Playbooks Published: February 20, 2026 Stop pitching product features. Learn how to structure risk reversals, performance guarantees, and value-based pricing to close more B2B sales. ## 3 Simple Sales Funnels Every Early B2B SaaS Needs URL: https://omentir.com/blogs/3-simple-sales-funnels Markdown: https://omentir.com/blogs/3-simple-sales-funnels.md Category: Playbooks Published: February 19, 2026 Stop relying on single-channel growth. Learn how to configure sales-led outbound, self-serve product trials, and inbound content funnels to scale your MRR. ## Navigating the Existential Crisis of Early SaaS Development URL: https://omentir.com/blogs/existential-crisis-early-saas Markdown: https://omentir.com/blogs/existential-crisis-early-saas.md Category: Guides Published: February 18, 2026 Bootstrapping a new product? Discover how to manage founder mental health, avoid feature-chasing distractions, and stay focused on outbound validation. ## Why Direct Message Sales Beat Paid Ads for Early Startups URL: https://omentir.com/blogs/why-dm-sales-beat-paid-ads Markdown: https://omentir.com/blogs/why-dm-sales-beat-paid-ads.md Category: Guides Published: February 17, 2026 Stop wasting budget on Google and LinkedIn ads. Discover why direct message outbound drives higher feedback density and lower CAC for early B2B SaaS. ## Reaching the C-Suite: How Small Teams Target High-Level Execs URL: https://omentir.com/blogs/reaching-the-c-suite Markdown: https://omentir.com/blogs/reaching-the-c-suite.md Category: Guides Published: February 16, 2026 Stop sending long pitches to busy executives. Learn how small teams use short copy, clear triggers, and safe pacing to get C-suite replies. ## Scaling from $0 to $10k MRR: The Outbound Engine Strategy URL: https://omentir.com/blogs/scaling-to-ten-k-mrr Markdown: https://omentir.com/blogs/scaling-to-ten-k-mrr.md Category: Guides Published: February 14, 2026 Learn the exact pipeline math, multi-profile setups, and daily habits required to scale your B2B SaaS from zero to $10,000 in monthly recurring revenue. ## Building in Public: How Transparency Drives B2B Leads URL: https://omentir.com/blogs/building-in-public-b2b-leads Markdown: https://omentir.com/blogs/building-in-public-b2b-leads.md Category: Guides Published: February 13, 2026 Stop posting generic corporate updates. Learn how sharing revenue, code, and sales metrics builds trust and generates high-quality B2B inbound leads. ## Finding Your Early Adopters: A Practical Outbound Framework URL: https://omentir.com/blogs/finding-early-adopters-outbound Markdown: https://omentir.com/blogs/finding-early-adopters-outbound.md Category: Guides Published: February 12, 2026 Stop wasting campaign volume on slow enterprise buyers. Master this outreach framework to source, pitch, and convert early adopters into design partners. ## LinkedIn Weekly Connection Limits: What Happens When You Hit Them URL: https://omentir.com/blogs/linkedin-weekly-connection-limits Markdown: https://omentir.com/blogs/linkedin-weekly-connection-limits.md Category: Automation Published: February 11, 2026 LinkedIn does not publish a fixed weekly invite number. Here is what it does publish, why the popular 100-a-week figure is only a rumor, and how to work under the real limit. ## How to Warm Up a LinkedIn Account Without Getting Restricted URL: https://omentir.com/blogs/how-to-warm-up-linkedin-account Markdown: https://omentir.com/blogs/how-to-warm-up-linkedin-account.md Category: Automation Published: February 9, 2026 LinkedIn can lock invitations for a week if a quiet account suddenly sends too many. Here is a conservative four-week warmup, plus what to do if you already hit the limit. ## The Ultimate Guide to LinkedIn Account Health and Safety URL: https://omentir.com/blogs/linkedin-account-health-safety Markdown: https://omentir.com/blogs/linkedin-account-health-safety.md Category: Automation Published: February 8, 2026 Keep your sales profiles safe. Discover how to manage cookies, session geolocations, API routing, and pacing limits to maintain high account health scores. ## Protecting Your Personal Brand While Automating Outbound Sales URL: https://omentir.com/blogs/protect-personal-brand-outbound Markdown: https://omentir.com/blogs/protect-personal-brand-outbound.md Category: Guides Published: February 7, 2026 Learn how to automate outbound campaigns without compromising your personal brand. Discover the review queue and copywriting rules that protect reputation. ## How Unipile Ensures Safe and Encrypted LinkedIn API Access URL: https://omentir.com/blogs/unipile-safe-linkedin-api Markdown: https://omentir.com/blogs/unipile-safe-linkedin-api.md Category: Automation Published: February 6, 2026 Learn how Unipile secure API routing protects B2B outreach. Discover cookie encryption, regional proxy IP mapping, and safe integrations. ## Understanding the Psychology of Spam: Why Prospects Report Messages URL: https://omentir.com/blogs/psychology-of-spam-outreach Markdown: https://omentir.com/blogs/psychology-of-spam-outreach.md Category: Guides Published: February 5, 2026 Stop getting flagged. Understand the psychological triggers that make prospects report sales messages as spam, and learn how to rewrite your copy. ## The Importance of Gradual Outbound Ramp-Ups for New Profiles URL: https://omentir.com/blogs/gradual-outbound-ramp-ups Markdown: https://omentir.com/blogs/gradual-outbound-ramp-ups.md Category: Guides Published: February 3, 2026 Stop burning new outreach profiles. Discover how platform security algorithms analyze volume spikes, and learn how to configure a safe 4-week ramp-up curve. ## LinkedIn Spam Filters: What They Catch, and What They Do Not URL: https://omentir.com/blogs/linkedin-spam-filters-how-they-work Markdown: https://omentir.com/blogs/linkedin-spam-filters-how-they-work.md Category: Guides Published: February 2, 2026 LinkedIn's own rules ban using invitations as ads. Here is what the company publishes about spam, what its transparency report shows, and how to stay out of the filter. ## The Complete Compliance Checklist for LinkedIn Outreach in 2026 URL: https://omentir.com/blogs/linkedin-outreach-compliance-2026 Markdown: https://omentir.com/blogs/linkedin-outreach-compliance-2026.md Category: Guides Published: February 1, 2026 Stay legally compliant. Discover the GDPR, CAN-SPAM, and platform rules sales teams must respect when automating outreach campaigns in 2026. ## Legal - https://omentir.com/minimum-booking-guarantee - https://omentir.com/privacy-policy - https://omentir.com/terms-of-service