---
title: "Sponsorship Deliverables and Make-Goods With AI Agents | Kylon"
description: "A sponsorship team audits deliverables against proof in Box and Mailchimp, settles make-goods and credits in Attio, and approves every change in a shared Kylon room."
url: "https://kylon.io/use-cases/sponsorship-deliverables"
language: "en"
---
[HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Sponsorship Deliverables: Make-Goods and Credits Backed by Proof of Performance
Use Case8 min read
# Sponsorship Deliverables: Make-Goods and Credits Backed by Proof of Performance
Every sponsor deliverable is checked against its proof in Box and its Mailchimp send, missed ones get a make-good or a credit in Attio, and sponsor replies and rate changes are absorbed without rewriting the audit. The sponsorship lead approves each change.
[Get started](https://app.kylon.io/sign-up)
Kylon TeamProduct
November 6, 2026
## Proof of performance lives in one place and the tracker in another
A sponsorship season is a long list of promises: board rotations at each event, a feature in the newsletter, a read on the podcast, a hospitality package for the sponsor's guests. Each one is delivered by a different team and proved by a different artifact, a photo, an aircheck, a send report. When something is missed or late, the sponsor is owed a make-good placement or a credit, and the policy says which.
The deliverables tracker is a sheet in Google Drive kept by a coordinator, the proof is filed in Box, the newsletter sends live in Mailchimp, and the sponsor deals and their credits sit in Attio. Sponsors reply with confirmations and objections by email. The tracker is usually close, which is what makes its errors costly: a line marked delivered with no proof behind it becomes a credit nobody issued.
## Who works in the room
People
- Sponsorship operations lead
Approves every verification status, make-good, credit and bonus placement, and signs off the close-out
- Partnership managers
Own each sponsor relationship and send every note to the sponsor
- Sponsorship coordinator
Keeps the deliverables tracker and files proof in Box as teams send it
- Finance
Confirms sponsor payments and applies credits to invoices
Agents
- NovaDeliverables auditor
Checks every tracker line against its proof in Box and, for newsletter placements, the Mailchimp send report, and proposes a verification status
BoxMailchimpGoogle Drive
- MycoMake-goods and credits
Applies the make-good policy to missed or late deliverables, proposes make-goods, credits and bonus placements, and writes Attio once they are approved
AttioGoogle Drive
- FinSponsor correspondence
Drafts notes and replies to sponsors for partnership managers to send, and puts delivery questions to the event and newsletter teams
[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack)
Nova leads the audit and is the room's default agent. For a busy event day it splits the proof files across parallel helpers and gets one verified list back. Myco owns dispositions, credits and bonus placements, so a question about any of those reaches it without a mention, and it writes to Attio through a lasting grant the sponsorship lead approved for the room. When Myco has an approved outcome, it opens a thread for Fin with the sponsor, the deliverable and the offer, and Fin drafts the note for the partnership manager.
## From audit to close-out notes
The make-good policy, the credit rates and the bonus inventory for each event are in Google Drive and summarized in the room guidelines, along with one standing rule: an audit's verification status records what the proof showed at the time.
```mermaid
flowchart TD
audit["Nova checks every tracker line
against its proof in Box"]
ok1["Sponsorship lead approves
each verification status"]
disp["Myco proposes make-goods, credits and
bonus placements under the policy"]
ok2["Sponsorship lead approves
before Attio is written"]
paid["Finance confirms
a payment cleared"]
recheck["Myco re-checks every
deliverable for that sponsor"]
draft["Fin drafts the reply"]
send["Partnership manager sends it"]
rate([The late rate changes])
credits["Myco recomputes only the
credits on late deliverables"]
ok4["Sponsorship lead
approves the new amounts"]
news["Nova compares Mailchimp send
reports with each package"]
decide["Sponsorship lead
decides any shortfall"]
note["Myco writes a close-out note
per sponsor to Attio"]
sign["Sponsorship lead signs off"]
audit --> ok1 --> disp --> ok2
ok2 --> paid & rate
paid --> recheck --> draft --> send
rate --> credits --> ok4 --> news --> decide
send & decide --> note --> sign
class audit,disp,recheck,draft,credits,news,note agent
class ok1,ok2,paid,send,ok4,decide,sign person
class rate event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42
```
| Stage | What happens | Who acts | Who decides |
| --- | --- | --- | --- |
| Tracker audit | Every tracker line is checked against its proof in Box and, for newsletter deliverables, the send report in Mailchimp | Nova | The sponsorship lead approves each verification status |
| Dispositions and credits | Missed or short deliverables get a make-good or a credit under the policy, recorded on the sponsor's deal in Attio | Myco | The sponsorship lead approves before Attio is written |
| Bonus placements | Make-goods are placed into the next event's bonus inventory in policy order, and any that do not fit fall back to credit | Myco | The sponsorship lead approves the allocation |
| Sponsor replies | Confirmations and objections are recorded, and a cleared payment re-checks every deliverable for that sponsor under the full policy | Myco, then Fin for the replies | Finance confirms the payment and a partnership manager sends each reply |
| Late-rate change | Credits on late deliverables are recomputed at the new rate, and dispositions stay as they are | Myco, checked by Nova | The sponsorship lead approves the new amounts |
| Newsletter results | Mailchimp send reports for the season's sponsored issues are compared with what each package promised | Nova | The sponsorship lead decides any shortfall |
| Close-out | A close-out note per sponsor is written to Attio from the final records | Myco | The sponsorship lead signs off |
Stages of a sponsorship deliverables review. Sponsors, deliverables and amounts in this example are illustrative.
## When a sponsor writes back
Sponsor replies change the record in specific ways, and only those. When finance confirms that a sponsor's overdue payment has cleared, every deliverable for that sponsor is re-checked under the full policy, because a make-good that was held may now be owed. When a sponsor confirms after the fact that a hospitality package was delivered, the confirmation is recorded on the deal, but the verification status the audit set stays as it was, since the audit found no proof at the time.
A late-rate escalation is narrower still. It changes the credit amount on each late deliverable, and Myco recomputes only that figure. The disposition, the make-good and the bonus placement do not move. Each change is posted in the thread with the old and new value, so the sponsorship lead can approve the set in one pass.
## What the checks catch
- A tracker line marked delivered with no photo, aircheck or send report in Box behind it
- A newsletter feature that went out in Mailchimp without the sponsor's block
- A verification status overwritten after a sponsor's later confirmation, which belongs alongside it instead
- A cleared payment that re-checks one of a sponsor's deliverables and misses the other
- A late-rate change that alters dispositions instead of only the credit amounts
## What stays with people
- Approving every verification status, disposition, credit and bonus placement before Attio is written
- Sending every note to a sponsor, which Fin prepares as a draft in Gmail
- Confirming payments and deciding objections
- Signing off the close-out notes
## Integrations in this workflow
Kylon is not a sponsorship management system, and it is not built to replace one. It sits across the CRM, file store and email tools the team already works in, and gives the handoffs between them one place to happen.
- Attio
- Box
- [Gmail](https://kylon.io/integrations/gmail)
- Google Drive
- Mailchimp
- [Slack](https://kylon.io/integrations/slack)
- **Attio** holds each sponsor's deal with its deliverables, credits, bonus placements and close-out notes
- **Box** keeps the proof of performance for every deliverable
- **Mailchimp** shows the send report for each sponsored newsletter issue
- **Google Drive** keeps the deliverables tracker, the make-good policy and the credit rates
- **Gmail** carries sponsor confirmations and objections, and each reply is a draft a partnership manager sends
- **Slack** is where the event and newsletter teams post delivery news on the day
## Where to start
One event and its sponsors is enough to begin. Connect Attio and the Box folder where proof is filed. The room guidelines should open with one rule: a deliverable counts as delivered only when its proof is in Box, and the sponsorship lead approves every credit before it is written to Attio.
> “If the proof is not in the folder, the deliverable is not done, however sure the tracker looks.”
## Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set-up prompt
Set up our sponsorship deliverables desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Attio, Box, Gmail, Google Drive, Mailchimp and Slack. Tell me which ones still need connecting.
2. Ask me who works this desk: the sponsorship operations lead, the partnership managers, the sponsorship coordinator and finance. Help me invite them to this Room.
3. Build a Sponsor Deliverables App with Deliverable, Sponsor, Outcome and Status columns, one record per deliverable. Pull the open lines from the tracker in Google Drive.
4. Check every tracker line against its proof file in Box and, for newsletter deliverables, the Mailchimp send report. Propose a verification status for each line and show me every one that has no proof behind it.
5. Apply our make-good policy from Google Drive to any missed or late deliverable and propose a make-good, credit or bonus placement. Draft each sponsor note as a Gmail draft. The sponsorship lead approves every verification status, credit and placement before Attio is written, and a partnership manager sends every reply.
6. Write the audit order, our credit rules, the bonus placement priority and who approves what into this Room's guideline so every deliverable follows the same path.
7. After one clean event season, offer to turn the tracker audit into an Automation.
Before you start, ask me for our rules one at a time.
[Get started](https://app.kylon.io/sign-up)
Your first company harness. Where humans and agents run your business together.
[Get started](https://app.kylon.io/sign-up)
## More Use Cases
[View all](https://kylon.io/use-cases)
[
### Ad Creative Approvals: A Launch Board That Matches What Is Actually Live
The agency's launch sheet is audited against live Meta Ads campaigns and Instagram posts, every creative gets a status and a launch window on the Miro board, and holds, budget cuts and late approvals are absorbed mid-wave. The desk lead approves every board change.
Media, publishing & agenciesApprovals & reviewsMarketing operations
](https://kylon.io/use-cases/ad-creative-approvals)[
### Ad Delivery Make-Goods: Every Shortfall Settled as a Bonus Placement or a Credit
Insertion orders are reconciled against delivered impressions and contract terms in one Kylon room. Agents work Attio, the Notion delivery report and the Outlook contract threads, re-run bonus allocations when numbers change, and the ad operations lead approves every outcome.
Media, publishing & agenciesMarketing operations
](https://kylon.io/use-cases/ad-delivery-makegoods)