SMF·LEMLIST
Can a prompt replace Lemlist?
CRM & sales outreach — cold email personalisation
Exhibit tracking slip
Verdict
The signature trick — a screenshot or image with the recipient's company name burned into it, and a landing page addressed to them by name — is a sitting's work with a headless browser and an image library. That part genuinely rebuilds. The rest of lemlist is lemwarm, a network of thousands of real mailboxes warming each other, and that is a network effect you cannot join by writing code. Personalisation without deliverability is a beautifully addressed letter in a spam folder.
Exhibit A — The prompt
Received on31.07.2026Build a personalised-artefact generator for outreach. It produces images and one-page microsites; it never sends anything.
Stack: your choice, plus a headless browser (Playwright or Puppeteer) and Postgres. One command via Docker Compose, and the README must note that the browser image is large.
Templates are HTML with {{field}} placeholders and a declared output: image or page.
Image output: render the template at a fixed size and export PNG. Support two composition modes that cover most real use.
1. Overlay: place text and a logo at coordinates on a background image, with a per-field maximum width so a long company name shrinks or wraps instead of overflowing. Getting that right is most of the work.
2. Screenshot: load a URL taken from the recipient row, wait for network idle with a timeout, optionally dismiss cookie banners with a configurable selector list, and capture the viewport with an optional annotation drawn on top.
Page output: render to a static HTML file under a per-recipient random token, written to a folder any web server can serve. No JavaScript in the output, no tracking, no analytics — a page that phones home defeats the purpose.
Batch: take a CSV, generate one artefact per row, and write an output CSV with the original columns plus a local path or a URL. Make it resumable — a rerun skips rows whose artefact already exists — and cap concurrency, because a headless browser will happily eat every core you have.
Add a preview screen that renders three sample rows from the CSV before committing to the whole file, since template bugs are only visible on real data. Include a deliberately awkward sample: a very long company name, a name with accents, and an empty field.
Empty-field handling is a first-class decision: per placeholder, choose skip-the-row, use-a-fallback, or fail-the-batch. Never render "Hi {{firstName}}" literally.
Write tests for text fitting at the maximum width and for the empty-field policies.
Do not send email, do not connect a mailbox, and do not implement open or click tracking.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 lemwarm, the shared warm-up network across thousands of real mailboxes
- B.2 sending, scheduling and the deliverability operations behind them
- B.3 the lead database and the phone-number lookups sold as credits
- B.4 the multichannel steps that mix email with LinkedIn and calls
- B.5 inbox-placement reporting across providers
Exhibit C — Why people still pay: warm-up network
Because personalisation only pays off if the message is read, and being read is a deliverability problem that lemwarm exists to solve. The image generator is the demo; the warm-up network is the product.
Questions
Does personalised imagery actually lift replies?
It gets attention when it is specific and it is ignored when it is a template with a name pasted in. The screenshot-of-their-own-site variant tends to do better than a logo overlay, because it proves you looked.
Why generate static pages with no tracking?
Because a page that loads analytics from a third party is slower, easier to filter and, if you are emailing people in Europe, drags consent obligations into a cold outreach you probably cannot justify. A static page with a random token is enough.
How do I actually send these?
From your own mailbox, in small numbers, by hand or with the scheduler described in the Instantly entry. The artefact generator is deliberately decoupled so it cannot become a bulk sender by accident.
Can I export my lemlist campaigns?
Leads and campaign statistics export as CSV. The templates, images and lemwarm history do not come with you, so if a particular image template is working, rebuild it from the rendered output before you cancel.
Related tools
Receipt