🦾Eric Nowoslawski

I am a direct response outbound lead generation expert. And by that jumble of words, I mean that I leverage cold email to build predictable revenue pipelines for my clients. 

I leverage over 20 databases to merge Firmographic, Technographic, and Persona data to build highly targeted playbooks with my clients. 

I believe we need to arm sales teams with the knowledge of their total Target Addressable Market and teach them how to score that Market for which companies have the most pain and need their solution. 

The best way to do this is to look at public indicators such as open jobs data, employee growth/attrition, social media growth, web traffic, new product launches, employee sentiment, individual employee tech investment, company tech stacks, etc.

With this data, not only are you only messaging with people that you know have a problem that you can solve, you also are armed  with powerful messaging that cuts through the noise. 

I teach sales teams to embrace technology and multiply what is possible per employee.

Founder

2 years of effort went into the Prospeo.io Company/Contact API and this is why it was WELL worth the wait.

2 years ago Jon asked me, "If there were a database that could do anything you want, what would you wish it would do?"

I had a laundry list of ideas from

- Data accuracy and transperancy
- Organization tools for the team
- API capabilities

And then, I didn't hear from them for a little while. We kept using their email finding tool in all our Clay tables as a happy customer of course but I thought they were just focusing on that.

Then Hugo reaches out to me and says, "Hey, we finished the database the way you wanted. Want to have a look?"

I sign in to Prospeo V2 and my mouth is on the floor of everything they built. Good things definitely take time and they crushed it on this one.

I go over my favorite parts in the video down below but here are my favorite features you should check out if you don't watch the video and go straight to the site.

- Data quantity - I did comparisons of searches against Sales Navigator and was extemely happy with the counts that come back for the same filters on people and company searches in sales nav vs. prospeo

- Data quality - Every profile I checked worked at the company Prospeo says that they work at. I tried to be sneaky and check a friend that I know changed jobs a week ago and they already had that in their database.

- Email quality - All emails are SMTP verified with bounceban on top of that.
The API is so great. I just spent the christmas break making a company database we are going to scrap and just use their's.

- When you enrich a person, you get the company data with the API response so you don't have to worry about double spending on companies!

- The platform is so fast to make searches in.

- Your team can visually make searches and then click a button to get all of the JSON of that search to quickly get that search with their API.

I think they are just starting to launch it and I would highly recommend checking it out to help with your company and contact finding workflows. 

We are starting to switch a lot of TAM links internally over to them so we can stop downloading and uploading so many CSVs!

Not paid to post this or anything. 

Just found it last week and thought they did a really great job and other people would like to see it!

Check it out here! 

https://lnkd.in/dJw9eAEy

Founder Growth Engine X | Clay Enterprise Partner

Tomorrow, join me and many other outbound minds to discuss the state of outbound in 2026. (of course focused on cold email because I'm not qualified to talk about anything else). 

We’ll cover the dreaded Gmail AI filter tweet that hasn’t even been rolled out yet that everyone is asking about. 

Deliverability trends we are seeing from sending 7M emails per month on behalf of our customers

The way data is getting more accurate and cheaper and combining this with AI can cheaply laser target your ICP. 

I’ll leave the link to register in the comments. Hope to see you there! 

Vaibhav Namburi
Harris Kenny
Nick Abraham
Wesley Hoang 🛠️♠️
Alex Fine🌲
Christian Oland
Matthew Lucero
Enzo Carasso 🧲

I built a way to monitor your customer's LinkedIn content with a RapidAPI endpoint and Cursor so you can reach out to your ICP and name drop a customer they have heard of. Here's the step by step on how to do it.

I think one of the best ways that we can reach out to an ICP is if they already know of one of our successful case studies. 

You could ask your customer for a referral, but that puts work on them. 

You can monitor who they already know and reach out as if it's a regular message, and the prospect will actually have heard of the social proof you're mentioning. 

To set this up, all I did was give a voice note while walking my dog and Cursor took care of the rest. 

I hope you can even copy and paste this post and give some more context and set it up yourself. 

Step 1

Get the Rapid API endpoint. If you comment "monitor", I'll send it to you. Sorry to play this game but LinkedIn hates external links. 

Step 2

Use the MCP in RapidAPI and connect that to Cursor

Step 3

Explain what you want it to do. 

"Hey Cursor, I want to use this endpoint to build a micro app that I can enter a comma separated list of linkedin companies. I want you to 

1) find all of the posts of the linkedin companies
2) Find all of the people that work at the company and find their posts
3) Pull all of the people that have liked and commented on the posts and filter for XYZ titles and company size. 

Step 4

Add a little bit more to the prompt above about how you exactly want this to work.

Step 5

Enter Plan mode in Cursor. Drop your prompts and watch the plan

Step 6 

Edit/Approve the plan. I was lucky that Gemini Flash got this done in one shot, so I'm hoping I can pass this on and help others use it too. 

Again, comment "monitor" and I'll send it to you but if you don't want to wait for me, searching rapidapi(.)com(user)apibuilderz should help those that want to search on their own!

This workflow I made with Cursor and hosted on Railway saves me 6 hours a week on email deliverability tasks and our customers get much more consistent results from it. 

Over the last 6 months, we really systematized our email deliverability infrastructure. 

No more guessing and then ordering domains that we thought felt right. I built an SOP for everyone that I can give away at the end of the post. 

We would miss customers. Over order for some, under order for others. It was crazy. 

So we got extremely scientific about it. 

We keep all domains marked as status, Active, Insurance, or Cancel in Supabase. 

We always want to keep AT LEAST 50% of our Active daily sending volume in Insurance so that we can always rotate our domains. 

Every Friday, I would use a python script that would get the reply rates of all the domains in our campaigns so I could make decisions of what should be cancelled and what should be rotated from Insurance to Active. 

Once I had the numbers, spreadsheet warfare would begin. 

Making sure that every customer had enough and we didn't cancel too many domains. Numbers wouldn't look right so I'd check them manually. It was a mess.

Now, every Friday, I run this little Preview Global Rebatch and it send me a slack message with every customer, their daily send goal, how many domains are active, how many domains do we suggest to cancel, how many domains I need to buy more of, etc. 

And I hit accept and not only does it change all the statuses in our Supabase, it also pulls all of our customer's campaigns and swaps out the old domains for new domains. 

Easily my favorite workflow for deliverability. 

If you want our email deliverability SOP that goes over how we do this and how we work with Hypertide.io and Zapmail.ai to get it done, comment "primary" and I'll comment it back to you!

Here's the prompt to get you started building your own google maps scraper with Claude code or Cursor. 

One of my favorite things about LLMs and coding is that my team can build things that impact our business and then everyone can use. Bharatt Arorah built this google maps scraper for us and it's been so easy to use. 

Then when someone else on the team wants to add to it, it'd be really easy for them. 

This scraper is built on a RapidAPI endpoint that gives us 3,000,000 requests per month for $100 a month. 

Here's the prompt I'd give for Cursor or Claude Code to figure this out for you. 

First connect to the Rapid API MCP and then run this because it'll ask you to restart. (I don't use the MCP to actually run the code. I just use it to connect to the documentation to help set everything up). 

If you need the list of zip codes don't ask me or your mother for it. Ask Chat GPT literally asking "Do you know of any GitHub repositories that have all of the zip codes in the United States, or any other public ways that you can download that information easily?" and it'll come up, I promise. 

Long Text not optimized for a linkedin post AT ALL. 

Hey cursor, can you explore this Google Maps endpoint and build a plan for me that would be able to create an input where I can say a Google category, and then you'd be able to scrape it?

Here is a file of all the zip codes around the United States so that you have something to parse by. Search every one of these zip codes with my keyword to then find the companies that are in those areas. Build something into it that includes logic that, if a company is in a different business category that is excluded from my results, I want to be able to filter for the category. Let me know if we could exclude the cities and also run multiple category searches in one run. Set up the database schema to pull the zip codes from SupaBase. Literally go one by one doing a search across each of the zip codes. I also might wanna specify that I want to include certain cities, exclude certain cities, or include and exclude states in the future as well. Let's also add the filters for that to be possible as well. 

Hope that helps and provides a good lead gen project for people trying to get into coding with Cursor or Claude code.

Send those companies over to a Clay webhook to have a contact finding waterfall and you're all set!

I have to admit, six months ago I didn't get the point of MCPs.         
                                         
This post is for people who were like me. Also for my employees who are reluctant to start using these tools.                     
                                         
What is an MCP (Model Context Protocol)?                    
                                         
Think of it as a gateway for an AI agent to understand a tool.         
                                         
Instead of asking an agent to read API documentation (it will miss things),  
you connect it to an MCP. The agent figures out:                
 - What endpoints exist                             
 - What payloads to send                            
 - How to actually accomplish your task                     
                                         
Then you ask it to write the TypeScript or Python to make those API calls   
directly.                                   
                                         
Way more efficient. Way fewer tokens.                     
                                         
 My biggest tip:                                
                                         
 We're not actually doing a lot of work with MCPs as in moving data or doing work with MCP.             
                                         
We use them so agents understand the API documentation better.         
                                         
The MCP helps the agent learn the tool. Then we have Claude write actual code that calls the APIs.                                
                                         
That's the workflow:   
                           
 1. Connect MCP                                 
 2. Agent learns the tool                            
 3. Agent writes the automation code                      
 4. You run the code directly                          
                                        
 If you've been confused about MCPs, hopefully this helps.

A couple of customers have asked me what I think about this announcement from Google and here's my humble prediction. 

I'm not going to be naive and say that this won't have any affect on cold email. But also, even the video doesn't explain very well what this will do. 

I think that there is a best case scenario and a worst case scenario. 

Best case - this is an overall summarization of the email meaning that the preview text we optimize our first lines for today won't be as important as optimizing for how the summary will come across. 

A recipient can see the offer (maybe even stated cleaner than what an average copywriter can do) and choose to open or disregard. 

Worst case - it becomes a new spam filter and labels all external emails you haven't received before as spam with no preview. 

I truly think the actual outcome will be somewhere in the middle and lead magnets will become more and more important so you aren't just pitching calls and getting hung up in the spam filters. 

Truly, no one knows but it's not in my inbox yet but excited to see it when it is so we can start playing with it and see how it affects the channel.

Founder - Content Marketing Media and Co-Founder - Cobalt Keys. Elite approaches to Cold Email, Lead Generation, AI Agents, and Visibility. Certified @Clay and @Instantly Experts and Partners.

Besides building and launching Signaliz.com, at CMM we are proud to be the only known company globally with certified expertise in Clay, Instantly, Hey Reach, Octave and Maildoso: The five cornerstone platforms that power modern outbound strategy. This unique combination allows us to deliver a fully integrated lead generation, outreach, messaging, and deliverability solution that no other agency can match.

Our done-for-you approach delivers consistent results through:

- Advanced AI and API-powered workflows that adapt to your evolving needs
- Strategic implementation focused on building sustainable growth pipelines
- Data-driven methodologies that prioritize measurable ROI

We've developed other strategic partnerships with industry leaders while continuously developing new collaborations with specialists in outbound video, email verification, and critical lead generation technologies.

Partner with us to experience our unique approach: qualified leads, meaningful meetings, and tangible growth that strengthens your competitive advantage.

Josh Whitfield

"COLD EMAIL IS DEAD" - "GOOGLE KILLED COLD EMAIL"

This is the problem with this headline click bait....guess my inboxes didn't get the message! 

Clearly great offers plus great solutions still get results!  Thank you Instantly.ai

Founder @ Signaliz & CMM | Building Intentional Outbound

Here are a few things agencies are doing in 2026 to get ahead:

1) Using Supabase: caching emails, verifications, results. Saving significant time and money by not paying for every API call.

2) Vibe coding in LOVEABLE. A few weeks ago, a client was left high and dry from a previous CRM vendor. We rebuilt their CRM in a day. To be fair it wasn't that complex but we integrated it into Instantly.ai to capture their replies in real time.

3) Digging deep on AI...using tools like Manus AI to understand layers of complexity with browser based and deep layer computer agents.

4) Understanding tools like Firecrawl and Cursor and how they can dramatically change your approach to finding data and lead generation.

2026 will be the year the AI alters work for the better, and if done right clients and results will benefit.

We’re on a mission to build the best email-finding tool in the world.

Over the last few weeks, we learned a critical lesson - Stop reinventing the wheel. Perfect the process.

Here’s exactly how we approached it 👇

1) We built a rock-solid foundation
Using Trigger.dev, Cursor and hundreds of GitHub commits, we created a repeatable, observable process where every run is traceable. Each run completes in under 99 seconds—critical because this needs to work synchronously inside tools like Clay

2) We expanded coverage with newer solutions - We brought in some new providers like BlitzAPI to improve reach without sacrificing speed.

3) We layered in proven powerhouse tools like LeadMagic, Prospeo.io, Icypeas, BetterEnrich, A-Leads and others—all orchestrated to maximize coverage, not complexity. Not to mention, these are the providers we use at CMM, sending 10+ million emails monthly, we know they work.

4) We obsessed over data quality, we studied the flow end to end and never compromised on one rule: Only verified emails.

Every result is validated using MillionVerifier and Bounceban—no exceptions.

Today, I believe we’ve landed on the best solution possible. Something agencies can rely on—and companies can scale with.

Looking ahead, we realized not everyone makes API calls or uses automation tools. So we made it simpler. We added a clean interface inside SIGNALIZ:

- Upload a CSV 
- Get results back fast.
- Export via webhook or download as a CSV—your choice.

Want to test it, comment "Email"....we will provide the deets on setting up a Signaliz account with 1000 credits which equals 1000 verified emails...

I made the classic founder mistake: I built what was impressive instead of what was useful. For months, I chased complexity, layered systems, agentic workflows, clever abstractions. It looked like progress. It wasn’t.

Over the last month, something clicked. We stripped everything back to the fundamentals:

Finding companies - Finding emails - Finding contacts - Finding signals

Nothing sexy. Nothing novel. Just the things that actually make money.

We run an agency too, and this is where the honesty comes in: if we can’t do these four things exceptionally well, no amount of AI sophistication matters. For us or our clients.

So yes, we’re still building a serious Signals platform. The API already exists, clients use it 250K times a month, but we’re done skipping the basics. 

Also, we are going to give users the ability to get credits when they need them, 100 or 100K, no more forcing a subscription when all you need to spend is $2.32 to get value.

Maybe this fails. That’s real. But if it works, something important changes.

When you need a clean, current list at 1/10th the cost of bloated data providers selling decayed data, you’ll have another option.

We’re committing to evolving with AI responsibly, building what actually works, and passing those savings to customers. Not to win headlines, to give the little guy a real chance, the same one we were given. Preview below...

We are seeing a new type of customer emerge and I am pretty excited:

1) They have a GTM team and/or Sales Team

2) They already have all the tools Clay - Common Room - Salesforce - HubSpot - Octave - Instantly.ai, RB2B and so many more....as the DJ at my wedding said "all the stuff" (story for a different time).
3) They are AI centric, see what is coming, and trying to balance where to spend their time and manage costs/ROI.

But...orchestration is hard, cohesiveness and putting it all together is not simple.

For example, how to connect SFDC Closed Losts - re-source Contact Data - enrich to see if they are in our revised ICP - create relevant messaging knowing they were back on our website yesterday.

Think about it....how do all these systems connect, where is there overlap, what is the perfect flow.

Pretty excited to be solving these problems. 

I think back to the days of being a Product Manager of 4 Agile teams at a Fortune 500 who build data science solutions, did RPA, implemented process automation, and worked with cloud data. Those days were preparing us for this change in GTM, and it is here.

It is starting to be more evident that even some of the biggest companies in the world still need us lego enthusiasts...one GTM block at a time.

Claude Code has been instrumental in helping me build some of our most robust API and MCP calls lately. Everything connects to GitHub, and from there we use Cursor to extract commits and publish workflows to Trigger.dev.

What’s been revolutionary is strapping together disparate API calls into organized flows that take advantage of:

→ No timeouts
→ Structured retries
→ Batching to mitigate volume
→ Eliminating rate limit challenges

We keep stacking more MCPs into this. A typical flow now looks something like:

Import a list via webhook → Run Exa to get company info → Use Firecrawl to extract signals → Find and Verify emails with seven providers → Push to CRM or outbound tools (honestly the easiest part)

GTM feels different now. Excited to keep finding faster, more orchestrated ways to push the envelope.

Have you noticed the shift in GTM? Since they are both friends and experts in the field, I pay attention to everything they say:

- 🦾Eric Nowoslawski sharing tips on finding locals businesses with Google Maps using Cursor.

- Brandon Charleson dropping the goods on context engineering, MCP servers, Claude Skills

- Michel Lieben 🧠 mentioning in a recent pod about using vibe coding to spin up tools for articles to highlight capabilities

These 3 lead some of the top agencies in the world. Like us, they have figured out that GTM is significantly changing in front of our eyes.

Cursor - Claude Code - MCP - Skills - md files.....git commits...

If you aren't exploring, you are falling behind. Make sure you are paying attention, because things are evolving faster than the .com era, I promise.

Let's give the backstory of building our newest api - Find Verified Email:

A few weeks ago we launched the first version of it. My devs at CMM put it through the ringer. Great coverage, they love it. But then one told me, I am still using waterfalls and finding more emails than we find. Challenge accepted!

Back to the drawing board. 
1) Implemented Trigger.dev to eliminate polling errors and stabilize volume
2) Did some mad Cursor coding to get the flow correct
3) Tested against every email finding and verifying tool I could test

Here is where we landed. Across tens of thousands of tests, we find the email 83% of the time. 74% are verified, including catch_alls. We kept the cost at 1 cent per verified email.

All in all, we got 9 stacked api calls. We are verifying using our agency standard, which gets us less than .005% bounce rates across millions of emails.

There is always going to be someone better, but I can sleep at night knowing we are cracking a code at scale, helping our agency and customers get better results, and constantly driving excellence in our business.

PS: All that hard work on copy and leads is for nothing if your email bounces...hence the focus.

Imagine being able to find companies, find contacts, find verified emails, or find signals. Except you don't need a plan...you get them when you need them. 

Staging in a list, importing and exporting where ever you want, when you want.

API - Webhook - CSV - Your Tools

Does such a thing exists...soon:)

For the last two weeks, we’ve been building an autonomous campaign builder for SIGNALIZ

To be clear, this isn’t an “AI SDR.”

Think about it like this:
1) You pull companies that match your ICP.
2) You find leads inside that ICP (and yes, you can map personas with tools like Octave).
3) We source emails using 7 different email providers, then verify them with validation and catch-all checks.
4) You enrich everything with signals, prompted, informed to your ICP
5) Using your own copy agents or a prompted copy framework, the campaign is created end-to-end.

This workflow will power our agency CMM so trust me, it will be good enough for production when launched.

And if that’s not enough:

a) LinkedIn messaging is built in
b) Campaigns can be exported to Instantly.ai or HeyReach.io
c) Everything can be scheduled and run on whatever cadence you want

Now for the hard part, because this system touches so many APIs, conditions, and workflows, it’s been the biggest technical challenge we’ve faced building Signaliz so far.

We don’t want a boring, cookie-cutter campaign builder, we want something you can test, evolve, make decisions with, and actually get results from.

That means dealing with:
- Rate limits
- Worker orchestration
- Long-running workflows
- Non-blocking, concurrent API calls

Today, we’re taking big steps forward.

Thanks to Cursor, Trigger.dev and learning how to properly manage edge functions in Supabase, we’re making serious progress.

- API calls that used to time out now completes reliably.
- Workflows with 10+ concurrent API calls run smoothly.
- A visual flow of every API call and cloud cost management

It’s a reminder of how much GTM is about to change. When tools absorb the complexity and pain, the game changes. Can’t wait to deploy our campaign builder and help shape the future of GTM. Onwards and upwards!

Things that will make us less popular than other Signals tools:

1) We won't pay you to post about us (sucks not being included in all those GTM graphs but our loss I guess)

2) We wont be slipping Benjamins over to big tools to integrate us...if they think we are worth the effort, we will gladly provide our well written API docs or MCP

3) We won't force charge your credit card after a generous free trial.

4) We will charge the same amount for credits at the beginning of the month and during mid month should you need more

5) We will always be cancel anytime and provide full roll-over credits because you paid for them and we don't have any investors to piss off.

Let me know if I missed anything...happy to add to our do not do list...

Raw, unedited - Building The Campaign - our most recent video:

1) finding companies
2) contacts
3) verifying emails
4) find signals with deep intelligence
5) pushing to Instanty and Heyreach using Clay

About time we tied it all together....

Just the technical capability it takes to stitch this together:

1) Find companies by agentic research, models, designated apis: based on your ICP, signals, whatever.

2) Find contacts using agentic research, get validated emails that are verified and with catchall verifcation

3) Build, schedule, choose the lead count

4) Draft copy, incorporate Octave agents, customized a saved CTAs, value props, etc.

5) Enrich copy with signals or prompt into personalization

6) Export to HeyReach or Instantly - or export to a list

7) Manage multiple clients and campaigns, saved drafts, improve any step.

It is coming - the future of campaign building with SIGNALIZ

If you are not thinking about how to orchestrate all of your processes using computer use and broswer agents, you should be. 

Trust me, the days of running tables and building campaigns, step by step, is coming to an end 💡

Searching for companies is always an act of congress, not anymore:

1) Search by your ICP, Prompt, Filters, Technographics
2) Comprehensive and detailed, includes revenue, social media URLs, etc.
3) Export to a list, CSV, webhook instantly
4) Cost effective and did I mention fast

See for yourself:

When I was a Product Manager, I led four agile teams:

 • Data science
 • Data implementation (cloud)
 • RPA (robotic process automation)
 • Process mining

The goal was ambitious: build productive, ROI-positive solutions that worked together across all four teams.

We lived in agile mode. Sprints, forward planning, constant alignment, and endless conversations about the definition of done.

Fast forward to today, in a slightly ironic twist of fate:

We’re now doing all four at the same time:

 • Building LLM-powered signals
 • Implementing backend edge functions, vectors, and workers
 • Automating workflows like email validation
 • Mapping and improving the process every single day

Back then, I never imagined I’d be building a SaaS that merged these disciplines into one system.

But that’s exactly what we’re doing now.

In 2026, we’ll launch our first major release: an end-to-end Signal Campaign Engine.

It brings the experience of a proven agency together with the world’s best technologies, designed to help teams grow faster, smarter, and with measurable ROI.

I can’t wait to show you what happens when all of this comes together 🚀

taplio

The Battle

🦾Eric Nowoslawski

Josh Whitfield

Followers

Posts

Engagements

Likes

Performance Score🦾Eric Nowoslawski's LinkedIn Performance

Performance ScoreJosh Whitfield's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

🦾Eric Nowoslawski

Josh Whitfield

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}🦾Eric Nowoslawski's LinkedIn Performance

Performance ScoreJosh Whitfield's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance Score🦾Eric Nowoslawski's LinkedIn Performance