All the tools
Download

Here are the three columns your creator spreadsheet is missing. If you fix nothing else after reading this, fix these.

  • Last verified date. Not last contacted. The date you last checked that the numbers in the row were still true. Without it, every figure in the sheet has the same apparent authority, whether it was checked yesterday or in March.
  • Why they are in the list. One line. Six months later nobody remembers, and the name gets researched from scratch by someone who does not know it was already researched and rejected once.
  • Category conflicts. Which competitors they have worked with, and when. This is the field that stops an awkward conversation before it starts, usually about four minutes before a call.

Everything else in this article is about how a roster goes wrong. Those three columns are how you notice.

How a roster goes stale, week by week

Every creator spreadsheet dies the same way, and it is not the spreadsheet's fault.

Week one, someone builds it beautifully. By week three a couple of creators have changed what they post about, which nobody notices because nobody re-reads a sheet they built. By week six the follower counts are wrong, two creators have stopped posting entirely, one has quietly done a deal with a competitor, and the status column has become a field nobody trusts enough to act on.

The problem is not the format. A spreadsheet is a perfectly good container. The problem is that a spreadsheet cannot re-check itself, and the person who could is busy doing the work the spreadsheet was supposed to support.

The prompt that makes a roster worth having

This is the monthly re-check. It is the only prompt here that genuinely changes the economics of keeping a list, because it returns exceptions rather than a report.

ROLE
Creator CRM operator with Favikon MCP access.

VARIABLES
{{LIST}}        = Q4 France shortlist
{{ER_DROP_MAX}} = 20             # percent
{{SILENT_DAYS}} = 45
{{CATEGORY}}    = project management software
{{LAST_CHECK}}  = 2026-08-01

TASK
Re-check every creator in {{LIST}} against their state at
{{LAST_CHECK}}, and return ONLY the exceptions:
1. engagement rate down more than {{ER_DROP_MAX}}%
2. no post in the last {{SILENT_DAYS}} days
3. changed niche
4. worked with a brand in {{CATEGORY}} since

OUTPUT
One table — handle | flag | what changed | value then |
value now | recommended action
Nothing else. Do not list the creators who are unchanged.

CONSTRAINTS
- One row per creator even if several flags trip. Put the most
 serious flag in the flag column.
- This is a hygiene pass, not a re-scoring. Do not re-rank.

QUALITY CHECK
A healthy roster returns 10 to 20% of its names. More than half
means {{LAST_CHECK}} is wrong, or the list was never verified
in the first place.

The last line of the OUTPUT block is the one people delete and should not. A report on everyone is a document. A list of exceptions is a Monday morning.

Organise by next action, not by platform

Most creator databases are sorted by platform or follower count. Neither tells you what to do next, which is the only question a roster exists to answer.

Split {{LIST}} into four groups: ready to contact, already worked with us, needs re-vetting, do not pursue. For each creator give me one line on why they are in that group.

Four groups, each with an obvious next step. The "do not pursue" group is the one that saves the most time over a year, because it stops the same name being rediscovered and re-researched every quarter by someone new.

At what size a spreadsheet stops working

Roughly speaking: when the number of creators multiplied by the number of fields you care about exceeds what one person will actually re-check in an afternoon. For most teams that lands somewhere between 40 and 60 creators.

Below that, a spreadsheet plus a calendar reminder is genuinely fine, and anyone telling you otherwise is selling something. Above it, the sheet does not break loudly. It just becomes quietly wrong, and keeps being used, which is worse than breaking.

Prepare the outreach in the same breath

For everyone in "ready to contact", draft a first message referencing something specific and recent from their content. Vary the reference per creator, do not reuse a template.

Where to run it

Lists and creator organisation live in the Favikon app, and Favy can build and re-check them by prompt on every plan. For the same operations from Claude or ChatGPT, connect the Favikon MCP.