Claude Project: Your Persistent Revenue Strategy Assistant

What You'll Build

A persistent Claude Project that functions as a hotel-specific Revenue Strategy Assistant — one that already knows your property, your comp set, your pricing philosophy, and your recurring challenges before you type a single word. Every report draft, rate justification, and competitive analysis you run through it will reflect your specific market and property context automatically, without you re-explaining the basics each session.

Why This Matters for Revenue Managers

The biggest friction in using AI daily isn't knowing what to ask — it's spending 5-10 minutes re-establishing context every single time. A Claude Project eliminates that entirely.

What You'll Need

• Claude Pro subscription ({{tool:Claude.plan}} — {{tool:Claude.price}}/month)
• 30-45 minutes to write your property context document
• Your current comp set and STR report handy for reference
• A clear sense of your pricing philosophy (rate floor, MPI targets, discount rules)

Architecture Overview

Claude Projects stores a persistent "system prompt" — a context document you write once that loads automatically into every conversation. Your Revenue Strategy Assistant project will contain: property overview, comp set details, market characteristics, pricing rules, and a standing instruction set for how you want the AI to respond to different request types.

Build Guide

Phase 1: Write Your Property Context Document

This is the most important step. Open a text document and write out the following sections. Be specific — vague context produces vague outputs.

Property Overview (10-15 sentences)

Cover: hotel name and brand (or independent), number of rooms, room type breakdown (standard king, double queen, suites), property location and neighborhood, star rating or segment (select-service, full-service, boutique), primary guest mix (corporate transient, leisure, group, extended stay), key amenities (F&B, meeting space, parking, pool), physical condition or recent renovations, and any brand standards or restrictions that affect pricing.

Example:

Comp Set (one line per property)

List 4-6 competitors with: name, brand, room count, segment, distance from your property, and one-line positioning note.

Example:

Market Characteristics (5-8 sentences)

Cover: demand seasonality patterns, top demand drivers (corporate corridors, events, universities, hospitals), known citywide events calendar, new supply entering market, compression periods, and any local market quirks that affect pricing.

Pricing Philosophy (bullet list)

Be explicit about your rules:

• Rate floor (weekday / weekend / minimum)
• MPI target range
• Policy on following comp set rate drops
• Minimum length of stay triggers
• How you handle distressed inventory (value adds vs. discounting)
• Blackout dates or events where you never discount

Standing Instructions

Tell the AI how you want it to behave:

Phase 2: Create the Claude Project

1. Open Claude.ai and navigate to Projects (left sidebar or home screen)
2. Click New Project
3. Name it: "Revenue Strategy Assistant — [Your Hotel Name]"
4. Click into Project Instructions (the gear icon or "Add instructions")
5. Paste your full property context document into the instructions field
6. Save

Phase 3: Test and Calibrate

Run these test prompts in a new conversation inside the project to verify context is working:

• "Summarize our competitive positioning in one paragraph" — should produce a property-specific answer without you providing any data
• "Our Friday pickup is 12 rooms behind pace with 10 days out. What should I check first?" — should reference your comp set and pricing philosophy
• "Draft a 3-sentence GM email explaining why we're holding rate at $229 this weekend despite 72% occupancy" — should reflect your market and pricing rules

If outputs are generic, go back and add more specifics to the relevant context section.

Real-World Walkthrough: Monday Morning Rate Review

Without the project: You open Claude, paste 4 paragraphs of hotel context, describe the comp set, explain your pricing philosophy, then ask your question. 8-12 minutes before you get useful output.

With the project: You open the project and type:

Claude responds with a property-specific rate recommendation and a draft email ready to edit — in under 60 seconds. Total time: 3 minutes including editing.

Over a 5-day week, this saves roughly 40-60 minutes of context-setting time on AI interactions alone.

Customization Options

• Multi-property: Create one project per property if you manage multiple hotels; each has its own context
• Seasonal refresh: Update the instructions quarterly when demand patterns shift or new supply enters the market
• Comp set changes: Update when a competitor opens, closes, or repositions; outdated comp set context produces wrong recommendations
• Add uploaded documents: Claude Projects supports file uploads — load your current STR summary, budget, or annual event calendar as reference files

Maintenance

• Quarterly: Review and update market characteristics, especially new supply and demand driver changes
• Annually: Refresh pricing philosophy after budget season; update room mix if renovations occurred
• As needed: Update comp set when properties change significantly

What This Won't Do

• Access real-time data from your PMS, STR, or rate shopping tools — you still need to paste in current numbers
• Make rate decisions autonomously — it advises; you decide
• Replace your RMS for automated pricing recommendations; it works alongside tools like IDeaS or Duetto on the human communication layer