# Run memberships and supporter perks

Memberships can provide more predictable recurring support when your profile has regular content momentum.

## When to use memberships

Memberships work best when you can:

* Post consistently
* Offer clear supporter value
* Maintain communication with members

## Membership tier structure

Start simple with 1 to 3 tiers:

* Supporter tier: community support and recognition
* Insider tier: extra updates and behind-the-scenes content
* Premium tier: highest access and priority perks

## Perk design principles

Good perks are:

* Realistic to deliver
* Valuable to members
* Clear in frequency and scope

Examples:

* Members-only posts
* Monthly race recap
* Priority Q\&A responses
* Digital supporter assets

## Keep retention in mind

To reduce churn:

* Deliver perks on time
* Communicate clearly during race-heavy periods
* Thank members publicly (with permission)

## Troubleshooting

### Members join but quickly cancel

* Improve onboarding for new members
* Clarify what they receive and when
* Increase consistency of members-only updates

### I cannot keep up with perks

* Simplify tier promises
* Reduce custom one-off rewards
* Focus on repeatable monthly value

## FAQ

### Should I launch memberships immediately?

Launch once you can post consistently and fulfil perks reliably.

### How often should I post members-only content?

A reliable monthly minimum is a good baseline. More frequent updates can improve retention.

## Next steps

* [Post updates and content](/reference-guides/updates-and-content.md)
* [Understand analytics and transactions](/reference-guides/analytics-and-transactions.md)


---

# Agent Instructions: 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:

```
GET https://docs.sponsordriven.com/reference-guides/memberships-and-perks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.