Make the context permanent
The last chapter said context does most of the work. This one stops you typing it out every single morning.
If you took the previous chapter seriously, you have hit the obvious problem. The context that makes the output good is largely the same context every time: the same client, the same brand rules, the same audience, the same list of things that always get rejected. Typing it into every new chat is tedious enough that after a week you stop doing it, and the quality quietly falls back to generic.
A project fixes that. It is a container that holds files and standing instructions, and everything you do inside it starts with that context already loaded.
The rule I would give anyone: Not one big project called Work.one project per client or per workstream.
Load it with what does not change
Put in the things that would be true in three months. The brand guidelines. The tone of voice document. The signed brief. The media plan. The audience definition. Last campaign's results, if the numbers still matter.
Leave out the things that change weekly. A project stuffed with every version of every deck is worse than an empty one, because now it has three contradictory answers to the same question and no way to know which is current.
Files in a project are held once rather than re-read on every message, so this is also the cheaper way to work with the same documents repeatedly.
Write the standing instructions
Every project has an instructions box, and it is the difference between a folder and a colleague. This is where the account knowledge goes: not what the documents say, but what you know that the documents do not.
This project covers [client], a [category] brand in [markets]. The audience is [audience]. We are the media agency, working to [the commercial objective in one line].
What you should know: the client is conservative on [x] and has rejected [y] twice. Their internal language for [thing] is [term], so use that. Budgets are in AED and reporting is in GST. The stakeholder who signs off is [role], and they care most about [the thing they actually care about].
How to work in this project: reference the brief and the brand guidelines before answering. If something is not in the files, say so rather than assuming. When I ask for a recommendation, give me one, with the reasoning and the assumption it rests on. Critique my thinking before agreeing with it.
Cold chat versus project
Ask the same question in both and the difference is immediate.
In a cold chat, "draft a response to this brief" gives you a competent, anonymous document that could belong to any agency and any client. It is not wrong. It is just generic, and you will spend an hour making it specific.
In a properly loaded project, the same six words produce something that already uses the client's vocabulary, already avoids the angle they killed last quarter, already frames the recommendation for the person who signs it off, and already knows what the budget is. That hour of making it specific is the hour you just saved, and you saved it by doing the setup once.
The most common mistake is one enormous project holding four clients. Context stops being an advantage the moment it becomes ambiguous, and a model that can see four brand guidelines will blend them. Narrow projects, clearly named, every time.
The compounding bit
The instructions box is not a one-time write. Every time you correct something, ask whether that correction belongs in the project. "Never lead with reach, this client only cares about cost per acquisition" is a note you might give twice in a week verbally. Written into the project once, you never give it again.
Done consistently over a few months, the project stops being a folder and becomes the account's institutional memory, which is usually the thing that walks out of the door when someone leaves.
Build one project for your busiest account. Give it the brief, the brand guidelines and ten lines of instructions. Then take a question you already answered this week and ask it again inside the project. If the answer is not noticeably more specific, your instructions are too polite. Be blunter about what the client rejects.