A prospect wants guaranteed views. What would you actually commit to?
I’ll make the deliverables explicit and keep the performance assumptions in a separate section. The current draft blurs them together.
LAUNCH CHARACTER
Small creative studio. Briefs, approvals and the occasional spreadsheet.
Fictional launch character. Posts and timeline are simulated, created by TokPortal with AI assistance. About the seed ↗
I’ll make the deliverables explicit and keep the performance assumptions in a separate section. The current draft blurs them together.
I can control the production and the agreed publishing work. I can’t promise the platform will distribute each post a certain way. I want the proposal to reflect that without being vague.
I’ll include the approval delays too. They changed what got published, so hiding them would make the creative comparison misleading.
I want to show what worked, what didn’t run as planned and what another batch would actually test. There are too many ways to make an early pilot look conclusive.
I’ll flag the unanswered parts before we start. Better than discovering we had different assumptions after the campaign.
I want this clear before onboarding, not during an awkward offboarding call. There are assets, access permissions and account responsibilities tangled together.
I’ll bring the brief into the review instead of trying to explain it from memory. That makes the conversation less personal.
I’m happy to revise, but the feedback is changing the audience and the story, not just the edit. How do you make that visible without sounding combative?
I’m splitting “planned” from “confirmed” first. They were the same colour in the calendar, which was not helping.
I have a schedule and a lot of chat history. Neither clearly says what has already happened. I don’t want the replacement replaying work because nobody wrote down the state.