System · Built + rolled out · Ampersand · 2023

The capacity model

A month of calendar work, finished in three days. Planned, not rushed.

~8brands through one intake
3 daysfor a month's calendar
3 rolesin every pod
Monthsplanned in advance
The problem

Agency calendars slip everywhere, and for a reason: work arrives from every direction, and nobody plans against what a working day actually holds. The cost is quiet: rushed posts, pushed calendars, and good designers doing their best work at midnight. Running Ampersand's creative output, I decided to treat it as what it is: a planning problem wearing a creative costume.

The model

Every job enters through one intake, with an owner and a date, and the plan is built on real capacity. A designer's day holds three new posts plus changes. A motion designer's holds two social videos. Once the day is honest, the calendar is honest.

It ran on a spreadsheet. The system was the thinking, not the software.

The capacity arithmetic: a designer's day holds 3 new posts plus changes, a motion designer's holds 2 social videos, a pod is brand manager plus designer plus motion, and a brand's month of calendar work takes 3 days
The arithmetic the plan is built onAmpersand, 2023
The structure

The team ran in pods: a brand manager, a designer and a motion designer who owned their brands end to end, so around eight brands shipped in parallel instead of queuing behind each other. The result: a brand's full month of calendar work finished in three days, and calendars locked months in advance.

The legacy

The model outlived the moment it was built for. The same thinking runs my estimation and capacity work at S51 today.

The moving parts
IntakeOne queue, every job owned and dated
CapacityReal per-person daily throughput
PodsBrand manager + designer + motion, per brand
Version2026 © Anand Jeeva
Local time— IST