> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.pricelabs.co/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.pricelabs.co/_mcp/server.

# 03 · Weekend premium check

Pricing

Any portfolio

\~3 min

Read-only

**Who it's for — and what to expect:** you suspect your weekend pricing leaves money on the table — or takes too much — and want the answer in numbers, not instinct. Expect a small table comparing your weekend vs weekday prices to your market's (both listed and actually booked), plus the market's weekend demand, and a direct numeric answer. Be ready for the honest outcome: sometimes the data says your premium is fine and the real issue is elsewhere.

> **Before you start**
>
> Same connection; new chat; read access is enough. Works even if your listing's
> price sync is off.

## The prompt

Copy-paste as one message:

**`Weekened premium check`**

```text Weekened premium check wordWrap
Compare my weekend vs weekday pricing to my market's for listing [ID] on [your PMS] — weekends meaning Friday and Saturday nights, over the next 90 days.

Use these PriceLabs tools: get_listings, then get_neighbourhood_data (detail mode, with prices, occupancy and future prices — my own prices are in its future_prices).

Output: a small table — my average weekend vs weekday price, the market's (listed and booked), and the market's weekend vs weekday occupancy — then answer with numbers: am I charging enough weekend premium, or is my real issue elsewhere?

Flag any data you couldn't retrieve — and if my own booking data is too thin to split weekends from weekdays, say so rather than guessing.
```

> **Pro tip**
>
> The answer is often about the level of your prices, not the shape of your
> week — that finding is worth more than the question you asked.

**Goes well with:** [Market position](/mcp/cookbook/market-position) · Pacing dashboard (coming)