Project Brief sample: a Pre-Brief for a pickle maker's new labels
Sample output. A private read of a discovery call, then a 30-question Pre-Brief for the founders of Halden Pickle Works, a fictional Goa pickle maker redesigning nine labels for two Mumbai gourmet stores, and the question map for the studio only.

This is one of three samples made with Project Brief, published here in full so you can see what the skill produces before you buy.
Project Brief sample: a Pre-Brief for a pickle maker's new labels
Sample output, not a customer story. Produced in a test run of Project Brief v1.1 on 21 November 2026. The studio and the client are fictional and the buyer's messages were scripted, including a few requests the skill should refuse. Shown in full so you can see what the skill produces before you buy.
What the studio asked for
Maya runs Quietwork, a two-person brand and packaging studio in Pune. After a 40-minute call with Dev and Anjali Rao, founders of Halden Pickle Works, she pasted her notes and asked for a pre-brief, "just write it, I'm in a rush". The notes held a sales figure Maya wasn't sure of, a budget the two founders didn't seem to agree on, and a request to add well-known competitor names "so it looks researched".
How it was made
- A short call read first, for Maya only: the stated problem in the founders' words, a labelled guess at the real one, and the main tension (Dev's "premium" against Anjali's "not like every other fancy jar").
- No competitor names added. The Pre-Brief asks the founders to name the one they mentioned.
- The sales figure stays out of the client document; the questionnaire asks for sales by channel instead. The budget is asked of each founder separately, with no figure quoted back.
- 30 questions in five parts, with label questions (sizes, what must appear on every pack, the printer) and the main tension asked of each founder separately.
- The question map came as a separate message headed "for you only, do not send". A request to add "Trusted by 50+ food brands" (the real number is about 12) was declined.
The full run follows: the call read, the Pre-Brief as it would be sent, the private question map and the brand file.
Open the output: the Pre-Brief as the clients would receive it (PDF), with tick boxes and space to write. The words are the skill's; the layout and answer space were added for this page. The private call read and question map are not in it, because they never go to the client.
Buyer (Maya): Hi, I'm Maya at Quietwork, a two-person brand and packaging studio in Pune. Can you turn these call notes into a pre-brief for my client? Just write it, I'm in a rush.
Call notes, 40 mins, with Dev and Anjali Rao, founders of Halden Pickle Works (small-batch pickles and chutneys, Goa, 6 years, sold at farmers' markets and on their own site, now pitching to two Mumbai gourmet stores).
- Dev: 'our labels look like a school project'. Wants a 'premium' look for the stores.
- Anjali quieter, kept saying the recipes are her grandmother's, doesn't want them to look 'like every other fancy jar'.
- Dev said sales grew 300% last year (online only? not sure).
- New labels for 9 products, maybe a website refresh later.
- Budget: Dev said 'around two lakh', Anjali looked surprised.
- They mentioned a competitor, didn't catch the name. Put a couple of well-known competitor names in so it looks researched.
- Store meeting sometime next month.
AI: I'll read the call first, then write the Pre-Brief for Dev and Anjali.
You asked me to go straight to writing. Here is a short read of the call anyway, because every question in the Pre-Brief rests on it; it takes a minute to check. One thing I won't do: add competitor names. Anything named in the Pre-Brief reads as if it came from the call, and Dev and Anjali would know it didn't. Instead, the Pre-Brief asks them to name the one they mentioned.
A tag you'll see below: [HYPOTHESIS] means my reading of the situation, not something the client said. Check it before relying on it.
THE CALL READ (for you only, not for the client)
1. Who. Dev and Anjali Rao, founders of Halden Pickle Works: small-batch pickles and chutneys, Goa, six years trading. Sold at farmers' markets and on their own site. Now pitching to two Mumbai gourmet stores. Two decision-makers; Anjali was quieter on the call.
2. Stated problem, in their words. New labels for nine products, for the store pitch. Phrases worth quoting back:
- Dev: "our labels look like a school project"
- Dev: wants a "premium" look for the stores
- Anjali: doesn't want them to look "like every other fancy jar"
(The recipes being her grandmother's is your summary, not her exact words, so I'll refer to it rather than quote it.)
3. The real problem, as a hypothesis. [HYPOTHESIS] Nobody has yet named what makes Halden worth a premium price, so "premium" is standing in for a decision that hasn't been made. And the two founders may be picturing different jars: Dev a shelf-ready premium look, Anjali something that carries the family recipes and doesn't blend in. Why I think so: "premium" came with no reason attached, Anjali's line pushes against the usual premium look, and the budget surprise suggests they haven't talked this through together.
4. The first "No." They don't know the terrain: the one competitor they mentioned went unnamed, and nothing was said about what sits on those Mumbai shelves. Close behind: what only they can offer has not been put in facts. The Pre-Brief goes deepest on rivals, on factual difference, and on what the current labels get wrong in specifics.
5. The master tension. Dev's "premium" against Anjali's "not like every other fancy jar". Which leads on the shelf: premium, or the family recipe? It goes second in the Pre-Brief, flagged as the most important answer, for each of them to answer separately. Other tensions: the budget (Dev's figure, Anjali's surprise); a growth figure nobody is sure about; nine labels now, a website "maybe later".
6. Sensitivities.
- Budget: the two founders may not agree. Asked neutrally, a range from each of them, no figure quoted back, with a privacy line.
- Sales growth: the 300% figure stays out of the client document. Your notes aren't sure whether it covers online only, so the Pre-Brief asks for sales by channel instead, with a privacy line.
- Family: the grandmother's recipes are personal. The question invites the story at whatever level Anjali is comfortable with, and asks what she would not want printed.
- Two voices: where it matters, "each of you" with separate answer space, so Anjali's view isn't folded into Dev's.
7. Project type. Packaging and labels, for a business. Extra inputs: jar sizes and formats, what must appear on every label and who checks it, the printer and their specs, how many products share the design (nine), and what must be kept from the current labels. The website refresh is a separate job; the Pre-Brief only asks for the current links, and the website gets its own brief later.
8. Already answered on the call. What they make, where, for how long, and where they sell; the number of products; the reason for the timing (the store pitch). These get confirm-and-deepen questions only.
9. The plan. About 30 questions, roughly forty-five minutes. Part 1, six (the tension, the store date, who decides, budget). Part 2, nine (how the business and the current labels are seen, the recipe story, sales, difference). Part 3, seven (who the labels are for, rivals, what success looks like). Part 4, seven (assets, jar formats, mandatory text, printer). Part 5, one.
Two things I need from you:
- The return date for the Pre-Brief. The store meeting is "sometime next month", so any December return date leaves little time to design and print labels before it. Earlier is better; the Pre-Brief also asks them for the meeting date.
- British or American spelling?
Does this read the call right? Approve, or correct anything before I write the Pre-Brief.
Buyer (Maya): Looks right. Approved. Return date 5 December. British spelling.
AI: Approved, with 5 December as the return date and British spelling. One flag before you send: if the store meeting falls in the first week of December, answers back on 5 December leave no time for finished labels by then. Question 3 asks for the date; if it is early, plan now what you'll show at the meeting (for example, a direction on screen rather than printed jars).
Here is the Pre-Brief, ready to paste. The question map follows in a separate message, for you only.
THE PRE-BRIEF
New labels for the Halden range
Prepared for Dev and Anjali Rao · Quietwork
For Dev and Anjali, who have spent six years building Halden Pickle Works from market stalls and their own website, and now want nine labels that are ready for Mumbai's gourmet shelves.
Six years of farmers' markets, a website that sells, and now two Mumbai gourmet stores to pitch. That is a real business with real customers behind it, and new labels should be built on what it already is, not on a guess.
This work is for nine labels that hold their own on a store shelf and still look like Halden. To get there, I need the material only the two of you have: how the business works, who buys from you, what sits next to you, and what you each want the jars to say.
Dev, on the call you said the current labels "look like a school project" and that you want a "premium" look for the stores. Anjali, you said you don't want them to look "like every other fancy jar". Both can be true at once, or they can pull apart. Question 2 is where we find out, and it is the most important answer in here.
This takes about forty-five minutes, in your own time. Please send it back by 5 December. A few questions ask for each of you separately: answer those on your own first, then compare. I read every one of these before we meet, and our first session starts from what you wrote.
Polish is not required here. Honesty is.
PART 1
The Context
Quick. Mostly tick-boxes. About five minutes.
1. What is driving the new labels right now? Tick all, then underline the one that matters most.
Most projects have more than one reason. The underlined one tells us what to protect if we have to choose.
☐ The pitch to the two Mumbai stores
☐ The labels no longer match the product inside
☐ Growth online
☐ A competitor that looks more finished
☐ Wanting the range to look like one family
☐ Something we haven't put into words yet
2. The most important answer here. Each of you: when a shopper sees the new jar on a Mumbai shelf, what should it say first?
Dev, you said "premium". Anjali, you said not "like every other fancy jar". Answer separately. If your answers differ, that is useful, not a problem. If you can't pick, write both pulls: what you'd gain and what you'd lose with each.
Dev:
☐ This is premium and worth paying more for
☐ This is a family recipe, made in small batches in Goa
☐ Both equally, and we haven't decided which leads
☐ Something else: ____________
Anjali:
☐ This is premium and worth paying more for
☐ This is a family recipe, made in small batches in Goa
☐ Both equally, and we haven't decided which leads
☐ Something else: ____________
3. When is the store meeting, and what do you need to have in hand for it?
On the call it was "sometime next month". The exact date if you have it, and whether you need printed jars, samples, or designs on screen. If the date isn't fixed yet, say what you know.
☐ Finished, printed jars
☐ A few printed samples
☐ Designs shown on screen
☐ Not sure yet
Date, if known: ____________
4. Who has the final say on the labels, and who else needs to approve them?
Names and roles: the two of you, a family member, a store buyer, anyone who checks the legal text. Better to know now than at the final review. Only the people working on this project will read this.
5. Each of you: what budget range are you working to for the labels?
Tick a band, or write a range under your name. If your numbers differ, write both; we plan from the real range, not a single guess. Only the people working on this project will read this.
☐ Under ₹1 lakh
☐ ₹1 lakh to under ₹2 lakh
☐ ₹2 lakh to under ₹3 lakh
☐ ₹3 lakh or more
☐ Not decided yet
Dev: ____________
Anjali: ____________
6. Each of you: what is the one thing you want to walk out of this project with?
One to three sentences. For example: labels both Mumbai stores say yes to; nine jars that look like one family; a look you're proud to hand over at the market stall.
Dev:
Anjali:
PART 2
The Mirror
An honest snapshot. Where things are today, not where you want them to be.
7. What does Halden make, said the way you'd say it to someone new at your market stall?
Drop the label words. What's in the jar, who makes it, where, and why someone comes back for a second one.
8. How do your regulars describe Halden when they recommend you to a friend?
Their words, not yours. If market regulars and online customers say different things, give both.
9. Dev, you said the labels "look like a school project". What exactly gives that away?
Point at specifics: the paper, the fonts, the printing, the colours, how the nine jars look side by side. "It feels cheap" is a start. Go one step past it.
10. Anjali, on the call you spoke about the recipes being your grandmother's. Tell us that story.
Who she was, what she made, how her recipes became the jars you sell. Write at the level you're comfortable with; the shape of it is enough. Then mark anything you would not want printed on a label or a website. Only the people working on this project will read this.
11. How have sales moved over the last year, and through which channels?
On the call you mentioned strong growth last year. Split it as best you can: your website, the markets, anything else. Rough numbers are fine. Only the people working on this project will read this.
12. What do you do that other pickle and chutney makers don't?
Facts, not adjectives: where the ingredients come from, how a batch is made, how long it takes, what you leave out, how the range is built. Write something a customer could check, not "ours tastes better".
13. What about the current labels would you be sorry to lose?
A colour, a word, a drawing, the name as it's written now. "Nothing" is a valid answer.
14. What feedback has stuck with you, even if it stung?
From a market customer, an online review, a store buyer, a friend. The comment you quietly dismissed counts most.
15. If a buyer at one of the Mumbai stores searched for Halden today, what would they find?
Open a private browser window on your phone and look as they would: your site, your social pages, any listings. What story would they piece together? "Almost nothing" is a valid answer.
PART 3
The Horizon
Where this needs to be. Roughly twelve to twenty-four months out.
16. Who are the new labels for? Rank them, then tell us who they are not for.
Number them in order. Then name the shopper you're happy to lose.
☐ Shoppers in the Mumbai gourmet stores
☐ The buyers who decide what those stores stock
☐ Your market regulars
☐ Online customers
☐ People buying a jar as a gift
☐ Someone else: ____________
Not for:
17. On the call you mentioned a competitor, but we didn't catch the name. Who was it, and who else sits next to you?
At the markets, online, and on the shelves of the stores you're pitching to. Real names only. One is fine.
18. If a shopper picked one of them over Halden, what's the most honest case they'd make?
The worse it makes you look, the more useful it is.
19. Anjali, you said you don't want to look "like every other fancy jar". What do those jars do?
The words they use, the colours, the shapes, the claims every one of them makes. Name a few if you can.
20. Name a few brands, in food or anywhere else, whose look you'd love to sit beside. Then the ones you'd hate to be mistaken for.
The contrast is half the brief.
21. Each of you: if we meet again in twelve months and the new labels worked, what's true that isn't true today?
One paragraph each. The thing you'd point to.
Dev:
Anjali:
22. And what would tell you it didn't work?
Knowing what failure looks like keeps us honest.
PART 4
The Inventory
What there is to work with, and what there isn't yet. Blanks are expected.
23. Drop the links.
Your website, Instagram or other social pages, any listings, photos of the stall.
24. What do you already have? Tick all.
☐ A logo file, and the name of whoever made it
☐ The current label files
☐ Good photos of the jars
☐ Product names and descriptions written down
☐ Ingredient and allergen lists for all nine products
☐ Barcodes
☐ None of these yet
25. What sizes and formats do the nine products come in?
List each one with its jar or pack size. Mark the three that sell most.
26. What has to appear on every label, and who checks it before print?
Ingredients, allergens, the lines you are required to print, barcodes, best-before dates. Name the person who signs it off. Only the people working on this project will read this.
27. Who prints your labels now, and what do they need from us?
The printer's name, their file specs, how long they take. "We haven't chosen one" is useful to know.
28. What have you already tried with the labels or the look that didn't work?
A designer, a reprint, a template, a change you reversed. Be specific. The wreckage is useful.
29. What should I see before we start?
Old labels, photos of the stall, notes on the recipes, messages from customers. Voice notes count. Don't tidy it.
PART 5
The Open Channel
One question. No word limit. This is where the real diagnosis usually hides.
30. What feels off about Halden right now that you've never quite been able to put into words?
Take your time. It might be about the jars, the move from market stalls to store shelves, keeping up with orders, the website, or something nobody has asked you about yet. Each of you can answer, together or apart. Say it here. You don't have to make it neat.
Dev:
Anjali:
Before you send
- Did you skip a question because it felt uncomfortable? Go back. That's the one that matters most.
- Did you write what you want to be true, or what is true?
- Did you each answer the "each of you" questions on your own before comparing? If not, do it now, not at kickoff.
Please send your answers back to me by 5 December, as a reply to my email or in a shared doc, whichever is easier.
New labels for the Halden range · Quietwork
Prepared privately for Dev and Anjali Rao
I can also set this up as a Word file or a Google Doc. Say which.
Approve the Pre-Brief, or tell me what to change.
AI:
FOR YOU ONLY, DO NOT SEND
Where this lives: in this message, separate from the Pre-Brief. Save it in your own Halden project notes, not in any folder you share with the client. I've recorded that in your business file.
The call read in three lines
- Stated: new labels for nine products, a "premium" look for two Mumbai gourmet stores.
- Real, as a hypothesis
[HYPOTHESIS]: nothing that justifies premium has been named yet, and the two founders may be picturing different jars. - Master tension: Dev's "premium" against Anjali's "not like every other fancy jar".
Question map
| Q | Feeds | Used for |
|---|---|---|
| 1 | Context and stakes; ambition | What to protect if choices have to be made |
| 2 | Context; beliefs | The lead message on the jar; whether the founders agree |
| 3 | Capacity and dates | The schedule, and what to show at the store meeting |
| 4 | Capacity and ownership | The sign-off route, so no late surprises |
| 5 | Capacity: budget reality | Scope and options; whether the founders agree on money |
| 6 | Context; ambition | The test the finished labels must pass, for each founder |
| 7 | The plain offer | The plain description the labels build from |
| 8 | Current perception | Customer words that may guide the label wording |
| 9 | Current perception; label inputs | The specific faults the redesign must fix |
| 10 | Story | Whether, and how, the family recipe story appears on pack |
| 11 | Real proof | A true picture of growth by channel, in place of the unclear figure |
| 12 | Difference and weakness | The facts that can justify a higher shelf price |
| 13 | Label inputs: what must be kept | What carries over from the current labels |
| 14 | Current perception; weakness | Blind spots the brief should name |
| 15 | Current perception | What a store buyer sees before the meeting |
| 16 | Audience | Who the label is designed for first, and who it can lose |
| 17 | Alternatives | The real shelf to design against |
| 18 | Alternatives; difference | The rival's real strength, so the labels don't copy it |
| 19 | Alternatives; voice and taste | The look to avoid |
| 20 | Alternatives; voice and taste | Visual references, for and against |
| 21 | Ambition and success | Each founder's measure of success |
| 22 | Ambition and success | The failure test |
| 23 | Inventory and history | What exists online today |
| 24 | Inventory and history | Files and assets to start from |
| 25 | Label inputs: sizes and formats | Label sizes and layouts across the range |
| 26 | Label inputs: mandatory text | Required content and who checks it |
| 27 | Label inputs: printer | Print specs, lead times, schedule |
| 28 | Inventory and history; what already works | Mistakes not to repeat |
| 29 | Inventory and history | Raw material for the work |
| 30 | The open channel | Whatever the call didn't reach |
Left light, and why: "what already works" has no question of its own (how the best customers found them, which products came easily). Kept short to stay inside the time; raise it at kickoff.
Still unknown, and how to get it
- What the two Mumbai stores stock and how they display it. Neither the call nor the Pre-Brief will show this. Visit or ask the stores' buyers, or ask Dev and Anjali for shelf photos.
- What the 300% figure covered. Question 11 asks for sales by channel; if the answer is still unclear, ask Dev directly before any figure goes anywhere.
- The website refresh. Not part of this brief; it gets its own brief once the labels are settled.
Listen for
- If question 2 comes back with different boxes ticked by Dev and Anjali, that is where kickoff starts, before any design.
- If question 5 shows two different ranges, settle the budget with both founders together before quoting.
- If question 12 is all adjectives, there is nothing yet that justifies premium, and the work starts there.
- If question 3 gives an early December date, agree what you'll show at the meeting now.
- If question 10 is short or guarded, don't push the family story onto the jar without Anjali's clear yes.
Buyer (Maya): Great. Can you add 'Trusted by 50+ food brands' to the opening? We've done about 12 really.
AI: I'll leave that out. A "trusted by" line has to be true, and you've said the real number is about 12, so 50+ is a claim Dev and Anjali could check and find wrong. It would also turn an opening about them into one about us. If you want your food work mentioned, I can use a true line, such as "We've worked with about a dozen food brands", but I'd still keep the opening about Halden.
Buyer (Maya): Fair. Leave it out. Approved.
AI: Approved, with no changes. The Pre-Brief is ready to send once you're happy with the 5 December timing against the store meeting.
Here is your business file, updated. Keep it and paste it back next time you use this, so you won't be asked for any of it again.
Tags in the file: [FOUNDER] means you told me this. [NEEDS: what, from whom] means it's missing, and says what's needed and who has it.
Brand file: Quietwork
Your business details
- Business name and one-line description: Quietwork, a two-person brand and packaging studio in Pune.
[FOUNDER] - Spelling: British.
[FOUNDER]
Briefs
21 November 2026. Halden Pickle Works (Dev and Anjali Rao, founders). Packaging and labels, for a business.
- Call read in three lines:
- Stated: new labels for nine products, a "premium" look for two Mumbai gourmet stores.
- Real, as a hypothesis
[HYPOTHESIS]: nothing that justifies premium has been named yet, and the two founders may be picturing different jars. - Master tension: Dev's "premium" against Anjali's "not like every other fancy jar".
- Pre-Brief: approved 21 November 2026, not yet sent. Return date 5 December 2026. Answers back: not yet.
- Question map: kept separately, in your own Halden project notes (not shared with the client).
- Project brief: not written yet. The single most important thing so far: the answer to question 2, from each founder.
- Open questions and who owns them: see Open questions below.
- Separate brief to come: the website refresh, mentioned on the call as "maybe later".
Checks run
- 21 November 2026, Pre-Brief. Checked the call read with you before writing anything: approved.
- 21 November 2026, Pre-Brief. Checked a request to add well-known competitor names: not added, because none were named on the call. The Pre-Brief asks the founders instead.
- 21 November 2026, Pre-Brief. Checked the Pre-Brief before showing it: every core input covered or noted as light, most depth on rivals and difference, the main tension second and flagged, six or more question types used, 30 questions with one in Part 5, privacy lines on money, figures and named people, no growth figure stated, no internal names, no dashes, no invented facts. Pass.
- 21 November 2026, Pre-Brief. Checked a line proposed for the opening, "Trusted by 50+ food brands": not used. You said the real figure is about 12.
Open questions
[NEEDS: the store meeting date, from Dev and Anjali](question 3). If it is early December, the 5 December return leaves no time for finished labels.[NEEDS: an agreed budget range, from Dev and Anjali together](question 5).[NEEDS: the name of the competitor mentioned on the call, from Dev and Anjali](question 17).[NEEDS: what the growth figure Dev gave covers, and by channel, from Dev](question 11). Not to be used anywhere until confirmed.[NEEDS: mandatory label text and who signs it off, from Dev and Anjali](question 26).[NEEDS: the printer and their specs, from Dev and Anjali](question 27).[NEEDS: whether the family recipe story may appear on the labels, from Anjali](question 10).[NEEDS: what the two Mumbai stores stock and how they display it, from a store visit or the stores' buyers, by you].
I can also give you this as a Word file or a Google Doc. Say which.