01-projects/phdata/competitive-intel/managed-agent-handoff

Weekly Claude partner CI debrief - spec

2026-10-22

Debrief spec

Purpose: show where the Claude services market is heading, how phData itself is seen in public, and what both mean for phData's positioning. This is not a news digest. Every section answers "so what?"

Competitive intelligence (CI) 101

Good CI answers a few standing questions, called key intelligence questions:

  1. Who is gaining ground, and how? (tier moves, new logos, new offers)
  2. What are competitors claiming to be best at, and is that claim shifting?
  3. Where is the crowd thin, and do we have a right to win there?
  4. What would change our plan if it were true?

Common failures to design out:

Standing sections

(a) Tier movement. New partners, promotions and demotions, shown as counts by tier with the names. Give the reason if a public source states it. Context: tiers are Select (10+ certified staff, 2+ joint customers in production in the last 12 months, 1+ public story), Preferred (100+, 15+, 3+), and Global Premier (1,000+; 100+ across 3+ regions; 15+; a joint business plan). "Certified" means a current Anthropic certification plus Claude use in the last 90 days. Standing refreshes daily and is verified quarterly. Promotions happen Jan 1 and Jul 1 (plus an extra review on Oct 1, 2026, already past). Demotions happen only at the Dec 31 annual review, after 90 days' notice. In the first brief after each Jan 1 and Jul 1, lead (a) with a promotion-cycle summary against the last pre-cycle snapshot. Source: https://www.anthropic.com/news/services-track-partner-hub. Flag movement that appears outside a promotion date as worth checking.

(b) Positioning claims. What competitors list as specialties: industries, use cases, product focus (Claude Code vs Cowork vs Teams/Enterprise vs the direct API), and cloud surfaces (Bedrock, Vertex, Microsoft Foundry). Report only changes since last week, plus a running count such as "N Preferred partners now list healthcare". The seed has industry counts, not industry names, and no profile fields for Select partners. Until a run can read profiles, counts use products, deployment surfaces and regions for the 56 Preferred and Global Premier partners.

(c) White space. Where the crowd is thin, compared with phData's public strengths: Snowflake Partner of the Year 7 times, AWS Premier partner, Anthropic Preferred tier, and healthcare, financial services and manufacturing. Name one thin spot and one crowded spot each week, with the counts behind them.

(d) Watched-set deep dive. The tracked short list (see [[DECISIONS]]). For each one that has news: public case studies, announcements, hiring signals (public job posts that mention Claude or Anthropic), and conference talks. Slalom comes first and always gets its own line, even with no news (a direct competitor Ben named). Skip other partners with no news, and give a one-line "no change" roll-up for the rest.

(e) phData public image. How phData itself shows up in public, tracked like a competitor. Each week: (1) press and newswire mentions of phData; (2) phData's own announcements, blog posts and case studies; (3) changes to phData's Claude directory profile (tier, products, case studies, last-updated date) and its Snowflake and AWS partner listings; (4) public talks, podcasts or webinars featuring phData people; (5) how phData is described next to competitors in third-party coverage (analyst notes, comparisons, "top partners" lists). Report counts and the one or two items that change how phData is perceived, with tone tagged [positive], [neutral] or [negative] and the basis for the tag. Public sources only: no employee review sites, no personal social accounts, no internal information. If nothing appeared, one line: "No new public mentions since YYYY-MM-DD."

(f) So what for phData. One short paragraph, then at most 3 bullets. Each bullet carries a confidence tag. Bullets are implications for positioning, not tasks.

(g) Sources. A numbered list. Every claim above cites a number. Give the URL and the date accessed.

Format rules

Hard rules for the agent

Seed context