⚠️
Dummy Data Disclaimer: All project names, client names, team members, throughput metrics, and operational data are AI-generated for demonstration. No real production company data is shown.
📋 Executive Summary

The Problem: Three Tools, Zero Visibility

The production company had a 24-person creative team producing video content, social media assets, and ad campaigns for 40+ clients. Project management lived in ClickUp, client deals and revenue in Salesforce, and capacity planning in a Google Sheet that was perpetually 2 weeks out of date.

Every Monday standup devolved into the same questions: "How many projects are in post-production right now? Which editor is overloaded? What's our on-time delivery rate this month? Are we on track for revenue targets?" Nobody could answer without tab-switching between three tools and mentally stitching the data together.

We built an integration layer that pulls data from all three systems via APIs and Zapier, normalizes it into a unified operations model, and feeds a real-time dashboard showing project pipeline, team utilization, throughput velocity, bottleneck identification, and revenue alignment — all in one view.

40%
Fewer missed deadlines
Bottleneck visibility
3→1
Tools checked for status
Single source of truth
6 hrs
Weekly time saved on reporting
Ops manager freed up
82→94%
On-time delivery rate
+12 points in 90 days

Before & After

❌ Before
📋ClickUp for project tasks — no capacity view
☁️Salesforce for revenue — disconnected from production
📊Google Sheet for capacity — always stale
Monday standups: 45 min of status-chasing
🔴Bottlenecks discovered after deadlines missed
🤷"How loaded is the team?" — nobody knew
✦ After
🖥️Single command center — all 3 sources unified
🔗Real-time sync via API + Zapier webhooks
🗓️Live utilization heatmap per team member
Monday standups: 15 min with dashboard open
🟡Bottleneck alerts fire before deadlines break
📈Throughput, velocity, and revenue all visible

Integration Architecture

Three data sources feed into a Zapier-based integration layer that normalizes project, staffing, and revenue data into a unified model:

System Architecture
📋
ClickUp
Tasks · Statuses · Time
☁️
Salesforce
Deals · Revenue · Clients
📊
Sheets
Capacity · Rates · PTO
API
Zapier
8 Zaps · Webhooks · Transforms
JSON
📊
Ops Dashboard
Pipeline · Heatmap · KPIs
🎬 Finding #1

Post-Production Is the Bottleneck — 34% of Projects Stall There

The production pipeline has 6 stages: Brief → Pre-Production → Shoot → Post-Production → Review → Delivered. The unified dashboard immediately revealed that Post-Production had the highest WIP count and the longest average dwell time — 4.2 days versus the 2.5 day target.

34% of all in-progress projects were sitting in Post-Production at any given time, and the two senior editors were running at 115%+ utilization. The solution wasn't to hire more editors — it was to shift color grading and audio mixing to two underutilized junior team members who had the skills but weren't being assigned that work.

Average Days in Stage

Time projects spend in each production stage

Monthly Throughput — Projects Delivered

Completed projects per month (Jan–Dec)

Key insight: The bottleneck wasn't a capacity problem — it was an assignment problem. Two editors at 115% while two juniors sat at 60%. Rebalancing work within the existing team (not hiring) increased throughput 28% in the first month.

👥 Finding #2

The Utilization Heatmap Revealed a 55-Point Spread

Team utilization ranged from 58% (a motion designer with skills nobody was assigning to) to 113% (the lead editor drowning in every project). The heatmap below shows weekly utilization by team member — darker red means over capacity, darker green means underutilized:

The heatmap made an invisible problem visible: the team had a structural imbalance. Certain roles were chronically overloaded while others were underutilized — not because of skill gaps, but because the assignment process (a Slack message from the PM) defaulted to the same 5 people out of habit.

💰 Finding #3

High-Effort Projects Weren't Always the Most Profitable

By connecting ClickUp hours to Salesforce deal values, we calculated effective hourly rate per project for the first time. The results were surprising: short-form social content ($185/hr effective rate) was 2.4× more profitable per hour than long-form brand videos ($78/hr) — despite brand videos having higher absolute deal values.

This insight directly influenced the sales team's prioritization: they began weighting pipeline toward higher-margin project types rather than chasing large but low-margin brand work.

Effective Hourly Rate by Project Type

Revenue ÷ actual hours logged (ClickUp × Salesforce)

Revenue vs Hours — Project Scatter

Each dot = one project. Slope = profitability.
📅 Finding #4

On-Time Delivery Rose from 82% to 94% in 90 Days

The combined effect of bottleneck visibility, utilization rebalancing, and proactive capacity alerts produced a 12-point improvement in on-time delivery rate within the first 90 days. Late deliveries dropped from an average of 14 per month to 5.

The biggest driver wasn't working faster — it was earlier visibility. When the dashboard shows a project has been in Review for 3 days (target: 1.5), the PM gets an automated Slack alert before the deadline breaks. Previously, late was discovered on the due date itself.

On-Time Delivery Rate (Monthly)

% of projects delivered by deadline — before and after dashboard launch

Project Type Mix — Monthly Volume

Stacked by content type

Key insight: 70% of late deliveries traced back to the Review stage — client feedback loops averaging 3.2 days instead of the 1.5-day target. The dashboard now tracks "days awaiting client feedback" as a separate metric, making client-side delays visible alongside production-side delays.

⏱️ Finding #5

Monday Standups Went from 45 Minutes to 15

Before the dashboard, the Monday standup was a painful round-robin: each PM opened ClickUp, scrolled through their tasks, narrated status updates, and someone tried to take notes. The meeting regularly ran 45 minutes and still left questions unanswered.

Now, the standup opens with the dashboard projected on screen. The ops lead walks through the production board (30 seconds), flags bottlenecks in red (30 seconds), shows the utilization heatmap (30 seconds), and reviews the 3–5 projects at risk (5 minutes). PMs only speak if they have something the dashboard can't show. Total time: 15 minutes.

Weekly Operations Meeting Duration (Minutes)

Before dashboard (Jan–Jun) vs after (Jul–Dec)

Interactive Operations Explorer

Select a project type and time period to explore throughput, utilization, and delivery metrics:

Production Operations — Command Center
Monthly Throughput
Stage Dwell Time
On-Time Rate Trend
Utilization Distribution

Key Features

🎬 Live production Kanban

Real-time board pulling from ClickUp API showing all projects across 6 stages with type badges, client names, assignees, and days-in-stage indicators.

🔥 Team utilization heatmap

Week-by-week utilization per team member with color intensity encoding. Instantly shows who's overloaded, who's underutilized, and where to rebalance.

💰 Revenue-per-hour alignment

ClickUp hours × Salesforce deal values = effective hourly rate per project type. Revealed social content is 2.4× more profitable than brand video.

🚨 Bottleneck alerts

Projects exceeding stage dwell time targets trigger Slack alerts to the PM and ops lead — before the deadline actually breaks.

📅 On-time delivery tracking

Delivery rate, late-project analysis, and client-feedback delay tracking. Distinguishes production-side vs client-side causes of lateness.

⚡ 8-Zap integration layer

ClickUp webhooks, Salesforce Connected App, Google Sheets API — all orchestrated through Zapier with error monitoring and retry logic.

The Outcome

82 → 94%

On-time delivery rate

45 → 15 min

Monday standup duration

6 hrs/week

Ops manager time reclaimed

Is your creative team flying blind on capacity?

If your projects live in ClickUp, revenue in Salesforce, and capacity in a spreadsheet — I can connect them into one operations view.