Spec Work in the AI Era: The Free Pitch, Now AI-Generated
The arithmetic of spec work has not moved: finished work before a fee. What moved is who can produce the finished-looking part, and what a designer now has to prove.
Pillar 05
Proof of Work
The no-spec argument has always rested on one fact: design is the work, and the file is just the receipt. Spec work was wrong because it asked for the receipt before agreeing to pay for the work. Generated mockups are the same request with the production handed to a machine. What has changed in 2026 is that the designer now has a second problem, which is proving that the work happened at all.
That is what this pillar is for. Proof of work means provenance and authorship for designers: the process files, version history, signed Content Credentials, disclosure clauses and portfolio records that show a piece of design was made by you, in your studio, by the route you say it was. It is the paid answer to the free pitch, because a client who can see the process stops asking for the comp. It is also the honest answer to the client who arrives with an AI-generated logo and wants to know why it cannot simply be "finalised".
The pieces here are practical. Each one ends with something you can use on Monday: a reply to paste into an email, a clause to hand to a lawyer, a checklist for a case study, a table of what each kind of evidence actually proves. None of them sell a tool. Where a standard exists, such as the C2PA specification behind Content Credentials, we explain what it records and, just as carefully, what it does not.
Read them alongside the older pillars. What spec work actually is still defines the request; AI and the Designer covers pricing and scoping when a generated draft is on the table; Rates, Contracts, Scope holds the contract language this pillar adds a disclosure clause to; and The Professional Record keeps the history that explains why the profession is having this argument for the third time. The AI disclosure clause tool and the spec value calculator are the working companions to the essays.
Two threads run through everything here. First, evidence is cheap to keep and expensive to reconstruct: name your versions, export the history, write the process note while you still remember why you rejected the second direction. Second, disclosure is a line item, not an apology. A contract that says what was generated, by whom, and what is warranted protects the designer and the client equally, and it is the only thing that makes "did a machine make this" a question with a documented answer.
Maintained by the no-spec editors. Last reviewed September 24, 2026.
All pieces in this pillar
AI Mockups Are the New Unpaid Pitch
A generated render arrives with the fee already set at nothing. What the file is actually missing, and how to price the work that remains without arguing about the render.
How to Prove a Design Is Yours: Process Files, Version History, Provenance
The evidence a working designer keeps so that authorship can be shown on demand, what each layer proves, what it cannot, and the difference between making a design and owning it.
Content Credentials for Designers: What C2PA Records and What It Does Not
A working designer's guide to Content Credentials: what the signed C2PA manifest actually records, how to attach it at export, how a client checks it, and where it stops being proof.
The AI Disclosure Clause: What a Design Contract Should Say
Why a clause beats an apology, the three things it has to settle, a client-side version, and two drafts you can paste into your next agreement before a lawyer reads it.
Portfolio Provenance: Showing Process So the Work Is Believed
A polished portfolio can now be made without doing the work. What each case study should show so a hiring manager or client believes it, and why the same page answers the spec request.
AI-Generated Logos: Copyright, Trademark and Who Owns the File
A client arrives with a free generated logo and asks you to finish it. Here is what they actually own, what the Copyright Office will register, and how to price the job.
Version History as the Design Record: Figma, Adobe and Proof of Authorship
What the version history in Figma and Adobe actually records, where each tool quietly throws it away, and the habits that turn it into a record you can hand a lawyer.