Explore

02/19/2026

Needing discussion – Today (wedge already decided)

Helper tiers in v0 (reality vs labels)

Confirm how we present Coordinator / Concierge / Pro Planner in the UI while it’s still just BG + TG behind the scenes. Event Coordinator Concierge Pro Planner

⁠

Service Levels⁠

Decide: on v0, do we only surface “Concierge” as the main CTA, or still show all three with “Concierge (recommended)” highlighted.

Still show all three with “Concierge (recommended)” Level Up Service whenever need to.

Minimal Playbook CPT fields for v0

Agree on the exact v0 field list for Party Playbook:

Event basics (type, date, guests, city).

Categories selected (DJ, photo booth, etc.).

Estimate: total range + category breakdown.

Internal notes (BG’s notes for quoting).

Decide which “nice-to-have” fields are explicitly out of scope for v0 (timeline, run-of-show, affiliate list, vendor shortlist).

Estimator UX and copy (Austin-only v0)

Decide the v0 form questions (what we actually ask on the page) vs. what we infer later.

Approve the key result-screen elements:

Cost range phrasing (e.g., “Most events like yours cost between X and Y”).

Single main CTA text (“Talk to a Concierge (free – talent pays)”).

Estimator rules table ownership

Confirm how the rules-based calculator is managed:

BG owns a simple price-bands table (could be a Google Sheet or WP options).

TG reads it; no UI editor in v0.

jurnee⁠

⁠

Decide the first guest-count bands (e.g., 0–50, 51–100, 101–150, etc.) and how we handle edge cases.

Payments: v0 approach and “Stripe-on” trigger

Decide v0:

Option A: no on-site payment yet; BG sends manual invoice/links.

Option B: one simple Stripe deposit flow with clear terms.

docs.stripe⁠

⁠

If Stripe is later, define the switch condition: e.g., “Turn Stripe on after 3 accepted Quotes or 10 serious Playbooks.”

⁠

Estimator + Playbook → Quote funnel (focused discussion)

Define the “Quote” object for v0

Agree what a Quote is in v0:

A human-written offer (email or lightweight template) generated from a Playbook, not a complex proposal system.

involve⁠

⁠

Decide whether we:

Store Quote as a status + notes on Playbook (“Quote Sent”, “Quote Accepted”), or

Add a tiny Quote CPT linked to Playbook, containing: selected vendor type(s), price, deposit, terms summary.

Funnel steps from Estimator → Playbook → Quote

Confirm the linear flow:

Estimator submitted → Playbook created automatically.

BG reviews Playbook, sanity-checks budget, and pings 1–2 vendors manually.

Once at least one vendor confirms, BG creates Quote (status change or new Quote record).

Client accepts Quote (email confirmation or simple “Approve” step).

Decide where in WordPress BG actually clicks to “Create Quote” or set “Quote Sent”.

Minimal funnel metrics to track weekly

Decide on 3 numbers to report in “This Week” before each meeting:

Estimator submissions.

Playbooks that reach “Quote Sent”.

Quotes marked “Booked” (even if paid off-platform in v0).

Agree which role updates these metrics (likely BG) and where they live (This Week page vs a simple shared doc).

⁠

If you want, next step I can turn this into a ready-to-paste “Needing discussion” section for Meeting #N in your Meeting Notes page.

When clients pay with credit cards we need to charge a transaction fee. Bonus for vendors who perform well.

Vendor asks client post-event to do review (make it easy to review, inside email dialog for quick review, review posted on Trust Pilot)

Then bonus to vendor from agency 2-5% for top performers Trust Pilot:

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.