# Solshine × Fuega May 1 — Outcome Capture (Brady-fillable)

**Filed:** 2026-05-04 by CC. **Status:** TEMPLATE awaiting Brady-fill. **Why:** Fuega May 1 was Solshine's intended first pour. No postmortem, Airtable event row, or sales data was captured between May 1 and May 4. This template surfaces the right questions; Brady fills in <15 minutes when convenient. Output becomes input for May 15 Fuega prep.

---

## 1. Did Solshine pour happen at Fuega May 1?

- [ ] Yes — full keg poured
- [ ] Partial — some pours, didn't finish keg
- [ ] Yes but with substitutes — SKU A jars or brewed-on-site samples instead of keg
- [ ] No — skipped Solshine for the event entirely
- [ ] Other — see notes below

**Notes:**

```
<Brady-fill: short freeform context>
```

## 2. Production path

How did the keg/samples get produced?

- [ ] Mesa Local First commercial kitchen (preferred path)
- [ ] Friend's commercial kitchen one-off
- [ ] Brady's home kitchen (cottage food jars only)
- [ ] Pre-existing batch from prior production
- [ ] Other:

**Production date:**

```
<Brady-fill: actual production day>
```

**Production venue:**

```
<Brady-fill: kitchen used>
```

## 3. Cup count served (if poured)

| Pour size | Cups served | Price | Revenue |
|---|---|---|---|
| 4 oz tasting | __ | $__ | $__ |
| 8 oz cup | __ | $__ | $__ |
| 12 oz cup | __ | $__ | $__ |
| Comped (free) | __ | n/a | $0 |
| **Total** | __ | | $__ |

## 4. Revenue collected

| Channel | Amount |
|---|---|
| Cash | $__ |
| Square / card | $__ |
| Stripe / online | $__ |
| **Total revenue** | $__ |

## 5. Customer feedback (3-5 quotes)

```
<Brady-fill: actual things people said about Solshine — taste, hydration feel, willingness to buy again>

1.
2.
3.
4.
5.
```

## 6. What worked

```
<Brady-fill: specific things that went smoothly — pour speed, taste reception, signage, etc.>
```

## 7. What didn't work

```
<Brady-fill: friction points — temp control, equipment, customer confusion, pricing, etc.>
```

## 8. COGS validation

Per H185 keg-pour model, estimated total COGS per 15.5-gal keg = $500-580. Actual:

| Component | Estimate | Actual |
|---|---|---|
| Ingredients (nettle/horsetail/lemon/honey/etc) | ~$125 | $__ |
| Mesa Kitchen rental (4-6 hr) | $80-120 | $__ |
| Brady labor (5 hrs × $50/hr) | $250 | $__ |
| Sanitation supplies | $10 | $__ |
| Keg amortized | $10-30 | $__ |
| Cups + tap consumables | ~$30-50 | $__ |
| **Total** | **$500-580** | **$__** |

If actual COGS came in higher → re-run pricing analysis (H185 keg-pour model) before May 15 Fuega.

## 9. Adjustments for May 15 Fuega

Based on May 1 learnings, what changes for May 15?

- [ ] Increase cup price (which size, to what)
- [ ] Decrease cup price (which size, to what)
- [ ] Switch pour size mix (more 4oz tastings vs 8oz cups)
- [ ] Different equipment (jockey box vs ice bath, etc.)
- [ ] Different signage / pricing display
- [ ] Pre-event marketing push to drive Solshine awareness
- [ ] Stay the course — May 1 was the right model
- [ ] Skip Solshine at May 15 entirely (focus on dance event)
- [ ] Other:

**Notes:**

```
<Brady-fill>
```

## 10. Phase 2 trigger watch

Per H185 keg-pour model, Phase 2 bottling triggers after 5 events with all of:
- Average >50% net margin per pour
- Average >$300 net revenue per event
- >20% repeat customers by event #5
- 3+ unprompted shipping-request asks

May 1 contribution to trigger watch:

| Trigger condition | May 1 result | Running average |
|---|---|---|
| Net margin per pour | __% | __% |
| Net revenue this event | $__ | $__ avg |
| Repeat customers | __ (if anyone returned for refill or 2nd) | __% |
| Shipping requests | __ | __ cumulative |

**Events toward 5-event trigger:** 1 of 5 (May 1 = event #1; May 15 will be event #2)

---

## How to use this doc

1. **Brady opens this** when convenient (15-min sit-down)
2. Fills in the `<Brady-fill>` blocks with actual data + memory
3. Saves the file
4. Next session, this becomes the input for May 15 Fuega prep + the running Phase 2 trigger tracker

If Brady can't recall some details (e.g., exact cup count) → "estimated ~__" is fine. The point is to capture signal, not perfect data.

---

_Filed S83-H185-C (2026-05-04 by CC). Template-only. Brady-fillable. Becomes the May 1 → May 15 bridge once filled._