FF · Future Creative Network
Weekly
Heartbeat
Brand Creative & Communication · Weekly Output & Capacity Summary
Powered by Dapur (live) + Team Roster + Load Score Log · AI narratives by Claude
02 · Capacity Snapshot
Who's available — and who's at riskDapur exclusive
Source: Team Roster + Load Score Log
Headcount by Discipline
| Discipline | Heads | Available |
|---|
| GD | 21 | 0 |
| Copy | 14 | 0 |
| Art | 13 | 0 |
| Motion | 6 | 0 |
| FA Artist | 6 | 0 |
| Strategy | 3 | 0 |
| Social Media | 2 | 0 |
⚠️ Top 5 highest-load people (live)
| Name | Team | Disc. | Load | vs FULL |
|---|
| Aldi | Dimbas | GD | 70 | 1.7× FULL |
| Jonathan | Dimbas | Copy | 55 | 1.3× FULL |
| Dita | Dimbas | GD | 50 | 1.2× FULL |
| Ruben | Dimbas | GD | 35 | LOADED |
| Audy | Dimbas | GD | 25 | MODERATE |
Burnout signal: All 5 are Team Dimbas. Concentration risk on Telkomsel workload — worth a redistribution conversation.
03 · Executive Summary
The big picture
68% completion · 0 past airing
Week Narrative
FF is operating 222 jobs across 7 clients, with Telkomsel making up 97% of the portfolio in Dapur — a structural concentration that the migration plan will rebalance. 68% completion rate (150/222) is on par with industry pulse, while zero jobs are past their airing date — operationally clean. The shadow signal is on the capacity side: three of Team Dimbas's GD/Copy are 1.2–1.7× past FULL. Without a redistribution lever, this concentrates execution risk in one station. Forward look: PM migration to populate the other six stations is the unlock for both data accuracy and team load balance.
Active Status Mix (72)
| IN PROGRESS | 35 | 49% | |
| TO DO | 12 | 17% | |
| AWAITING CLIENT | 10 | 14% | |
| ON REVISION | 8 | 11% | |
| ON HOLD | 3 | 4% | |
| PRODUCTION | 1 | 1% | |
| UNKNOWN | 3 | 4% | hygiene |
Job Category Split
| Category | Active | Done | Total |
|---|
| 📣 Existing Client | 62 | 147 | 209 |
| 🎯 Pitch | 1 | 0 | 1 |
| — (no category) | 9 | 3 | 12 |
Note: Pitches live in Revenue Intelligence, not Dapur. v1 spec will join the two for full pitch pipeline.
04 · Client Health Snapshot
All clients, one view
Sorted by Total volume
| Client | Active | Done | Total | % Done | Health |
|---|
| TELKOMSEL |
67 | 148 | 215 | 69% |
|
| GSC |
1 | 2 | 3 | 67% |
OK |
| Biore |
1 | 0 | 1 | 0% |
In progress |
| LIXIL |
1 | 0 | 1 | 0% |
In progress |
| Others (PITCH ONLY) |
1 | 0 | 1 | 0% |
Pitch |
| Unassigned |
1 | 0 | 1 | 0% |
Hygiene |
Concentration insight
Telkomsel = 97% of Dapur volume. The "16-client cross-cut" view is theoretical until migration completes. Until then, Dapur is structurally a Telkomsel ops tool — already strong on capacity layer, status granularity, and real-time cadence, but the multi-client portfolio narrative belongs to v1.
05 · Pitch Pipeline
What's in the funnelDapur exclusive
Active pitches in Dapur
RI
Source of truth (next: link)
v1
Will pull from Revenue Intelligence
| Job Title | Client | Status | Priority |
|---|
| Shell Helix — Social Media Blabla |
Others (PITCH ONLY) |
UNKNOWN |
🟠 HEAVY |
Architectural note
Pitches mostly live in Revenue Intelligence (Lark Base), not Dapur — that's where the P&L Gate runs and verdicts get logged. The "1 active pitch" here is a placeholder record. v1 of /heartbeat will join Dapur + RI to produce the real pitch funnel view: active pitches, weighted pipeline, gate verdicts pending, win rate trends. Joining ops + revenue data in one weekly view is a uniquely FF capability.
06 · Needs Attention
On the radar
Past airing, on hold, hygiene
0
Past airing date + active
3
Status UNKNOWN (hygiene)
12
Missing Category (hygiene)
⏸️ On Hold (3)
| Job Title | Client | Team |
|---|
| SIMPATI — Billboard Giant Wall T3 Soekarno Hatta | TELKOMSEL | Dimbas |
| SIMPATI — Surprise Deal Eligible | TELKOMSEL | Dimbas |
| KV Hot Promo 160K dan 15K | TELKOMSEL | Dimbas |
🩹 Hygiene gaps (15)
| Type | Count | Action |
|---|
| No Account Status | 3 | Set status |
| No Job Category | 12 | Set 📣 Existing |
| No Client | 1 | Assign client |
| No PM PIC | 43 | PM to claim |
PM PIC unassigned = 60% of active jobs (43/72). Real story: Angga owns most by default, but the field is blank. Worth a quick batch-claim sprint.
07 · Team Load
Where the weight sits
Active jobs · Load Score sum
| Creative Team | Active Jobs | Load Score | Distribution |
|---|
| Team Dimbas |
68 | 335 |
|
| Team Dilchong |
2 | 8 |
|
| Team Yodha |
1 | 2 |
|
| Unassigned |
1 | 5 |
|
Migration signal
Team Dimbas carries 94% of active load (335 of 350 pts) — because Telkomsel is 97% of Dapur volume and Dimbas is the Telkomsel pod. The other 6 stations (Yodha · Edwin · Maya · Brigitta · Fadila · Vincent) barely register — not because they're idle, but because their workload hasn't migrated. The Expo Model assumption (Billie 3 · Audrey 2 · Angga 2) requires this migration to be complete before per-station load comparisons become meaningful.
08 · PM Load
Who's orchestrating
Active jobs by PM PIC
Active Jobs per PM
| PM PIC | Active | % |
|---|
| Unassigned |
43 |
60% |
| Angga |
28 |
|
| Billie |
1 |
|
| Audrey |
0 |
— |
Priority Distribution (active)
| Priority | Active |
|---|
| 🟠 HEAVY | 68 |
| 🟡 MEDIUM | 2 |
| 🔵 SUPER LIGHT | 1 |
| — unset | 1 |
68 of 72 active jobs at HEAVY priority — Telkomsel tactical defaults to HEAVY. This is a priority hygiene gap, not a missing-dimension problem. PM-led priority review sprint will restore discrimination faster than adding new fields.
09 · What This Run Surfaced
The three things to fix first
Tier 1 priorities · before /heartbeat v1
🔴 PRIORITY 1 — Migration
Non-Telkomsel jobs into Dapur
Today: 97% Telkomsel. Until other 6 stations have real workload in Dapur, the multi-client portfolio narrative is aspirational.
Unlocks: real Client Health, real Team Load, real PM scoreboard.
🔴 PRIORITY 2 — PM Hygiene
PM PIC mass assignment
43 of 72 active jobs unassigned (60%). Plus 15 records with missing Status / Category. PM-led sprint, 1 afternoon.
Unlocks: honest PM Load slide, real per-station accountability.
🔴 PRIORITY 3 — Cron Stability
Load Score Log uptime
Only 3 snapshots (6/4, 6/9, 6/11). Missed 6/12–6/14 — Mac asleep. Trend data is the strongest moat; losing it = losing the differentiator.
Fix: caffeinate LaunchAgent or migrate to cloud cron.
The deeper point
Burnout signal (Aldi 1.7× FULL), cron rot, hygiene debt — all surfaced by one prototype run. The value of /heartbeat isn't the export; it's the weekly forcing function. Every Tier 1 fix above was invisible until the report was built. That's the case for making this weekly.
10 · Appendix
Active jobs — full list
72 active · sorted by priority + team
| # | Job Title | Client | Team | PM | Status | Priority |
|---|