How Many Active Campaigns Can a Small Marketing Team Run at Once?

Calculate a small team’s campaign limit from usable hours, bottleneck review, handoffs and risk reserve, with formulas and worked scenarios.

Short answer: answer: Calculate usable campaign hours, subtract business-as-usual work and a provisional 15–25% exception reserve, then divide the remainder by each campaign’s weekly production, review and coordination demand. Check the scarcest role separately and use the lower limit. The reserve is a CDM starting assumption to replace with observed unplanned hours; for the illustrative four-person team below, the safe mix is two standard campaigns plus one light test.

Counting campaign names is misleading. A newsletter test and a regulated multi-creator launch are both “one campaign,” but their handoffs, review load and exception risk are incomparable.

Utilization is also a trap. Planning every available hour makes normal variance look like failure. Capacity includes the ability to absorb correction, partner delay and tracking defects.

The Campaign Work-in-Progress Formula

The Campaign Work-in-Progress Formula combines team hours, bottleneck hours, coordination load and reserve. CDM’s position is: capacity is set by the scarcest review or handoff, not by the number of ideas or empty calendar cells. A campaign is active once it consumes production or review capacity, even while “waiting.”

Step 1: calculate usable weekly hours

For each role:

Usable hours = paid hours – fixed meetings – administration – support – leave allowance

Then:

Plannable hours = usable hours × (1 – exception reserve)

Do not use contracted hours as production capacity. Measure the components for four weeks.

Illustrative four-person team:

Subtract 40 hours for business-as-usual lifecycle, reporting and community work. Reserve 20% of the remaining 72 hours—14.4, rounded to 15—for exceptions. Campaign capacity is 57 hours weekly.

Step 2: size campaign demand

Count focused production, required review, coordination/handoff and monitoring. Use recent actuals, not optimistic briefs.

Two standard campaigns plus one light test require 46 hours, leaving 11 of the 57 for variance. Three standard campaigns require 54, leaving only three; the mix fits arithmetically but violates the intended protection. One complex plus one standard uses 48 and may fit if the review bottleneck does.

All numbers are CDM simulation assumptions, not measured benchmarks.

Step 3: calculate the bottleneck cap

For each specialist, total available campaign hours and demand. Suppose the Growth Lead has eight weekly campaign-review hours. A standard campaign needs three, complex needs six and light needs one. Two standard plus one light consumes seven and fits. One complex plus one standard consumes nine and fails even though total team hours fit.

Safe campaign mix = minimum(total-hour capacity, each role’s capacity, risk-policy capacity)

Do not average roles. Ten spare content hours cannot approve a claim when the evidence owner has none.

Step 4: add handoff load

Each formal transfer consumes preparation, clarification and acceptance. Estimate from logs. If a standard campaign has four handoffs at 30 minutes for both sender and receiver, coordination costs four person-hours—not two clock hours. Include it once in the campaign load.

Reduce handoffs through shared briefs and parallel review, but do not delete necessary rights, consent or claim checks. “Faster” is not capacity if it externalizes correction.

Step 5: validate with flow history

Kanban defines WIP as started but unfinished work and recommends explicit limits. ProKanban identifies WIP, throughput, work-item age and cycle time as core flow measures. Track all four for campaigns.

Little’s Law relates WIP, throughput and lead time under stable conditions: WIP = throughput × lead time. If the team completes two campaigns per month and campaigns spend six weeks active, average WIP around three is consistent. The relation is descriptive, not permission to ignore campaign-size variation or unstable arrivals.

Campaign capacity calculator

Use these inputs:

• role-level usable hours;
• BAU hours by role;
• exception reserve percentage;
• campaign load by class and role;
• handoff person-hours;
• required specialist review;
• historical throughput and 85th-percentile cycle time;
• active work already committed.

Output three views: arithmetic maximum, bottleneck maximum and recommended WIP. Recommended WIP should be below the hard maximum until four to eight weeks of predictable flow exists.

Worked planning scenario

The illustrative team has 57 campaign hours and eight Growth Lead review hours. Its proposed portfolio is one complex launch, two standard campaigns and two light tests: 86 team hours and 14 lead-review hours. It does not fit.

The decision options are:

1. run the complex launch plus one light test: 40 hours and seven review hours;
2. run two standard plus one light: 46 and seven;
3. outsource production, which does not remove internal review and coordination;
4. delay or reduce scope.

The team selects option 2 for four weeks. It keeps the complex launch in Ready, where preparation that does not consume scarce review can continue only within a separate small cap. New executive work must displace an active item.

At an illustrative $70 blended rate, 15 reserved hours represent $1,050 of weekly paid capacity. That is not waste; it buys response ability. If actual exceptions average only five hours over eight weeks, reduce the reserve cautiously rather than immediately selling all ten remaining hours.

Failure signals

The cap is too high when work-item age rises, review queues exceed service level, campaigns are repeatedly “90% done,” corrections increase or BAU degrades. It may be too low when items finish predictably, reserve remains unused and customer demand waits despite stable quality.

Change one variable at a time. Adding a contractor may increase production while worsening review load. Automation can reduce setup but adds monitoring and exception paths. Recalculate the bottleneck, not merely total hours.

Keep a weekly capacity ledger showing planned hours, actual hours, review demand, unplanned work and displaced commitments. Reconcile it after each campaign closes. If estimates miss repeatedly in one stage, update that class rather than applying an unexplained buffer to every campaign.

Related guides

• What Evidence Should a Brand Give Creators Before They Make Product Claims?
• How Do You Check Sponsorship Disclosure in the Final Rendered Creator Post?

Frequently asked questions

Is three active campaigns the right limit for every small team?

No. Three is the output of the illustrative mix, not a universal benchmark. Your limit depends on campaign class, usable hours, business-as-usual work, review bottlenecks, handoffs and exception risk. Begin below the calculated maximum, observe throughput and cycle time, then adjust.

A two-person regulated team may run one; a five-person team with standardized low-risk tests may run more. Define what “active” means consistently before comparing counts. Recalculate after team leave, major launches or workflow changes, and publish the displacement rule so leadership cannot silently add a fourth commitment.

Does waiting work count toward WIP?

Yes when it still consumes attention, review slots, deadline risk or coordination. A campaign waiting for rights can age and block downstream work even if nobody edits it today. Show Waiting separately and assign a chase date, but do not pretend the portfolio is free.

If the team has no executable action and has made no commitment, move it back to Ready or Parked. This distinction prevents phantom capacity without penalizing genuine external delay. Measure waiting age and blocked person-hours separately: elapsed delay affects commitments, while the latter affects immediate capacity and avoids double counting.

How large should the exception reserve be?

Start with 15–25% of capacity and replace that assumption with observed unplanned hours. The worked example reserves about 20%. Launch periods, volatile platforms or regulated work may need more; stable recurring programmes may need less. The reserve should have entry rules so ordinary scope creep does not consume it.

If unused, spend it on maintenance or discovery, but keep work interruptible rather than converting every hour into another deadline. Review the previous eight weeks, use a percentile or conservative range, and include both incident response and small mandatory work that bypasses intake.

Can outsourcing increase the campaign limit?

Only when production is the binding constraint and internal briefing, review, rights and integration capacity remain available. A contractor can remove eight editing hours yet add two handoff hours and three review hours. Put those in the calculator.

Outsourcing may still be correct for specialist or variable demand, but a team whose bottleneck is founder approval or evidence will create a larger queue, not more finished campaigns. Run one bounded commission, record internal person-hours and acceptance defects, then update the load assumptions before increasing outsourced volume or promising additional campaigns.

How should we size a new kind of campaign?

Break it into production, review, handoff, monitoring and likely exception hours by role. Use a range and choose the conservative end for the first run. Keep it as its own class until several examples produce useful history.

Do not call a creator launch “standard” because the media budget is small; rights, multiple partners and disclosures can dominate workload. After completion, compare estimated and actual hours without punishing honest uncertainty. Record which assumption missed—scope, review, waiting or rework—so the next estimate improves rather than applying one unexplained contingency percentage.

What metric shows overload earliest?

Work-item age and bottleneck queue often warn before missed launch dates. Track how long active campaigns have remained unfinished against historical expectations, plus the age of required reviews. Rising WIP with flat throughput is another warning. Utilization alone can look healthy while flow collapses.

The caveat is data maturity: if history is sparse, use explicit service-level expectations as hypotheses, then revise them rather than presenting estimates as predictive certainty. Pair the signal with correction and BAU quality, since faster campaign completion achieved by neglecting customer journeys or evidence is not sustainable capacity.

Next decision: Use a realistic creator campaign timeline and RACI

Related reading: Run the creator campaign operating playbook · Design creator approvals without killing the idea · Build a creator dashboard executives will trust

Sources and research notes

• Kanban University, The Official Kanban Guide.
• ProKanban.org, Kanban and the four flow metrics and Basic metrics of flow.
• Scrum.org, Little’s Law and agile flow.
• Lean Enterprise Institute, Lean operations.

Research checked 26 September 2026. CDM conducted no original time-log study. Every team size, hour, rate, campaign class, reserve and output in the calculator is an illustrative simulation. Little’s Law depends on stable-system assumptions and should not be applied mechanically to heterogeneous campaigns; replace estimates with local flow data.