client-projects/clients/spice-nvybe/MEETING_PREP_KAY.md

Kay Meeting Prep — Spice N'Vybe Alignment

Date: July 4, 2026 Purpose: Align on scope, priorities, and data access — not a sales pitch Reference: SNV_AI_Scope_of_Work_v2.pdf (client's signed SOW)

---

🎯 Meeting Approach

Tone: Discovery + Alignment, not a demo or sales pitch.

We've reviewed their SOW in full. We didn't build it, so we're not showing them a dashboard they haven't seen yet. Instead, we're figuring out what they actually need so we can start building what matters.

"Kay, we've reviewed your SOW in detail. A few things we want to nail down so we can start building immediately."

---

❓ Key Questions for Kay (in Priority Order)

1. What's the ONE thing you need working first?

The SOW sequences the Dashboard (M01) last in Weeks 11-14, after everything else. Is that still your priority order, or has that changed?

Probe options if he's unsure:

• Dashboard with real financial data?
• Chatbot for the Cloud Kitchen team to look up SOPs/menus?
• Training system you mentioned already has a foundation?
• CRE listings coming in automatically?

Our recommendation (if he asks):

"The fastest path to value is getting the Dashboard live with just one data source — SpotOn sales data. That gives you real numbers in 2-3 weeks. We layer on Plaid, QBO, and everything else after."

2. MarginEdge — do you use it?

It's referenced in M01, M02, and M03. If they use it, we need API access to scope integration. If they don't, we drop it.

3. Gmail + Google Calendar in the Dashboard — critical or nice-to-have?

The SOW mentions unanswered email queue and a calendar widget. Find out: is this MVP, v1.1, or not pressing?

4. Existing Training System — what's there?

SOW says M06 "extends the existing kitchen training system already in operation". We need to see what they have before we scope.

5. CRE Scraper — how do you want to handle it?

Loopnet/Crexi scraping is legally grey. Do they accept a browser-automation approach, or do they prefer a paid data feed?

---

🔑 Critical Unlocks (Need These to Start)

#	Item	Who's responsible	Status ⬜
1	SpotOn API keys — Oakland Park + Ft. Lauderdale	Kay	⬜
2	QBO OAuth access — realm ID, Intuit dev account	Kay	⬜
3	Plaid credentials — client_id + secret, or Link flow	Kay	⬜
4	MarginEdge — yes/no? If yes, account access	Kay	⬜
5	Gmail API — needed for M01?	Kay	⬜
6	Google Calendar API — needed for M01?	Kay	⬜
7	M06 existing training system — can we see it?	Kay	⬜

Pitch if hesitating: "The single biggest unlock is data access. If we can get SpotOn, QBO, and Plaid credentials this week, we can have a live prototype running in 2-3 weeks."

---

🗺️ Our Real Delivery Priority (Not the SOW's Sequence)

Phase	What	Why
Week 1	Get API keys	Everything blocks on this
Weeks 2-4	M01 core dashboard (SpotOn sales first)	Fastest visible win — real numbers
Weeks 4-6	M01 + Plaid + QBO	Full financial picture
Weeks 6-10	M05 Chatbot (RAG)	Quick win — we have the inference infra
After	M02, M03, M04, M06, M07	Based on what Kay prioritizes

Key truth: Don't build M01 last. A live prototype with real data in 3 weeks builds more trust than a 16-week timeline.

---

📋 Conversation Flow

1. Opening — Set the Frame (2 min)

"Hey Kay, thanks for the time. We've gone through your SOW thoroughly. I want to make sure we're building what actually moves the needle for you, so I've got a few questions to align on before we start."

2. What's Priority #1? (5 min)

"Your SOW sequences the Dashboard last. Is that still the plan, or has the urgency shifted?"

Let him talk. Listen for what he actually cares about.

3. Data Source Check (5 min)

"To build anything, we need access to your data. Let me run through what we'll need..."

Go through the Critical Unlocks checklist above.

Key framing:

"For QuickBooks — read-only access to invoices, P&L, and payables. For banking — Plaid is view-only, we can never move money. For SpotOn — sales and labor data only."

4. Scope Clarifiers (5 min)

"A few quick clarifiers from the SOW..."

• MarginEdge?
• Gmail/Calendar in Dashboard — critical or nice-to-have?
• Training system — can I see the current version?
• CRE scraper — how do you want us to handle the legal side?

5. Close — Next Steps (3 min)

"Once we have those API keys, I can have a working prototype with your real data in 2-3 weeks. How does that timeline feel to you?"

Confirm:

• Who's the point of contact for each data source
• Tentative ETA for credentials
• When to follow up

---

🚨 Potential Objections & Responses

Objection	Response
"The SOW already says all this — why are we rehashing it?"	"We're not rehashing — we're confirming. The SOW sequences things one way. I want to make sure that order still works for you before we invest time building."
"I'm not comfortable giving bank access."	"Plaid is read-only — can see balances and transactions, never touch money. Same tech QuickBooks and Venmo use."
"I need everything at once, not phased."	"I can build faster by starting with what matters most and adding layers. A live dashboard with sales data in 3 weeks is more useful than a complete plan in 3 months."
"Who sees our data?"	"Stays on our private infrastructure. No third parties, no cloud sharing."

---

📝 After the Meeting — Capture

Come back and tell me:

1. Kay's priority #1 — what does he want first?
2. API keys — which did he commit to? When?
3. MarginEdge — yes/no?
4. Gmail/Calendar — must-have or optional?
5. M06 training system — what exists?
6. CRE scraping — his stance?
7. Timeline — what did you both agree on?

I'll update the project plan and start building as soon as credentials land. 🦅