01-projects/phdata

andrew meeting prep

2026-07-31·project·status: prep-brief
phdataandrewanthropic-tiger-teamcareermeeting-prepdsa-tal

Prep brief - the Andrew meeting

Ticket: "Prep the Andrew meeting - get staffed on the work he was actually hired for" (Notion 3aff7d4936d1819c856ae06a37c51d5c).

Meeting context

Who Andrew is: the friend who recruited the founder to phData, and his manager/lead through the 2026-06-18 reorg ([[2026-06-08-1-1-andrew]]). During the reorg Andrew was pulled onto what phData internally calls the "Anthropic Tiger Team" - the team building phData's Anthropic partnership/adoption practice, goal $10M from $0 ([[2026-06-18-applied-ai-reorg-career-fork]]). Andrew wants to pull the founder onto that team.

Date: unconfirmed. The most current vault source (memory project_income_seat_gap_400k, logged 2026-07-31) says "meeting in two weeks (~2026-08-14)" as stated by the founder that same day. That is a founder estimate, not a calendar-verified date - treat it as approximate. The 2026-06-18 career-fork doc separately said Andrew himself looked "likely to move [to Tiger] in ~a month" from that date (~mid/late July); the 2026-07-31 memory implies that move already happened ("Andrew... was pulled onto an Anthropic Tiger team"). Confirm the actual meeting date against the calendar before relying on this brief's timing assumptions.

What's driving it: this is not a routine 1:1. Per the 2026-07-31 memory, the founder disclosed that he was hired as a Snowflake + Claude specialist, but both client engagements assigned to him since starting have been strictly Microsoft Copilot Studio buildouts - not the work he was hired or planned for. The mechanical risk named to him: in a consultancy, staffing runs on demonstrated experience, so two Copilot engagements risk making him "the Copilot person" by default, and a third assignment would lock it in. The Andrew meeting is the intervention point before that ratchet closes.

What "the work he was actually hired for" means

Talking points / questions for the founder to bring

  1. Name the staffing mismatch directly, as a fact pattern, not a complaint. "I was brought on as the Snowflake + Claude specialist. Both engagements to date have been Copilot Studio. I want to break that pattern before a third one locks it in." This is the founder's own framing, already counseled to him - lead with it plainly.
  2. Ask Andrew explicitly what he requires of a "first pull" onto the Tiger team - certs held, deployment track record, ramp/travel expectations. This is genuinely unknown; the 2026-06-24 research brief on the Anthropic partner model flagged it as an open question only Andrew can answer ([[2026-06-24-anthropic-tiger-team-partner-model]]). Don't assume the CCA cert alone is sufficient - confirm what else counts.
  3. Get the "first pull" commitment named and explicit, not a dotted line. The 2026-06-18 career-fork doc's own open action was "Lock the explicit first-pull commitment with Andrew - not a vague org-chart dotted line, but Andrew saying plainly 'you're my first pull when I move to Tiger.'" If Andrew has already moved, ask directly: "Am I still the first pull, and what's the timing?"
  4. Confirm the CCA exam registration links to phData's partner record, not just his personal escalator. Per the Anthropic partner-model brief, phData's Services Track tier is scored on active-certified individuals + production customers + public case studies - the founder can personally supply all three legs (cert, a named deployment, story permission) if his cert counts toward phData's counter and not just his own +$5k bonus. This has a deadline behind it (cert target 2026-11-22) and should be confirmed before, not after.
  5. Bring a proposal, not a grievance. Counsel already given and worth repeating in the room: state the specific work he wants, why he's the obvious pick (hired for exactly this profile, low-overhead Lionsgate engagement = evidence he's pull-ready), and the cert landing 11/22 as a concrete, non-arguable timing anchor - rather than opening with "I'm unhappy with my staffing."

Open risks / unknowns (don't guess past these)

Sources