Decide whose job it is first

This week a small team I work with agreed that everyone on it gets their own Claude account, and that the shared login their marketing ran on comes off within a week or two.

A shared login hides who does what. Whatever it produced carried no name, and nobody could say whose instructions it was following or who was meant to check the result.

A personal account starts from a different question, whose job is this. Each person sets theirs up around their own week, with their own files and their own instructions, and each person checks what it produces.

The day we spent together went at each person's own pace. One person finished the full set-up and was working on a daily optimisation task of their own by the afternoon, another got about two thirds of the way through, and two had not started when the day ended.

We agreed one exception before we finished. A daily email that scores a person's ad campaigns goes straight to that person, with no draft stage and no approval first. It is internal and it has one owner, and every other message stays as a draft until someone reads it.

Whose job it is comes before which tool, and an owner can settle that this afternoon with a pen. Take last week and list every job, who did it and how long it took. A job with a name beside it can be counted, checked and handed on, and a job that belongs to a shared login has none of those.

A designer's hour and an owner's hour are priced differently. Price each job at the rate of the person who did it, and the total tells you what the week cost before any tool is chosen.

The Capacity Indicator does that count with you. You list last week's jobs, it shows which of them Claude could take off you, and it prices the hours at the rate of whoever does the jobs, with the research behind each range shown on its line.

It is free, and you can start it at capacity.yourspinstate.com