SMF·SENDSPARK
Can a prompt replace Sendspark?
Screen recording — screen recording, walkthroughs and product demos
Exhibit tracking slip
Verdict
Sendspark's actual mechanic is narrow and clever: one recording, and a personalised first frame per recipient — their name written on screen, their own website behind it — so the thumbnail in the email looks made for them. Generating those frames from a CSV and serving a page per recipient is a weekend. What it also is, unavoidably, is bulk outreach tooling, and a build like this deserves guardrails rather than a throughput setting.
Exhibit A — The prompt
Received on31.07.2026Build a personalised video landing-page generator. It produces links; it never sends anything.
Recording: capture screen, camera, or both with the camera as a corner overlay, using the browser's own capture APIs with an explicit permission prompt and a visible recording indicator. Save locally as WebM and transcode to MP4 with ffmpeg.
Recipients: import a CSV with columns for name, company, email and an optional website URL. Validate the file and show a per-row preview before anything is generated. Cap the batch at a modest number, defaulting to 50, and require an explicit acknowledgement to raise it — see the note on scope below.
Personalised opening frame, which is the mechanic. For each recipient, generate a still frame composited from: the video's own first frame, the recipient's name and company rendered in a chosen style, and optionally a screenshot of their website captured by a headless browser. The generated frame becomes the video's poster image and its first second, so the thumbnail in an email reads as made for that person. Cache website screenshots by domain, respect robots.txt, and skip a site that refuses rather than retrying.
Landing page per recipient: a static page at an unguessable URL with the video, a heading using their name, a short message with template variables filled from their row, and one call-to-action button the sender configures. Pages are static files, so serving a hundred of them costs nothing.
Output: a CSV back, with the original rows plus each recipient's page URL and poster image path, ready for the sender to use in whatever they already send email with.
Analytics, kept minimal and honest: count page opens and video plays per recipient, storing only a count and a first-seen timestamp. Do not store IP addresses, user agents, or approximate locations, and do not notify in real time. The point is knowing whether a message landed, not watching someone.
Scope guardrails, stated in the README and enforced in the build: this tool does not send email, does not hold a mailing list, does not import contacts from anywhere, and does not integrate with an email platform. It generates assets for messages a person sends deliberately, one at a time or in a small batch. Bulk personalised video is one small step from bulk unsolicited email, and the batch cap and the absence of a sender are the design saying so.
Out of scope: sending email, CRM integration, sequences or follow-ups, a hosted service, and any contact enrichment or discovery.
Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the CRM integrations that pull the recipient list and log the send
- B.2 hosted delivery and the video CDN behind it
- B.3 the email sequence tooling that actually sends the messages
- B.4 engagement notifications routed to a sales team
Prior art
Exhibit C — Why people still pay: capture polish, hosting, and collaboration
Because it only works inside the outreach workflow. A folder of links you paste by hand is not a sales tool; a button inside the CRM that generates and sends is.
Questions
Can I import my Sendspark videos and contacts?
Videos download and can be re-uploaded. Contacts export as CSV, which is exactly the input format here. Existing landing-page URLs stop working when you leave, so anything already sent should be allowed to expire naturally.
Why cap the batch size?
Because the difference between thoughtful outreach and spam is volume, and a tool that makes ten thousand personalised videos as easy as ten is a tool for the second thing. The cap is a speed bump with an acknowledgement behind it rather than a hard limit, but it is deliberate.
What does it cost to run?
Static pages and video files on cheap object storage with a CDN in front, so a few dollars a month plus egress. Website screenshots run locally through a headless browser at no cost. The heaviest term is video bandwidth if a campaign actually gets watched.
What is the one thing that does not survive the rebuild?
Being in the workflow. Sendspark generates the video from inside the CRM, drops the link into the sequence, and tells the rep when it was watched. A folder of links and a CSV is the same asset with all the leverage removed.
Related tools
Receipt