Stop Correcting, Start
Delegating to Claude

Running a web design agency for ten years and then working as a business manager in a small marketing firm for another ten certainly taught me this: a bad brief gets you a bad result, no matter how good the person on the other end is. Vague instructions, no reference points, "just make it pop" - and you'd be back for revision round three still nowhere near what the client actually wanted. The problem was never really with the designer. It was that nobody had agreed what "finished and good" looked like before the work started.

Claude works exactly the same way, and most people brief it like they've never briefed anyone in their life. One rushed line, hit send, hope for the best - it's using Claude like a one-armed bandit and expecting a jackpot. When it comes back wrong, they correct it. It comes back different but still wrong, so they correct it again. Ten messages later they're worn out, and what they've got still isn't quite right.

The people who get real hours back each week treat it differently. They take a proper brief before anything gets built, then they leave it alone to get on with the job. No hovering, no re-explaining, no chasing revisions. That's the whole shift - and it's the same shift that separates a smooth agency job from a painful one.

We came across a similar framework in a guide by Mariah Brunner, which is worth a read. Here's how we actually put it into practice running Claude Cowork day to day for BUDD 7 and our clients.

Take a proper brief first

No creative or designer worth their fee starts work without a brief. Same principle applies here: before Claude touches a single file, get it to think the whole job through and show you its approach first. In Cowork, tell it plainly - "don't make any changes yet, walk me through your approach first" - and it will read what it needs, reason through the job, and hand you a plan to sign off before anything is created or edited.

The value is mistakes get caught on paper, not in the finished document, spreadsheet, or website file. It costs you two minutes of reading. It saves you the round where you have to explain, again, that it's gone off in the wrong direction.

Ask the questions a good (prompt) designer would

A good designer never takes a one-line brief at face value. They ask about the audience, the must-haves, the tone, the deadline - because the client rarely spells out everything they need first time, and why would they? Claude will do exactly the same, but only if you tell it to. Add a line like this to almost any request:

That single sentence changes the whole dynamic. Instead of filling the gaps with guesses, it surfaces the decisions that are actually yours to make - tone, format, which job this is for, what "finished and good" looks like. You answer a few quick questions up front, and you'll skip whole rounds of "no, not quite like that."

Once it's briefed, get out of the way

This is the part that actually buys back the hours. Once you've got a plan you're happy with, you don't need to hover over every stage like some kind of micro-manager. In Cowork, this is what the task list is doing in the background - breaking the job into stages and working through them in sequence rather than stopping to ask permission at every turn.

This only works safely because you did the first two steps properly. You're not turning it loose on a vague idea, you're letting it execute a brief you've already seen and signed off. That's the difference between reckless and efficient, and it's exactly why we always insist on a quick plan-and-approve step before the AI gets to work.

Keep the style guide current

Every marketing department or agency has a style guide, and every new starter reads it before they touch a live project. Project instructions do the same job for Claude - they're what it reads at the start of every session to understand your business, your preferences, and how you like things done. The better the file, the less you ever have to repeat yourself. It's genuinely one of the biggest time-savers a small business has available to it.

Make it a habit: any time you teach Claude something, correct a recurring mistake, or agree a new way of doing things, tell it to add that to the project instructions so it remembers for next time. Each session starts a little sharper than the last. One rule worth keeping though - don't let the file balloon. It's loaded in every time, so a bloated file quietly wastes space that could be used thinking about your actual request. When you add something new, it's worth trimming something old or no longer relevant.

The brief, ready to copy

Here's a brief template built around the same principles, adapted for Cowork. Paste it at the start of anything you want to properly hand off, fill in the one bracket, and it takes care of the questioning and planning stage automatically.

If you find yourself doing a certain kind of job often, it's worth saving this as a Claude skill rather than retyping it each time - or you can add it in your project instructions.

Fewer rounds, better work

Briefing properly isn't a time waste, it's the opposite. You make the decisions up front, where they're quick and easy to change, then let Claude get on with carrying them out. Brief, approve, release - the same process that back in the day made the good agency jobs great. That's how a twenty-message correction marathon turns into a few good questions and a finished result, first time.

This is exactly the kind of thing we can help small business owners get to grips with as we support their adoption of AI - not just what it can do, but how to actually brief it so it saves you time rather than creating another new job of double-checking everything. If that's the bit you're stuck on, give Natasha a buzz in the chat.