The Collab That Flattered Me Into a Bad Fit — and the Checklist I Use Now

Last spring, a creator I admired sent me a DM that felt like a warm hug with a business plan attached. She loved my voice, my feed, my 'whole vibe.' She said the project was 'basically made for me.' I read it twice, felt seen, and started clearing space on my calendar. Notice what I did not do: ask for a scope, a budget, a timeline, or a single written deliverable.

That collaboration looked like a dream on paper — mostly because there was no paper. It went sideways in the slow, polite way these things do. I want to walk through what I missed, not to relitigate a bad month, but because creators get pitched like this every day. The flattery is real. The risk is real too.

The DM Was the Red Flag

The message was long and specific about my work, which made it feel credible. She referenced two old posts and a newsletter I had forgotten I wrote. That level of attention is flattering, and it is also easy to perform. When someone leads with admiration and follows with 'we should do something,' the admiration can act like a deposit. It makes you feel like you owe them a yes.

Looking back, the clues were stacked right there. She described the project as 'fluid.' She said we would 'figure out the details together.' She mentioned a budget 'once we see how it performs.' Every sentence sounded collaborative. None of them sounded like a commitment.

Vague Deliverables Are a Boundary Test

We agreed I would create content for her audience and she would feature it on her platform. That was the whole brief. I did not know how many pieces, what format, who approved them, or when they would go live. I told myself we were being organic. In reality, I was handing over my time and my name with no shape around either.

The first ask was a short video. Then it became three videos and a newsletter mention. Then it was a live event appearance. Each request arrived as a small favor, so each one felt rude to refuse. That is how scope creep works: it does not show up as a giant demand. It shows up as a series of friendly asks that you did not agree to in writing.

Flattery Is Not a Payment Method

There was no upfront fee. I was told the exposure would be huge and the relationship would lead to bigger things. Maybe it would have. But exposure does not cover my rent, my software subscriptions, or the afternoon I spent reworking a video for someone else's feed. I am not against unpaid collaborations in theory. I am against unpaid collaborations that pretend to be paid opportunities until you ask a direct question.

The bigger issue was control. Without a written scope, I had no way to say 'this is outside our agreement' without sounding difficult. Without usage terms, I did not know where my face and voice could show up. Without a timeline, I could not plan around the work. I kept waiting for the partnership to feel real. It never did.

The Three-Question Gut Check I Use Now

Before I say yes to any collaboration, I run a short internal review. It takes ten minutes and has saved me from at least two expensive headaches.

First: can I explain the deliverables to a friend in one sentence? If the answer is 'kind of,' the answer is no. Second: is there a number, a date, and a person who approves the work? If any of those are missing, we are not ready. Third: would I still want this if the other person never complimented me again? That one stings, but it works.

My Actual Vetting Checklist

I keep a checklist in a Google Doc now. It is not glamorous, but neither is chasing an invoice.

• Deliverables: exactly what I am making, in what format, and how many.
• Timeline: draft dates, approval dates, and publish dates.
• Money: fee, payment schedule, and who covers production costs.
• Usage: where the content can live, for how long, and whether it can be edited.
• Exclusivity: whether I am blocked from working with competitors, and for how long.
• Approval: who signs off, and how many rounds of revisions are included.
• Exit: what happens if the project stalls or one of us needs to stop.
• Credit: how I am named, tagged, and linked.

If a collaborator pushes back on all of this, that is information. A real partner does not need me to be confused in order to feel comfortable.

What I Do Differently Now

I still get excited about collaborations. I want to. The difference is that I no longer treat excitement as due diligence. I ask for the boring stuff early, before I have emotionally moved my calendar around. I put the scope in writing even when the other person says it feels unnecessary. I keep the first project small enough that a bad fit does not take down my month.

The collaboration I missed was not a scam, exactly. It was a mismatch dressed in flattery. The lesson was not to stop trusting people. It was to stop outsourcing my boundaries to someone else's enthusiasm. My brand is built on the work I actually make, not the projects I almost made because someone said nice things in my DMs.