A practical scope decision

One-off project or ongoing retainer?

If you create AI UGC, the right working model depends on the brief in front of you, your available capacity, and how much planning the client actually needs. Use this comparison to shape a clearer next conversation—not to predict an outcome.

See the comparison Ask about your situation

Scope first

Decide what is countable before you decide how often you will deliver it.

Rights in writing

Treat platform, term, territory and paid-use questions as part of the brief.

Cadence with limits

A recurring rhythm needs a clear feedback path and a clear availability boundary.

The decision in detail

Compare the work, not the promise.

Both models can be valid. The useful choice is the one whose scope, rights and communication expectations you can state clearly and support consistently.

01
Defined brief

One-off project

A defined brief with a finite delivery and handoff.

02
When ongoing work fits

Ongoing retainer

A recurring agreement with planned output and review points.

Comparison details by working model

One-off project

A defined brief with a finite delivery and handoff.

Commitment

Agreement shape
Finite scope, delivery date and handoff
Capacity planning
Schedule one project around current availability
Commitment to the client
Commit to the stated project scope

Deliverable planning

What gets planned
Fixed deliverables, formats, revisions and handoff
Brief changes
New work may need a new scope or timeline
Planning horizon
One brief and its delivery window

Usage-rights scope

Rights to define
Platforms, term, paid or organic use and territory
When use changes
Revisit scope if the placement or term expands

Communication expectations

Touchpoints
Kickoff, review and final handoff
Feedback rhythm
Consolidated feedback against the brief
Availability boundary
Response expectations for the project window

Fit considerations

Often fits when
The client has a specific campaign or test brief
Watch for
Scope expansion, unclear rights or extra revisions
Useful next step
Write the brief, deliverables, rights and handoff terms

Ongoing retainer

Highlighted fit

A recurring agreement with planned output and review points.

Commitment

Agreement shape
Recurring scope, cadence and review point
Capacity planning
Reserve capacity across the agreed cadence
Commitment to the client
Commit to the stated period and working rhythm

Deliverable planning

What gets planned
Planned batch or rhythm, with explicit scope limits
Brief changes
Define change boundaries and what rolls forward
Planning horizon
Several cycles or a stated review period

Usage-rights scope

Rights to define
Use per cycle or term, plus renewal and reuse boundaries
When use changes
Review rights when placement, term or territory changes

Communication expectations

Touchpoints
Recurring check-ins or async updates at an agreed cadence
Feedback rhythm
Feedback windows and a decision owner per cycle
Availability boundary
Response expectations without promising unlimited access

Fit considerations

Often fits when
The client has a repeatable content need and can plan ahead
Watch for
Unclear volume, open-ended availability or rights creep
Useful next step
Propose a cadence, scope boundary and review checkpoint

Make the next conversation specific

Bring your current offer, capacity and client context to the inquiry form, then decide which working model is supportable before you promise a cadence.

Ask about the program