CLIENT · CORPORATE REBELS
// product: viral loop
SPAN 01

Turn attendees into
brand ambassadors.

↳ annotation: enrich · composite · dispatch · share

01 / The Challenge

Creating a personalized “I’m Attending” social graphic for every summit attendee is a manual nightmare. Previous attempts with Photoshop templates yielded only ~50 assets, leaving huge organic reach on the table.

02 / The Protocol

We built a Viral Looppipeline. It scrapes each attendee’s LinkedIn profile for their photo, composites a branded asset in bulk with BannerBear, and dispatches it by email. No human ever touches it.

STACKMake / BannerBear / Clay
VOLUME215 Unique Assets
DISTRIBUTIONEmail / Self-Serve Form
FIG.02

The Viral Loop Engine

LIVE ARTIFACT
VIRAL LOOP ENGINERUNNING
ASSETS: 142
EST. REACH: 124.0k
Sarah Jenkins
Processing ID #8821
Clay: Fetch Profile
BannerBear: Composite
Kit: Dispatch Email
Queue
Waiting in queue…
Waiting in queue…
CORPORATE REBELS SUMMIT 2025 - 21&22 NOVEMBER - BARCELONA
Meet me at
Corporate
Rebels
Summit 2025
21&22 NOVEMBER
The future of work is already here. Are you in?
Sarah Jenkins
LinkedIn
Excited to join the Corporate Rebels summit next week! 🚀
▲ 42💬 8
Campaign Results
148k+
Organic LinkedIn Impressions
65
Attendees Posted (30% conv.)
€0
Ad Spend Required
Self-Serve Generator

Attendees outside the bulk run build their own image via a public form.

> corporate-rebels.com/summit-2025/image-generator
FIG.03

How the Loop Runs

7-TOOL PIPELINE

One attendee record goes in; one personalized, on-brand image comes out, through seven stacked tools. The bulk run handles ~70% of attendees automatically; everyone else self-serves through a public form that feeds the exact same pipeline.

Orchestration · Make
01
Scrape profilesPhantombuster
collect attendee LinkedIn photos
02
Enrich dataClay
fill in existing attendee info
03
Clean formattingOpenAI
fix ALL-CAPS names + casing
04
Composite imageBannerBear
personalized asset via API
05
Store + collectGoogle Sheets
data in, image URL back
06
Fire webhooksApps Script
trigger on each new row
07
OrchestrateMake
runs the loop end-to-end
Deliver
emailed to attendee · ready to post
Two intake paths
Path A · Bulk run~70%

Scraped + enriched attendees are generated in a single activation (191 images in ~5 minutes), then emailed automatically.

Path B · Self-servePublic form

Everyone outside the bulk run builds their own image through a public Typeform that feeds the same generation pipeline.

PER IMAGE →
1 Typeform response8 Make operations1 BannerBear credit
FIG.04

From “Nice to Have” to “Must Share”

CLAY → BANNERBEAR → KIT

The friction in sharing event excitement is usually asset creation. Attendees want to share, but they don’t have a designer. So the post never happens, and the organic reach evaporates.

By automating the design, we removed the friction. Clay enriches attendee emails with LinkedIn data, BannerBear places their headshot into a high-fidelity template, and Kit emails them a direct download link.

The result? A flood of “I’m attending!” posts that dominated the feed in the weeks before the summit. That is buzz money literally cannot buy.

Dynamic
Image Generation
Enriched
Participant Data
Zero
Manual Work
Viral
Network Effect
FIG.05

Results

CR SUMMIT 2025 · ORGANIC
189
Posted to LinkedIn

Attendees who shared their personalized image organically.

350k+
Organic Impressions

Estimated views across attendee posts in the run-up.

€15k+
Ad-Budget Equivalent

Spend needed to buy the same LinkedIn visibility.

191
Images / 5 min

Composited in a single automated Make activation.

↳ baseline: ~50 hand-made PSD images in the prior edition · target reach ~3,000 attendees

FIG.06

Field Report

“The summit was fantastic — and the buzz around the event was brilliant, both beforehand through the visuals and afterwards. Top collaboration, and we’re really happy with how smoothly it all ran. Let’s definitely look at doing it again next year.”

Pim de Morree

Pim de Morree

Co-founder, Corporate Rebels

Corporate Rebels

Next Case Study · QDN-01

Q-Dance: Controle Carla

View Case Study