Contact only as many creators as your smallest work budget can support: preparing pitches, handling replies, or making partnership decisions. Estimate all three before sending. In the hypothetical worksheet below, a team can prepare 60 pitches but has decision capacity for only 22 new contacts. A higher-response scenario reduces that limit to 12.
This is a staffing calculation for your influencer outreach strategy. It does not set a sending allowance or establish permission to contact someone. Limit the list to creator-welcomed business inquiries that applicable rules permit. Use the contact-data review guide before treating a public address as eligible for outreach.
Count the work a new contact creates
A prepared pitch is only the first task. A creator may ask about timing, send a rate card, suggest another format, or need a decision from someone outside the inbox team.
Modash's recruitment guide separates outreach, negotiation, and onboarding. That distinction matters for staffing. Saving time on the first message leaves the later work to be funded.
For this worksheet, split work into three budgets:
- Preparation: checking the selected creator's fit, adapting the pitch, and recording the contact.
- Reply handling: reading, routing, answering, and recording the conversation, including declines and closure work.
- Decision work: reviewing a proposal and deciding what the team can offer or approve.
Include scheduled follow-up preparation in the first budget if it belongs to an eligible, still-open conversation. Include every anticipated handling touch in the second budget. Do not count only the minutes needed to send the first answer.
If one person does all three jobs, divide their available time between them. Counting the same hour in two budgets creates capacity that does not exist.
Fill in the staffing worksheet
Choose a planning window before choosing a batch. The example uses the next five working days. Deduct meetings and unrelated campaign work before entering available time. Then subtract commitments to existing conversations and reserve time for uncertain work.
All figures in this article are hypothetical assumptions, not industry benchmarks or observed campaign results.
| Work budget | Available minutes | Existing work | Reserve | Minutes for new batch |
|---|---|---|---|---|
| Pitch preparation | 360 | 60 | 60 | 240 |
| Reply handling | 720 | 240 | 120 | 360 |
| Partnership decisions | 180 | 60 | 30 | 90 |
The decision-maker has only 90 minutes left for the new batch. Another teammate's spare inbox time cannot replace those minutes unless that teammate has authority to make the decisions.
Atlassian's guidance on work-in-progress limits recommends matching limits to specialist skills. Applied here, the person who approves scope or spending needs a separate capacity check.
For your own worksheet, name the owner of each row and confirm their availability. A nominal weekly allocation does not help if the approver is away when the proposals arrive.
Calculate the contact ceiling
Use assumptions that match the planning window and campaign type. Here, a replying creator means a unique person who sends a human reply during that window. Automatic responses do not count toward that rate, although processing them still takes time that belongs in your workload budget.
Use the reply-rate measurement guide to keep the denominator and observation window consistent when replacing assumptions with your own records.
| Input | Hypothetical assumption |
|---|---|
| Preparation per new contact | 4 minutes |
| Share of new contacts expected to reply | 40% |
| Handling per replying creator across the window | 15 minutes |
| Share of replying creators needing a decision | 50% |
| Decision work per creator needing a decision | 20 minutes |
Calculate each limit separately and round down:
- Preparation limit = 240 / 4 = 60 contacts.
- Handling limit = 360 / (0.40 × 15) = 60 contacts.
- Decision limit = 90 / (0.40 × 0.50 × 20) = 22 contacts, rounded down from 22.5.
The batch ceiling is the smallest result: 22 new contacts for this window. This calculation assumes separate, non-overlapping time budgets. If review happens twice, include both reviews in the decision-time estimate.
A ceiling based on averages is a planning estimate. It cannot promise that every reply will arrive evenly or take the assumed time. It also says nothing about how many partnerships the team will secure.
Test the case where more creators reply
A larger response can create more work than the team planned for. Before using the ceiling, test a busier scenario.
Keep the same time budgets, but assume 60% of contacts reply and 60% of those conversations need a decision.
| Limit | Base scenario | Higher-response scenario |
|---|---|---|
| Preparation | 60 | 60 |
| Reply handling | 60 | 40 |
| Decision work | 22 | 12 |
| Smallest limit | 22 | 12 |
The higher-response decision limit is 90 / (0.60 × 0.60 × 20), rounded down to 12. Under these assumptions, plan the first batch around 12 contacts. Choosing the lower scenario limit is a precaution, not a validated forecast.
With no campaign history, begin with a batch small enough to absorb an unusually high response, potentially every creator replying. Time the work, record unresolved conversations, and revise the assumptions before increasing volume. A guessed reply rate should never justify a batch the team cannot recover from.
Check daily coverage before releasing the batch
A five-day budget can conceal a busy morning. Suppose the hypothetical team has 72 minutes of reply-handling time per day. Twelve creators all replying together could require 180 minutes under the 15-minute handling assumption.
Dividing the batch into two groups of six reduces the first release. It still does not guarantee a smooth arrival pattern. Before releasing the second group, account for replies already waiting and potential late replies from the first group.
Set a team response target that the staffed calendar can support. That target is your operating choice, not a universal creator expectation. Avoid starting a batch before a coverage gap unless someone can handle the resulting work.
Name one owner and a backup for each open conversation. The shared-inbox ownership guide covers the handoff details; the staffing worksheet needs their booked minutes.
Make the next batch depend on unfinished work
The Kanban Guide describes starting new work when capacity is available and tracking unfinished work and its age. For outreach, apply that principle at each release decision.
Before sending more invitations, review:
- Replies waiting for a human answer, especially those past your team's target.
- Proposals waiting for an internal decision and the approver's next available time.
- Open conversations likely to require more work, including late replies from earlier batches.
- Accepted partnerships that now need onboarding time from the same people.
Pause new contacts when overdue replies or blocked decisions consume the available budget. Reassign work only to someone with the time and authority to do it. Raising the contact target will not clear an approval queue.
Carry unfinished work into the next worksheet. A new week does not erase an old conversation. For multiweek negotiations, reserve future handling and decision time before treating the current batch as affordable.
At the next planning meeting, fill in the three available-time rows with their owners. Calculate the smallest contact limit, test a higher-workload case, and release only the first group that the staffed calendar can support.
