It starts with a handshake or a Zoom call. You pitch your idea. The client seems excited. You do the work — a logo, a spec document, a prototype, a campaign concept. You deliver it.

Three months later, they launch something that looks remarkably like what you built. When you bring it up, you hear: "We were already thinking along these lines before we talked to you."

This is not a rare scenario. It's common enough that there's a name for it: spec work theft. And it's extraordinarily hard to fight after the fact.

Why freelancers are especially vulnerable

Employees have paper trails — Slack messages, internal wikis, tracked commits, email threads with colleagues that establish timelines. Freelancers often have only their own records, which are easy for opposing parties to dismiss as self-serving.

NDAs help with confidentiality but don't prove creation date. Contracts define ownership but assume everyone agrees what was created and when. Invoices show billing dates, not creation dates.

The moment you're in a dispute, you're trying to reconstruct a timeline from emails, file metadata, and memory — all of which can be challenged.

The specific situations that cause problems

Spec work and proposals. You create a detailed proposal — wireframes, strategy deck, technical specification — and the client passes on the engagement. Later you discover they built exactly what you proposed, internally. Without a timestamped record of your proposal, proving prior art is nearly impossible.

Discovery disputes. A client claims the direction you took was their original instruction, not your creative contribution. Who conceived of the specific approach? Without a timestamp on your initial draft, it's your word against theirs.

Delivery disputes. The client claims the final deliverable doesn't match what was scoped. You need to show what you actually delivered, not what they're now claiming you delivered.

Revision ownership. In long engagements with many iterations, questions arise about which version of the work is the "original" and whether subsequent modifications belong to you or the client.

The habit that prevents most of this

Seal your work before you send it. Every significant deliverable, every proposal, every design iteration that represents your creative contribution — sealed before it leaves your hands.

When you seal a document, you get a cryptographic timestamp: a SHA-256 hash of the exact content, signed with an Ed25519 key, certified by an RFC 3161 timestamp authority, and anchored to the Bitcoin blockchain. The public verification URL is permanent, verifiable by anyone, and tied to that specific version of that specific file.

What this means in practice:

  • You can prove the proposal existed before the client's alleged "internal development"
  • You can prove the final deliverable was exactly what you claim it was
  • You can produce a verifiable chain of dated documents showing your creative process

The moment it matters

Most freelance IP disputes don't end up in court. They end when one party can produce evidence quickly and the other can't. A public verification URL that you can pull up in ten seconds — showing your exact proposal content, timestamped three months before the client's product launch — changes the dynamics of that conversation immediately.

Bad-faith clients are counting on you not having this. They're right about most freelancers. Don't be most freelancers.

What to seal

  • Every proposal before you send it
  • Every significant design iteration
  • Every final deliverable before handoff
  • Your scope documents and creative briefs
  • Any reference materials or mood boards that represent your creative direction

50 seals free every month. Seal the next proposal before you hit send.