In Q4 2025 we ran a 6-week Creator-Led Pipeline Pilot for Engine, a cloud infrastructure tool in closed beta. This is the full attribution data — every creator, every UTM, every conversion event. We're publishing this because the devtool marketing industry runs on vague claims and undisclosed results, and we believe transparency builds trust. Here is exactly what happened.
// Campaign Setup & Hypothesis
Engine needed developers to sign up for their closed beta. They had a genuinely strong product — a container orchestration tool that simplified Kubernetes cluster management — but no organic distribution. Their LinkedIn ads were producing $180+ CPAs with low-intent signups. Their paid search was burning budget on keywords that attracted the wrong developers. Our hypothesis: 5 technical creators in the cloud infrastructure space could drive higher-intent trials at a fraction of the LinkedIn CPA.
The brief to Engine before the pilot started: "If our creators do their job, your signups will activate at a meaningfully higher rate than your paid search leads, because the people arriving have already seen 15–20 minutes of your product being used by an engineer they trust. You're not starting from zero. You're starting from 'I've seen this work in the hands of someone like me.'"
Budget allocation for the pilot: $8.5K management fee + $31.5K creator fees (pass-through at cost) = $40K total. 773 signups = $51.75 CPA. Previous paid search CPA was $143. LinkedIn CPA was $182.
// Creator Selection Process
We built a 47-creator universe across cloud-native, DevOps, and infrastructure content. Sources: YouTube channels with relevant content, LinkedIn thought leaders in the DevOps space, technical newsletter authors, Discord community moderators, and open-source contributors with large GitHub followings in the Kubernetes/container ecosystem.
From that universe we ran each creator through our 11-point rubric (see How to Vet a Technical Creator in 20 Minutes). The 5 selected creators and their contribution:
- Creator A: Cloud infrastructure YouTuber, 82K subscribers — 312 signups (40%). Primary vehicle: 24-minute tutorial on container orchestration with Engine.
- Creator B: DevOps newsletter, 14K readers — 187 signups (24%). Primary vehicle: deep-dive newsletter issue comparing container orchestration approaches.
- Creator C: LinkedIn technical thought leader, 28K followers — 142 signups (18%). Primary vehicle: 3 LinkedIn posts across 3 weeks covering different aspects of Engine's architecture.
- Creator D: Open source contributor, Discord community lead — 89 signups (12%). Primary vehicle: organic community discussion seeding + Discord AMA.
- Creator E: Technical blogger, high domain authority in DevOps space — 43 signups (6%). Primary vehicle: written tutorial + comparison post.
// Content That Drove Results
Creator A's 24-minute YouTube tutorial ("Building a production-ready container orchestration setup with Engine") drove 40% of all signups and ranked on YouTube search within 3 weeks for "container orchestration setup" and "Engine Kubernetes alternative." The video was genuinely technical — it showed real configuration, real edge cases, and real performance benchmarks. It didn't feel like a sponsored video; it felt like a senior engineer sharing a real workflow decision.
Creator B's newsletter performed better than expected because their audience skews senior (engineering managers and staff engineers who are actively evaluating tools). The average trial from Creator B's newsletter had a 7.2% trial-to-demo rate vs. the campaign average of 5.3%.
Creator D's Discord seeding drove the lowest volume (89 signups) but the highest-intent leads: 9 of 89 (10.1%) progressed to demo request — double the campaign average. Community-sourced signups came in already having asked questions about Engine, often already having read the docs.
// Full Attribution Methodology
Every creator had a unique UTM source and a dedicated landing page variant. The UTM structure:
- utm_source=youtube / newsletter / linkedin / discord / blog
- utm_medium=creator
- utm_campaign=engine-pilot-q4-2025
- utm_content=creator_a_container_tutorial (unique per creator per piece)
The UTM links were placed in YouTube descriptions (above the fold), in newsletter text, in LinkedIn post comments, and in Discord pins. Every landing page preserved the UTM source through the beta signup form into Engine's CRM (HubSpot). We ran a 2-week audit after signup to verify attribution was intact across 98.3% of signups.
// What Didn't Work
Short-form content underperformed significantly. Creator C ran a LinkedIn experiment with a 60-second video alongside their standard text posts. The video got 3x the impressions and 0.3x the clicks. Developers on LinkedIn engage deeply with text posts from credible engineers; they scroll past short-form video.
Creator E's "Top 5 Kubernetes Alternatives" listicle format drove clicks but poor conversion. The trial activation rate from listicle traffic was 28% vs. 61% for tutorial/deep-dive content. Readers who came through listicles weren't ready to try Engine — they were still in comparison mode.
We also had one creator brief go poorly: a written brief without a technical review led to a blog post that described Engine's architecture incorrectly. The post was corrected within 48 hours but the 6-hour window where it was live drove 23 signups who churned immediately — they had been misled about a capability the product didn't have.
// The SQL Data
41 of 773 signups (5.3%) progressed to demo request within 6 weeks of trial start. Of those 41 demos, 12 progressed to active sales opportunities within 90 days. 6 had closed or were at contract stage at the time of writing. Total influenced pipeline: $1.2M. Closed revenue attributable to the pilot at the time of writing: $290K.
For context, Engine's previous sales cycle from paid search lead to demo was averaging 67 days. From creator campaign trial to demo was 31 days. The creator-sourced trials moved faster because they arrived with existing product context.
// Key Lessons From This Campaign
- Long-form tutorial content (15–25 min) drives 4x the trial conversion of short-form content in the DevOps space.
- Creator selection by ICP specificity matters more than creator reach. Creator D (89 signups) drove better SQL rates than Creator E (43 signups) despite similar volumes.
- Technical brief quality is non-negotiable. One incorrect brief cost us 23 churned signups and a creator relationship that took 2 weeks to repair.
- Attribution must be built before day one. We had zero attribution gaps because we built the UTM structure before briefing any creator. Don't launch without it.