Manage concert sponsorship leads in My Matches

A promising show can move from discovery to sponsor outreach quickly. Concert Matches gives promoters, agencies, and brand teams one view of saved concerts and submitted sponsorship requests while keeping those states distinct.

A concert opportunity is not one thing. It may be a show your team saved for research, a sponsorship request already submitted, or both. Treating those states as interchangeable creates bad handoffs: colleagues assume outreach happened when it did not, or read a request as proof that commercial inventory exists.

Cultiq’s Concert Matches view brings saved concerts and sponsorship requests into one list. It shows the artist and tour context, available market, city, and date details, any stored match score, and a requested label with status when a request exists. The view helps the team see where an opportunity sits. It does not confirm rights or commercial feasibility.

TakeawayUse Concert Matches as a pipeline index: one concert, one visible record, and a clear distinction between saved interest and submitted request.

What the Concert Matches view solves

Concert research often fragments across tabs, decks, and inbox threads. A promoter may save a London show while an agency colleague submits a sponsorship request for the same opportunity.

Concert Matches combines saved and requested records for the same concert rather than showing duplicate rows. A single item can therefore indicate that the concert is saved, has a request, or carries both states. The requested badge also exposes the current request status stored in the workflow.

That consolidation supports coordination, but it is not a substitute for a campaign brief, rights map, or negotiation record.

Start in Concert Discovery

Open Concert Discovery and review opportunities against a defined sponsor brief. Start with the campaign objective, target audience, priority buyer market, timing, activation capacity, and category restrictions.

For a US campaign, New York or Los Angeles may deserve review when the brand can activate there. London may support a UK objective; Seoul, Tokyo, Paris, Dubai, or Singapore may fit other plans. The city and date must serve the brand’s operating reality.

When a concert deserves more research, save it. Saving preserves the opportunity in Concert Matches; it does not submit a request or imply access to sponsorship inventory.

Read each row as a workflow state

Use the visible fields as navigation and context, then attach your team’s decision note outside the row.

Click View to return to the concert detail with the My Matches context preserved. Recheck material schedule facts against official artist, promoter, venue, or ticketing sources before they enter an external proposal.

Add a simple operating note

Concert Matches shows product state; your team should record decision state. For every active opportunity, maintain five short fields:

1. Why now: the campaign reason this concert is under review.
2. Market case: why the city matters to the brand and audience.
3. Known evidence: dated, sourced facts that support the idea.
4. Must confirm: rights, inventory, category conflicts, assets, price, approvals, and participation questions.
5. Next action: one owner, one deadline, and one expected output.

The request status tells you what the product record says; the operating note tells colleagues what must happen next.

Decide when to request sponsorship

Submit a request only when the team can explain the brand, objective, audience, priority market, proposed sponsor role, timing, and material unknowns.

Before advancing, ask:

• Does the concert answer a real market and audience need?
• Is the proposed activation specific enough to discuss?
• Have schedule facts been checked recently?
• Are projections labeled as hypotheses rather than facts?
• Does the request list what only authorized parties can confirm?

For the diligence behind this step, use Review an announced tour before sponsor outreach and Map concert sponsorship rights and assets before outreach.

Keep removal separate from request status

The Concert Matches view lets you remove an item from the saved list when it is no longer useful there. Before removing it, preserve the reason in your decision record. A concise note such as “US launch moved outside the announced date window” is more useful than silently deleting the opportunity.

Removing saved interest is not the same as withdrawing, rejecting, or completing a sponsorship request. If a request record exists, treat its status as a separate workflow and follow the appropriate authorized process for any change.

Turn the view into a weekly sponsor review

Once a week, open Concert Matches and review every item in three passes: saved-only opportunities that need qualification, requested opportunities that need a next action, and items that no longer answer the brief. End with an owner and date for each active concert.

Open My Matches to review Concert Matches, explore concert opportunities, or see how Cultiq supports promoters. For broader entertainment-partnership strategy and facilitated deal support, visit WENOTIFT Insights.

FAQ

Does saving a concert submit a sponsorship request?

No. A saved concert is retained for review. Submitting a sponsorship request is a separate action.

Can one concert appear twice if it is saved and requested?

Concert Matches merges saved and requested records for the same concert into one item and shows the requested state on that item.

Does a request status confirm sponsorship inventory or a deal?

No. Rights, inventory, category availability, pricing, terms, approvals, and artist participation require confirmation from authorized parties.

What happens if I remove a saved concert after requesting sponsorship?

Saved state and request state are separate. A concert with a request can remain visible through its request record, so preserve your decision note and manage the request through the appropriate workflow.