LongRun
All posts
Cold Email

AI Personalization That Does Not Sound Like AI: Our Perplexity + Claude Research Workflow

Jul 20, 20255 min read

You have seen the emails. "I loved your recent post" attached to a post you never wrote. A first line that swaps in your company name and nothing else. Every B2B buyer can now smell AI mass mail in about two seconds, and most of them delete it faster than that. If you are a founder running outbound yourself, the fear is reasonable: turn on AI personalization and you risk sounding like every other tool spraying the same template.

The problem is not AI. The problem is that most setups ask a model to write before it knows anything. We run it the other way: research first with Perplexity, write second with Claude, and gate everything behind a hard relevance check. Here is the exact workflow, why each step exists, and how it stays specific across tens of thousands of sends.

Why most AI personalization sounds like a robot

The default pattern is a single prompt: give a model a name, a title, and a company, then ask for a personalized opener. The model has no real information, so it does what models do when starved of facts. It generalizes. You get "as a leader in the SaaS space" or "I imagine scaling is top of mind." That is not personalization. That is a horoscope.

Real 1:1 writing needs a real fact the recipient recognizes as true and specific to them: a funding round that closed last month, a role they posted, a tool in their stack, a position they took on a podcast. The model cannot invent these without hallucinating, and a hallucinated detail is worse than no detail because it gets caught. So the fix is structural. You separate the job into two: a research step that finds verifiable facts, and a writing step that turns one good fact into one good sentence.

Step one: Perplexity does the research, not the writing

Perplexity runs first, inside our Clay tables, as an enrichment step against each prospect. We are not asking it to be clever. We ask it narrow, factual questions: what did this company announce in the last 90 days, what roles are they hiring for, what does the founder say publicly about their go to market. Because Perplexity returns sources, we can check whether a claim is real before it ever reaches the writing step.

This matters because the data underneath outbound is usually worse than people think. Decayed Apollo lists, stale titles, and people who changed jobs six months ago are the norm, not the exception. A research step that cites its sources is also a quality gate: if Perplexity finds nothing specific and nothing recent, that prospect gets routed to a generic, honest path or dropped, not forced into a fake personal line. We have run this across 1,800-plus production Clay tables and enriched 950,000-plus contacts, and the single biggest driver of reply quality is not the prompt, it is whether the research found something true.

Step two: Claude writes from the fact, with constraints

Claude gets the verified research and a tight brief. The rule we enforce: one specific fact, one sentence, then straight to the point of the email. We explicitly forbid the tells that mark a message as automated. No "I came across your profile." No "as a fellow founder." No restating the company's own tagline back at them. The opener references the real fact, and the rest of the email is about the recipient's likely problem, not our product.

The constraints are doing most of the work here. A model writing freely drifts toward marketing language. A model handed a fact and told to write four short, plain sentences for a busy engineer stays grounded. We also pin tone to the sender, not to a generic "professional" register, because a real person wrote it and a real person will reply to it. This is the same approach behind our ATI campaign: 78,000 emails, a 37 percent positive reply rate, and 300,000-plus CAD in pipeline, where the personalization was tied to specifics about each retailer rather than a swapped variable.

Step three: pair personalization with a trigger, not just a fact

A specific fact is good. A specific fact plus a reason you are reaching out now is better. We feed signal-based triggers into the same workflow: a funding event, a hiring spike, a tech-stack change, a job change at the account. The research confirms the signal, Claude writes to it, and the email answers the question every recipient asks silently: why me, why now.

This is how the Chateau Constellation campaign reached 177 interested wine importers, by timing outreach to trade-fair calendars, and how LeverageRx pulled 143 interested physicians from a single campaign at a 46 percent positive share. The personalization was not decoration. It was the reason the timing made sense to the person reading it.

Why this holds up at volume (and where deliverability fits)

None of this matters if the email lands in spam, and over-templated, low-relevance mail is itself a spam signal: identical structure across thousands of sends trains filters to flag you. Genuinely varied, fact-grounded copy reads as human to both the recipient and the inbox provider. That, combined with proper sending infrastructure, is why we hold 98.5 percent average inbox placement against the roughly 60 percent typical of shared infra, with bounce between 0.15 and 0.9 percent.

The workflow scales because the expensive judgment, finding a true and recent fact, is automated by the research step, and the writing is constrained enough to stay consistent. For the operator who keeps saying "my specialty is not sales, I'm an engineer," the point is that you should not be hand-researching prospects at 11pm. A system does the research and the first draft; you spend your hour a week on the replies that matter. See how the full 3-month pilot assembles this, or run your copy through the free spam words checker before you send.

FAQ

Questions, answered.

Will recipients be able to tell the email was written with AI?
Not if the workflow is built correctly. What gives AI mail away is generic, fact-free language, not the use of a model. When the email opens with a true, specific, recent detail about the recipient and then gets to the point in plain sentences, it reads the way a person who did their homework would write. The research step is what makes this possible: Claude only writes from facts Perplexity verified with sources, so there is nothing vague or invented to expose it.
Why use both Perplexity and Claude instead of one model for everything?
They do different jobs. Perplexity is the research layer: it finds and cites verifiable facts about a prospect, which lets us check that a detail is real and recent before using it. Claude is the writing layer: handed a verified fact and tight constraints, it produces a sentence that sounds human and specific. Asking one model to research and write in a single prompt is where hallucinated details and generic openers come from, because the model fills gaps with guesses instead of facts.
Does AI personalization help or hurt deliverability?
Done well, it helps. Inbox filters penalize sending patterns that look templated and identical across thousands of messages. Copy that is genuinely varied and grounded in real, prospect-specific facts looks human to filters as well as to people. Paired with dedicated domains and warmed mailboxes, this is part of how we hold 98.5 percent average inbox placement versus roughly 60 percent on shared infrastructure. Personalization is not a deliverability trick on its own, but uniform mass mail actively works against you.

Want this built and run for you?

LongRun builds the outbound system, runs it, and hands it over at day 90. Book a strategy call to scope yours.