An offer arrives in a DM: we work with AI accounts, paid posts, competitive rates, send your handle. No number, no brief, no contract, and a request to continue on Telegram. Sometimes it is a real agency having a bad week. Often it is a reseller who has already sold your audience without asking you, and who will disappear when the client asks why the post read like a press release.

The word network covers both. One is a roster with a process behind it. The other is a spreadsheet of handles and an inbox. You cannot tell which one messaged you from the pitch, because the pitch is identical. Six questions separate them, and every one has a checkable answer.

Ask before you post, not after. What follows is each question, the answer that should worry you, and the answer to get in writing before you spend an hour on a draft. None of it requires a lawyer, and all of it fits in one email. Agencies that work this way will send the answers without being pushed; the ones that will not are the reason the questions exist.

Who writes the post?

Watch for a draft in the first message, a template with the product name left blank, or the promise that a copywriter will “match your voice”. That last one means nobody has read your posts.

Ghostwriting leaves traces you can find in ten minutes. Three placed posts that open the same way. The same transition into the link. A closing line that sounds like a landing page in every one. Read them side by side and ask whether the same person wrote all three.

Ask who writes the sentences and who has final say over them. If the answer is the client, the agency is renting your account and your audience is paying for it. If the answer is “we collaborate”, ask what that means when the two versions disagree, because collaboration usually means the person paying wins.

One test settles it faster than any answer. Ask for a brief they have already sent a creator, with the client’s name removed. A real brief is short and specific: the claim, the facts, the objections, the assets. If they cannot produce one, they have been forwarding a product link and a deadline and calling it a process.

Our rule: the creator writes the post. We send a brief with one claim, three facts, the objection the post has to answer, the assets, and the window. A client who demands exact wording gets the brief declined. The terms are published.

What can the client change?

If a client can rewrite your sentences, they bought your account. The tell is an approval loop that never closes, or legal notes arriving with a new paragraph twenty minutes before the window opens.

Ask what the client sees before publication: the draft, the final text, or nothing at all. There is a legitimate middle here, and it is worth naming. A client reading the draft to check a factual claim is doing its job. A client editing your second sentence because it “does not pop” is writing the post and using your name to sign it.

Then ask the question that reveals the process: what happens when you and the client disagree and the clock is already running? A network that answers “we will sort it out” has never had to.

Our rule: one factual review round, answered inside 24 hours. Facts, links, and disclosure. No sentence rewrites and no tone notes. What the creator wrote is what publishes, and the window moves before the wording does.

How and when do you get paid?

Warning signs: payment on performance, payment once the client pays us, payment in exposure and future work, or a rate that appears only after the draft is written.

Ask for the number in writing before you commit. Then ask four more things. The payment date. Who invoices whom. What happens if the launch slips after you posted. And whether the fee covers the post alone or the post plus the reply hour, because those are different jobs and the second one is where the afternoon goes.

A network that will not name a figure in a contract before the work is done is telling you the figure is not real. The same goes for “competitive rates” in a first message: it is a sentence with no number in it, and it costs nothing to write.

Invoices matter more than creators expect. Ask whether you invoice the agency or the client, whether a purchase order is involved, and what happens when the client pays late. If the answer is that you wait, ask how long. The creator who finds out in month three that payment depends on a client’s accounts-payable calendar is the creator who stops answering messages from that agency.

Our rule: a fixed fee per post, agreed in writing before the creator commits, with the payment date in the agreement. Creators invoice ChirpLift, not the client. No commission, no per-impression payment, and no clawback when a post underperforms.

What happens when the product is bad?

You find out on launch day. The demo does not work, the benchmark in the brief came from a different build, or the claim holds only for a configuration nobody runs. The network’s position is that the product is not theirs.

Ask what happens when a client’s claim does not hold. Ask whether you can decline after reading the brief, and whether declining costs you future work. That second half is the part that describes the relationship: an agency that docks you for saying no is an agency that needs your yes more than your judgement.

Ask for access before you commit when the product allows it. A two-day trial answers more than a page of claims, and a client who will not give a creator a login is telling you something about the product.

Then ask what the network does when you are already committed and the problem appears. The good answer has a name attached to it: a person who will call the client, a window that can move, and permission for you to say in the replies that a feature is not ready. The bad answer is that the post is already scheduled.

Our rule: a product that would waste your audience’s time is not briefed. Read the brief, decline if you disagree, and lose nothing by it. If a problem turns up after you post, you say so in the replies. Nobody asks you to delete criticism.

What does disclosure require?

Any version of “we would rather it looked organic” is the answer. It arrives dressed as concern about reach, or as a claim that the label hurts distribution. The request itself tells you what the network thinks of your audience, and what it will ask you to do next time.

Ask exactly what the post will say about the payment: the platform label, a line of plain text, or both. Ask what happens if the client objects to the line. Ask it in writing, in the agreement, because on launch day you are the one answering for it in the replies and the client is not.

Our rule: every paid post carries X’s paid-partnership label and a plain-language line saying the creator was paid. A post that hides either does not run, and hiding it ends the relationship. There is no exception for a client who asks for one.

Can you leave?

Exclusivity rarely announces itself. It hides in a paragraph about category exclusivity, in a minimum post count, or in a retainer that turns a quiet month into a debt.

Ask what happens if you stop. Ask whether past posts have to stay up, whether you can work with a competitor of a past client, and whether a declined brief counts against you. Get the exit in the same document as the fee, not in a verbal promise made on a call you did not record.

Notice periods are worth reading twice. Thirty days is normal for a retainer and meaningless for per-post work. If the agreement asks for exclusivity in a category, ask what the category is, in writing, because “AI” is not a category and covering it would end your account.

Our rule: no exclusivity, no minimum post count, no retainer. Creators work with other agencies and other clients, including competitors. A quiet quarter costs nothing.

Six questions and an hour of email. A network that answers them in writing is worth a call, and the answers make the next conversation shorter. If a network will not answer these in writing before you post, that is the answer.