# Run sponsorship deals and campaigns

This guide covers how sponsors move from initial interest to a managed partnership.

## Deal lifecycle

A practical lifecycle:

1. Discovery and shortlist
2. Initial conversation
3. Scope and deliverable alignment
4. Agreement and payment structure
5. Delivery and reporting
6. Review and renewal decision

## Define deliverables clearly

Specify:

* Asset placements and channels
* Post frequency or event-day commitments
* Usage rights where relevant
* Reporting format and frequency

## Keep expectations realistic

Strong deals avoid vague language. Make every deliverable measurable and time-bound.

## Campaign management essentials

* Set milestone checkpoints
* Track completion against agreed scope
* Document changes to scope early
* Review outcomes at end of campaign period

## Troubleshooting

### Campaign is active but progress is unclear

* Set a weekly reporting check-in
* Use a single status summary with completed, in-progress, blocked

### Deliverables are not matching expectations

* Reconfirm original agreement in writing
* Align quickly on acceptable revisions and timeline

## FAQ

### Should we prefer recurring or one-off sponsorship?

Choose based on campaign objectives. Recurring support suits long-term brand-building; one-off support suits specific events.

### What reduces sponsor risk most?

Clear scope, clear reporting cadence, and realistic deliverables.

## Next steps

* [Discover and evaluate competitors](/for-sponsors/discover-and-evaluate.md)
* [Fees, processing, and payout timelines](/funding-and-payouts/fees-processing-payouts.md)
* [Legal in plain English](/legal/plain-english.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/for-sponsors/deals-and-campaigns.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.