---
name: taster-event-planner
description: Use when you sell a food, drink or other product people can sample, and want to test versions on real buyers in person while also filming content. It plans a one-day tasting event: setup, a sampling script, a shot list, a taster card, and a decision rule set before the day.
---

# Taster event planner

You plan a one-day public tasting that does two jobs: it tells you which version of a product real buyers prefer, and it produces video and photos you can use for a long time. You write the plan, the script, the scorecard and the decision rule. You never invent results.

<!-- needs: written by tools/add-needs.mjs from the blocks' inputs. Edit that tool, not this section. -->
## Before you start
This skill runs on its own. What's below makes the result better, but none of it is required.

**Works best with** (or they can paste their own instead):
- **Brand brain** (its products and buyers part), made by the [Website brand brain builder](https://useaiblocks.com/skills/website-brand-brain-builder): your facts, products, buyers, claims and voice, in one folder of eight files.

**Recommended steps before this one** (optional; do each once, then reuse what it makes):
1. **Brand brain** with the [Website brand brain builder](https://useaiblocks.com/skills/website-brand-brain-builder). Bring your website, customer words (optional), your results (optional).
2. This one.

**From the brand brain, read:** `00-start-here.md`, `offers.md`, `customers.md`, `proof-and-claims.md`, `voice-and-look.md`. Take the chosen offer's facts, approved claims with their conditions, buyer quotes and voice lines. Source notes and rejected ideas never go into the result.

How to start:
1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In Claude Code, look in the project too: a brand brain is a folder with `00-start-here.md` in it (often `brand-brain/`). If it's there, read that file and the files above. Look for the other things by name.
2. **If something is missing, advise, don't block.** In one short message, say this skill works on its own and will be better with your brand brain. They can attach them, paste them, or say where they are (in Claude Code, a file path). Name the recommended steps above as a suggestion, with their links. Then ask: "Add them, or shall I go ahead with what you've given me?" If their message already says to go ahead, skip this and start.
3. **When they say go ahead,** do the whole job with what you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. Keep the answer tight: say each point once, merge steps that give the same thing, and aim for under 700 words unless the job truly needs more. In CHECKS MISSED, name only the checks that failed, or write “none”.

**Tools that do this best:**
- **Any good chat AI:** Builds the plan, the card and the rule, and checks the cost line.
- **Google Forms:** Lets you key in the taster cards afterward and count them fast.
<!-- /needs -->

## What you need
- **The versions to test** (required): for example flavours, recipes, sizes or packs, and what each is.
- **The target buyer** (required): who should taste. One or two lines.
- **Budget and city** (required): what you can spend and where. Include permit and venue costs.
- **How you will film** (strongly advised): who films, with what, and what you plan to do with the footage.

Does not fit: products that cannot be sampled (large items, software, anything that needs weeks of use). It also does not fit a brand with no event budget. A big free event costs real money, so cost it before planning. The method comes from one founder's experience with a drinks and supplements brand. It suits food, drink and other sample-able goods. Leave it out for other products.

## Steps
1. **Cost it first.** List venue, permits, product, staff, signs, camera help, insurance and clean-up. If the total is more than the decision is worth, say so and offer the small version in step 9.
2. **Plan fewer, bigger events.** The founder runs about one big public event a quarter, free and open to everyone, instead of many small ones. A big event can bring in the people who actually buy, not only influencers.
3. **Work backward from the content.** An event that cannot make good video is mostly useless. A so-so event with great content is still a win. Write the shot list before the setup: wide shots of the crowd and the queue, close-ups of reactions on first taste, product in hand, the sign, the people picking a favourite. Film so the footage lasts years; the founder still uses event footage from three years ago.
4. **Plan consent for filming.** Put up clear signs saying filming is happening, use a short release for anyone shown close up or who speaks on camera, and do not film children without a parent's permission. Check local rules.
5. **Test unreleased versions on real people.** With about 10 versions, ask 100 to 150 people. The founder's example: if about 135 of 150 like one version, that is enough to act on, provided they match your buyer. That is one person's illustration, not a statistical rule.
6. **Screen first.** Ask passers-by one question so only people who match your buyer taste. State the question and the answer that qualifies.
7. **Trust a small real sample.** The founder says he would take about 50 real tasters over data he buys. He says paid third-party data and post-purchase surveys misled him. That is his experience. A sample of 50 is still small, so use it for a direction, not a sales forecast.
8. **Beware the loud minority.** His story: about 50 comments a day asked for a vegan product, the brand placed a large order, and it sold about 50 bags. The commenters were a few vocal people. Check who is asking before you place a large order.
9. **Small version and your own team.** If an event is too costly, use your own team as a test panel, but only if they match your buyer. Staff know the brand and want to please, so treat their votes as a first filter, not proof.
10. **Write a one-line taster card.** Three items: do you like it (score), would you buy it (yes or no), and what price do you expect. Add a pick-your-favourite line across versions. Keep the card to one side of a card.
11. **Set the pass rule before the event.** Write it down. Example shape: "A version goes forward if at least X of the matching tasters like it, and at least Y say they would buy at a price within our range." Choose X and Y yourself. The founder's example had about 90 percent liking one version out of many. Adjust the bar to how costly a wrong call would be.
12. **Write the day plan.** Setup, signs, the sampling script (what staff say, what they must not say, such as health claims), allergen and safety information, how to record the cards, and when to film.
13. **Plan the read-out.** How the cards are counted, who counts, and what the next step is for a pass, a tie and a fail.

## What you hand back
Use these labels in this order:

```
COST
Venue: <...> | Permits: <...> | Product: <...> | Staff: <...> | Filming: <...> | Insurance and clean-up: <...> | Total: <...>

ONE-DAY PLAN
Before: <permits, signs, release forms, allergen info>
Setup: <layout, stations, queue>
Screening question: "<...>" | qualifies if: <...>
Sampling script: <what staff say, what they must not say>
Timeline: <hour by hour>

SHOT LIST (for the footage)
1. <shot> | when | who films | consent needed: <yes/no>

TASTER CARD
1. Like it: <1 to 5>
2. Would you buy it: <yes / no>
3. What price do you expect: <...>
4. Pick your favourite of the versions: <...>

DECISION RULE (set before the event)
Goes forward if: <X of N matching tasters like it AND Y say they would buy at a price within range>
Tie: <...>  Fail: <...>
Read-out: <who counts, when>
SAFETY AND LEGAL: <food safety, allergens, permits, consent for filming; check local rules with a qualified person>
CHECKS MISSED: <none | list>
```

<!-- next: written by tools/add-needs.mjs from the blocks' outputs. Edit that tool, not this section. -->
## After this
When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:
- **Set up AI to work for you** with the [AI workflow handoff planner](https://useaiblocks.com/skills/ai-workflow-handoff-planner). It takes the plan.
- **Make an offer people want** with the [Lead cost and friction planner](https://useaiblocks.com/skills/lead-cost-and-friction-planner). It takes the plan.
- **Plan what to test** with the [Reach-before-repeat planner](https://useaiblocks.com/skills/reach-before-repeat-planner). It takes the plan.
- **Write the ad copy** with the [Story image ad writer](https://useaiblocks.com/skills/story-image-ad-writer). It takes the plan.
- **Make video ads** with the [Video ad shot list maker](https://useaiblocks.com/skills/video-ad-shot-list-maker). It takes the shot list.
If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.
<!-- /next -->

## Checks
- The cost covers venue, permits, product, staff, filming and clean-up, and a total.
- The decision rule is written before the event and names who counts as a valid taster.
- The screening question matches the target buyer.
- The shot list was written before the setup.
- Consent for filming is planned, and children are not filmed without a parent's permission.
- No health claim appears in the sampling script. Food safety, allergen and permit information is planned, with a line telling the owner to check local rules with a qualified person.
- The founder's numbers are labelled as one person's illustration, not as rules.

## If something is missing
- No versions: `MISSING: the versions to test`.
- No target buyer: `MISSING: target buyer`; do not choose a screening question.
- No budget: `MISSING: budget`; give the plan without the cost line and say the cost is unknown.
- No filming plan: `MISSING: who films`; give the shot list anyway.

## Avoid
- Running an event that cannot make good video, unless the test itself is the only goal.
- Letting passers-by who are not your buyer vote.
- Treating loud online comments as demand without checking who they are.
- Counting staff opinions as proof.
- Quoting 135 of 150 or 50 tasters as statistical rules.
- Health claims in the sampling script.
