# Creative brief: A scent, in your words

A completed example of the Rainbrand creative brief template, filled in from a saved run: the concept Codex made for Kaorium in October 2026, published at rainbrand.com/examples/kaorium/. Every entry comes from that run's prompt, its Rainbrand Brief, its outputs or its Reviews. Where the run recorded nothing, the field says so instead of guessing.

| | |
| --- | --- |
| Owner | Rainbrand, for its examples page. Codex wrote the brief and made the pieces |
| Approver | Not recorded. No human sign-off is in the saved run |
| Date and version | October 23, 2026, v1 (the date the Brief was requested) |
| Brand | Kaorium, added to Rainbrand from kaorium.com |

## 1. Background

_Why this project exists now._

Kaorium runs advisor-led fragrance consultations: people react to scents and word cues, and an advisor guides them to a fragrance. The project is a concept for putting a scent into words before or during that conversation. Why now: not recorded; this was a concept, not a commissioned campaign.

## 2. Objective

_One change you want, with a number and a date, and how you will measure it._

Unknown. The run set no target or metric. A real version of this brief would need one, for example how many consultations start with words chosen on the site.

## 3. Audience and markets

_Who, specifically, and where._

People looking for a fragrance who will meet an advisor in person. Markets: not stated. The brief forbade naming or inventing retail locations.

## 4. Insight

_Something true about the audience that the idea can build on._

Not written down in the run. The concept implies one: people find a scent hard to describe, and a few chosen words give the advisor somewhere to start. Treat this as an assumption to test, not a finding.

## 5. The one thing to say

_The single message, in one sentence._

Choose up to three words for the scent you want, and take them to an advisor.

## 6. Proof

_The claims the assets may make, each with its source._

None. The pieces make no claims about fragrances, results or Kaorium's technology, by design (see Don'ts).

## 7. Tone for this piece

_Only what is specific to this project._

Kaorium's voice, as the Brief described it: concise, human and sensory. For this concept, let the person's chosen words speak for themselves, with no interpretation added.

## 8. Deliverables

| Asset | Format and size | Channel or placement | Due |
| --- | --- | --- | --- |
| Website concept | One responsive screen, captured at 1440 px desktop and 390 px phone | Concept page | Not recorded |
| Conversation card | A5 portrait, print | In-store consultation | Not recorded |

## 9. Mandatories

_What every asset must include._

- The title "A scent, in your words".
- On the website: "Choose up to three words.", the action "See my words", the result label "Your words" and the line "Take these words to an in-store advisor."
- On the card: four writing areas labelled "Words (up to three)", "Scent / vial", "Memory" and "Advisor notes", left blank.
- On both: a disclosure that this is an illustrative conversation starter, not live Kaorium AI or a fragrance recommendation.
- Kaorium's SVG logo exactly as supplied, Flecha M for display headings and Akkurat Mono for everything else.
- The palette: warm neutral #E7E3D5 background, olive #53591A text, lime #DBFF00 primary button with a plum #64213D label.

## 10. Don'ts

- No fragrance results, recommendations or "signature scent".
- No retail locations, performance figures or product claims, and no unlaunched fragrance.
- Don't present the website or card as Kaorium's live service, and don't replace the advisor or the in-person consultation.
- Don't reuse the press image of the scent console as a layout: it carries another site's watermark.

## 11. AI use

_What AI may do, and what a person makes or checks._

Codex wrote this brief, requested the Rainbrand Brief and made both pieces. Rainbrand Reviews checked every capture. What a person checks before anything is used: not recorded, because this was a concept for an examples page.

## 12. Budget

Not recorded.

## 13. Timeline

| Milestone | Date |
| --- | --- |
| Brief agreed | Not recorded |
| Rainbrand Brief requested | October 23, 2026 |
| First concepts | October 23, 2026 (Review round 1) |
| Final assets | Not recorded (after Review round 2) |
| Live | Published as an example on rainbrand.com |

## 14. Review and approval

Two rounds of Rainbrand Review on five captures (four website states and the card), checking colour, typography, logo and copy. Round 1 found the phone button set in capitals instead of sentence case; Codex fixed it. In round 2 the card passed all four checks. On the four website captures the colour check came back uncertain: the plum label on the lime button was hard to measure, and a style check outside Review confirmed the value. Final approval: not recorded.

---

## Design brief additions

- Where it will be seen: desktop and phone screens; the card is printed and handled at a counter.
- Specifications: A5 portrait for the card. Print colour and production specifications (bleed, margins, colour mode) were not in Kaorium's sources, so the Brief said to keep the card restrained rather than claim a print system.
- Content supplied: all copy came from the brief and the Rainbrand Brief; images came from Kaorium's own library.
- Existing assets to reuse: the SVG logo, two butterfly images as quiet accents, the Flecha M and Akkurat Mono font files.
- References: a photo of the vial console as reference only; the watermarked press image not to be reused.
- Accessibility: not stated in the brief. The website was built with keyboard-operable word controls and a three-word limit.
- Handover: the website as one HTML file and the card as an image; print files not recorded.

---

_From rainbrand.com/blog/creative-brief-template/. The blank template is in the same folder._
