tp tate@programs flow live
tate@programs ~/templates/launch-proof-promo-flow may 2026

elevencreative flow blueprint / public template

Turn launch evidence into short product clips people can actually verify.

Most promo videos start with a vibe and end with claims nobody can inspect. This flow starts with proof: repo status, shipped pages, sample reports, user workflow, and launch constraints. The output is a reusable set of scripts, scene prompts, captions, and QA checks for short launch videos.

open blueprint copy prompt pack submission plan sources
input
launch proof
output
3 promo cuts
rule
claim only what is shown

why this exists

A launch video should be a compact evidence system.

trend radar

The current creative-tool wave is moving toward reusable multi-modal workflows, not one-off clips. ElevenCreative Flows is a node canvas for image, video, speech, music, sound effects, and composition pipelines. Contra is running an ElevenCreative challenge around useful, reusable Flows templates.

The useful wedge for software builders is proof-led launch media: a short video that shows what shipped, what changed, what the buyer can trust, and which claims are backed by visible artifacts. That works for product launches, hackathon submissions, client handoffs, and paid review deliverables.

node blueprint

Reusable flow structure.

prompt pack

01 / intake

Proof Intake

Collect product name, audience, shipped URL, repo/package links, three concrete proof bullets, and claims that must not be made.

inputs: url, repo, claim_allowlist, claim_blocklist

02 / distill

Evidence Distiller

Convert messy launch notes into a short proof table: claim, visible evidence, user value, and confidence level.

output: verified_claims[]

03 / scripts

Three Script Variants

Create a 15-second hook, a 30-second buyer-proof cut, and a 45-second walkthrough without inventing numbers or outcomes.

output: hook, proof_cut, walkthrough

04 / scenes

Scene Prompt Builder

Turn each script beat into visual prompts: terminal frames, screenshot callouts, report snippets, UI transitions, and evidence overlays.

output: scene_prompt[]

05 / audio

Voice, Music, SFX

Generate plain narration, restrained music direction, and low-noise interface sound cues that do not bury the proof.

output: voice_script, music_brief, sfx_cues

06 / gate

Fact And Safety Gate

Flag unsupported claims, private data, hidden customer names, financial promises, unreadable captions, and clips that show sensitive tokens.

output: pass, revise, cut

prompt pack

Copy into the relevant Flows text nodes.

proof_distill.prompt

Evidence distiller

You are turning a software launch into proof-led promo material.

Use only the provided evidence. Do not invent adoption, revenue, awards, benchmarks, security status, customer names, or production usage.

Return:
1. Five verified proof bullets.
2. Three buyer-facing claims that are safe to say.
3. Three claims to avoid.
4. A one-line positioning sentence.
5. Any proof gaps that should be fixed before publishing.

script_variants.prompt

Three cuts

Create three concise video scripts from the verified proof table:

15s Hook:
- one problem
- one visible proof point
- one concrete result

30s Buyer Proof:
- who it is for
- what changed
- what the viewer can inspect
- call to action

45s Walkthrough:
- setup
- three visible steps
- final proof screen
- grounded next step

Keep the language direct. No hype words. No unsupported numbers.

scene_prompts.prompt

Visual system

Convert the selected script into a scene list.

Style: realistic software launch console, sharp typography, calm colors, visible proof callouts, terminal windows, browser frames, report snippets, repo/package badges, and clear captions.

For each scene return:
- duration
- visual prompt
- on-screen text
- evidence shown
- transition
- caption line

Every on-screen claim must map to a provided proof bullet.

fact_gate.prompt

Final gate

Review the script, captions, scene prompts, and source evidence.

Classify each line:
- pass: directly supported
- revise: close but too broad
- cut: unsupported, risky, private, or misleading

Also check:
- private keys, emails, addresses, tokens, and internal URLs
- claims of guaranteed revenue, safety, or compliance
- caption readability
- whether the CTA matches the actual offer

Return a publish decision and the exact edits required.

submission plan

How this becomes a challenge entry.

open Contra topic

build

Recreate the nodes in ElevenCreative Flows

Use the node structure and prompts above. Keep one generic software launch example and one Tate Programs example so the template feels reusable, not single-use.

export

Export proof assets

Export the flow preview, a sample 15-second clip, and a screenshot of the fact gate output. Use clean captions and visible evidence callouts.

submit

Post early, then refine

Contra challenge guidance allows multiple unique submissions. Post the strongest version early enough to collect engagement, then resubmit only if the guidelines allow and quality improves.

reuse

Turn it into paid work

The same workflow can sell as a Launch Proof Media Pass: proof extraction, three scripts, visual prompt map, caption set, and a publish-safe fact gate.

source trail

Current signals used for the template.

contra

ElevenCreative Challenge

Contra's public challenge topic describes the current ElevenCreative challenge as a build for useful, creative, reusable Flows templates with an $11k prize pool.

open challenge post open topic

rules

Contra challenge mechanics

Contra's help center says challenges are contests for independents, prizes vary, winners are chosen by judges, and some challenges include community favorite or promoter prizes.

open help article

elevenlabs

Flows docs

ElevenLabs documents Flows as a node-based creative canvas with image, video, speech, music, sound effects, templates, non-destructive iteration, and Studio export.

open Flows docs

launch proof media pass

Need a proof-led launch clip instead of a generic product video?

Send the product link, repo, or sample report. The useful output is a proof table, three short scripts, a scene prompt map, and a publish-safe fact gate.

open ticket