Interactive field guide
Should this become recurring work?
Use five observable checks to decide whether to document a proposal, run a bounded pilot, clarify the fit, or step away.
Before you propose
Review the full retainer-client fit guide for discovery context.
Select the state that matches evidence you can name, not a hopeful assumption.
Let the result set the next conversation, not promise an outcome.
The scorecard
Evidence first. Direction second.
This is a conversation aid for a prospective client relationship. It is not a test of your worth or a prediction of what the work will produce.
Assessment in progress
Check all five areas before choosing a direction. 0 of 5 assessed.
Progress
0/10
editorial points · 0/5 checked
Next step: Use the prompts to collect observable evidence, then select one state in every area.
Budget & payment readiness
A recurring arrangement needs a payment process that can be named before you reserve capacity.
- The client can describe the recurring content need and the budget or payment process attached to it.
- Invoice timing, deposit expectations, usage fees, and what changes the scope are written down.
Recurring demand & next cycle
Look for a real upcoming cycle, not only a general statement that the brand wants more content.
- There is a defined upcoming campaign, launch, publishing cycle, or testing window.
- The recurring deliverables, formats, turnaround, and client inputs can be counted.
Communication & decisions
The working rhythm should make it possible to get useful briefs, decisions, and feedback on time.
- You know who owns the final decision and how questions will be answered.
- The feedback channel, review rhythm, revision limit, and response expectations are agreed.
Discovery fit & rights
A retainer proposal should follow a specific fit conversation about the audience, product, and work.
- Audience, product, channel, creative scope, and required inputs are specific enough to brief.
- The client can confirm permissions, claims review, likeness or asset use, and the requested rights.
Warning signs & boundaries
Risks are decision data. Naming them is a way to protect the working relationship, not a judgment about a person.
- Payment or rights are not vague; scope is not unlimited or shifting; and approvers are not in conflict.
- The timing is workable and no one is asking for unsupported guarantees or unsafe working conditions.
Keep exploring
Make the next conversation specific.
Read the full fit guide for questions and warning signs, or ask for program details if you want context on the wider creator pipeline.