# Q3 Planning Sync — Thursday, 2:30pm
*Conference room B. Ran long (~45 min). Some folks late.*

---

**Attendees:** Priya, Marcus, Lin, Devon, Jess (late ~5 min), Sam (joining from airport, kept dropping off)

**Context:** Trying to lock down the Q3 roadmap. Three big bets, not enough people. Marcus wants to push the analytics feature out of Q3. Priya pushed back. Lin was on her laptop half the time.

---

## Notes (raw — please clean up)

- marketing wants the new landing page live by Aug 15 — that's the hard date, sponsor already promised the board
- analytics thing is still up in the air. marcus says we should kill it for Q3 and use eng on the migration. priya disagrees, says we promised it to a customer
- migration: someone needs to look at the failed jobs from last week. lin mentioned 3 of them, said she'd grab logs but didn't say when
- the API rate limit thing is a problem. devon brought it up twice, nobody had a number for him
- "we should follow up on the website redesign" — jess, vague, no owner
- sam kept dropping off, missed the deploy schedule convo, will need to loop in
- follow-up: schedule a smaller meeting with just priya + marcus to resolve analytics question. sometime next week. priya to send invite
- budget: no answer on whether we can hire a contractor for the migration, finance hasn't replied
- sam mentioned the legal review of the new ToS is still pending, not sure who's tracking that
- lin to send her updated timeline (she kept saying "I'll send it tomorrow" for the last two weeks)
- DevOps will handle the deploy schedule, will share by EOD Friday
- ACTION: someone needs to draft the analytics decision doc so priya and marcus can talk about it with data

---

*This is the kind of messy notes you actually have. Don't clean it up before giving it to the AI — the mess is the point. Let the AI sort it out.*