Professional Motion Graphics Explainer Video
Budget: $1,500 – $3,000 USD
I’m putting together a clear, polished explainer and need a motion-graphics animator who can translate my message into an engaging visual narrative. The video will serve an instructional purpose, so the graphics must prioritise clarity and flow while still feeling fresh and modern.
3. Storyboard
Scene 1 – CCTV (Today)
• Inside a sewer pipe using traditional CCTV crawler footage (I can provide this if you need)
• Grainy, low-light, limited visibility
Purpose: Establish current state (reactive, constrained visibility)
Scene 2 – Evolution to Drone and/or 360 camera shot (I can provide this)
• Seamless transition from CCTV to drone-based inspection
• Improved mobility, lighting, and coverage
Purpose: Show advancement in data capture capability
Scene 3 – vSite / 3D Capture (see the link below for a music video that demonstrates this concept)
• Environment transforms into a 3D point cloud / mesh model
• Pipe becomes measurable and digitized
• Subtle overlays (geometry, dimensions, defects)
Purpose: Shift from visual inspection to quantifiable data
Scene 4 – Live Data Integration (Sensors)
• Pipe becomes semi-transparent
• Flow visualized (levels, movement, direction)
• Sensor nodes appear, transmitting data
Purpose: Introduce real-time system behavior
Scene 5 – Network Expansion
• Camera pulls back to reveal interconnected pipes
• Manholes extend toward the surface
• Maintains dark, high-contrast environment
Purpose: Show system connectivity
Scene 6 – Surface Integration (Toronto Context)
• Transition to above-ground view
• Recognizable Toronto elements (street grid, urban form)
• Maintain linkage between underground and surface
Purpose: Connect infrastructure to city operations
Scene 7 – City-Scale Visualization
• Zoom out to full Toronto view
• Overlay network with flow-based heatmap:
o Red = high flow
o Yellow = moderate
o Green = normal
Purpose: Demonstrate real-time, city-wide awareness
Scene 8 – Digital Twin
• Transition to system-level interface or command view
• Display live network behavior and system state
Purpose: Present final state: integrated digital twin
Final Frame
• Clean visual end state with no text (Option B)
4. Technical Direction
• Maintain engineering realism (pipe types, dimensions, flow behavior)
• Avoid overly abstract or sci-fi visuals
• Ensure transitions feel continuous and intentional
• Keep visualization grounded in plausible infrastructure representation
5. Production Notes
• Duration: 60–90 seconds
• Resolution: 4K preferred (minimum 1080p)
3. Storyboard
Scene 1 – CCTV (Today)
• Inside a sewer pipe using traditional CCTV crawler footage (I can provide this if you need)
• Grainy, low-light, limited visibility
Purpose: Establish current state (reactive, constrained visibility)
Scene 2 – Evolution to Drone and/or 360 camera shot (I can provide this)
• Seamless transition from CCTV to drone-based inspection
• Improved mobility, lighting, and coverage
Purpose: Show advancement in data capture capability
Scene 3 – vSite / 3D Capture (see the link below for a music video that demonstrates this concept)
• Environment transforms into a 3D point cloud / mesh model
• Pipe becomes measurable and digitized
• Subtle overlays (geometry, dimensions, defects)
Purpose: Shift from visual inspection to quantifiable data
Scene 4 – Live Data Integration (Sensors)
• Pipe becomes semi-transparent
• Flow visualized (levels, movement, direction)
• Sensor nodes appear, transmitting data
Purpose: Introduce real-time system behavior
Scene 5 – Network Expansion
• Camera pulls back to reveal interconnected pipes
• Manholes extend toward the surface
• Maintains dark, high-contrast environment
Purpose: Show system connectivity
Scene 6 – Surface Integration (Toronto Context)
• Transition to above-ground view
• Recognizable Toronto elements (street grid, urban form)
• Maintain linkage between underground and surface
Purpose: Connect infrastructure to city operations
Scene 7 – City-Scale Visualization
• Zoom out to full Toronto view
• Overlay network with flow-based heatmap:
o Red = high flow
o Yellow = moderate
o Green = normal
Purpose: Demonstrate real-time, city-wide awareness
Scene 8 – Digital Twin
• Transition to system-level interface or command view
• Display live network behavior and system state
Purpose: Present final state: integrated digital twin
Final Frame
• Clean visual end state with no text (Option B)
4. Technical Direction
• Maintain engineering realism (pipe types, dimensions, flow behavior)
• Avoid overly abstract or sci-fi visuals
• Ensure transitions feel continuous and intentional
• Keep visualization grounded in plausible infrastructure representation
5. Production Notes
• Duration: 60–90 seconds
• Resolution: 4K preferred (minimum 1080p)