Marketing and sales teams wanted a personal landing page for every contact, but building them by hand doesn't scale. I built a platform in eight weeks that does it: upload a contact list, map its columns to a template, preview with real data, and generate a unique page, with personal images, video, and forms, for every contact. It has run 1,000+ campaigns and generated 100K+ pages, processes around 100,000 contacts in roughly an hour, and serves each page in about 60ms.
At a glance
A landing page with someone's name, company, and a relevant message gets far more attention than a generic one. But making one per contact means copying a page thousands of times, and generating them all in one request either times out or freezes the app.
The company needed a reusable engine: any template, any contact list, any campaign, without a developer building each one.
A campaign owner uploads contacts, maps each column to a template variable, and previews the result with real contact data before anything is generated. Missing fields fall back to defaults instead of leaving gaps on the page.
Import contacts
CSV, Excel, Google Sheets, or JSON, with validation and duplicate checks.
Map the columns
Fields become variables like {{contact.firstname}}, with fallbacks.
Preview with real data
See exactly what a real contact's page will look like.
Generate in the background
Each contact is its own job, processed in parallel.
Share unique URLs
Every contact gets a page, tracked separately.
Collect and export
Form responses and activity, exported as CSV.
Generation never runs inside a web request. The job is split into one small task per contact and placed in Redis-backed queues. Workers process tasks in parallel, retry failures, pick up where they left off after a restart, and report progress to the dashboard. That's how the platform handles around 100,000 contacts in roughly an hour while the app stays responsive. Once generated, each page is served in about 60ms.
Pages can include video blocks with the contact's name, image, or company. Video is far heavier than text, so it runs in its own service and never slows down page generation.
Every page can also carry a form. Responses are saved against the campaign and the contact, shown in the dashboard, and exported as CSV alongside the generated URLs and activity.
1,000+
campaigns run
100K+
personalized pages generated
~100K/hour
contacts processed
~60ms
page response time
100,000 pages can't be built in one request. Small, retryable jobs make large campaigns reliable.
Trade-off: Job tracking, workers, and retries to build and run.
Video rendering is slow and heavy. Isolating it lets it scale separately and keeps page generation fast.
Trade-off: One more service to deploy and monitor.
Every spreadsheet names its columns differently. Mapping first means any template works with any list.
“We upload a contact list and an hour later everyone has their own page. We run it for every campaign now without needing a developer.”
A page generated for one specific person, using their name, company, image, or other details from your contact list. Each person gets their own URL, so you can see who visited and what they did.
Split the work into one small job per contact and process the jobs in the background with a queue. Workers run in parallel, retry failures, and report progress. Trying to do it all in one request is what makes most tools time out on large lists.
Yes. A video template can insert a contact's name, photo, or company. Because rendering video is heavy, it should run as its own service so it doesn't slow everything else down.
More work
2024
Vet clinic website that grew bookings from about 20 to 120 a week
2024
Executive search website: enquiries up from 7 to 20 a month
2026
D2C food store: 30K+ monthly visitors and 75% repeat customers
2026
AI chatbot SaaS: 30+ businesses and 100K+ messages handled a day