Ten creators are small enough for personal relationships—but too many for memory to be the operating system.
At this stage, the agency does not need enterprise software or layers of management. It needs a complete roster, one accountable owner per outcome, one work queue, a predictable weekly rhythm and a short list of controls that the team actually follows.
Reliable service
Clear promise × visible work × accountable owner × review cadence
Healthy 10-creator portfolio
Creator value + creator trust + delivery quality + commercial discipline − unmanaged exceptions
Section 1
Define the Portfolio You Are Actually Managing
“Ten signed creators” is not an operating definition. Decide who is active, what the agency owes each person and which relationships are being tested, grown, prioritized or maintained.
Assign every creator
- Lifecycle stage and 90-day objective
- Named relationship owner and backup
- Service tier with inclusions and exclusions
- Primary platforms and content cadence
- Commercial priority and category conflicts
- Next review date and current risk status
Use four practical stages
- Explore: time-boxed validation with capped effort
- Grow: recurring service against clear milestones
- Scale: priority resources for proven opportunity
- Network/paused: relationship retained without implied daily service
- Move stages through evidence and a recorded decision
- Never let inactive creators silently consume active capacity
Section 2
Give Every Creator One Accountable Owner
The creator owner is responsible for context and outcome, even when specialists complete the work. Creators should not have to navigate the agency to discover who can help.
| Responsibility | Creator owner | Specialist / support |
|---|---|---|
| Relationship | Expectations, goals, health and escalation | Provides relevant updates |
| Content | Priority and final coordination | Localization, editing, publishing support |
| Campaign | Creator fit and expectation alignment | Brief, approvals, delivery and reporting |
| Finance | Explains status and resolves exceptions | Reconciliation, statement and payment execution |
| Decision | Owns or routes it by written authority | Recommends within specialty |
Owner
One person is answerable for the next outcome and creator communication.
Backup
A named teammate can find the record and continue essential work during absence.
Escalation
Only defined legal, financial, reputation, safety or relationship risks reach leadership.
Section 3
Create One Source of Truth
Use a spreadsheet, database or work tool the team can maintain consistently. Tool choice matters less than required fields, ownership and update discipline.
| Record area | Minimum information |
|---|---|
| Identity | Legal/display name, contacts, time zone, language and emergency channel |
| Agreement | Term, territory, exclusivity, commission, services, rights and notice dates |
| Accounts | Platforms, handles, ownership, authorized users and recovery method |
| Strategy | Audience, content pillars, China objective, stage and current priorities |
| Operations | Owner, service tier, publishing cadence, approval rules and recurring tasks |
| Commercial | Rate guidance, restrictions, active leads, campaigns and conflicts |
| Finance | Payee, settlement currency, required documents, balance and payment status |
| Health | Last contact, current risks, open decisions and next formal review |
Section 4
Run Every Deliverable Through One Workflow
Capture
Put every request into the shared work queue; do not leave the only copy in chat.
Clarify
Record the output, owner, deadline, inputs, approver and definition of done.
Schedule
Reserve capacity and expose dependencies before promising a delivery date.
Produce
Work from the approved brief and source files with visible status and version control.
Review
Check quality, claims, rights, platform fit and required creator or brand approval.
Deliver
Record the final asset or live link, approval evidence, date and any commercial obligation.
Learn
Add performance, feedback, cost and follow-up to the creator or campaign record.
Every work item needs
- Creator and project/campaign
- One accountable owner
- Specific output and definition of done
- Priority and due date
- Inputs, dependencies and approver
- Status, next action and final evidence
Suggested statuses
- New / needs clarification
- Ready / scheduled
- In progress
- Waiting for creator/brand
- In review / revision
- Approved / scheduled
- Published/delivered / closed
Section 5
Set a Predictable Weekly Cadence
Monday • 30–45 min
Portfolio and workload planning
Review all ten creators, upcoming output, active campaigns, deadlines, capacity conflicts and the week’s three highest priorities.
Daily • 10–15 min
Exception check
Discuss only work that is late, blocked, newly risky or needs a decision. Update the system before or during the check.
Midweek • 30 min
Content and campaign review
Batch approvals, calibrate quality and unblock dependencies rather than creating continuous interruption.
Friday • 30 min
Close and learn
Confirm delivery, record links and evidence, reconcile open commitments, note learning and assign next actions.
Monthly • 60–90 min
Creator portfolio review
Review stage, health, performance, economics, service level, commercial opportunity and continue/change/pause decisions.
Section 6
Control Capacity Before Work Becomes Late
Count work by service demand, not creator headcount. One launch, one high-touch campaign and eight stable creators can be harder than ten steady publishing schedules.
Planned load
Recurring creator work + committed campaigns + onboarding/projects + review/admin reserve
Safe capacity
Available team time − meetings − leave − quality buffer − incident reserve
Plan weekly
- Content units by type and complexity
- Campaign deliverables and approval rounds
- Creator meetings and onboarding work
- Finance, reporting and administration
- Named deadlines and specialist bottlenecks
- Buffer for revisions and real exceptions
When demand exceeds capacity
- Protect contractual and high-risk commitments
- Clarify or reject incomplete requests
- Move discretionary work visibly
- Change scope or deadline with the stakeholder
- Use approved backup capacity
- Escalate the trade-off—never hide the overload
Section 7
Control Campaigns from Brief to Collection
Before acceptance
Scope and fit
Confirm parties, deliverables, timeline, fee, usage, exclusivity, claims, approvals, cancellation and creator acceptance.
During delivery
One campaign record
Track the approved brief, assets, versions, feedback, approval evidence, live links and deviations.
After delivery
Close commercially
Capture performance, report, invoice, receivable, creator settlement input, rights end date and renewal action.
Section 8
Protect Quality, Rights, and Account Access
Pre-publish / delivery check
- Correct brief, format, platform and account
- Names, links, tags, dates and pricing accurate
- Claims supported and required disclosure present
- Music, footage, image and likeness rights cleared
- Creator and brand approvals recorded
- Final file/version and posting plan confirmed
Account and payment controls
- Creators retain clear account ownership
- Named individual access; no informal shared passwords
- Least privilege and multi-factor authentication
- Recovery method and offboarding procedure
- Two-person approval for payment/access changes
- Incident contact and evidence-preservation steps
Section 9
Use a Small Decision-Oriented Scorecard
Delivery
On-time %
Late work and cause
Quality
First-pass %
Revision reason
Creator
Health status
Contact and risk
Content
Output + signal
By goal/platform
Campaign
Pipeline + live
Delivery/renewal
Finance
Revenue + due
Collection/payout
Capacity
Load vs safe
By role/queue
Portfolio
Stage movement
Invest/change/pause
Choose definitions the team can apply consistently. Review trends and exceptions; never use one content result or one vanity metric to make a portfolio decision.
Section 10
Manage Exceptions Without Letting Them Become the Model
The founder owns everything
Assign routine decisions and publish escalation rules; otherwise ten relationships become ten interruption streams.
Every creator gets a custom service
Define a base service and approve exceptions consciously, with an owner and capacity cost.
Chat becomes the database
Keep conversation where it is convenient, but move commitments, approvals, files and status into the shared record.
Followers determine attention
Allocate service using opportunity, strategic fit, responsiveness, economics and agreed commitments—not vanity alone.
Urgency overrides the queue
Define what qualifies as urgent and what work is displaced. Everything cannot be priority one.
Reporting happens from memory
Update records during delivery so the weekly review is a decision meeting, not a data-reconstruction meeting.
Exception record
Request + reason + decision owner + displaced work/cost + deadline + prevention lesson
Section 11
Install the System in 30 Days
Week 1
Make the roster visible
- Create all ten creator records
- Confirm agreements and active commitments
- Assign owner, backup, stage and service tier
- List every open risk and next action
Week 2
Centralize the work
- Choose the shared work queue
- Agree fields, statuses and definition of done
- Move all current deliverables and campaigns
- Start daily exception checks
Week 3
Set controls and cadence
- Launch weekly planning and closing reviews
- Introduce content/campaign checklists
- Document access and payment approvals
- Baseline workload, delivery and quality
Week 4
Review and simplify
- Run the first portfolio review
- Remove unused fields and duplicate reporting
- Fix the largest recurring bottleneck
- Publish owners, escalation rules and next 30-day target
Section 12
10-Creator Operating Checklist
Portfolio
- All ten creators have current records
- Stage, service tier, owner and backup assigned
- Contract obligations and review dates visible
- Inactive relationships do not imply active service
Execution
- Every commitment enters one work queue
- Owner, output, deadline and approval are explicit
- Weekly cadence is protected
- Overload produces a visible trade-off
Control
- Campaign scope and approvals are recorded
- Quality, rights and disclosure checks are used
- Account/payment changes have safeguards
- Critical incidents have an escalation route
Management
- Scorecard supports decisions, not reporting theater
- Creator health and economics are reviewed monthly
- Exceptions are recorded and reduced
- Founder is not required for routine execution
Keep relationships personal and operations visible.
A ten-creator agency works when every creator knows who owns the relationship, every commitment has a home, every week has a rhythm, and exceptions trigger decisions instead of silent overload.
“At ten creators, the best operating system is not the biggest—it is the one the whole team trusts and uses.”