Replace lemlist

lemlist lists 22 features. How many does your team use?

Stop paying per seat for the rest. Pick the lemlist features your team actually uses, and we build your own version that you own.

Pick your features

Good fit

We can build almost all of lemlist.

Core outbound workflow (sequences, CRM-style lead lists, unified inbox, deliverability checks) is buildable, but the 650M lead database, live calling, WhatsApp/SMS/LinkedIn delivery and mailbox warm-u

6 we build fully10 need an outside service3 simplified3 we can’t build

What lemlist does

Read from lemlist’s public website. Each feature is marked with what we can honestly build.

Lead finding and enrichment

650M+ lead database
Search a large built-in database of prospects using ICP filters.
We can't build this. Requires a licensed contact database of hundreds of millions of records; we cannot build that data asset.
Email finder and verifier
Find and verify business email addresses for leads.
Simplified version. Verification via SMTP checks or a third-party API is possible; a full proprietary database is not.
Phone number finder
Find phone numbers for leads.
Simplified version. Only with a paid third-party data provider; no proprietary phone database.
CSV and CRM lead import
Upload leads from a CSV or CRM and map fields.

Multichannel sequences

Email sequences
Build multi-step email campaigns with delays and conditions.
Needs an outside service: Amazon SES. Sending through a transactional/bulk email provider the owner must pay for.
Automated follow-up workflows
Trigger next steps based on opens, replies and other events.
LinkedIn prospecting and voice messages
Automate LinkedIn connection requests, messages and voice notes.
We can't build this. Requires automating LinkedIn accounts, which we cannot deliver as a reliable product.
In-app calling
Place calls directly from the app.
Needs an outside service: Twilio. Browser calling via a telephony provider is possible; carrier network is rented, not built.
SMS campaigns
Send SMS steps in sequences.
Needs an outside service: Twilio. Requires an SMS gateway account; we build the sequencing only.
WhatsApp prospecting
Send WhatsApp steps in sequences.
Needs an outside service: Twilio. Requires WhatsApp Business API access; no direct carrier-level control.

Unified inbox

Shared inbox for replies across channels
See and reply to replies from all senders in one view.
Needs an outside service: Gmail API and Microsoft Graph. Two-way Gmail/Outlook sync is needed for true inbox threading; without it, only send-side replies are captured.

Deliverability

Mailbox warm-up
Warm up mailboxes to build sender reputation.
We can't build this. Needs a large network of real mailboxes exchanging mail; cannot be built standalone.
Deliverability monitoring and alerts
Monitor mailbox and domain health and alert on issues.
Needs an outside service: Resend. Can check DNS (SPF/DKIM/DMARC) and bounce rates; reputation scoring from inbox providers is not available.

AI outbound agents

Intent signal agents
Detect and act on buying-intent events.
Needs an outside service: OpenAI or Anthropic API. Can process owned event data with an AI model; third-party intent feeds are not included.
Data enrichment agents
Pull structured insights from websites and CRM data.
Needs an outside service: OpenAI or Anthropic API. Website and CRM enrichment buildable with an AI model; LinkedIn scraping is not reliable.
AI-personalized copy
Generate personalized email copy per lead.
Needs an outside service: OpenAI or Anthropic API. Uses a hosted LLM API the owner must pay for.

Integrations and APIs

CRM sync (HubSpot, Salesforce, Pipedrive)
Two-way sync of leads and activities with CRMs.
Simplified version. Possible via each vendor's API, one integration at a time; not 58 native integrations.
Webhooks and REST API
Expose data and events to other tools.
Slack notifications
Notify a Slack channel on replies.

Reporting and team

Campaign dashboards and reports
Track opens, replies and meetings per campaign.
Roles and team access
Manage team members and permissions.

Video and content outreach

Personalized video messages
Record and share video in sequences.
Needs an outside service: Mux. Browser recording and upload are buildable; video hosting and streaming must be rented.

What you’d bring

We write all the code. These features only work on outside services, and those accounts are yours to open and pay for directly.

Sending notification emails: Resend

Free allowance, then pennies per thousand emails. Billed by the provider.

Bulk email campaigns: Amazon SES

Pay per email sent, pennies per thousand. Billed by the provider, not us.

SMS and WhatsApp messaging: Twilio

Pay per message. Billed by the provider.

Phone calls: Twilio

Pay per minute plus number rental. Billed by the provider.

Storing and streaming video: Mux

Pay for minutes stored and streamed. This grows with use. Billed by the provider.

AI features: OpenAI or Anthropic API

Pay per use, billed to your own account by the model provider. Our Claude credits are never used.

Syncing Gmail or Outlook inboxes: Gmail API and Microsoft Graph

Free to call. The review, and the yearly re-assessment Google requires, is the real cost. A sync provider like Nylas charges per connected inbox and handles the review for you.

What we can’t build

650M+ lead database. Requires a licensed contact database of hundreds of millions of records; we cannot build that data asset.
LinkedIn prospecting and voice messages. Requires automating LinkedIn accounts, which we cannot deliver as a reliable product.
Mailbox warm-up. Needs a large network of real mailboxes exchanging mail; cannot be built standalone.

Build only the lemlist features you use

Pick your features, choose what it connects to, and see the price before you start.

Pick your features

Replace lemlist

lemlist lists 22 features. How many does your team use?

Stop paying per seat for the rest. Pick the lemlist features your team actually uses, and we build your own version that you own.

Pick your features

Good fit

We can build almost all of lemlist.

6 we build fully10 need an outside service3 simplified3 we can’t build

What lemlist does

Read from lemlist’s public website. Each feature is marked with what we can honestly build.

Lead finding and enrichment

650M+ lead database
Search a large built-in database of prospects using ICP filters.
We can't build this. Requires a licensed contact database of hundreds of millions of records; we cannot build that data asset.
Email finder and verifier
Find and verify business email addresses for leads.
Simplified version. Verification via SMTP checks or a third-party API is possible; a full proprietary database is not.
Phone number finder
Find phone numbers for leads.
Simplified version. Only with a paid third-party data provider; no proprietary phone database.
CSV and CRM lead import
Upload leads from a CSV or CRM and map fields.

Multichannel sequences

Email sequences
Build multi-step email campaigns with delays and conditions.
Needs an outside service: Amazon SES. Sending through a transactional/bulk email provider the owner must pay for.
Automated follow-up workflows
Trigger next steps based on opens, replies and other events.
LinkedIn prospecting and voice messages
Automate LinkedIn connection requests, messages and voice notes.
We can't build this. Requires automating LinkedIn accounts, which we cannot deliver as a reliable product.
In-app calling
Place calls directly from the app.
Needs an outside service: Twilio. Browser calling via a telephony provider is possible; carrier network is rented, not built.
SMS campaigns
Send SMS steps in sequences.
Needs an outside service: Twilio. Requires an SMS gateway account; we build the sequencing only.
WhatsApp prospecting
Send WhatsApp steps in sequences.
Needs an outside service: Twilio. Requires WhatsApp Business API access; no direct carrier-level control.

Unified inbox

Shared inbox for replies across channels
See and reply to replies from all senders in one view.
Needs an outside service: Gmail API and Microsoft Graph. Two-way Gmail/Outlook sync is needed for true inbox threading; without it, only send-side replies are captured.

Deliverability

Mailbox warm-up
Warm up mailboxes to build sender reputation.
We can't build this. Needs a large network of real mailboxes exchanging mail; cannot be built standalone.
Deliverability monitoring and alerts
Monitor mailbox and domain health and alert on issues.
Needs an outside service: Resend. Can check DNS (SPF/DKIM/DMARC) and bounce rates; reputation scoring from inbox providers is not available.

AI outbound agents

Intent signal agents
Detect and act on buying-intent events.
Needs an outside service: OpenAI or Anthropic API. Can process owned event data with an AI model; third-party intent feeds are not included.
Data enrichment agents
Pull structured insights from websites and CRM data.
Needs an outside service: OpenAI or Anthropic API. Website and CRM enrichment buildable with an AI model; LinkedIn scraping is not reliable.
AI-personalized copy
Generate personalized email copy per lead.
Needs an outside service: OpenAI or Anthropic API. Uses a hosted LLM API the owner must pay for.

Integrations and APIs

CRM sync (HubSpot, Salesforce, Pipedrive)
Two-way sync of leads and activities with CRMs.
Simplified version. Possible via each vendor's API, one integration at a time; not 58 native integrations.
Webhooks and REST API
Expose data and events to other tools.
Slack notifications
Notify a Slack channel on replies.

Reporting and team

Campaign dashboards and reports
Track opens, replies and meetings per campaign.
Roles and team access
Manage team members and permissions.

Video and content outreach

Personalized video messages
Record and share video in sequences.
Needs an outside service: Mux. Browser recording and upload are buildable; video hosting and streaming must be rented.

What you’d bring

We write all the code. These features only work on outside services, and those accounts are yours to open and pay for directly.

Sending notification emails: Resend

Free allowance, then pennies per thousand emails. Billed by the provider.

Bulk email campaigns: Amazon SES

Pay per email sent, pennies per thousand. Billed by the provider, not us.

SMS and WhatsApp messaging: Twilio

Pay per message. Billed by the provider.

Phone calls: Twilio

Pay per minute plus number rental. Billed by the provider.

Storing and streaming video: Mux

Pay for minutes stored and streamed. This grows with use. Billed by the provider.

AI features: OpenAI or Anthropic API

Pay per use, billed to your own account by the model provider. Our Claude credits are never used.

Syncing Gmail or Outlook inboxes: Gmail API and Microsoft Graph

Free to call. The review, and the yearly re-assessment Google requires, is the real cost. A sync provider like Nylas charges per connected inbox and handles the review for you.

What we can’t build

650M+ lead database. Requires a licensed contact database of hundreds of millions of records; we cannot build that data asset.
LinkedIn prospecting and voice messages. Requires automating LinkedIn accounts, which we cannot deliver as a reliable product.
Mailbox warm-up. Needs a large network of real mailboxes exchanging mail; cannot be built standalone.

Build only the lemlist features you use

Pick your features, choose what it connects to, and see the price before you start.

Pick your features