Urgent.News

What's breaking now, across thousands of outlets.

Tech

From 3 lines to 2 cold emails: a worked example

Most cold emails fail before the first word because the writer never pinned down who they're writing to. Here's the method I use: start from three lines, then build two emails from them. It's fully worked below so you can copy it. Step 1: Write the 3 lines Niche: who you sell to, narrow enough that you could name 20 of them. One-line offer: the result you deliver, not the features. Three prospect…

Cold emails often fail before they even begin because the sender doesn't clearly identify who they're reaching out to. The process I recommend begins with three concise lines: the target niche, a one-line solution, and three potential customer personas. Let's break this down with an example.

First, outline the niche - who you're selling to. In this case, independent dental clinics with 2-5 chairs in the US. Next, define the one-line offer - the result you provide, not the features. Here, the service is filling last-minute cancelled appointments through text within an hour. Finally, identify three prospect types - practice owner-dentists, office managers, and clinics that recently added a new hygienist.

Once you've established these three lines, create two tailored emails. For the office manager, highlight their pain point - spending morning hours calling patients for a 2pm slot. Offer a solution that texts existing patients who requested an earlier appointment, with an average response time of 40 minutes and no extra front desk software needed. Keep it short, with one concrete number, one clear ask, and under 90 words.

For the owner-dentist, focus on revenue loss due to cancelled appointments. On average, a 3-chair clinic sees 4-6 same-day cancellations per week, amounting to roughly $80,000 in lost income annually. Present the text-based solution that refills these slots within the hour, without requiring office staff to make any calls. Ask if reviewing their own data on cancellations would be helpful.

A few guidelines to follow: each email should address one prospect type only, begin with a statement about the recipient, include one number, one ask, and under 100 words overall. The subject line should sound like it came from a colleague, lowercase with specificity. To try this method, write your three lines and apply the steps. If assistance is needed drafting the initial two emails, send your three lines to survivorops@atomicmail.ai for a free sample.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I Published 24 Articles in 5 Days. Here's What Actually Moved — and What Took 3 Days to Show Up.

"I Published 24 Articles in 5 Days. Here's What Actually Moved — and What Took 3 Days to Show Up." published: true tags: seo, contentstrategy, webdev, indiehackers description: "A solo dev's content…

  • Developer published 24 articles in 5 days, boosting ToolVault's search visibility
  • Post on post-quantum cryptography climbed to top-10 pages within a day, gaining 18 visits
  • Google Search Console shows impact after 3-day lag, emphasizing importance of 72-hour evaluation

How to get eBay sold listings data in 2026 (findCompletedItems is dead)

If you build anything that needs eBay sold prices, 2026 broke your stack twice. Here is the current state of every route to completed listings data, and working code for the one that still works.

  • eBay removed findCompletedItems API in 2026, leaving developers without sold listings data access.
  • Marketplace Insights API limited release, requiring approved business case for access.

The Evil of Optional Parameters: When Having too Many Options is Self Destructing

You are the main developer of agents.com, an app that lets an organization manage an army of AI agents. You’re designing an admin page where an admin within an org can see each agent and the skills…

  • Optional parameters create contradictory and impossible states, confusing developers.
  • Defensive code required for consumers to interpret responses, increasing complexity.

"Your file never leaves your device": how to test that claim (and the Chromium catch)

Lots of web tools now say "runs in your browser, nothing is uploaded". I make one of them ( Drible , 53 file tools, 48 of which run client-side), and at some point I realised the claim was just a…

  • Many web tools claim client-side operation, but claim can be tested.
  • Test involves capturing network requests for file signatures and non-GET requests.
  • Chromium fails test due to not exposing file upload bodies to Playwright.

More from Saturday 10 October →