1. How it usually happens
The scene is familiar: discovery call, enthusiasm, "send me a quick proposal so we see if we can work together".
You prepare:
brilliant headline, landing structure, creative concept, maybe some visual or ad copy. You send everything.
Then three classic variants happen:
- client disappears
- client returns months later with surprisingly similar campaign
- client passes your material to another supplier "to develop it"
The curious thing is there's often no strategy behind it. Drafts travel inside companies as internal notes, are saved, modified, reworked. At some point nobody remembers where they came from.
A copywriter told of finding his exact word-for-word headline on a live campaign for a client "still evaluating". Client, in good faith, thought it was an internally born idea.
2. What you need to prove
Here the point is not proving idea is genius. You need to prove it already existed in a precise form and before a certain use.
Concretely:
- that draft (landing or campaign) was already structured
- that it included distinctive elements (copy, structure, visual concept)
- that it was shared on a certain date
- that any subsequent versions derive from it
- that content is not generic but recognisable
In practice:
"This proposal already existed like this, before appearing elsewhere."
3. What to collect
For a creative draft, value lies in details. The more complete material is, the clearer the work done.
Collect:
- landing mockup (Figma, PDF, complete screenshots)
- page copy (headline, sections, CTA)
- ads concept (texts, visuals, variants)
- source file (Figma, PSD, copywriting documents)
- email or messages sending proposal
- any voice notes or calls explaining concept
- received client brief
- intermediate versions if showing evolution
A useful detail: full landing screenshot (full scroll) is worth more than three separate images. Tells the logic, not just pieces.
4. How to proceed
Effective protection starts before sending draft.
When you have a ready proposal:
- gather everything in coherent set (mockup + copy + notes)
- export stable version (PDF or complete images)
- assign clear file name (client + date + proposal type)
At this point:
- use ExistBefore to timestamp that version
- keep original files without modifying them
- send proposal via traceable channel (email, platform)
After sending:
- avoid updating same draft without creating new version
- if modifying, repeat process
- keep link between file and communication
A useful habit:
before every "exploratory" send, create a small documented package. Takes a few minutes and prevents infinite reconstructions later.
5. Mistakes to avoid
Some behaviours make drafts easily reusable without trace:
- sending only editable links (e.g., Figma without snapshot)
- sharing ideas in chat without ever saving them in structured file
- sending partial screenshots not telling complete project
- not keeping source files
- reusing same file updating it without versions
Other useful precautions:
- always insert context reference (client, project) in draft
- avoid overly "clean", adaptable materials without context
- keep explanations too, not just files
Free timestamping lets you quickly secure every proposal, so you have a clear reference if material resurfaces elsewhere.
6. After documenting
Once you have documented draft, you can also better manage client relationship.
You can:
- clarify it is preliminary material
- better define what is included and what is not
- use draft as base for formal proposal
- monitor any reuses over time
If you notice suspicious similarities:
- collect published campaign or landing examples
- compare them with your material
- evaluate direct confrontation, starting from concrete elements
Having orderly documentation changes how you face these situations: fewer abstract discussions, more clear elements to base on.