Should you propose another influencer collaboration? A repeat-project checklist
Review unfinished promises, contact preferences, and the new project scope before approaching a past creator partner. Includes two completed decision examples.
Before proposing another influencer collaboration, confirm that the previous project is closed, check the creator's latest contact preferences, and assess the new scope on its own terms. A successful earlier campaign does not mean the creator is available or interested now. If a payment question, promised deliverable, refusal, or contact restriction is unresolved, hold the new proposal and assign someone to resolve the record first.
This checklist is for a new project after an earlier collaboration, not a reminder to someone who has not answered your current pitch. Its output is a recorded decision: prepare one new proposal, hold it for a named reason, or exclude the person from that outreach. The examples are fictional; no creator was contacted to prepare them.
First decide whether this is a new project
| Situation | Appropriate work |
|---|---|
| The earlier proposal has no reply | Review its conversation and contact preferences using the history and follow-up guide |
| Work is still waiting for scope, approval, delivery, or payment clarification | Finish or resolve the current project with its assigned owner |
| The earlier collaboration is closed and you have a genuinely new brief | Use this repeat-collaboration review |
| A different person is taking over the existing work | Use the campaign handoff checklist |
Changing the campaign name does not close unfinished work. Nor does an old “happy to collaborate” note override a later refusal or stop request. Read the latest relevant conversation before writing a new pitch.
Check the previous relationship before the new opportunity
Start with the records that could rule out contact. Keep a reference and the time checked, rather than copying entire private conversations into a planning file.
| Check | Evidence to inspect | Decision when missing or conflicting |
|---|---|---|
| Earlier work is closed | Final deliverable/approval record, promised follow-through, shipping or payment questions where relevant | Hold; ask the internal owner to reconcile the open item |
| Current contact preference | Latest relevant Instagram conversation and the manual suppression ledger | Exclude a confirmed stop request within its scope; hold unclear or conflicting evidence |
| New reason to collaborate | Current content and relevance to the new audience and product | Hold if the only reason is that you already have the handle |
| Capacity and timing | What you actually know now, separated from dates in the old project | Treat availability as unknown until the creator responds to an appropriate new proposal |
| New offer is reviewable | Deliverable, dates, proposed compensation, review process, and proposed usage | Prepare the missing details before contact |
The person responsible for the old project should close its open actions. The new-project owner should not bury an unresolved promise under a fresh offer. If a stop request is clear, do not contact the creator to try to overturn it or approach through a second brand. If the scope is uncertain, hold while the internal reviewer checks the original evidence.
Write the differences before drafting the message
Use a short change note: previous project → proposed project. Write what the new project asks the creator to consider, including any new work using existing material. Do not describe earlier approvals, compensation, dates, or availability as automatically applying to the new proposal.
For example: “Earlier: one desk-setup Reel for the spring launch. Proposed: one newly made winter Reel, with separately proposed dates, compensation, and brand-channel use.” That tells the owner why this is new work. “Same again” does not.
Use the collaboration brief to prepare the proposal. If the new scope needs a fresh quote, use the rates inquiry guide. These are proposal-planning tools; they do not settle the creator's agreement or interpretation of an earlier contract.
Completed example 1: ready to propose, not approved to launch
All IDs and events below are fictional. IDs containing sample: are not valid Instagram handles.
| Review item | Recorded finding |
|---|---|
| Creator and organization | sample:partner_a, sample_org |
| Previous project | sample_spring_01, one desk-setup Reel |
| Closure evidence | Final content approved 2026-10-15; payment confirmation recorded 2026-10-17; owner closed remaining actions 2026-10-20 |
| Current preference | Conversation reviewed 2026-11-10 10:00 KST: creator invited a brief for the next project; no applicable restriction found in reviewed brand/organization records |
| New scope | sample_winter_01: one new winter Reel, proposed publication 2026-11-30; compensation and proposed brand-channel use written in brief v1 for fresh review |
| Still unknown | Current availability, acceptance of the proposal, and any requested changes |
| Owner and next action | sample_project_owner checks brief v1 and prepares one invitation to review it |
| Decision | Eligible to propose after campaign preflight; no campaign work or publication assumed approved |
Draft for this fictional context: “Hi , thank you again for the spring desk-setup collaboration. We have a separate winter project in mind: one new Reel, with proposed dates, compensation, and brand-channel use in a fresh brief. Since you invited the next brief, may I send it for your review?”
The message explains why the team is returning and presents the new decision. It does not assume acceptance because the previous work went well. The current invitation to share a brief is the supporting context here; do not copy that claim into a real message unless the conversation supports it.
Completed example 2: hold the new proposal and resolve the old work
This case is also fictional and uses a deliberately invalid sample ID.
| Review item | Recorded finding |
|---|---|
| Creator and organization | sample:partner_b, sample_org |
| Previous project | sample_autumn_02, content delivered but a payment question remains unresolved in the work notes |
| Previous refusal and latest preference | Conversation checked 2026-11-10 10:15 KST: creator declined the 2026-11-01 winter offer and asked for no new offers while the payment question is being checked |
| Proposed new idea | A second winter concept under another brand in sample_org |
| Conflict | A team note says “repeat partner, okay to pitch,” but predates the decline and contact preference |
| Owner and next action | sample_operations_owner reconciles the payment question through the existing project process and records the latest evidence; sample_project_owner removes the new pitch from prepared recipients |
| Decision | Hold all new offers from this organization while the stated condition is unresolved; no second-brand approach and no sales reminder |
| Review trigger | Internal evidence that the old issue is resolved, followed by a fresh check of the current contact preference. Resolution alone does not authorize a new pitch |
Completed internal handoff note: “Do not send the second winter proposal to sample:partner_b. The 2026-11-01 refusal and latest contact preference take priority over the older repeat-partner note. Operations owns the open payment question. Keep the new offer on hold and re-evaluate contact preferences before any future proposal.”
There is no new sales DM to send in this case. Routine resolution of an existing project belongs to that workstream, not to a new outreach campaign. If review instead confirms a broader stop request, record its scope in the suppression ledger and exclude the person accordingly.
Turn the review into a usable decision
- Identify the prior project, new project, brand, organization, and owner.
- Inspect closure records, later refusals, and current contact preferences. Preserve a timestamp and evidence reference.
- Resolve restrictions first. Exclude confirmed stop requests within their scope; hold unfinished work, uncertain identity, or conflicting records.
- Write the new scope and what changed. Mark availability, quote, and acceptance unknown until verified.
- Record prepare, hold, or exclude, with one next action and the owner. Keep held people out of prepared sending files and remaining campaign recipients.
- If eligible, complete the brief and preflight before preparing one appropriate proposal. Record the actual response manually and revise the next action accordingly.
DM Studio can help send a separately prepared message, but it does not infer relationship quality, settle project completion, detect a reply, or share a team CRM. Keep project decisions in your manual outreach tracker. External notes do not automatically update a saved campaign.
Frequently asked questions
How long should we wait before proposing another project?
There is no universal interval in this checklist. Use project closure, a relevant new opportunity, and current contact preferences. A calendar date alone does not resolve an unfinished promise or clear a stop request.
Can we reuse the old brief and quote?
Use them as background, then state what changed and what needs fresh confirmation. Do not present earlier scope, compensation, availability, or approvals as automatically carrying over. Prepare a reviewable new brief before asking for a decision.
What if the creator declined one project but not future contact?
Record the precise refusal and context. A declined idea is not automatically an organization-wide stop, but it is not an invitation to keep pitching variations either. Hold when future-contact scope is uncertain, and check the latest conversation before deciding on a new approach.
Does “repeat partner” mean we can bypass the suppression review?
No. A later preference can change what contact is appropriate. Check the same brand and organization records you would check for a new candidate, and do not use another sender or brand to evade a restriction.