Animation Ultra-Premium Cinematic System for SaaS B2B PM Tool | reduce bounce 40% | PID 00302

EXECUTION BRIEF — ANIMATION ROLE Act as a senior commercial video director, motion designer, editor, and prompt engineer. Your job is to produce an executable shot plan and generation brief, not a generic “premium cinematic” description. Optimize for a believable finished video that an editor can assemble and a video model can reproduce consistently. PROJECT Industry: SaaS B2B PM Tool Audience: a product leader or engineering manager at a 50–200 person software company Primary problem: too much project status is trapped across tickets, chat, and spreadsheets Creative goal: reduce bounce 40% Goal interpretation: clarity and immediate relevance Business objective: Make the first visual answer the visitor's likely question: “Is this for me, and what does it do?” Do not interpret the goal as permission to add louder effects or unrelated hooks. Category: Animation Target duration: 12–30 seconds Format: 16:9 master with clean edges and optional transparent/solid background version CREATIVE CONCEPT Center the video on a clean project workspace with one realistic workflow: backlog → owner → deadline → shipped. The viewer should understand the situation before the first third of the runtime. show one concrete before/after workflow change rather than generic dashboard glamour The creative should feel natural kitchen/vanity, using soft window daylight. Use a 65mm macro visual language and slow slider push-in. Keep the camera movement subordinate to the message: motion should reveal, compare, demonstrate, or create emphasis—not exist merely to look expensive. CATEGORY EXECUTION single visual metaphor or system; introduce → transform → resolve. Choose a coherent animation language—flat 2D, dimensional 3D, or graphic motion—and stay in it. Use deliberate easing and readable staging rather than random effects. Use one animation system throughout: stable geometry, consistent stroke/edge treatment, repeatable palette, readable timing, and no accidental style drift between shots. SHOT-BY-SHOT PLAN 1. OPENING — Establish the subject and problem immediately. Specify the starting frame, subject position, action, and what changes during the first 1–2 seconds. No logo-only opening. 2. DEVELOPMENT — Show the single core action. Give each shot one job. If the story needs multiple steps, cut only when the information changes. 3. PROOF — Show an observable product behavior, physical detail, customer moment, or supplied evidence that supports the claim. Never substitute abstract “success” imagery for actual proof. 4. PAYOFF — Resolve the action with a clear end state. Leave enough clean screen time for approved copy or CTA when the format requires it. 5. END/LOOP — For looping formats, design the last movement to return naturally to the opening state. For non-looping formats, end on the strongest useful frame rather than a decorative logo animation. CONTINUITY RULES Keep the main subject consistent in shape, color, material, identity, wardrobe, hand position, and environment. Keep lighting direction and focal length stable unless a deliberate shot change is specified. Do not morph between unrelated objects. Do not change the product design from shot to shot. For exact interface or packaging text, use supplied assets and add typography in post. Do not ask the generation model to invent legible small text. AUDIO / EDIT Minimal clicks, swells, or texture sounds synchronized to key transformations. Edit on action or information change. Avoid excessive whip pans, speed ramps, glitch transitions, or artificial “epic” impacts. Preserve enough natural pauses for comprehension. Captions, legal lines, product claims, and CTA copy should be added from approved text during post-production. CLAIM AND ASSET DISCIPLINE Do not invent unreadable interface text; use supplied screen recordings or simple abstract UI blocks. Only use product facts, customer quotes, statistics, certifications, medical/financial claims, property details, or performance claims that are supplied and approved. If a required fact is missing, mark it as [APPROVED INPUT REQUIRED] rather than inventing it. NEGATIVE / FAILURE CONDITIONS No flicker, temporal instability, object morphing, identity drift, warped hands, duplicate objects, impossible reflections, fake UI text, accidental logos, watermarks, unreadable captions, random camera shake, excessive motion blur, plastic skin, generic stock-footage look, or visual elements unrelated to the core problem. Do not add a second product, second narrative, or second CTA. OUTPUT SPECIFICATION Return: • a concise concept statement; • the ordered shot list with approximate seconds, framing, camera action, subject action, environment, lighting, and transition; • the exact generation prompt for each shot; • the negative prompt shared by the shots; • post-production notes for supplied UI, captions, CTA, color, sound, and export; • one fallback shot for any scene that is likely to fail in generation. QUALITY GATE Shapes, icons, and repeated objects must remain stable; motion must explain the idea instead of merely decorating it. Also verify: - The first frame makes the subject and context identifiable. - Every shot has one clear purpose. - The core product/subject remains consistent. - No unsupported claims are introduced. - The requested aspect ratio and duration are achievable without relying on invisible or contradictory instructions. - The result could be handed directly to a director/editor without asking what “premium” means. - The creative goal is treated as an optimization target, not a guaranteed outcome. SUCCESS TEST A professional reviewer should be able to answer “Who is this for?”, “What is happening?”, “Why should I care?”, and “What should I do next?” from the finished cut. Make the first visual answer the visitor's likely question: “Is this for me, and what does it do?” Do not interpret the goal as permission to add louder effects or unrelated hooks.