In short
Client revisions go well when you translate each piece of feedback into one testable change, keep every round traceable, and speak up when a request will damage the fragrance or fall outside the agreed scope. Clients describe experiences, and they cannot usually tell you what to change. Finding out what they mean is part of the job, and it uses all of your earlier work on evaluation and versioning.
What you will learn
- Translate feedback into testable formula changes
- Keep each round traceable and within scope
- Complete a brief response within a stated cost
Before this lesson: Professional Presentations
Translating feedback
| They say | It may mean | A test to try |
|---|---|---|
| Too old | Powder, aldehydes, heavy rose, or a reminder of a person | Ask which moment; reduce one suspect at a time |
| Too sweet | Vanillin, ethyl maltol, lactones or fruit | Remove one sweet line, keeping body |
| Too strong | Diffusion, a harsh woody amber or a high dose | Lower the suspect; distance test |
| Doesn't last | Weak base, or adaptation by the wearer | Ask someone else to assess at set times |
| Cheap | A harsh note, a thin heart, too much of one thing | Compare against the reference they respect |
| Not quite there | Anything | Ask what is closest so far, and what's missing |
Ask three questions: at which moment, compared with what, and what would make it right? Record the answer in their words before you interpret it.
Running a round
- Summarize. Confirm in writing what you understood.
- Plan. One hypothesis per mod, such as "reduce sweetness by removing ethyl maltol."
- Make and test it. Compare against the last version, blind, before you send it.
- Check your constraints. Cost, restrictions and allergens may have moved.
- Send with a note. What changed, in client language, and what to look for.
- Log it. Use your mod log.
When to push back
You need not simply comply. Speak up where:
- A request would break a restriction, a claim or a cost constraint. Show the numbers.
- A change will damage what the client chose earlier. Offer a side-by-side version to demonstrate it.
- Feedback is contradictory. Go back to the decision maker.
- Requests exceed the rounds agreed. Refer to scope, and agree what comes next.
- The brief has really changed. Say so, and reset the plan.
Offer it as advice, and let the client decide on matters of taste. On safety and legal requirements, however, do not bend. Ask for guidance from the responsible people.
Revision fatigue
After several rounds, everyone's nose and judgment get tired. Signs include rejecting versions they liked earlier, or going round in circles. Try a blind comparison of round 1 against the latest. Sometimes the earlier version wins. Take a break, or suggest bringing in a fresh assessor. Your version history makes this possible.
Level 11 project: a response to a mock brief
Bring the level together in one project, as if for a paying client.
- Get a brief written by another person, or use the sample from reading a brief, and add a stated cost target per kilogram.
- Write your interpretation, questions and a one-page scope.
- Build two directions, and cost both.
- Present them to someone playing the client, on strips.
- Complete at least two revision rounds, keeping a mod log.
- Finish with a final cost, a restriction self-check marked for confirmation, and a one-page handover summary.
Assess yourself. The project is complete if the final formula meets the stated cost or you explain the gap, each round traces to a specific piece of feedback, the record lets a stranger remake any mod, and your summary says what remains unverified. Ask your "client" for a written comment. You should not imply that the formula has been stability tested or safety assessed unless it has.
Practical exercise: Level 11 project: a brief response
Complete the Level 11 project above. Allow for at least two weeks, since feedback and aging take time.
You have done this well if you could hand your file to another perfumer, and they could tell what the client asked for, what you tried and why you chose what you did.
Common mistakes
- Making several changes per mod. You will not know what they responded to.
- Treating every comment as an instruction. Some need a question first.
- Losing the version a client liked. Keep every retained sample.
Knowledge check
Written and reviewed by the RUŌOD Lab team. This is general education, not legal, regulatory, medical or safety advice. Example dilutions and exercises are for learning, are not validated products, and have not been safety-assessed. Completing a lesson confers no qualification. How we check these lessons.