Output preview — future paid product · no video has been rendered
Product Commercial Pack — Output Preview
The Product Commercial Pack is a single approved 1080p MP4, the script and captions behind it, a structured scene plan, and platform-ready cutdowns for seven channels — every item gated by recorded approval.
Section 1
Product intake summary
The operator completes a structured intake before any script or render path is activated. The summary below shows what the intake record looks like in a future commercial session. All fields are operator-supplied.
Intake is operator-submitted and operator-held. All proof points and performance claims are supplied by the operator. Klariven does not verify external claims. Claims must have operator-held documentation before approval at the intake gate.
Section 2
Approved and prohibited claims
The approved claim set bounds all script output. The prohibited claim set blocks script elements before render dispatch. Both lists are locked at intake and cannot be overridden by the commercial pipeline.
Approved claims — example format
Claims the operator has documented. These are example-format only and must be backed by operator-held evidence before approval.
- Reduces time-to-value from 14 days to 3 days (operator-documented)
- 40% reduction in support tickets within 60 days (operator-documented)
- Automated onboarding — no developer setup required
- Works inside existing product stack — no migration required
- Free trial available — no credit card required
Prohibited claims — always blocked
Claims that are blocked regardless of operator request. None of the following are permitted in script output.
- Fake testimonials — fabricated customer quotes are blocked
- Fake customers — invented brand names or logos are blocked
- Unsupported claims — any claim without operator-held documentation is blocked
- Guaranteed ROAS — no guaranteed return on ad spend
- Guaranteed conversions — no conversion rate guarantees
- Fake founder or customer voice — consent is required before any voice synthesis
Section 3
Script preview
The approved script is included in every export packet. The two formats below show the output shape for 15-second and 30-second commercials. These are preview examples, not rendered videos. No audio or video has been generated.
[0:00–0:04] Hook: "Most SaaS users never finish onboarding. Here's why yours will."
[0:04–0:10] Proof: "Flowbase Pro cuts time-to-value from 14 days to 3 — no developer setup required."
[0:10–0:15] CTA: "Book your 20-minute walkthrough. Link below."
Preview example only. Final script is operator-approved at the script approval gate before render dispatch.
[0:00–0:05] Hook: "Your users are churning before they see value. The average SaaS onboarding takes 14 days."
[0:05–0:12] Problem: "You built a great product. But if users don't activate fast, they leave — and your CAC never pays off."
[0:12–0:22] Solution: "Flowbase Pro automates your onboarding flow, adds an in-product checklist engine, and fires behavioral triggers at the right moment — no developer required."
[0:22–0:27] Proof: "Customers document a 40% drop in support tickets within 60 days of deployment."
[0:27–0:30] CTA: "Book a 20-minute walkthrough. No credit card required."
Preview example only. Final script is operator-approved at the script approval gate before render dispatch.
Section 4
Scene plan
The scene plan is a structured document included in every export packet. It maps each shot to its product placement, voiceover reference, and approval checkpoint. This is a preview example, not a render instruction.
Scene plan is reviewed at the scene approval gate. Render dispatch is blocked until the scene plan is operator-approved. export blocked until post-render approval. This is a preview example only.
Section 5
Platform rail outputs
Platform-specific copy for every selected rail is included in every export packet. No API connection is made on behalf of the operator — distribution is always operator-controlled.
Post copy and hook variants for organic reach. Long-form awareness format for the professional buyer network. No LinkedIn API connection in MVP1.
Example output shape
Hook variant · body copy · proof point · CTA · 2–3 post alternatives
Video description, tags, and chapter markers formatted for YouTube upload. Operator uploads the MP4 and pastes the description manually. No YouTube API connection in MVP1.
Example output shape
Title variant · timestamped description · recommended tags · chapter markers
Copy pack for X — six output formats included. No API connection in MVP1.
Example output shape
Headline, subheading, and CTA copy matched to the commercial script. Operator pastes into their existing landing page. No page builder or publishing integration in MVP1.
Example output shape
H1 variant · subheading · feature bullets · CTA button copy · above-fold layout notes
Script excerpt formatted for cold or warm outreach. Operator sends via their own email tool. No email API connection in MVP1.
Example output shape
Subject line variant · opening hook · proof point · CTA line · video link placement guidance
Launch headline, lede, and CTA button copy for a product launch page or announcement. Operator publishes manually. No launch platform API in MVP1.
Example output shape
Launch headline · lede paragraph · bullet proof points · CTA copy · tagline variant
Talking points and usage guidance for partner or influencer distribution. Operator sends directly. No influencer API or network connection in MVP1.
Example output shape
3–5 talking points · permitted claim summary · prohibited claim reminders · usage guidance brief
Section 6
Export packet
What the operator receives after all approval gates are passed. Every export packet includes four primary deliverables and five provenance and safety records. export blocked until post-render approval.
MP4 video
1080p minimum · 15s or 30s · watermark included · post-render operator-approved
approved script
Full voiceover text · commercial mode reference · voice profile reference
captions/SRT
Caption track file · embedded option available · timing accuracy threshold required
scene plan
Structured shot document · product placement map · approval checkpoint log
Provenance & safety refs — also included
platform cutdowns (LinkedIn, YouTube, X, Landing page, Sales email, Launch page, Partner / influencer outreach) · signed provenance manifest · claim-safety checklist · consent refs · music/sound license refs
Export packet is operator-reviewed before any download is possible. This preview shows the output shape only.
Section 7
Governance posture
ConsentGate, credit accounting, and approval requirements that govern every commercial session. These rules are locked and cannot be bypassed by any routing or provider decision.
Credit posture
- video credits, not unlimited video. Credits are finite and tied to render sessions.
- Credits are reserved at RenderRequest creation and consumed only on confirmed provider success.
- provider success confirmation is required before credit consumption.
- failed provider renders may refund or release credits back to the ledger.
- customer-requested re-render consumes credits from the operator's ledger.
- No public credit pricing is finalized until rendering ships.
Approval posture
- Six approval gates govern every session: intake, script, scene, pre-render, post-render, export.
- No provider output becomes final without post-render approval.
- export blocked until post-render approval. This rule cannot be bypassed by any routing decision.
- Operator remains responsible for final commercial approval in MVP1.
- Render dispatch is blocked until the pre-render gate is passed.
Rendering is not live yet. · Upload is not live yet. · provider integration is future only · Operator posts manually · No social account connection in MVP1 · No auto-publishing in MVP1 · No X API, OAuth, scheduling, scraping, or engagement automation in MVP1 · Klariven does not post to any platform. Distribution is always operator-controlled.