How to Brief a Creator for a True Pre-Launch Product With No Existing Reviews or Social Proof

What's genuinely different about a pre-launch brief?

A pre-launch brief differs from an ordinary brief on three points no other Academy article covers together: the creator has nothing to compare the product to — no prior reviews, no personal experience, no competitor comparison to lean on. The product is often secret until a fixed launch moment, which typically requires an NDA before the briefing can even happen. And because there's no track record to build a claim on, the creator's wording is more tightly constrained than usual — see the documentation section below.

Ordinary brief vs. pre-launch brief

The NDA protects the brand's secret — it doesn't excuse ad disclosure

The two duties solve two different problems, and one cannot substitute for the other. An NDA is a private agreement between brand and creator about when product information may be shared publicly — it protects the brand's commercial interest in a controlled launch. The ad disclosure duty under Markedsføringsloven § 6(4) is something else: it protects the consumer, not the brand, and applies the moment a creator has received a benefit in exchange for talking about the product — whether or not the product is publicly known yet.

In our assessment, it's therefore logically impossible for a private NDA to excuse a duty that exists to protect a third party (the consumer) who isn't a party to the NDA at all. An NDA can lawfully require that the creator not reveal the product name, price or launch date before the embargo lifts — but it cannot lawfully require that the creator skip marking the post as advertising once it goes live. The two can coexist without conflict: a post can say "ad for [brand] — more details at launch" without revealing anything the NDA protects.

What can a creator honestly say with nothing to compare it to?

With no review history, the Academy's own article on the documentation requirement under Markedsføringsloven § 13 applies at full strength, just earlier in the process: a concrete, measurable effect or comparison claim must be documentable before it's used — and a creator meeting the product for the first time has, by definition, no basis to document an effect over time or a comparison to alternatives.

The practical consequence for the brief: ask the creator for a first impression, not a review. The word "review" itself signals a judgement built on experience that doesn't exist yet. State explicitly in the brief that the content should be framed as the experience of encountering the product — unboxing, design, first use — not a conclusion about how it performs over time.

Expectation-setting for a product that might still change

A pre-launch product is often not in its final form when it's briefed: packaging, price or even features can still change before launch. The ordinary expectation-setting before a collaboration applies in full here — deliverables, timing, usage rights, approval and payment — but the pre-launch scenario needs one extra item: what happens if the product changes after the content is made. Agree in advance whether the creator needs to approve an updated version of the content if a visible detail (packaging, a price mentioned in the post) changes before launch — it's cheaper to agree this now than to discover it the day before launch.

Six elements a pre-launch brief has to add

Build on the UGC brief template or the campaign brief template with these six additions:

1. NDA and embargo date as named fields

Not a verbal agreement — write the precise embargo date and time into the brief, separate from the NDA document itself.

2. An explicit ban on undocumented effect and comparison claims

Write it in as a "must avoid" field, not just a general caution — see the table above.

3. "First impression" as the wording, not "review"

Put the word directly into the brief's angle field, so the creator carries the frame themselves.

4. A contingency clause if the launch date slips

See the full worked example below — without this clause, a delayed launch becomes a renegotiation instead of a formality.

5. Ad disclosure on the go-live post itself

Separate from the NDA, see the disclosure rules — the labelling duty applies regardless of the embargo.

6. An approval workflow matched to the embargo

Content needs to be ready and approved before the embargo lifts, but only posted at the actual launch — not before.

Decision framework: standalone NDA, or is a contract line enough?

IF the creator needs to see or hear about the product before agreeing to the collaboration → use a standalone NDA, signed before the briefing.

IF the product is only shared after the main contract is already signed → an embedded confidentiality line in the main contract is often sufficient.

See the full decision framework for the NDA form itself in NDA and confidentiality clauses in influencer contracts.

Worked example: what a missing contingency clause costs (hypothetical)

The figures below are a made-up example for illustration — not a real Make Influence customer case.

A brand briefs 4 creators on an unreleased product, 14 days before the planned launch date, at a fee of DKK 4,000 each — DKK 16,000 total. All sign an NDA with an embargo running to the launch date. Five days before launch, it slips by 5 days due to a supplier delay.

With a contingency clause agreed up front ("the embargo extends automatically with the launch date, at no additional fee"), the delay costs DKK 0 extra — the content sits ready and simply posts 5 days later.

Without the clause, each creator can reasonably ask for compensation for holding an already-finished post back longer than agreed. An illustrative (not documented) estimate of DKK 500 per day per creator gives 500 × 5 × 4 = DKK 10,000 in extra negotiated fees — 62.5% on top of the original budget (10,000 / 16,000), for exactly the same delay.

Common mistakes

• Assuming the NDA also excuses ad disclosure. See the section above — the two duties are independent.
• Using the word "review" in the brief for a product no one has tested yet. Use "first impression" instead.
• Letting the creator phrase a comparison with no data to base it on. See the documentation table above.
• No contingency plan if the launch slips. See the worked example — it's cheaper to agree this now than to renegotiate under time pressure.
• Only a verbal agreement on the embargo date. Write it in as a named field in the brief, not a side note in an email thread.

Make Influence's perspective

Our core model is built around a public, trackable link or discount code from day one — so a full pre-launch brief with an NDA and an embargo isn't something we use often in our own collaborations. When it does come up, our experience is that the one detail most often missing is a fixed, written embargo date tied directly to the tracking link that needs to go live the same day — without that link, a brand risks either an early leak or a gap where the product has launched but no tracking is set up yet.

FAQ

Can a creator call it a "review" if they've only had the product for a week before launch?

We recommend avoiding the word. A week of use doesn't support a documented effect claim — use "first impression" instead, and keep the content to what the creator can actually stand behind.

Can the NDA also cover the fact that the collaboration exists at all?

Only if it's worded that way — see the same question covered in the NDA article. Most NDAs protect specific product information, not the general fact that a collaboration is happening.

Does the post need to be marked as advertising even if the creator still can't reveal the product name?

Yes. Ad disclosure is about stating the commercial interest, not revealing product details — the two can coexist without conflict, see the section above.

What if the launch gets delayed after the content is already made?

That's exactly what the contingency clause in point 4 above should cover — agree in advance what a delay costs, instead of negotiating it under time pressure.

Should we always use a standalone NDA for a pre-launch briefing?

Generally yes, if the creator needs to see the product before agreeing to the collaboration — see the decision framework above and the full walkthrough in NDA and confidentiality clauses.

Can the creator say anything positive about the product with no documentation?

Yes — a clear, subjective opinion ("I'm excited", "the packaging looks great") needs no documentation. What needs documentation is a concrete effect or comparison claim, see the table above.

Does a briefing like this apply to a limited-edition drop as well?

The no-social-proof problem is the same, but a drop adds a second constraint on top: the stock itself, not just the embargo. See planning a scarcity-driven creator drop for allocation and sold-out handling once the embargo lifts.