Claude Cowork for Architects: Do Twice the Work in Half the Time

Let me ask you something. How much of your week did you actually spend designing last week?

Not "working on projects." Not "in the studio." Designing. The thing you trained six years for. The thing you tell people you do when they ask at a dinner party.

If you're like most architects I know, the answer hurts a little. Maybe a third of your time. Maybe less. The rest goes somewhere else — somewhere that has nothing to do with buildings and everything to do with files, folders, formats, and emails.

I've worked in architecture studios. I know what your Tuesday afternoon looks like. And I want to talk to you about a tool I've been using for a few weeks that is, slowly, giving me back the hours I never wanted to lose in the first place. It's called Claude Cowork, and if you run a studio — or work in one — I think you should know about it.

Be honest with yourself for a second

How many hours this month have you spent on:

• Renaming files. Endlessly. project_v2_FINAL_revised.dwg. Don't lie, you've made one of those today.

• Building the submission folder for a competition, panel by panel, according to a brief that goes on for pages.

• Converting between formats. PDF to JPG. DWG to PDF. DOCX to PDF. Again.

• Writing the same client email for the fifth time this quarter, because every project closeout sounds basically the same.

• Hunting for that document a colleague sent you two months ago that you know exists but cannot find.

• Reviewing competition briefs to decide which ones are worth entering.

• Cleaning up an archive folder that hasn't made sense since 2019.

None of this is design. None of it is what you trained for. And — this is the part that stings — none of it is properly delegated, because at most studios there's nobody to delegate it to without spending more time explaining than you'd save.

You already know this. The question is whether you're going to keep accepting it.

What Claude Cowork actually is

Claude Cowork is a desktop application from Anthropic that lets the Claude AI operate directly on your files and folders — not just answer questions about them.

You point it at a folder. You describe what you want. It does the task: reads your files, renames them, sorts them, converts formats, drafts documents, builds reports. It shows you the plan before acting and asks for confirmation on anything destructive. You stay in control.

You need a paid Claude subscription. Pro is $20/month. Max is $100–$200/month for heavier use. Runs on macOS and Windows. Sign up at claude.ai, download the desktop app, switch to Cowork mode in the sidebar.

That's the introduction. Here's the part that matters: what it can take off your desk this week.

Five tasks where Claude Cowork can save you real hours as an architect

1. Competition submission packaging

You know this one. The brief has six pages of submission requirements: file naming convention, folder structure, image resolutions, PDF specifications, maximum sizes. You've spent your Sunday night doing it more times than you want to admit.

Here's what you do instead. Drop your export folder and the brief PDF into a folder Cowork can access. Tell it: "Read the submission requirements in the brief and reorganise this folder accordingly. Rename the panels following the convention specified, flag any image that doesn't meet resolution, and create the submission folder structure they require."

Cowork reads the brief. It reads your file names. It does the work. It comes back with a list of what it found and anything that needs your attention.

You go from three hours of doing to twenty minutes of checking. The first time it works, you won't quite believe it. Verify everything by hand the first round. After that, you'll trust it.

2. Client reports after delivery

When you close a project, you should send a short delivery report — what was produced, formats, dates, revisions. It's small but it's the difference between feeling like a professional studio and feeling like someone who emailed some files. Most architects skip it because by the time the project closes, you're already mentally on the next one.

Keep a folder per project with the deliverables, the original brief, and any revision notes. When the project closes, tell Cowork: "Generate a client delivery report based on the contents of this folder. Use the structure of [previous report I like]." It produces a draft. You edit a paragraph. You send.

Twenty minutes instead of an hour and a half. And the reports come out better, because Cowork doesn't get tired toward the end. It doesn't skip the small details you used to skip.

3. The disaster archive

You know exactly which folder I'm talking about. Old Projects. Archive 2018-2022. Six layers deep, full of files named export_revised_v3_jp.tif with no logic anyone can reconstruct.

Give Cowork access to it on a quiet afternoon. Ask it to apply consistent naming, surface duplicates, and create a master index document. Make a coffee. Come back.

It won't be perfect — expect maybe 5% of files that it can't figure out from the filename alone, which you'll correct manually. But an afternoon of work fixes what would have taken you a week by hand. And let's be honest: you weren't going to do it by hand. It was going to stay broken until you retired.

4. Reviewing competition briefs to decide what to enter

You get sent a lot of briefs. Reading each one to assess timeline feasibility, deliverables, and whether the project is worth your team's time takes hours. So you skim. So you miss things. So you end up entering competitions you shouldn't and skipping ones you should have pursued.

Drop a stack of briefs into a folder. Ask Cowork to summarise the key information from each one in a comparison table: deadline, deliverables required, brief clarity, jury composition if mentioned, anything unusual.

The hours saved are real. But the better thing is the quality of the decision. You're comparing all the briefs on the same criteria, on a clear table, instead of reading the third one with the first one already half-forgotten.

5. Email drafts based on context

Project kick-off, revision delivery, project closeout. The same emails, slightly customised, every time. Keep your templates in a folder. Tell Cowork the context — "Draft a kick-off email for the new project at /folder, addressed to [client], based on the template in /templates" — and it produces a draft that's 80% there.

Small thing. Maybe ten minutes per email. But you send a lot of emails.

Where it's not magic

Tell you it's perfect and you'll stop trusting me. So:

It doesn't touch CAD, Rhino, or rendering software. It works on the layer around design — documents, images, PDFs, folders. Your design tools are still your tools. This is fine. You don't want AI inside your models either.

Complex Excel files confuse it. Multi-sheet workbooks with formulas can lose structure. Simple tabular data is fine.

Large file batches are slow. A folder with hundreds of files takes time. Worth it, but plan for it.

It's a research preview. Anthropic is open about this — things break sometimes. You're an early user.

Don't give it access to folders with sensitive client data without thinking it through. Read the security documentation. For most studio admin work the access controls are reasonable. Use your judgement on contracts and legal documents.

How to start this week

If you finish this article and do nothing, the article was useless. So:

1. Sign up for Claude Pro at $20/month. Don't jump to Max yet.

2. Download the Claude Desktop app. Cowork only runs there, not in the browser.

3. Switch to Cowork mode in the sidebar.

4. Pick one folder for your first task. Not your whole drive. Not anything sensitive. An old project archive works perfectly.

5. Start with one clearly scoped task: "Rename all PDFs in this folder following the pattern [project name]_[document type]_[date]". Watch it work. Check the result.

6. Build from there. One new task per week.

The mistake to avoid is giving it too much on the first try. Treat it like a new junior at the studio: explicit instructions, clear scope, check the output the first few times.

What AI doesn't do

I want to be honest about something I genuinely believe.

These tools are extraordinary at the mechanical layer of our profession. They're useless at the judgment layer.

When you're sitting in front of a site, deciding whether the new building should defer to the old one or stand against it — no tool helps. When you're choosing which atmosphere a render needs to convey to make a jury feel something, or to make a buyer fall for a development before it's built — no tool helps. That's you. That's your years of looking, thinking, getting it wrong, and getting it right.

What Cowork does is give you back the hours you weren't using for any of that. The hours that were going to file names and folder structures. So when a client calls you at six on a Friday with a real question, you have the energy to listen properly.

The takeaway

If you're spending more than three hours a week on file management, document admin, and routine reports — and you are, you just haven't measured it — Claude Cowork pays for itself in the first month. The Pro plan costs less than one billable hour.

Start with one folder. One task. Build from there.

The point isn't to become a power user. It's to take back the parts of your week that were never supposed to be design work in the first place.

One more thing. When the admin is finally off your desk and you're back to designing — at some point you'll need renders. Whether it's a competition, a marketing campaign for a residential development, an interior project for a private client, or a feasibility study for an investor: that's what we do at Render4tomorrow. Architects across Switzerland, Germany, France and Spain have trusted us with their projects since 2013. Get in touch and tell me about yours.

— Pedro J. López, co-founder at Render4Tomorrow