B2B Prospecting With AI Without Spam: Research Accounts First

B2B Prospecting With AI Without Spam: Research Accounts First

B2B prospecting with AI works best when the AI researches and prepares, and a human decides and holds the conversation. The most useful job for AI is understanding the account (what it does, where it is right now, who decides) and drafting outreach that only makes sense for that account, while respecting LGPD (Brazil's data protection law) and clear contact limits. Sending the same text to a huge list with the names swapped is spam, with AI or without it.

Key takeaways

• AI adds more value in account research and preparation than in sending messages.
• Use only public, professional sources, record where each piece of information came from, and discard personal data that does not help the outreach.
• Set limits in writing: who can be contacted, through which channel, how many times, and how a person opts out.
• Keep a person approving every first message, at least during the pilot.
• Start with a small list of accounts, one relevance hypothesis per account, and a metric agreed before you expand.

What changes when AI researches the account instead of blasting messages?

In mass prospecting, the bottleneck looks like volume: more contacts, more messages, more chances. The problem is that reply rates depend on relevance, and relevance requires understanding who is on the other side. That is exactly the work that gets skipped for lack of time, and it is where AI genuinely helps.

A language model can read a company's website, job postings, press releases, public interviews and event materials, then summarize in a few paragraphs what the company sells, to whom, what changed recently and which operational problems it probably faces. It can also suggest relevance hypotheses: why this conversation would make sense now, and for which role.

What AI should not do on its own is decide who to contact, state facts without a source, or send the message. Research and drafting are good tasks for automation. Choosing the approach and sending remain commercial decisions, with a named owner. This split is also a good general test, which we explain in what not to delegate to AI in business.

Which sources can AI use, and where does LGPD come in?

Start by separating company data from personal data. Information about the organization (segment, products, apparent size, open roles, news, announced partnerships) carries low risk. Information about individuals needs more care, even when it is published.

A practical rule for the research:

• Prioritize institutional sources: the company website, careers page, press releases, and event materials where the person took part as a company representative.
• Use personal data only to the minimum necessary: name, job title, company and professional channel.
• Do not collect or infer sensitive data, personal life, family, health, political opinion or religion, even if it appears on public profiles.
• Do not use purchased or leaked databases without knowing their origin and legal basis.
• Keep the source link for every claim used in the outreach.

LGPD allows more than one legal basis for processing data, and legitimate interest is the one most often discussed for B2B prospecting. It is not a blank check: it requires a legitimate purpose, proportionate use, transparency and the person's ability to object. The decision about which basis to use and how to document it should go through your legal counsel or data protection officer. The guidance published by ANPD, Brazil's data protection authority, is a good starting point for aligning that decision.

If the project involves broader processing or profiling, consider an impact assessment. And if any step produces automated decisions that affect a person, the right to review under the law comes into play, as we detail in automated decisions under LGPD.

Step by step: researching an account with AI

This routine works in a spreadsheet, a CRM or your own tool. The key point is that every step leaves a record someone else can check.

• Step one: define the ideal account profile in plain language (segment, type of operation, signs of need) and list which public signals show that an account fits.
• Step two: choose a short list of accounts, picked by humans, and confirm each one has a real reason to be there.
• Step three: ask the AI for an account dossier in a fixed format: what it does, who it sells to, recent changes, likely pain points and open questions. Every claim must come with a source link.
• Step four: mark what the AI could not find. A declared gap is worth more than invented filler.
• Step five: identify the roles likely to take part in the decision and confirm the names in a professional source, never from the model's guess.
• Step six: ask for a relevance hypothesis in one sentence, linking a verifiable fact about the account to the problem you solve.
• Step seven: write a short first message from that hypothesis and send it for human review.
• Step eight: record in the CRM the source, the legal basis adopted, the contact date and the outcome.

One important technical caution: web pages can contain text that tries to instruct the model, known as prompt injection. If the agent reads third-party content, treat that content as data, not as instructions, and do not give the agent permission to send messages or change the CRM without approval. OWASP publishes a guide on preventing prompt injection that describes practical controls for this.

How do you turn the research into relevant outreach?

Good outreach has three parts: a specific fact about the account, an honest connection to what you do, and a small ask. If any part could be swapped for another company without the text losing its meaning, the message is still generic.

Illustrative scenario: a company that sells fleet management software researches a regional carrier. The dossier shows, from public sources, that the carrier posted openings for dispatchers and announced a new branch. The relevance hypothesis is that the expansion increases the complexity of routing and delivery tracking. The message to the operations manager mentions the new branch, asks how the team tracks deliveries today, and offers to send a short resource, without asking for a meeting right away. If the dossier had not found the branch, the AI should flag the gap, and the salesperson would decide whether this account is worth approaching now.

A few criteria for reviewing the draft before sending:

• Every fact cited has a source that a person has checked.
• The message does not suggest intimate knowledge of the contact's life.
• The ask is proportionate: one question or one resource, not a long calendar block.
• There is a clear way out, such as saying it is not relevant and being removed from the list.
• The tone is that of someone who works at your company, not a model trying to sound friendly.

If the conversation moves forward, later qualification can use direct questions and the context already collected. For that stage, see how to qualify leads on WhatsApp with AI without turning the contact into a form.

Which contact limits should you set before starting?

Limits are what separate prospecting from commercial harassment. Define them before the first message goes out, and write them in a one-page document that the team and the tool both follow.

The minimum to decide:

• Allowed channels for first contact: work email, LinkedIn, business phone. For WhatsApp, outbound contact needs extra care.
• Maximum number of attempts per person and per account, and the minimum interval between them.
• How many people at the same company can be approached at once, so the account does not receive repeated messages from different teams.
• A stop rule: with no reply after the limit, the account leaves the cadence for a defined period.
• A suppression list: anyone who asked not to be contacted never comes back, and this applies to parallel tools and spreadsheets too.
• Send times and days that fit a professional routine.

On WhatsApp, platform rules weigh as much as the law. Outbound messages require prior consent and approved templates, and abusing them can get your number blocked. The details are in WhatsApp outbound messages: templates, opt-in and best practices. For cold prospecting, a different channel is usually more appropriate, and WhatsApp comes in after the person has shown interest.

Finally, treat an opt-out request as a priority event. If someone replies asking you to stop, the removal should be recorded the same day and honored in every system. This is also where the right to object under LGPD shows up in practice.

How do you apply map, limit, pilot and hand off?

The method we use for AI projects fits here with little adaptation.

Map: describe how prospecting works today. Who chooses accounts, where the information lives, how long research takes, what usually goes wrong, and what the current reply rate looks like. Without that baseline, you cannot tell whether AI improved anything.

Limit: define which data the agent can read, which tools it can use and which actions require approval. For prospecting, we recommend that the agent reads public sources and writes drafts, while sending and changing CRM records stay with a person. If you will connect it to your CRM, the article on integrating AI with your CRM through API, webhooks or MCP helps you choose the path with the lowest permission level needed.

Pilot: choose one segment and a small list of accounts, run the full flow with logs, and agree on a metric before you start. Good metrics combine quality and efficiency: preparation time per account, share of drafts approved without major edits, relevant replies and opt-out requests. To structure your decision criteria, see how to measure an AI automation pilot.

Hand off: at the end of the pilot, give the team the standard dossier, the limit rules, the records and a named owner. Then decide whether to expand, adjust or stop. Stopping is a legitimate result if the research did not improve the conversation. Anthropic recommends starting with the simplest solution and increasing autonomy only when there is evidence, and the same reasoning applies here. For a broader view of risk management, the NIST AI Risk Management Framework is a useful reference.

Frequently asked questions

Can I use AI to build contact lists and send at scale? You can use it to support research, but scale without relevance tends to produce complaints, blocked channels and legal risk. The safer path is to limit volume, review every first message and honor opt-out requests. If your contact base has an uncertain origin, resolve that before any automation.

Does LGPD prohibit B2B prospecting? There is no general prohibition, but the law requires a legal basis, a clear purpose, proportionate use and respect for the data subject's rights, including the right to object. Which basis to use and how to document it is a decision to make with your legal counsel or data protection officer, consulting ANPD guidance.

Can the AI write and send the first message on its own? Technically it can, but we do not recommend it at the start. The risk of unsourced claims, an inappropriate tone or repeated contact is larger than the time saved. Keep human approval on sending during the pilot, and loosen that control only based on data from your own flow.

How long does it take to know whether it works? It depends on your sales cycle, but the pilot should be short enough to allow adjustments and long enough to observe real replies. Define success in advance, for example less preparation time at the same quality, and evaluate the research and the conversation separately, because one can improve without the other.

Sources

• ANPD: Autoridade Nacional de Proteção de Dados
• OWASP: prevenção de prompt injection
• Anthropic: Building effective agents
• NIST AI Risk Management Framework