Spec work has one definition and it has not changed: design produced before anyone has agreed to pay for it, on the chance that payment follows if the client likes the result. Finished work first, fee later, maybe.
What changed is the supply side. A client can now type a paragraph into a prompt-to-mockup tool and arrive in your inbox with something that looks like a homepage. A contest can collect fifty entries in an afternoon because entrants are generating rather than drawing. The unpaid pitch did not go away when the tooling arrived. It got faster to request, cheaper to fake, and harder to refuse.
That leaves the designer with a second problem. You still have to decline the free pitch, and you now have to answer a question nobody asked in 2019: did a machine make this? Both have the same answer, which is the point of this article and of the Proof of Work hub.
The short answer. Spec work is still finished work delivered before a fee is agreed, and the generated mockup is its newest and most deniable form. Refuse it the way you always did, then keep the process record that shows the work is yours. That record closes the spec request and the "was this generated" question in one move.
What spec work is, and what did not change
Clients now use new words for an old ask. The site's plain-language explanation of what spec work is covers the mechanics: the designer speculates that unpaid effort will convert into a paid engagement, and the client keeps the option to walk away with the file. If the deliverable arrives before the contract does, it is spec, whatever the email called it.
The value has not moved either. Design is mostly the part the client never sees: the research, the discarded routes, the decision about which problem is actually being solved. A generated mockup skips all of it and produces the export. AIGA's position on spec work has argued for years that the practice harms clients because it severs the link between research and result. Generated entries sever it completely.
The four forms, updated for generated output
The open contest
Post a brief, collect entries, pay one, keep the option to use any. The breakdown of design contests explains why the volume of submissions was never proof of value. In 2026 a meaningful share of entries are generated from the brief text. The client sees a hundred options and holds a hundred renderings of the same prompt.
The invited shortlist
A few studios are asked to "share some initial thinking" before the contract. Agencies with reputations rarely submit generated comps under their own name, so the pressure shows up as a shorter timeline: if a competitor can turn three directions around in a day, the only way to match it is to generate.
The paid trial
A scoped first project at a steep discount. A fully paid trial is fine. The discount is the tell, and it has got steeper, because the client now believes a landing page "takes an hour." It takes an hour to generate one. Designing one that works takes what it always did.
The generated-mockup ask
The client arrives with a file they made themselves and asks you to "make it real" at a fraction of a design fee. The article on AI mockups as the new unpaid pitch covers this form in detail. The mockup is the client's spec entry, submitted to you, and the reduced fee prices your work as finishing rather than design. Every problem in it becomes yours to solve without the budget.
| Form | What the client thinks they are buying | What they actually get | The reply |
|---|---|---|---|
| Open contest | Many original ideas, pay for the best | Near-identical generated renderings, no research, no one accountable | Decline, offer a paid discovery phase |
| Invited shortlist | A low-risk preview of each studio's thinking | Fast comps built to win the pitch, safe rather than right | Offer a paid concept sprint, fee credited to the project |
| Paid trial (discounted) | A cheap test of the relationship | A rushed job at a rate that anchors every future quote | Accept at full rate with a tight scope, or decline |
| Generated-mockup ask | A head start that should cut the fee | A brief disguised as a deliverable, hard decisions unmade | Treat it as input, quote the full project, keep the process record |
Why generated entries make contests worse for the client
The designer's objection to spec was always about labor. The client's was weaker: the risk of mediocre work. Generated entries change that.
First, the output is undifferentiated. Entrants using the same category of tool, working from the same brief, converge on the same solutions, and so will any competitor who runs the same brief next year.
Second, there is no provenance. The client cannot establish who made the winning entry or whether it reproduces someone else's work. The US Copyright Office's registration guidance on AI-generated material states that material produced by a machine without sufficient human authorship is not registrable. A client who "wins" a generated logo may own nothing enforceable; the article on copyright and ownership of generated logos covers the consequences.
Third, no one can defend the decisions. When the board asks why the brand resembles a competitor's, the entrant is gone and could not have explained the choices anyway, because no person made them. A designer who did the work can walk into that room and account for every one.
Proof of process answers both questions
The spec request and the authorship question are usually treated as separate headaches. They have the same cure: a record of how the work was made.
A client sends a mockup and offers a third of your rate. If your reply includes a short description of your process (discovery call, two rounds of sketched directions, a version-tracked build, a decision log), you have explained why the fee is the fee, and you have described the artifacts that will exist at the end, which no generated file can produce.
The same artifacts settle the authorship question. The article on how to prove a design is yours walks through them: source files with layer structure, dated iterations, the discarded routes that show a person choosing. Figma's version history records every autosave and named checkpoint, and Adobe can attach Content Credentials to an export. The lane's guide to what Content Credentials record for designers explains where that record helps and where it does not.
A designer with a process record is hard to ask for spec, because the record makes the value of the unpaid part visible, and hard to accuse of passing off generated work, because the record shows the hands. The spec value calculator puts a figure on that unpaid part.
The reply script
You do not need to lecture anyone. You need one message that declines the spec arrangement, reprices the mockup as input, and puts the process record on the table.
Thanks for sending the mockup, it is useful as a starting brief. I should be upfront about how I work: I do not produce finished design before a project is agreed, and I quote from the problem rather than from a draft, because most of the work is deciding what the draft should have been. If you would like to proceed, the first step is a paid discovery session, with the fee credited to the project. Everything I deliver comes with the working files and version history, so you will always be able to show where the design came from and that it is yours to use.
Use it when a client arrives with a generated file and a reduced budget.
Frequently asked questions
Is a generated mockup from the client spec work if I did not make it?
The mockup is the client's spec entry, and the ask attached to it is spec in reverse: you are being asked to price finished-looking work as if the design were done. Treat the file as a brief and quote the project. The arithmetic of spec work does not care who ran the prompt.
Can I enter a contest and use a generator to keep my time cost near zero?
You can, and you will be one of fifty people producing the same output. You have also handed the client a file with no provenance and put your name on it, and if the entry reproduces protected work, yours is the name that gets the letter.
Does keeping a process record mean I cannot use generative tools at all?
No. It means the record shows where they were used and what a person did afterward. A version history with a generated starting frame followed by forty saves of human decisions is still a record of authorship. The AI disclosure clause article covers writing that into the contract.
How do I disclose generated work I did use without undercutting my fee?
Disclose it as a tool, as you would a stock library or a type foundry. State what was generated, what was edited, and what was designed. The site's pillar on AI and the designer covers pricing and scoping generated work so the disclosure reads as professionalism rather than confession.
What to do on Monday
Reread the last three inbound requests and name the form each one took. At least one is usually a generated-mockup ask hiding inside a "quick question." Reply with the script above and file the mockup as a brief. Then check that your current project has a version history and that the discarded directions still exist. That is your proof of process, and it is the asset that lets you decline spec work without an argument.
Start with the Proof of Work hub, then read how to prove a design is yours for the artifact-by-artifact checklist.