Animated Explainer — “Before & After Microsoft Fabric”
Summary
Freelancer Client is hiring: Animated Explainer — “Before & After Microsoft Fabric”.
Location: Remote
Compensation: $500–$900 USD.
PROJECT TITLE: 2-Min Animated Explainer — Microsoft Fabric
Internal corporate animated video for a bank's Cloud Platform
before Microsoft Fabric — and how Fabric solves it. Audience:
One-liner: "Before Fabric: five tools, five teams, 3AM alerts.
Slightly playful, exaggerated for comic effect. Real corporate
Skills: Animation, Video Editing, 2D Animation, Voice Over, AI Animation, AI Video
Source: Freelancer Client via Remote / Online. Apply on the source website.
Original
PROJECT TITLE: 2-Min Animated Explainer — Microsoft Fabric
(Before & After Story)
=== OVERVIEW ===
Internal corporate animated video for a bank's Cloud Platform
team. Shows real pain of managing multiple Azure data tools
before Microsoft Fabric — and how Fabric solves it. Audience:
internal data engineers, analysts, team leads.
One-liner: "Before Fabric: five tools, five teams, 3AM alerts.
After Fabric: one platform, one team, 9AM coffee."
=== TONE & STYLE ===
Slightly playful, exaggerated for comic effect. Real corporate
life but stylised — like a relatable tech meme brought to life.
Before: exhausting and absurd. After: calm and satisfying.
Flat 2D motion graphics. Stylised office environment. Simple
expressive characters. NOT 3D, NOT photorealistic.
=== COLORS ===
Before scenes: muted, tired — greys, dark navy #003F68
After scenes: vibrant — blue #0079C1, teal #39D4B9,
white #FFFFFF
Transition: blue wave sweeps left to right clearing chaos.
=== CHARACTERS ===
1. Data Engineer — overworked, 3 monitors, giant coffee
2. Data Analyst — waiting desperately for data
3. Team Lead — managing too many specialists
4. Security Reviewer — arrives with clipboard,
leaves with filing cart
5. Forgotten contractor — appears on 3AM call
=== TOOLS TO SHOW ===
BEFORE: Azure Data Factory, Azure Databricks, ADLS Gen2,
Azure Synapse, Power BI (disconnected), AWS S3, AWS Glue,
Azure Monitor — all separate, all painful.
AFTER: Single Microsoft Fabric workspace — pipelines, Spark,
warehouse, Power BI — all in one browser tab.
════════════════════════════════
ACT 1 — BEFORE FABRIC
════════════════════════════════
SCENE 1 — "Meet The Data Engineer"
Visual: Engineer at desk with 3 monitors — ADF on one,
Databricks on another, ADLS on third. Fourth laptop lands
from offscreen: AWS S3. Sticky note: "DO NOT RESTART
CLUSTER — ASK RAJ FIRST." Enormous coffee cup. Monday.
Narrator: "Meet your data engineer. Four screens. Three
Azure tools. One AWS account nobody fully owns. And a
sticky note that's been there since 2019."
SCENE 2 — "The Pipeline That Lives on Prayer"
Visual: ADF pipeline — one activity blinks red. Engineer
clicks. Error: "Databricks cluster timed out. Check Spark
logs." Spark log: 47,000 lines. They scroll. And scroll.
Pull back — it's 2:47AM. Pizza boxes. Slack buzzing.
Narrator: "When it fails — and it does fail — finding why
means ADF logs, then Databricks Spark logs, then ADLS
access logs. Separate places. Different formats."
SCENE 3 — "The Analyst is Waiting"
Visual: Split screen. Analyst types: "Hey, is sales data
ready?" Engineer winces. Calendar flips — 3 days pass.
Reply: "Almost ready, cluster issue + Synapse down.
Friday?" Analyst's plant has wilted.
Narrator: "That simple ask triggers a chain reaction across
ADF, Databricks, Synapse, and an ADLS folder structure
only one person truly understands."
SCENE 4 — "The Skills Spreadsheet"
Visual: Team lead at whiteboard: "ADF Team," "Databricks
Team," "Synapse DBA," "Power BI Dev," "ADLS Admin,"
"AWS Glue contractor." Draws line between ADF and
Databricks. Erases. Redraws with question mark. Marker
runs out. Uses crayon. Nobody notices.
Narrator: "Running this needs five specialists, each
speaking a different technical language. None cheap."
SCENE 5 — "Something Breaks. Chaos Ensues."
Visual: 3AM. Alert: "PIPELINE FAILED." Four people paged.
Each checks their tool: "ADF fine." "Cluster running."
"Warehouse up." "Storage accessible." All on a call,
pointing at each other. Fifth person joins — the AWS
Glue contractor. Nobody remembered they existed.
Narrator: "Is it ADF? Databricks? Synapse? ADLS
permissions? That AWS Glue job still running for reasons
nobody can explain?"
SCENE 6 — "The Security Review"
Visual: Security arrives with clipboard. "Where's data
encrypted?" — engineer points at three screens. "Who has
access?" — five Azure AD tabs open. "Audit logs?" —
Databricks logs, ADF logs, Azure Monitor, random storage
account. Clipboard overflows. Security leaves with
a filing cart.
Narrator: "Encrypted? Yes — three places, three configs.
Access control? Managed separately across ADF, Databricks,
Synapse. Audit logs? Everywhere."
════════════════════════════════
TRANSITION
════════════════════════════════
Visual: Chaos gets swept away by clean blue wave left
to right. White space. Microsoft Fabric logo appears —
calm, single, glowing. Text: "Then came Fabric."
Music shifts: tense → calm and optimistic.
════════════════════════════════
ACT 2 — AFTER FABRIC
════════════════════════════════
SCENE 7 — "One Platform, One Engineer"
Visual: Same engineer. Same desk. ONE screen. Fabric
workspace — pipelines, Spark, warehouse, Power BI in
one tab. Normal coffee. 9AM. Sticky note now reads:
"Have a great day :)"
Narrator: "Same engineer. One screen. No tool-switching.
No separate configs. No Raj."
SCENE 8 — "The Analyst Gets An Answer. Today."
Visual: Analyst types same message. Reply in seconds:
"Already in your Power BI workspace." Analyst blinks.
Still morning. Data is there, fresh, visualised.
Analyst looks suspicious — it doesn't disappear.
Plant is now healthy and flowering.
Narrator: "Pipeline, storage, and report — same place.
No handoff. No waiting. No Friday."
SCENE 9 — "One Team. Not Five."
Visual: Same whiteboard. Now: one circle — "Fabric Team."
Team lead smiles, caps marker, sits down. Ghost marks
of old chaos still visible behind. Team lead almost
draws more circles from habit. Stops. Satisfied.
Narrator: "One platform. One shared skill set.
Onboarding takes days. Not months."
SCENE 10 — "When It Breaks — You Find It Fast"
Visual: Alert: "Pipeline step failed — Row count mismatch."
Engineer clicks once. Fabric shows exact step, table,
cause, suggested fix. Fixed. Laptop closed. 9:15AM.
Engineer looks around waiting for chaos. Nothing.
Shrugs. Gets coffee.
Narrator: "One monitoring view. One audit log. Fix it
before lunch. Without paging four people at 3AM."
SCENE 11 — "Security That Doesn't Hurt"
Visual: Same security person arrives. Engineer opens
one Fabric screen — encryption, roles, audit trail,
private connectivity — all visible. Security checks
clipboard once. Nods. Gone in two minutes. Security
person looks slightly disappointed it was that easy.
Narrator: "One workspace. One identity model. One
encryption config. Your security team will actually
enjoy this part."
════════════════════════════════
CLOSING
════════════════════════════════
SCENE 12 — Closing Card
Visual: Split screen. Left (grey, muted): flashback —
chaos, 3AM call, filing cart. Right (bright blue):
calm engineer, one screen, healthy plant, 9AM.
Text fades in on right side:
"From Fragmented to Fabric."
"One platform. Built and ready. For your team."
"Cloud Platform Team | Microsoft Fabric"
Narrator: "The chaos was never your team's fault.
It was the infrastructure. We've fixed it.
Microsoft Fabric is live, proven, and ready.
Come build with us."
Music: warm resolution. Final note holds.
════════════════════════════════
DELIVERABLES
════════════════════════════════
- MP4, 1920x1080, 16:9, min 30fps
- Source file (After Effects or equivalent)
- Voiceover audio: separate WAV/MP3
- 2 revision rounds included
- Storyboard approval before animation begins
VOICEOVER: Warm, conversational, slightly wry.
Not an announcer. Provide 2 voice options.
MUSIC: Tense before → resolves warmly after.
Modern fintech tone. Provide 2-3 options.
TIMELINE: Storyboard in 5 days. Rough cut in
10 days. Final delivery within 18 days.
BUDGET: $500–$900 USD.
NOTE: Internal use only. Azure/Microsoft tool
logos must be accurate. Brand colors
are non-negotiable.
Location & Details
Apply on source →About this listing
This remote opportunity was imported from Freelancer and is shown here for discovery. To apply, follow the link to the original posting.