A landscape architecture studio turned a full drawing set into a draft spec in about six minutes

One Claude setup for the whole studio

We rolled out Claude Team with studio-wide instructions that set baseline rules for accuracy and brevity. We turned off location metadata, turned on chat sharing across the team, and organized work into projects. The team uses the desktop app for local files, with Gmail and Calendar connected and direct email sending switched off.

Proposals start from the studio's own templates

A proposal skill works from the studio's cover letter and proposal templates. It asks for the details that change from job to job, like phase durations and fee structure.

Specs drafted straight from the drawings

Team members drop in drawings and project details, pick a template, and get editable drafts in Word and Google Docs by email. A 50-sheet PDF set takes 5 to 20 minutes.

Claude can build the studio's automations

Through an MCP connection, Claude can create workflows in the studio's own n8n instance. The studio owns the whole setup.

An AI policy based on how the team works

A short survey of how the team already uses AI is shaping an acceptable use policy that protects the studio's intellectual property.

What changed

• Specs are drafted from the drawings instead of matched to templates by hand.
• Proposals start from a guided skill instead of a blank page.
• The whole team works from one shared, governed Claude setup.

Next on the list

The team is teaching Claude the studio's rendering style and testing automated checks that catch simple drafting errors before a person reviews the set.