I've been running cold email campaigns for clients for 3 years and the biggest shift I've seen isn't the tools. It's what actually gets a reply. Personalization used to mean scraping a name and company from LinkedIn, dropping it in the first line, and hitting send. "Hey {FirstName}, I noticed {Company} and thought..." That worked in 2022. It's dead now. Everyone's doing it and prospects can spot a mail merge from the subject line. What changed for me was treating personalization like actual research instead of a data field. Here's what I started doing: → I scrape the prospect's entire website. Not just the homepage. Blog posts, service pages, case studies, about page, even their contact form if it's there. → Then I feed all of that into OpenAI and have it analyze what they actually do, who they serve, and what problems they're likely dealing with. The AI doesn't just summarize. It finds the specific details nobody mentions in generic outreach. So instead of "I saw you work in logistics," the email opens with "Noticed you handle cross border freight into Mexico. Your blog mentioned customs delays eating 15% of delivery windows." That's the kind of line that gets opened because it doesn't sound like 500 other emails they got that week. The reply rates went from 2-3% with generic personalization to 8-10% with actual research. One prospect replied last week: "Your email won because you actually read our site. Everyone else sent the same template." The system I built does this automatically. Scrapes the website. Analyzes every page. Generates icebreakers that reference non-obvious details. It writes openers like a human who spent 20 minutes studying their business, except it does it for 1,000 prospects in an hour. Here's what I learned building this: Small prompt details make a massive difference. Having OpenAI shorten company names naturally (say "Stripe" not "Stripe Inc.") and reference specific pages beyond the homepage makes it feel real. The difference between "I saw your website" and "I saw your freight tracking dashboard lets customers get ETAs without calling" is everything.

I was sharing our community with our senior developer/director and telling him that what we’re doing here is going to change how we structure things in the company and create better results using Claude Code. I’m currently part of the lead team developing the company’s AI assistant model with multiple structured agents and layered analysis systems designed to support precise sales and marketing execution. I told him that I couldn’t really afford an enterprise-level account for Claude, so I haven’t been able to fully test everything I’ve been learning here as a VIP member. He spoke with the higher-ups and secured a 5-seat plan for me so I can continue applying what I’ve been learning, help the business grow in the future, and train the team using @Jake Van Clief notes...

In Part 1, I was riding high. I had Chrome, Edge, and Firefox all running simultaneously, tripling my speed on a massive D365 rebilling project. I felt like I’d cracked the code to being "efficiently lazy." Link: Mini-Series Part 1: The "Manual Hell" Rebill Project · Clief Notes But the victory was short-lived. I was driving the car at 100mph, but I didn't realize how much fuel I was burning. The Crash: 3 Hours to Zero The next morning, I fired up all cylinders. It was beautiful—until it wasn't. In under 3 hours, I burned through my entire token allotment. I was dead in the water with a 1.5-hour wait until my limits reset. With the clock ticking and sales reps still needing updates, I had to go back to doing it manually. And that’s when the "Aha!" moment happened. The "Tab" Breakthrough While I was clicking and typing manually to pass the time, I realized something: I wasn't really using the mouse. I was mostly hitting Tab and Shift-Tab to navigate the D365 fields. I asked Claude: "Can Playwright just 'Tab' through the browser instead of searching for elements and taking screenshots for every move?" Claude’s answer: YES. My jaw dropped. From "Visual Driving" to "Macro Speed" The old workflow relied on Claude "seeing" the screen via screenshots to make sure it was in the right spot. It was accurate, but heavy. I had Claude rewrite the interior workflow to a deterministic loop: 1. The Setup: I open the URL, set the filters, and select the first row. 2. The Loop: * Tab to Invoice → Enter. 3. Repeat. I added small buffers (100ms between tabs, 4s for page loads) to ensure D365 could keep up. See the video for how the flow runs in real life! The Result: 90% Savings & 10x Efficiency I asked Claude to evaluate the two methods. The numbers were staggering: Old "Visual" Flow: - Tool Calls: ~500 calls per 50 orders - Token Usage: 100% (High Burn) - Logic: Screenshot-dependent (Slow)