> 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+-advantages-and-disadvantages.md).

# Spot+ Advantages & Disadvantages

### Overview

Participants paid per spot per hour, with the spot rate equal to the court rate divided by the number of participants. Members got a discount on their spot rather than on the court. The Reservation Holder picked a time slot and a participant count, then invited the other participants. The Reservation Holder could elect to cover all, some, or none of the invitee spots.

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

#### Customer advantages

* Fairness — everyone paid their own way.
* Medium friction — the Reservation Holder didn't need to collect money from invitees outside the App.
* Options — the Reservation Holder could cover invitee spots or not.

#### Customer disadvantages

* Foresight — the Reservation Holder needed to know who they were playing with at the time of booking.
* Process errors — the Reservation Holder had to select the correct participant count at booking.
* Increased price — if invitees declined, the Reservation Holder was on the hook for their spots.
* Poor experience — Reservation Holders were often surprised that invitees didn't join.
* Stick philosophy — the model penalized the Reservation Holder with a higher final cost when invitees didn't accept.
* Extra charge — invitees in a Reservation could end up paying more than the regular court rate if the participant count was wrong.
* Credits — the Reservation Holder could not cover invitee spots using [Credits](https://help.podplay.app/en/articles/836545).
* Coaching Lessons — the Reservation Holder could not split the cost of a [Coaching Lesson](https://help.podplay.app/en/articles/833537) with invitees.

#### Club advantages

* Resolved the Non-member free-rider problem.
* Headline pricing per Reservation Holder was lower, even at the same hourly court rate.

#### Club disadvantages

* Operationally intensive with more room for error — the Front Desk had to ensure invitees accepted the invite, or the Club lost spot revenue.
* Staff became enforcers, chasing invitees to accept invitations.
* Staff had to update Reservations from the Dashboard for changing participant counts.
* Staff had to charge for differing participant counts or refund no-shows.
* The model introduced a "Stick" in the Customer experience.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.