> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/new-to-podplay/pricing-models/spot+-model.md).

# Spot+ Model

### How Spot+ Works

Spot+ is a dynamic version of the per-spot pricing model. The court rate stayed fixed (for example, $40), and the cost per participant moved up or down based on how many participants were on the court at the same time.

A Customer booking a Reservation selected the number of participants in the booking flow. After the Reservation was finalized, the Reservation Holder invited the other participants in the App — see [How can a Customer invite their friends to their Reservation?](https://help.podplay.app/en/articles/831489) for the invite mechanics.

At booking, the Reservation Holder paid only for their own spot. If they didn't invite their friends — or invitees declined — the Club did not receive the full court revenue. Once invitees accepted, they paid for their respective spots.

{% hint style="warning" %}
Spot+ pricing is no longer available. Use [Court+ pricing (Bill Splitting)](https://help.podplay.app/en/articles/2385857) instead. The information that follows is retained for historical context.
{% endhint %}

#### Pricing examples

At a $40/hour court rate, the per-spot cost worked out to $40 for 1 participant, $20 for 2 participants, and $10 for 4 participants. For 3 participants, the total had to be adjusted slightly because $40 doesn't divide evenly into three — a $14 per-spot price made the court total $42, the closest clean split.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/owners-playbook/new-to-podplay/pricing-models/spot+-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.