Strategy
Part of Creator discovery platforms strategy: a buyer decision first
Creator discovery platforms: a reversible ninety-day plan
A reversible ninety-day plan for creator discovery platforms: six phases, evidence checks, synthetic tests, approval gates and exit proof.
A reversible ninety-day plan for weighing creator discovery platforms and other routes, built on six phases, evidence checks, synthetic tests, approval gates and exit proof.
What to take away
- The investigation runs as six reversible 15-day phases, each with a stop condition.
- Every candidate attribute needs eight recorded entries, from source to deletion.
- Testing uses synthetic records in a non-production workspace, so no creator is contacted.
- A failed specialist gate stops a route; approval needs a readable export, an integrity check, a deletion instruction and a named fallback owner.
90-Day Investigation Timeline
- Days 1-15Define decision
- Days 16-30Map fields
- Days 31-45Collect route evidence
- Days 46-60Test without live people
- Days 61-75Examine campaign gates
- Days 76-90Decide and prove exit
Days 1 to 15: the decision card and the actor map
The decision owner writes a decision card covering the governance problem, creator eligibility, the intended output and the manual baseline. Name the advertiser user, the budget authority and the agency or talent intermediary. Add the supplier operator, the rights holder and the audience interest owner.
Stop if the brief depends on inferred age, residence or protected traits. Restart only with observable, permissioned eligibility evidence. The strategy framework note on bounded evaluation shows how the card expires.
Days 16 to 30: the eight-entry field dictionary
One row per candidate attribute, with the same eight entries every time.
Eight-entry field dictionary
| Entry | What the row records |
|---|---|
| Source | where it came from |
| Permission | basis it is held on |
| Definition | the agreed meaning |
| Status | claimed or verified |
| Timestamp | capture date |
| Purpose | why it is processed |
| Recipient | who receives it |
| Deletion | when it goes |
The ICO's guide to lawful basis says the basis should be determined and documented before processing begins. Treat research outreach, campaign negotiation and later promotion as separate purposes.
Example: a filled decision card
Fictional entry, shown for shape only.
Filled decision card
- Decision
- replace the manual creator register for one campaign
- Owner
- head of brand marketing, England
- Manual baseline
- in-house register, three named owners
- Stop condition
- brief needs inferred age or protected traits
The field dictionary must mirror the card, so a scope change forces a data-request change.
Days 31 to 45: equal-evidence requests to every route
Send the same written request to the manual register, to the incumbent managed service you already buy, and to a shortlist of creator discovery platforms — for example CreatorIQ, Traackr, Upfluence, Aspire, HypeAuditor, Modash, Klear or IZEA. Ask every route for the same security material, support terms and change notice, and keep the answer set identical so the evidence stays comparable.
Ask each route to evidence the same creator-specific capabilities: search coverage across the markets and languages you buy in, provenance for audience data, detection of fake followers and engagement fraud, campaign workflow from brief to payment, and integrations with your advertising, analytics and consent tooling. A route that cannot describe these in its own words has not answered the evidence request.
The NCSC Cloud Security Shared Responsibility Model shows which party controls each security task, and it certifies nobody. Verify the contracting entity at Companies House before shortlisting. Hold any route that cannot name its operator or its exit object.
Days 46 to 60: tests on synthetic records
Tests on synthetic records
- Fix the version and expected result before the run.
- Run the query set, saving the raw output.
- Repeat under a second permission set.
- Break it with duplicates, suppression and deletions.
- Compare the export with the on-screen view.
An accessibility specialist tests the real interface and the export, not a supplier statement. A failed critical control stops the route until remediation is evidenced and retested. The implementation note on synthetic records explains how to keep the test workspace away from any production tenant.
Days 61 to 75: the campaign gate register
Advertising, rights and safeguarding reviewers walk one hypothetical content path using approved test material. The ASA's influencer marketing advice resources cover recognisability and disclosure, and they are not platform approval. Check creator authority, incentive records and claim substantiation first.
Output is a gate register of pass, hold or reject, each with evidence. The CAP Code and the Consumer Protection from Unfair Trading Regulations 2008 govern how a paid post is identified, while UK GDPR and the Data Protection Act 2018 govern the records behind it.
One worked row shows the shape the register takes: reject — the disclosure label is missing from the test post; evidence: reviewer note against the approved test material; owner: brand marketing; retest once the creator contract carries the label.
Days 76 to 90: measures and exit proof
Operating measure from your own record: [numerator] of [denominator] eligible [event] in [period], with a source query and an owner.
A measure needs an event, an eligible population, a period and a source query. Never present it as reach or sales.
Before approval, produce a readable export, a published schema and an integrity check. Add a deletion instruction, a retained audit record and a named fallback owner. The commercial contracts note on data and exit belongs in the same approval file.
The Cabinet Office takeaway guide on contract management training accreditation advises building the exit plan early. Approve, narrow, return to manual work or stop. Set expiry dates for supplier, source, notice and contract changes. Confirm the plan with your own privacy and advertising advisers before you act on it.
Common questions
What does the ninety-day window commit us to?
A route decision for one English buying team, nothing more. Any phase can stop or close the investigation.
When should a route be stopped?
Stop where the brief leans on inferred age, residence or protected traits, or where source permission stays unresolved.
What has to exist before approval?
A readable export, a published schema and an integrity check. Then a deletion instruction, a retained audit record and a named fallback owner.
Does passing the gates make a platform compliant?
No. Gates test evidence at one point in time, while the cited ICO, ASA and NCSC material sets duties rather than approvals.
