Two tools, two jobs. This guide covers both: the Concordia team Claude for everyday work, and Claude Code for building trips. Written for Zene.
We use Claude in two places. Knowing which is which saves you a lot of confusion.
| Team Claude (the app / website) |
Thinking, researching, writing. Vendor emails, member messages, sales replies, ad copy, finding restaurants, planning. Your everyday tool. Lives in your browser or the Claude app. |
| Claude Code (on the Mac) |
Building and publishing. Reads and writes our real files, runs the villa scrapers, builds and publishes trip landing pages, updates budgets. The heavy machinery. |
Simple rule: writing or researching → Team Claude. Building or publishing → Claude Code.
This is the shared Concordia account. Everyone on the team has their own project inside it, so your chats stay yours and don't get muddled with anyone else's.
Open Claude, look at the left sidebar, click Projects, and open the one with your name on it. Always work inside your project, it already knows the Concordia voice and rules.
At the top of a new chat, paste a role setter so Claude knows what hat to wear. There's a full list in Chat Role Setters.md in the context pack. For example:
Then just talk to it. It stays in that role for the whole chat. There are role setters for Sales, Members, Trips, Marketing, Vendors and Ops.
For one-off jobs, grab a ready-made prompt from Chat Startup Prompts.md and fill in the blanks. For example:
It cannot touch our files, run the scrapers, or publish a website. For those, you need Claude Code, that's Part Two.
This is the powerful one. It builds entire trips: the folders, the villa shortlist, the budget, the member docs, and the live trip page. It works on our real files.
Cal has set up all the connections, the scrapers, the photo tools, the Google Drive access. You only ever sign into one thing: Google Drive on your Mac, so our files sync to you. If Claude Code says it can't find a file or a key, tell Cal. It's a sync issue, not something you did wrong.
Open Claude Code and paste this first, so it loads who we are:
After a planning call with Cal, Claude Code can build an entire trip in about an hour.
Decide destination, dates, headcount, budget, vibe. Fill the Trip Kickoff Brief template as you talk.
Drop it in the trip's Drive folder. This one document drives everything that follows.
Paste the Trip Builder prompt (from the pack) with your brief inside it, then let it work.
It hands back a trip folder, a live landing page link, a villa shortlist, a draft budget and draft vendor emails. Go through it together.
Send the vendor emails, chase deposits, lock the bookings, plug real numbers into the budget.
It searches Airbnb, VRBO and Booking.com and drops them into a Notion gallery with photos, prices and refund terms.
We don't make Canva brochures anymore, the landing page is the look book, and it's easier to share as a link.
You have a lot of room to run. Check with Cal before:
"When you're 90% sure, act. When you're not, ask. Never guess on money or on people."
Claude Code shows you what it's about to do before it does it. If it looks wrong, tell it to stop or undo. Nothing reaches a member or vendor unless you send it. The technical-looking bits are safe to let it handle, that's the whole point.
Talk to either Claude like you'd brief a very fast, very capable assistant. You don't need the technical words. Describe what you want in plain English and it figures out the rest.