You own the product, the date and the invoice. The design for the new flow sits in a design file, the small change you need sits in a chat message from three months ago, and the half page the sales team promised exists as a screenshot with no note about which environment it came from. Then the first build arrives, and it is not what you pictured. The developer can usually do the work. What they received was a thread.
A brief a developer can build from is a short pack, not a longer chat. It reads like a purchase order: the outcome you would approve, the current system, what done means, and one line on what this invoice does not buy. It does not try to name every class. Send it before the work starts, and use the same shape next month when the same team returns with another request. The goal is simple: a release you recognize, without a production surprise on the day you promised.
1. Where the surprise actually comes from
The surprise appears in review, not at kickoff. The page exists, and the traffic can already go there. You still reject it, because one step you care about was never written down: a payment state, a branch that must not see another branch, a form field sales said was required. The build did what it was told to do.
You hold the intent, the developer holds the repository. Each side assumes the other side filled the gap. Chat feels fast, so the gap stays in chat. A week later nobody can point to the message that decided the behaviour. Inherited products fail in the same place: a new team spends its first week finding out what is actually running, because a brief that lived in one person's head arrives in the same condition.
Write three lines before you attach files.
2. What to attach every time
A folder called “assets” and a sentence like “make it match the design” is not a brief. The developer can open the folder. They still cannot tell which file is current, which page or flow is in scope, or what to do when the design and the live product disagree.
Attachments usually follow the tool each person uses. A designer sends a file. A colleague sends a landing page URL, and sometimes a password in a private message because that helped once before. None of that is a brief: the developer fills the missing part by guesswork, and the guess becomes the thing nobody approved.
Attach the pack in one fixed order, every time. A fixed order is what lets the next person check your work without asking you first.
If part of your revenue comes from an online store, name the platform it already uses and name the shopping step that must change. Improve conversion does not tell anyone whether the change is in the catalog, the cart, or the return from payment. Adapting a live store is a different job from building a new one. The brief should say which job this is.
3. Write the behaviour, not the decoration
A brief that specifies colours but leaves the rule unstated will be tested on the rule. You will check who can see a record, what happens when a payment fails, and what the report must contain after a call is scored. Decoration is visible in a file. Behaviour appears only when a person tries the flow.
If your product connects to telephony, mail, accounting or a CRM, the result will be judged in the system your team already uses, not in the pull request. On one CRM project, call scoring connected telephony, messaging and accounting, then showed the result in a report. A retry was not allowed to create a second score, and one branch could not read another branch’s records. You do not need that exact stack in the brief. You need the equivalent sentences: which systems are in scope, what the person should see when the processing finishes, and what must stay true if the job runs twice. Add AI is not one of those sentences. The product is yours, so nobody else can answer this question for you.
For each flow in scope, write this:
4. Hand over the request, not the thread
A brief is a purchase order, and the developer builds what is written on it plus whatever the empty spaces allow. Treat it the way you treat any order: it names the buyer, the item, and the moment it was placed. A request priced from a call or a chat gets the cheapest reading, because that reading fits between two other tasks. Your own words then become a budget you never approved.
Questions will arrive, and that is normal. One rule keeps the gap closed: an answer given in chat is not an answer until it is in the brief. Paste the decision back into the document with a sentence of context, and the next question starts from the newer state. If a colleague promises a change in a call, the same rule applies. A promise that lives only in a recording is a promise the build cannot hear.
The same rule covers new ideas. Mid-flight, someone asks for something that is really a second order; the brief lets you park it without an argument, because the boundary was written before the work. When the scope does move on purpose, do not rewrite history: put a new three-line header at the top and mark the previous one as replaced. The file then shows what was ordered first and what was added later.
Access belongs to the order as well. Name which accounts the developer will receive and by when. “We will send access later” is not a plan: the developer either waits, or logs in to the only place that exists, which is production. If there is no second environment yet, say so in the brief before you promise a date, so the risk is priced while it is still cheap. Secrets still do not travel in the document. The brief lists the systems, and access comes through accounts your company controls.
5. One shape for every request
A defined project needs the whole pack. Ongoing work needs the same shape in a smaller form: outcome, boundary, what done means. The smaller form is what keeps a long collaboration from dissolving into a chat archive that nobody can quote back.
The shape also shows what an estimate is missing. A developer who can name what they are not doing in this release has read your order correctly. A vague answer means the brief failed at the one job it has, and the missing conversation happens anyway: later, and at a worse price. Fix the order, not the mood.
Reuse the file rather than starting a new one. Copy last month’s pack, change the outcome line, and the developer opens the same page you do. A new document every time recreates the thread you were trying to escape.
When to bring the developer in early
You can assemble this pack before a developer opens the repository. Bring them in before you promise the date when the change touches payments, a shared customer database, or a system you cannot describe, or when the current product was inherited and nobody has confirmed a second environment. A developer who sees the brief only after the team has heard it is nearly done inherits the surprise with you.
I take scoped work from product owners and teams, and the development that follows a written order. Services cover a defined project or an ongoing collaboration: performance, SaaS and backend systems, and AI integration. Selected work shows the kind of systems these briefs land on: an inherited product, an online store, a CRM that already has customers, each kept to the scope of that job. If your release needs a developer who works from a written pack, start with product development from scratch or write to me. Attach the outcome, what done means and the platform name. Nothing secret needs to travel with that note.