Eric: Bhutan Project
How to design, build, and maintain a high-end luxury travel website using Claude and Cowork — from a blank slate to a live site in under an hour.
I'm launching a high-end tour company for bespoke private journeys to Bhutan, targeting high-net-worth individuals in Texas. I need a website. How would I actually use Claude and Cowork to design, build, and maintain it?
Don't jump straight into having Claude build artifacts or code. If you skip the strategy step — defining the customer journey, creating a style guide, building a persona — Claude will produce generic output that misses your positioning entirely. "Answer in chat first" is how you keep Claude in thinking mode before it starts building.
Before any build work, map the full business model and website interaction in plain conversation with Claude.
Describe the business model
Curated Bhutan experiences with rare access, helicopter transfers to remote regions, tiered pricing up to ~$25K per person for 10 days.
Define the customer journey on the site
Arouse curiosity with a hook, showcase experience tiers as a menu, capture interest through a concierge-style form.
Have Claude map the full website structure
Hero, desire section, tier cards, trust section, form, footer — as a chat response, not as code.
Validate before moving on
This conversation becomes a reusable context document. Don't skip the sign-off step.
Use "answer in chat first" to keep Claude in strategy mode. This prevents it from prematurely building artifacts or code before the thinking is done. The chat output becomes your project brief.
Build a complete brand style guide using the Bhutan flag as the color palette foundation, then refine it for luxury positioning.
Seed the palette from a reference
Tell Claude to use the Bhutan flag colors (saffron, crimson, forest green) adapted for a high-end feel.
Claude generates the full guide
Full palette with hex codes, typography specs, photography direction, voice and tone rules, and layout principles.
Visualize, then export
Have Claude visualize the palette inline for quick review, then produce a downloadable Word document as the formal brief.
Save it to the project folder
This becomes a permanent context file that Claude references on every future task in this project.
A style guide isn't just for designers — it's a data asset for AI. Once saved to your Cowork project folder, Claude will apply it consistently across every output: website code, marketing copy, social posts, email templates. Create it once, use it forever.
Instead of asking Claude for a generic persona, teach it Harvard Business School frameworks and apply them to the Bhutan buyer.
Ask Claude to teach three Harvard persona frameworks
Jobs to Be Done (Christensen), Empathy Map (d.school/HBS), and Purchase Decision Journey (HBS Marketing).
Apply all three to the target customer
50–65 year old Texas HNWI, $10M+ net worth, "done everything" mindset.
Key finding: the website isn't the acquisition channel
The Texas network is. The website is the credibility checkpoint someone pulls up on their phone after hearing about you at dinner.
Save it to the project folder
The persona output becomes another context document that informs every future task.
Educating yourself on business frameworks while prompting produces dramatically better output. Don't just say "create a persona." Say "teach me Jobs to Be Done, then apply it to my customer." You learn the framework and get a superior deliverable in the same conversation.
With strategy, style guide, and persona complete, move into Cowork to build the actual site.
Create the folder structure
Bhutan → context (for style guide, persona, and brief documents).
Set up a Cowork project linked to that folder
Claude now has persistent access to all context files across every session.
Build the skeletal HTML structure
Have Cowork build a full skeleton using the style guide as the reference. Full structure in about 15 minutes.
Iterate from there
Refine copy, swap placeholder images, adjust tier details, test the form endpoint.
Cowork's power is persistent context. When the style guide, persona, and brief all live in the project folder, every task Claude performs is automatically informed by your brand, your customer, and your strategy. No re-explaining.
Beyond building the site, Claude can manage the project timeline and automate follow-ups.
Create an interactive Gantt chart
Have Claude build a Gantt for tracking project milestones — design, content, development, launch.
Schedule automated follow-ups
Discuss scheduling automated follow-up emails from milestone dates so nothing falls through the cracks.
Turn Claude into a PM layer
This shifts Claude from a one-off tool into an ongoing project management system for the entire build.
Model selection: Use Sonnet for most work (faster, cheaper). Switch to Opus for complex or accuracy-critical tasks.
Images: Connect to Google's Imagen model for AI-generated images rather than relying on Claude natively. Stock photos pulled from the web likely have copyright issues.
Slides and Canva: Claude isn't good enough yet at applying style guides to visual design tools. You still need a human designer for that last 10%.