All plays

Play 62 · Hospitality and local

ForRental revenue managersToThe host

Your rental is underpriced for concert weekend

A seven-step play for a short-term rental revenue manager. It starts from SeatGeek, stacks Vrbo, Agoda, StubHub and Resident Advisor on top, and ends in a message to the host that is useful before anyone replies.

Installs this workflow, five project tables and a draft campaign. Source access and any external outputs are checked before research.

Category
Hospitality and local
Sources
5
Steps
7

The workflow

  1. TriggerSeatGeekMajor events and their dates
  2. Evidence
  3. Artifact
    What you hand overA pricing comparison for the event dates: their price, comparable rentals, and hotel availability.
  4. Contact
    GliderFinds the host, with a verified work email and a phone
  5. Message
    Send itFrom your own mailboxes, evidence attached

Why it earns attention

Hosts set prices weeks ahead and miss the events that fill a town. The gap between their price and nearby rentals for one big weekend is money they can see in a single table.

The play in seven steps

  1. 01

    Find the big weekends

    SeatGeek
    What you pull
    Major concerts and games in the area over the next 90 days: venue, date and capacity. StubHub and Resident Advisor add demand signals and smaller events.
    Why it matters
    A stadium show fills every room in town. Hosts who priced weeks ago are underpriced for it.
    Example

    Stadium concert · June 14 · 60,000 capacity

  2. 02

    Compare their price with nearby rentals

    Vrbo
    What you pull
    Rentals within a mile of the venue: nightly price and availability for that weekend, and the host's own price.
    Why it matters
    The difference between their price and comparable listings is the money they are leaving behind.
    Example

    Host at $180 a night · comparable listings at $410 · most already booked

  3. 03

    Check the hotels

    Agoda
    What you pull
    Availability and prices at nearby hotels for the same dates.
    Why it matters
    If hotels are almost full, demand will spill over to rentals. It confirms the price can go up.
    Example

    Hotels within 2 miles 90% booked

  4. 04

    Build the comparison

    Your artifact
    What you build
    Their price, comparable listings, hotel availability and a recommended price for the weekend.
    Why it works
    The host can change the price in two minutes and see the result.
    Example

    Recommended $360 a night · about $540 more for the weekend

  5. 05

    Check before you send

    Compare like with like: size, bedrooms and distance. Check the listing is still available on those dates.

  6. 06

    Find the host in Glider

    Glider
    Search for
    HostProperty managerOwner
    Why them
    Individual hosts set their own prices. Hosts with several listings often use a manager.
    What you get
    A work email and a direct phone, with the email verified before it goes into a sequence.
  7. 07

    Send the evidence, then run the first test

    • Facts from the data (the number is the step)
    • What you built for them
    • One small ask
    Why it works
    It shows money they are about to leave on the table on a date they can see, and the fix takes two minutes.
    First test
    One major event, thirty listings priced well under comps.
    Success looks like
    Four hosts sign up out of thirty.

The sample message is hypothetical and its numbers are illustrative. Verify every claim, date and rule before sending.

Sources used

The five sources this play names. Each links to the other plays that use it.

All 63 GTM plays

Run this play with Glider.

Deploy the full workflow into a project. Conway checks your scope and source access, builds the evidence, and prepares outreach for review.