How to write a project brief for a contractor with Claude
Step by step: how to build a clear brief for a designer, copywriter or developer in one conversation with Claude, so you get the right result on the first try.
You hire a designer, a copywriter or a developer, explain the task out loud, and what comes back is nothing like what you pictured. Almost everyone who has worked with contractors knows the feeling. Here is how to close that gap in half an hour using Claude, the AI assistant from Anthropic that you talk to in plain text at claude.ai.
Why contractors deliver the wrong thing without a brief
The reason is almost always the same: the task lived in your head, and it reached the contractor as a couple of lines in a chat. A brief, a document that spells out point by point what, why and how the work should be done, closes that gap. With it, the contractor sees the same result you do before the work even starts, and stops guessing on your behalf.
The catch is that writing a brief is slow and boring, so business owners skip it and then pay for two or three rounds of rework. Claude removes that excuse: a full draft comes together in one conversation, and all you do is fix the details.
What a good project brief must contain
A good brief answers five questions, and the contractor should understand all five without calling you:
- What we are making. A concrete result instead of vague words. Not "a website", but "a one page site for booking manicure appointments with a request form and card payment".
- Why. Which business problem the work solves. This lets the contractor make small decisions alone instead of pinging you about every font.
- What you provide. The texts, logo, access, examples and references you hand over.
- What gets delivered. In what form the work is submitted: which files, in which formats, and where everything should live.
- Acceptance criteria. The specific signs that tell you the work is done, rather than "looks fine, I guess".
The last point is the one people drop most often, and it is exactly what saves you from arguments at payment time.
How to build a brief with Claude in one conversation
Do not ask Claude to write the brief straight away. It does not know your business and will start inventing. The right move is to have Claude ask you the questions and turn your answers into the document. Copy this request:
"You are helping me write a brief for a contractor. I am hiring [who: for example a copywriter for a landing page]. Ask me one question at a time until you have everything needed for a clear brief: the goal, the result, what I provide, the delivery format, deadlines and acceptance criteria. When you have enough, assemble the finished brief point by point."
Then just answer in your own words, briefly, without polishing. Claude turns "well, so that clients leave requests" into a concrete line in the brief. After ten to fifteen minutes of dialogue you have a structured document in hand.
How to check that the brief makes sense to an outsider
You know your project by heart, so you cannot see the gaps. Test the draft with Claude itself. Open a new chat, paste the finished brief and write:
"You are a contractor who just received this brief and has never heard about my project. Ask me every question you cannot start work without."
Every question Claude asks is a hole in your brief. Write the answers straight into the document and it becomes bulletproof. This trick is worth repeating for any text an outside person will read.
What to do when the contractor still asks questions
A real contractor will almost always clarify something, and that is fine. What matters is this: do not answer only in chat. Every answer that changes or refines the task goes into the brief itself. That way the document stays the single source of truth, and if a month later you disagree about who promised what, the answer sits in the file, not in a message feed.
If there are many edits, hand the whole thread to Claude and ask: "Build an updated version of the brief from these messages, and mark what changed compared to the previous one." You get a fresh version in a minute.
How to start right now
Take the next task you plan to hand off and run it through three steps: build the brief with Claude's questions, test it by having Claude play the contractor, then fill the gaps. Even if you used to work on a handshake, the difference shows on the very first order: fewer reworks, fewer arguments, a result closer to what you had in mind.
More walkthroughs of real work tasks with Claude are in our free materials: check the guides and try the first free lesson, where your digital twin learns to solve tasks like this alongside you.
AGINE Academy is an independent product and is not affiliated with Anthropic. Claude is owned by Anthropic.
Questions
For a one off trifle a verbal agreement is fine. But the moment money, deadlines and file handoffs enter the picture, a short brief of a few points pays off. It takes fifteen minutes with Claude and saves hours of rework and payment disputes.
No, and you should not let it. Claude does not know your business and will start making things up. Its strength is different: it asks the right questions and turns your plain answers into a structured document. The content is always yours.
Yes. The scheme is the same for design, text, code and ads: goal, result, input, output, acceptance criteria. Only the details inside the points change, and Claude adjusts its questions to the type of contractor if you say who you are hiring.
That is exactly what the acceptance criteria point is for. Check the delivery against it line by line. If the criteria were written concretely, the dispute is settled in a minute: either the point is met or it is not, and there is nothing left to guess.