Home/Claude Cowork/Briefing Guide
A working method

How to brief Claude Cowork
like an operator.

Most disappointing Claude Cowork output traces back to a vague ask, not a weak model. Here's the structure that gets you a usable first pass instead of a generic guess.

Briefing Claude Cowork well is the same discipline as briefing a capable assistant, just written down instead of assumed. Five things separate a brief that produces something you'll actually use from one that produces a generic first guess.

01

Name the task, not the tool

Not "help me with this spreadsheet", but "turn this weekly sales export into a one-page summary my manager can read in two minutes". Claude Cowork works towards an outcome far better than towards a vague request for help.

02

Hand over the actual inputs, not a description of them

The real spreadsheet, the real email thread, the real document, not your summary of what's in them. Claude Cowork works from the source; a description loses the details that decide the output.

03

Say what "done" looks like

A specific format (a table, a one-paragraph summary, a message), a specific length, a specific audience. "Done" left undefined gets you Claude's best guess at done, which may not match yours.

04

Ask for the first pass before you ask for the polished version

See the structure and the approach before refining tone and formatting. Correcting direction on a first pass is far cheaper than re-explaining after a polished version went the wrong way.

05

Turn what works into a repeatable prompt

Once a task is running well, save the exact instruction that produced it. Most of the value in Claude Cowork comes from turning one-off wins into a workflow you reuse every week without re-explaining it.

Want to see this method run against a real recurring task, start to finish? Read a full session walkthrough, or if you don't have a dedicated ops specialist, see what you can produce yourself with it.

See Claude Cowork coaching →
The Boffin Guarantee

Coaching designed
to end.

Reading the method is one thing; having someone check your first attempts against your actual recurring tasks is another. Three promises, in writing, if you bring it to a session:

01

First Session Promise

Leave your first session with a live workflow already running in Claude, or the session is free.

02

Independence Guarantee

You'll be working independently inside six sessions, or we'll keep going: up to two further sessions free.

03

24-Hour Match

Tell us what you do; we'll match you with the right specialist within 24 hours. Guaranteed.

Training a whole team? See Claude training for teams.
Questions

Things people
usually ask.

Get started

Bring your busywork.
We'll bring the specialist.

Bring a real recurring task to your first session and a specialist will run this method against it live. We'll match you within 24 hours, guaranteed.

Get matched free →
Free · 5 minutes · no card · matched within 24 hours