05 — Conor Sync Prep

Under review (2026-07-19): this doc may be retired — checking with Marko. Durable content has already been relocated: Conor's background/communication style is now in index.md's "Who's who", your testing philosophy is in 03 — How to Test, §0, and the weekly-sync reporting structure is folded into that same section. The first-meeting question list has moved to a personal working doc so it isn't lost. What's left here is meeting-day logistics only.

Conor Halpin is the client CEO (Pinley / Cara). He specifically asked to meet you: he wants to convey the product vision and see how you find and report issues. You'll have a first intro sync and then a recurring weekly QA sync.

Practical prep before the meeting

• Skim doc 01 (domain) so his construction terms land, doc 02 (scope) so you can speak to what is/isn't in July, and doc 03 §0 (your testing philosophy) so you can talk from it naturally rather than reciting it.
• Have the staging URL and at least one role login working (doc 03) so you can talk from having actually used it — even one session in the app before the sync makes your questions sharper.
• Bring one or two concrete observations from early testing if you have them — it shows him the QA lens immediately and is exactly what he asked to see.
• Marko likes to be on these calls (he runs the team + Linear) and records them; assume he'll join or send a recorder.
• Close the conversation with: "What I'd love from you: your view on what a successful pilot looks like, which workflows Alex and Jim live in every day, and where a bug would hurt most — so I aim my time where it counts."