Zovda
A rate card is treated as a reference document. It is closer to a price quote for a perishable good: the number was true for a window, and the window closes fast.
Budgets get built on cards that are two quarters old, and the gap between the plan and the quotes shows up as a negotiation problem instead of a data problem.
What a rate card should contain
- Price per deliverable, named precisely: one video, one image set, one appearance
- The platform and format the price refers to
- The performance window the price was based on
- Whether usage rights and duration are included
- The date the price was captured
The last field is the one that makes the card usable a year later, even if only as history.
Performance is a rolling window
A creator's last three posts are a better predictor of the next one than the average of last year. Prices follow the rolling window; cards that use lifetime averages lag by months.
Report both: the rolling figure the price reflects, and the longer trend, clearly labeled.
Deliverable differences dominate
Most of the variance between two quotes is not the creator's rate. It is what is included: exclusivity, revision rounds, paid amplification, the number of cut-downs.
Normalize deliverables before comparing prices, or the comparison measures the package, not the person.
Refresh and keep history
Update on a schedule, keep every previous version, and record why a number moved. A card with history answers the question "is this quote normal" in seconds.
Zovda maintains these collections through Datuva, where each price keeps its capture date. The creator rate cards collection shows the fields a card is built from.
Tell us what you are buying. We reply within one business day.