DEV Community: Md Kawsar

Smartlead vs Instantly: which cold email tool fits how you actually work

Md Kawsar — Fri, 09 Oct 2026 13:00:00 +0000

Their mid-tier plans are only about $3 apart. What really separates them is the audience: in-house teams that want lead data built in, or agencies that need control. Here's everything side by side.

Every cold email agency I know has this debate at least once a quarter. One person says, "Let's move everything to Instantly." Another says, "No, Smartlead works better for clients." And then out come the spreadsheets.

I see that debate from both ends. I scrape B2B leads for clients and I run an email verification platform, so I watch the data go in and the bounces come back. Smartlead vs Instantly is a question I hear all the time.

Here's the answer I really give people, with 2026 pricing, limits, and the details you won't find on either landing page.

The short answer first

Short on time? Here's the quick version:

Instantly suits in-house teams that want a polished tool with a lead database, placement testing, and a light CRM in the box.
Smartlead suits agencies juggling lots of client accounts that need separate workspaces per client, white-label dashboards, and solid API control.
The rest of this post explains why.

The prices are nearly the same. The workflows are very different. Choose the tool that fits how your team really runs campaigns.

2026 pricing, side by side

These are this year's published plans, based on GigRadar's 2026 comparison. Check each vendor's pricing page before you buy, since both change their plans often.

Smartlead

Basic: $39/month, 2,000 contacts, 6,000 emails/month
Pro: $94/month, 30,000 contacts, 150,000 emails/month
Unlimited Smart: $174/month
Unlimited Prime: $379/month

Instantly

Growth: $47/month, 1,000 contacts, 5,000 emails/month
Hypergrowth: $97/month, 25,000 contacts, 100,000 emails/month
Light Speed: $358/month

On the most popular middle plans, Smartlead Pro ($94) vs Instantly Hypergrowth ($97), the gap is just $3. Smartlead gives you slightly more contacts and sends, while Instantly packs in more features.

Both include unlimited connected email accounts and unlimited warmup on every plan. A few years ago that set them apart. Now it's standard.

The hidden costs

This is where the sticker price can mislead you.

Smartlead's add-ons: inbox placement testing costs extra, somewhere around $49 to $599 depending on volume, according to Artisan's breakdown. White-label client dashboards cost about $29 per client each month. There's no lead database built in, so you need your own data source.

Instantly's bundles: placement testing and a light CRM come included. There's also SuperSearch, a lead database with more than 450 million records. If you'd otherwise pay for Apollo or something like it, that saves you real money.

That means an in-house team that needs both leads and sending can spend less overall on Instantly, even with its higher base price. An agency that already has its own data keeps Smartlead's low price low.

Deliverability: the part that actually matters

Here's something people don't love hearing. Your tool matters less than your infrastructure. Your domains, DNS records, list quality, and sending volume decide whether emails reach the inbox. The platform is mostly the steering wheel.

Still, the two tools do differ:

Both use shared warmup networks. Some Reddit users say their open rates dropped suddenly because of warmup pool quality on Instantly, and GigRadar mentions it too. I'd call that anecdotal, but it's worth watching.
Instantly comes with placement testing, so you can see whether you're hitting inbox or spam before a campaign scales up.
Smartlead's mailbox rotation across unlimited accounts spreads volume thinly and evenly, which is exactly what agencies want.
And the basics still apply whichever tool you choose. Since 2024,Google's sender guidelines have required authentication and low spam complaint rates, and Microsoft tightened its rules for bulk senders in 2025. If SPF, DKIM, and DMARC aren't set up yet, close this post and fix that first.

Send a bad list through a great tool and it still bounces. Verify before every send.

Inbox management and replies

Replies are where deals get made, so this part deserves more attention than it gets.

Smartlead's Master Inbox gathers replies from every account in one place, with custom categories, webhooks, and the option to assign replies to team members. For an agency with several SDRs covering different clients, that assignment feature is a big help.

Instantly's Unibox handles the same job with a cleaner design and AI that labels replies automatically, such as interested, not interested, or out of office. For one in-house team, it's quicker to work in every day.

Agency features: Smartlead's home turf

If you run an agency, this is the section that settles it.

Smartlead gives every client its own separate workspace with isolated API tokens
White-label dashboards show clients their results under your brand
The API is solid enough to build custom workflows, reports, and integrations
Instantly offers workspaces as well, but reviewers say they feel more like saved campaign folders than truly separate client accounts. With two clients, that works fine. With twenty, Smartlead's setup saves you a lot of trouble.

What real volume costs: a worked example

Let's put real numbers on it. Imagine you want to send 30,000 cold emails a month, a typical goal for a small agency client or a committed in-house SDR team.

Inboxes first. If each inbox sends about 40 cold emails a day over roughly 22 sending days, it handles around 880 emails a month. That means you need about 35 inboxes. Spread them over something like 12 domains with 3 inboxes each, and you have a normal, safe setup.

Platform cost. Smartlead Pro ($94) and Instantly Hypergrowth ($97) both handle 30,000 sends a month easily. Since accounts are unlimited, connecting 35 inboxes costs nothing extra on either one.

The real bill. The platform is the cheapest piece. Domains and mailboxes cost a lot more. Google Workspace or Microsoft 365 seats run from a few dollars up to about $7 each, so 35 inboxes can cost $100 to $250 a month, before domain renewals. On top of that come lead data and verification.

So the total monthly cost for this setup often lands between $400 and $700, and the gap between Smartlead and Instantly barely registers. That's why I keep telling people to choose based on workflow.

AI features: handy, but they shouldn't decide it

Both tools push AI hard these days. Instantly offers AI reply labeling in Unibox and AI help with writing campaigns. Smartlead offers AI sorting in its Master Inbox and personalization helpers.

Honestly, AI-written cold emails sent at scale start to sound alike, and prospects can tell. The AI I'd really use is the boring kind: sorting replies so your team gets to interested leads first. Both tools do that fairly well, so it shouldn't be the reason you switch.

Which one should you pick?

This is how I'd make the call.

You're a founder or small in-house sales team without a lead source yet: Instantly. Getting SuperSearch and sending on one bill is tough to beat.
You're an agency with 5+ clients: Smartlead. Its workspaces, white-label options, and API control were made for you.
You already pay for Apollo, Clay, or scraped data: Smartlead's lower base price is the better deal, because you won't need Instantly's database.
You're developer-heavy and want to automate everything: Smartlead's API gives you more flexibility.
You want the least setup friction: Instantly's interface is smoother for non-technical users.

If you're thinking about switching

Switching is easier than most people expect, because the valuable parts sit outside the tool. Your domains, inboxes, and warmup history belong to your mailboxes, so neither Smartlead nor Instantly keeps them.

Here's how a clean switch works. Connect your current inboxes to the new platform and let warmup run there for a week while your old campaigns wrap up. Export your lead lists with their status so you don't email anyone who already replied or unsubscribed. Rebuild your best sequence first and leave the rest for later. Then keep the old account for one more billing cycle so you can look back at reply history.

The most common mistake I see is switching tools to fix deliverability. If your emails go to spam, the same domains and the same list on a new platform will go to spam as well. Fix the real cause first.

My cold email infrastructure checklist

No matter which tool you pick, I'd have this setup in place before the first campaign goes out.

Separate sending domains from your main domain. Keep your company inbox out of harm's way.
SPF, DKIM, and DMARC configured on every sending domain.
Warm up for at least two weeks before sending real campaigns.
Cap each inbox at a sane daily volume. Lots of teams keep it to around 30 to 50 cold emails per inbox each day.
Verify every list. Remove invalid and risky addresses, plus any catch-all addresses you can't confirm.
Test placement before you scale up a campaign.
Keep an easy opt-out in every sequence. It protects your sender reputation and shows respect for the people you email.

The verdict

The Smartlead vs Instantly debate often gets treated like a boxing match. In reality, the two have grown into tools for two different jobs.

Instantly is the all-in-one option for teams that want data and sending in one tidy package. Smartlead is the control panel for agencies managing lots of clients.

Choose the one that matches your workflow, then put your real effort into domains, lists, and copy. That's what decides whether cold email works. The tool just sends it.

Enjoyed this read? Be sure to follow me for more stories that make people feel things. You can also connect with me on LinkedIn or Telegram @kawsarlog for more updates on my work.

I do freelance scraping projects, so if you need some data collected feel free to contact me on LinkedIn or email at hi@kawsarlog.com

$150,000 per song: what the AI music lawsuit wave means for every AI company

Md Kawsar — Thu, 08 Oct 2026 15:00:00 +0000

Sony and Universal have pinned a theoretical $9 billion price on Suno and more than $4 billion on Udio. Here's where those numbers come from, why nobody expects them to be paid, and what AI builders should take away.

If you run an AI company, this number should get your attention: $9,153,900,000.

You get it by multiplying 61,026 sound recordings by **$150,000 **each, which is the highest statutory damage US law allows for willful copyright infringement. That's the theoretical maximum Sony Music and Universal Music Group have been pointing at Suno

No serious person expects Suno to pay nine billion dollars. The number was never supposed to be realistic. Its job is to be scary, and it's doing that job well.

I'm not a musician. My work is data pipelines and scrapers. Still, the AI music lawsuit fight is the best preview I've found of how training-data disputes will go for the rest of us. Let's walk through it.

How we got here, fast

Here's a quick summary of a long and messy timeline:

June 2024: The RIAA sues Suno and Udio for the major labels.
October 2025: Independent artists begin filing class actions against Suno and Udio.Later suits go after Mureka and Google's Lyria 3.
Late 2025: Warner Music settles with Suno, and Udio signs licensing deals with Universal and Warner.
May 21, 2026: Sony and UMG ask to add 61,026 recordings to their Suno case. They identified them with the Audible Magic fingerprinting service.
June 29, 2026: A judge won't let Sony add tens of thousands of new works to its Udio case.
July 20, 2026: Sony files a brand new lawsuit against Udio that covers more than 30,000 recordings.
September 2026: Sony and UMG sue Suno a second time, now aiming at its new v6 model.
So this is a whole wave of lawsuits, and each new one is bigger than the one before.

Where the $150,000 number comes from

Under US copyright law, a rights holder can pick statutory damages rather than proving what they actually lost. The normal range is $750 to $30,000 per work. When the infringement is willful, a court can award up to $150,000 per work.

Everything hinges on that per-work rule. How much a label lost on any one song doesn't matter. The math simply counts songs.

Here's how that counting adds up:

Original Suno complaint: 560 works, about $84 million at the max
Expanded Suno list: 61,026 works, about $9.15 billion at the max
Sony's second Udio suit: 30,000+ works, about $4.5 billion at the max

With statutory damages, your training dataset becomes a bill, and every file is a line on it.

The new twist: "model laundering"

To me, the September Suno suit is the most interesting one, because it targets a new model.

Suno says v6 was trained on licensed material, community interactions, and what its team learned. The labels say there's more to it. Their complaint claims Suno used knowledge distillation, meaning v6 learned from the outputs of older models that had been trained on unlicensed tracks. Variety quotes the complaint calling v6 "the fruit of the same poisoned tree."
If the court accepts that argument, it changes a lot. Retraining alone wouldn't wipe a model's history clean. The taint follows the lineage.

A huge number of AI products today come from distilling a large model into a smaller one. If courts decide distilled models inherit their parent's legal problems, plenty of companies will need to take a close look at their family tree.

Why the labels won't actually collect $9 billion

Headlines love these figures, so I want to be clear: the maximums are upper limits, and nobody should read them as forecasts.

Here's why they almost never get paid in full:

Willfulness has to be proven, and courts usually award much less than $150,000 per work
Judges resist cases that keep ballooning, as the Udio ruling showed
Fair use is still unsettled, and results vary from case to case
Most of these fights wrap up with licensing deals rather than damage awards
That last point is the pattern to watch. Warner settled and signed a license. UMG and Warner licensed Udio. Suno now has deals with Warner, BMG, and Believe. These lawsuits act less like a path to a verdict and more like a negotiation backed by a very big stick.

The artists who aren't in the room

The label cases grab the headlines, but the independent artist cases could end up mattering more.

The Class actions filed since October 2025 speak for songwriters, session musicians, producers, vocalists, and small labels. Their argument is straightforward: the systems learned from full tracks, vocal stems, and lyric sheets, and now produce music that competes with the very people who made the originals.

This matters because a major label's licensing deal only covers that label's catalog. A session player who appeared on hundreds of recordings, or an indie artist who released music alone, sits outside that deal. Warner or Universal getting a seat at the table doesn't give them one.

Even if every major label signs on, a long tail of rights holders can still sue. For AI companies, "we signed the big three" makes the risk smaller, but some of it is still there.

It also leads to a tougher question that nobody has solved yet: how do you fairly pay thousands of small creators for a model trained on millions of files? Per-stream royalties took years to work out, and per-training-example royalties haven't even begun.

What this means for AI companies outside music

This is the part that matters most to me. Music is only the first test. The same reasoning covers images, code, news articles, product data, and anything else collected at scale.

Your exposure is your file count

Because damages are counted per work, a company trained on 10 million copyrighted items has an exposure on paper that sounds ridiculous. That figure can still surface in investor due diligence, acquisition talks, and insurance quotes, even if it never reaches a courtroom.

Provenance is becoming a product feature

Saying "here's exactly where our training data came from" is becoming something you can sell. Udio and Suno both advertise their licensing deals now, and people buying AI tools are starting to ask about it.

Fingerprinting makes hiding hard

The labels used Audible Magic to find 61,026 of their tracks. Similar tools exist for images, text, and code. Betting that nobody will check your dataset is a bad bet.

People used to ask "is this legal?" Now they ask "can you prove where it came from?"

A practical checklist if you train or fine-tune anything

Scraping data for clients is my everyday work, so I've thought about this a lot. This is what I'd tell any small AI team.

Keep a data manifest. Record the source, the collection date, the license or terms, and how you used it. It's a dull spreadsheet that pays off later.
Separate training data from reference data. Collecting public prices for analysis carries a very different risk from feeding creative works into a generator.
Check the terms of every source. Just because something is public doesn't mean you can train on it.
Track your model lineage. If you distill from another model, note which one it was and what it was trained on, as best you know.
Prefer licensed or open datasets for anything that produces output competing with the original creators.
Talk to a lawyer before launch, instead of after a demand letter arrives. I'm not a lawyer, and this isn't legal advice.

Dates worth putting in your calendar

If you'd like to keep up without reading every filing, these are the key dates in the main Suno case, according to Music Business Worldwide:
September 30, 2026: fact discovery and depositions end. Any evidence about training data is now on the record.
April 9, 2027: dispositive motions are due. Each side will ask the judge to decide big questions, such as fair use, without a full trial.
Keep an eye on whether the court allows the 61,026-work expansion. The Udio judge rejected a similar request. If the Suno judge does the same, expect more brand-new lawsuits instead of bigger existing ones, just like Sony did with Udio.

The honest read

My feelings about this fight are mixed.

I understand why musicians are angry. If your work were used without permission to build a machine that competes with you, you'd be furious too. The independent artist class actions seem especially fair to me.

At the same time, "$9 billion" doesn't help anyone understand what's really happening. It's a number built to apply pressure. What actually happens, over and over, is a licensing deal where the biggest labels get paid and smaller creators wait to see if anything reaches them.

For AI builders, the lesson is to keep building and know your data the way you know your finances. In 2026, your dataset can turn into an itemized bill, and the people holding the receipts have gotten very good at counting.

Enjoyed this read? Be sure to follow me for more stories that make people feel things. You can also connect with me on LinkedIn or Telegram @kawsarlog for more updates on my work.

I do freelance scraping projects, so if you need some data collected feel free to contact me on LinkedIn or email at hi@kawsarlog.com

A Yemen weapons cell used Claude as its engineering team. Here's how Anthropic caught it

Md Kawsar — Wed, 07 Oct 2026 13:00:00 +0000

A small group leaned on Claude Code to write missile software. How it got caught says a lot about the way AI companies watch over their tools in 2026.

Somewhere in northern Yemen, a guided rocket failed its test. A few hours later, the people behind it were back in a chat window, asking an AI to explain what broke.

Of everything in Anthropic's September 2026 threat intelligence report,that's the detail I keep coming back to. I skimmed past the missile ranges and the geopolitics. What stayed with me was the reflex. Something failed, and their first move was to open Claude.

Claude is part of my daily work for scraping jobs and client automation. So when I read that a weapons cell "used Claude Code in place of human software engineers," two feelings hit me together. I felt a bit sick. I also really wanted to know how they were caught.

This post is about that second feeling. AI misuse enforcement has changed a lot without much noise, and if you build anything with AI tools, the new rules affect you as well.

What actually happened in Yemen

According to the report and coverage from Al Jazeera and Axios,operators in Houthi-held northern Yemen were working on three weapons programs: a guided rocket, a multi-stage ballistic missile, and another missile family that included a planned hypersonic glide vehicle.

They went further than a single chat. They set up a small org chart made of AI.

One Claude instance handled the coding
A second one did the research
A third checked the output, the way a senior engineer reviews code
Claude helped with flight-control code, simulations, and fixing guidance and navigation problems. When a guided rocket test failed, the team returned to ask for diagnostics. Anthropic says it has no evidence the group fielded a working weapon. Still, the group had built offline simulation tools too, so it was already becoming less dependent on Claude.

Putting together a three-person engineering team used to mean hiring. For this cell, it just meant writing prompts.

How they slipped past the first line of defense

Most headlines left this part out. Anthropic's safety systems did stop many of their requests. The cell worked around them with two simple tricks.

First, they hid the objective. No one wrote "help me build a missile." They asked about control loops, simulation math, and debugging, and each of those questions looks ordinary by itself.

Second, they split the project across many separate conversations. Every session looked innocent. The danger only became clear once you put them side by side.

Anyone who has scraped a site with per-session rate limits knows this trick. You spread the work out so no single request stands out. It's the same idea, used for a much darker purpose.

That's why filtering prompts on their own isn't enough anymore. A filter that reads one message at a time will miss a pattern that only appears across fifty.

What AI misuse enforcement looks like in 2026

After reading the whole report, I'd put the new approach in one sentence: enforcement moved from judging prompts to judging behavior.

Anthropic lays out several layers that work together.

Classifiers on individual requests. This is the original layer. It still stops a lot, and careful wording can still get around it.
Behavioral signatures across accounts. This layer watches account patterns, long-running workflows, reused templates, and sessions that look coordinated. The report says influence operators pasted the same Markdown "doctrine" files, almost word for word, into hundreds of sessions. Repetition like that works like a fingerprint.
Dedicated investigations. The Yemen case surfaced through internal investigations into weapons development, and people on Anthropic's team followed the leads by hand.
Outside tips and cross-platform data. Some tips arrive from partners or public reporting, and the team then checks them against activity on the platform.
Action after detection. Accounts are banned. The actor's behavior is turned into new automated detections, so the next similar operation gets flagged sooner. Indicators are passed on to government and industry partners.

The fifth layer interests me most. Each operation that gets caught teaches the detector something new. The system gets better by studying the people trying to beat it.

The Yemen case wasn't the scariest thing in the report

I went in assuming the missile story was the biggest news. After reading the rest, I'm less sure.

It covers a Chinese-speaking group, probably students plus someone interning at a security firm, running what Anthropic calls an autonomous "zero day exploit foundry." Swarms of agents took binaries apart in parallel and wrote exploits without human help.

There's also a money-driven crew that scanned 1.8 million Android APKs for leaked credentials and collected more than 2,100 Azure AD tokens in 34 hours. And a lone French-speaking hacktivist who built a full doxxing platform alone.

This is the line I can't shake:

"AI has collapsed the labor and tooling gap that used to separate state-sponsored operations from individual operators."
To me, that's the real headline. Sophistication no longer tells you who's behind an attack. One person with a strong agent setup can look like a small agency. The Yemen cell is simply the most dramatic example of that change.

Why a freelancer or small founder should care

Maybe you're thinking: I collect product data and build dashboards, so why should missile software matter to me?

It matters more than you'd expect. Three parts of this report affect everyday builders directly.

Your API keys are now loot

One Russian-speaking actor targeted AI vendors' evaluation sandboxes and took production API keys from about 30 AI companies in four days. According to the report, criminals now see AI keys the same way they see production credentials. A stolen key gives them something to sell, free compute, and cover, because every action traces back to your account instead of theirs.

Let that last point sink in. If someone takes your key and uses it for abuse, your account is the one that gets flagged.

Behavior-based enforcement can catch honest patterns too

When detection focuses on workflows and templates, heavy but honest automation can look odd. I run long agent sessions for data extraction and often reuse the same instruction files from job to job. That's ordinary for my work. On paper, though, it's the same kind of repetition detectors look for.

Honest users don't need to panic. It's still smart to keep your usage easy to explain, with clear project names, reasonable request rates, and a record of what each automation does.

"Split it across sessions" is not a clever workaround anymore

Some people try to slip past content policies by chopping a request into harmless-looking pieces. The Yemen case shows that this now gets investigated as a pattern. Legitimate work doesn't need tricks. And if the work isn't legitimate, the tricks are what draw attention.

A practical checklist for builders using AI tools

After reading the report, this is the checklist I'd give any freelancer or small team. Every item is easy.

Rotate API keys on a schedule. Do it every 60 to 90 days, and right away whenever a contractor leaves.
Never ship keys inside apps or public repos. The APK scanning case proves attackers dig through compiled apps. Route calls through a backend proxy instead.
Set hard spend limits on every AI provider account. A sudden jump in spending is often the first clue that a key leaked.
Separate keys per project and per client. Then a leak means revoking one key instead of all of them.
Keep a short note of what each automation does. If your account is ever reviewed, you'll have a clear answer ready.
Read the provider's usage policy once a year.It changes more often than most people realize. Here's Anthropic's if you've never looked.
Watch your own agents. Autonomous agents with web access and saved credentials have become targets. Keep logs of what they do.

What I'm still uneasy about

To be honest, I'm still not sure how I feel about all this.

On one side, the system did its job. A weapons cell was found, banned, and reported, and the detectors learned from it. That's a good outcome.

On the other side, the cell did get real help before anyone stopped it, and it still has simulation tools it can run offline. The report also says that when state-backed researchers were refused on a biology request, they just switched to a competing model. One company's enforcement only reaches that one company.

Then there's the privacy question people tend to avoid. Detection based on behavior means someone is studying behavior. That's great when it's aimed at bad actors. For everyone else, it's a trade-off we're accepting without much debate.

I don't have a tidy answer. I just think anyone building with AI should see this trade-off clearly and stop pretending it isn't there.
The takeaway

Most people will remember the Yemen story as "terrorists used AI for missiles." That's accurate, and it's frightening.

For most of us, though, the more useful lesson is a quieter one. AI misuse enforcement now watches patterns as well as prompts. Stolen keys become disguises. And small teams can work like large ones, for better and for worse.

So guard your API keys the way you guard passwords. Keep your automation boring and easy to explain. And next time a threat report comes out, look past the scary headline for a moment and study the method. That's where the lessons for your own business are.

Enjoyed this read? Be sure to follow me for more stories that make people feel things. You can also connect with me on LinkedIn or Telegram @kawsarlog for more updates on my work.

I do freelance scraping projects, so if you need some data collected feel free to contact me on LinkedIn or email at hi@kawsarlog.com