← Home
Partner Basecamp · Insights
London & San Francisco · May 18–21, 2026
2026-07-28 18:21 UTC · v3.3
n=142 D2 · 4 cohorts
London · San Francisco

Programme NPS +37 · 4 cohorts · 142 D2 respondents

4 v2 cohorts · 207 D1 respondents · Historical baseline NPS: +35

Programme NPS · all cohorts
+37
P 53% · Pa 32% · D 16%
n=142 D2 respondents
Cohorts
4
4 with full v2 data
Respondents
207
207 D1 · 142 D2

Cohort summary

CohortNPSP%Pa%D%D2 nD1 nMatchConf Δ
C6 London May 18–19, 2026+4357.1%28.6%14.3%213995%+0.24
C7 San Francisco May 19-20, 2026+3253.3%25.0%21.7%606583%+0.09
C8 San Francisco May 21-22, 2026+4354.1%35.1%10.8%374892%+0.32
C9 London May 20-21, 2026+3845.8%45.8%8.3%245588%+0.22

Conf Δ = D2 apply-AI minus D1 baseline (v2 cohorts only). Match = D1/D2 linked respondents.

London · San Francisco · programme snapshot

London
+40
P 51% · Pa 38% · D 11%
n=45 D2 · 2 cohorts
C6 London May 18–19, 2026, C9 London May 20-21, 2026
San Francisco
+36
P 54% · Pa 29% · D 18%
n=97 D2 · 2 cohorts
C7 San Francisco May 19-20, 2026, C8 San Francisco May 21-22, 2026

Same content and programme design. City split reflects internal team and audience differences.

Audience composition · 207 D1 respondents pooled

Pooled across all cohorts. NPS by org aggregated from v2 cohorts only (n ≥ 4 suppressed).

Function
Engineering
35%
Architecture
25%
Project and engagement mana…
25%
Business leadership
16%
Seniority
Manager or Senior Manager
29%
Senior practitioner
26%
Practitioner
22%
Director, Senior Director, …
17%
Partner, Managing Director,…
6%
AI Proficiency
Applying in practice
45%
Delivering independently
22%
Operating at the frontier
16%
Learning and exploring
16%

Organisation distribution · pooled

OrganisationDistributionn%
Accenture
4320.8%
Deloitte
4119.8%
PwC
2311.1%
Infosys
136.3%
Cognizant
94.3%
Reply
83.9%
Capgemini
73.4%
valantic
62.9%
Infomotion
52.4%
SFEIR
41.9%
Ascendion
41.9%
Fractal Analytics
41.9%
Sia
41.9%
Version 1
41.9%
Theodo
41.9%
Netlight
41.9%
NTT Data
31.4%
Lovelytics
31.4%
Praecipio
31.4%
Horváth
31.4%

NPS by organisation · aggregate (v2 cohorts, n ≥ 4)

OrganisationNPSn
Capgemini+75n=4
Accenture+72n=18
Deloitte+55n=33
Reply+50n=6
Infosys+36n=11
Version 1+25n=4
Cognizant-14n=7
PwC-31n=16

Day 1 calibration · confidence, depth, pace and relevance

Pooled across v2 cohorts. Confidence on 1–5 scale. Depth/pace as % of persona respondents.

D1 Confidence by Persona · mean /5
Architect
4.23/5 · n=52
85%
Developer
4.17/5 · n=72
83%
Transformation Lead
3.82/5 · n=83
76%

Bar = % of max scale (5). Pooled across v2 cohorts.

D1 Confidence by AI Proficiency · mean /5
Applying in practice
3.81/5 · n=93
76%
Delivering independently
4.43/5 · n=46
89%
Operating at the frontier
4.65/5 · n=34
93%
Learning and exploring
3.56/5 · n=34
71%

Bar = % of max scale (5). Pooled across v2 cohorts.

Content Depth by Persona · pooled

PersonaToo basicAbout rightToo advanced
Architect23%
n=12
75%
n=39
2%
n=1
Developer21%
n=15
76%
n=55
3%
n=2
Transformation Lead8%
n=7
76%
n=63
16%
n=13

Session Pace by Persona · pooled

PersonaToo slowWell pacedToo fast
Architect10%
n=5
85%
n=44
6%
n=3
Developer3%
n=2
92%
n=66
6%
n=4
Transformation Lead5%
n=4
81%
n=67
14%
n=12

Content Relevance by Persona · mean /5 · programme mean 4.08/5

Architect
4.35/5 · n=52
87%
Developer
4.00/5 · n=72
80%
Transformation Lead
3.98/5 · n=83
80%

Relevance = Day 1 session relevance rating (1–5). Pooled across v2 cohorts.

Outcomes · NPS by persona, proficiency and open text

Aggregate NPS breakouts from v2 cohorts (n ≥ 4 suppressed). 116 NPS open-text responses available.

NPS by Persona · aggregate (v2 cohorts, n ≥ 4)

PersonaNPS barNPSn
Architect
+66n=26
Developer
+31n=45
Transformation Lead
+28n=54

NPS by AI Proficiency · pooled (v2 cohorts, n ≥ 4)

ProficiencyNPSP%Pa%D%n
Applying in practice+2041.7%36.7%21.7%n=60
Delivering independently+5966.7%25.9%7.4%n=27
Operating at the frontier+5565.0%25.0%10.0%n=20
Learning and exploring+3552.9%29.4%17.6%n=17

Open text · NPS reasons · 116 responses

ConsistentDetractor
Skill-level mismatch limits value
"Advanced users already know how to build with Claude and understand AI engineering practices, while non-technical participants find the hands-on coding exercises inaccessible without prior Python knowledge."

The programme struggles with a wide experience spectrum; it neither challenges experienced engineers nor adequately scaffolds beginners, leaving both groups underserved.

ConsistentDetractor
Practical hands-on exercises need better design
"Some exercises were outdated or incomplete, required troubleshooting by Claude mid-session, and lacked clarity on what participants should do themselves versus delegate to Claude, undermining learning outcomes."

Exercise quality and intentionality are inconsistent; pre-built scaffolding sometimes obscures rather than reveals the underlying concepts and decision-making.

ConsistentDetractor
Delivery favours solo coding over dialogue
"The workshop emphasised individual heads-down work with Jupyter notebooks rather than group discussion, live demos, or facilitated dialogue; participants wanted more guided instruction and collaborative problem-solving."

Pedagogical approach prioritises independent exploration but misses opportunities to build conceptual understanding through shared reasoning and instructor-led modelling.

ConsistentDetractor
Content relevance to consulting roles unclear
"The programme is narrowly focused on engineering and technical building, but many participants are sales, business, or non-engineer roles; clients ask 'what is possible' and 'how to use AI', not how to troubleshoot agents."

Programme design assumes a developer persona; non-technical consultants struggle to translate technical deep-dives into client-facing value propositions and use cases.

ConsistentPromoter
Foundational knowledge and core concepts valued
"Promoters praised learning AI engineering fundamentals, latest Claude features, and practical methods to use the tool efficiently; this content is novel and differentiating compared to other Anthropic training."

The programme succeeds when it teaches Claude-specific techniques and industry-forward principles that participants cannot access elsewhere.

Confidence · D1→D2 deltas across all three dimensions

Apply-AI · Design-AI · Commercial confidence. D1 baseline → D2 delta. v2 cohorts only.

D1 → D2 Confidence by Dimension · per cohort

CohortD1 buildD2 apply-AID2 design-AID2 commercial
C6 London May 18–19, 20264.004.24
+0.24
4.05
+0.05
4.19
+0.19
C7 San Francisco May 19-20, 20264.084.17
+0.09
4.28
+0.20
4.28
+0.20
C8 San Francisco May 21-22, 20264.004.32
+0.32
4.14
+0.14
4.19
+0.19
C9 London May 20-21, 20263.954.17
+0.22
4.38
+0.43
4.17
+0.22

D2 value shown above; delta (D2 – D1) shown below in smaller text. Scale 1–5.

Confidence Delta by Persona · pooled

Architect
n=26
+0.34
Transformation Lead
n=54
+0.22
Developer
n=45
-0.00

D1→D2 apply-AI mean delta. Positive = gained confidence. Scale 1–5.

Confidence Delta by NPS Segment · pooled

Promoter
n=66
+0.17
Passive
n=39
+0.23
Detractor
n=17
+0.12

Promoters gain more confidence than detractors — or vice versa?

5 systematic patterns · 1 flag · 5 suggested queries

Systematic patterns = same direction vs programme NPS across ≥2 cohorts. Suggested queries pre-written for ask.py.

Function / Persona patterns · consistent across ≥2 cohorts

PatternDirectionAvg ΔCohortsSeen in
Architect scored above programme NPS in all 4 cohorts analysed (avg +28 pts)↑ Above programme+28 pts4C6 London May 18–19, 2026, C7 San Francisco May 19-20, 2026, C8 San Francisco May 21-22, 2026, C9 London May 20-21, 2026

AI Proficiency patterns · consistent across ≥2 cohorts

PatternDirectionAvg ΔCohortsSeen in
Delivering independently scored above programme NPS in all 4 cohorts analysed (avg +17 pts)↑ Above programme+17 pts4C6 London May 18–19, 2026, C7 San Francisco May 19-20, 2026, C8 San Francisco May 21-22, 2026, C9 London May 20-21, 2026

Organisation patterns · consistent across ≥2 cohorts

PatternDirectionAvg ΔCohortsSeen in
PwC scored below programme NPS in all 2 cohorts analysed (avg -60 pts)
Likely reflects audience fit, not delivery variance.
↓ Below programme-60 pts2C7 San Francisco May 19-20, 2026, C8 San Francisco May 21-22, 2026
Accenture scored above programme NPS in all 2 cohorts analysed (avg +35 pts)
Likely reflects audience fit, not delivery variance.
↑ Above programme+35 pts2C7 San Francisco May 19-20, 2026, C9 London May 20-21, 2026
Deloitte scored above programme NPS in all 2 cohorts analysed (avg +17 pts)
Likely reflects audience fit, not delivery variance.
↑ Above programme+17 pts2C7 San Francisco May 19-20, 2026, C8 San Francisco May 21-22, 2026

Outlier flags

● High passive rateHigh passive rate in C9 London May 20-21, 2026 (46%). Passives are the most likely source of churn — explore what would convert them to promoters.

Suggested ask.py queries

Run these commands from the Partner Basecamp/ folder to investigate the patterns above. Add --save when you have a conclusion to commit to the insights cache.

Architect — persona pattern
Architect scored above programme NPS in all 4 cohorts analysed (avg +28 pts)
cd "$REPO" && python3 _scripts/ask.py --question "Why does Architect consistently score +28 pts above programme NPS across 4 cohorts — is this audience fit, content relevance, or delivery?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c6-c9/insights-data-c6-c9.json" --save
Delivering independently — proficiency pattern
Delivering independently scored above programme NPS in all 4 cohorts analysed (avg +17 pts)
cd "$REPO" && python3 _scripts/ask.py --question "Why do Delivering independently AI proficiency participants rate the programme +17 pts above average — what does the D1 calibration data tell us?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c6-c9/insights-data-c6-c9.json" --save
PwC — org pattern
PwC scored below programme NPS in all 2 cohorts analysed (avg -60 pts)
cd "$REPO" && python3 _scripts/ask.py --question "What explains PwC's persistent below-programme NPS score across 2 cohorts, and what would change it?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c6-c9/insights-data-c6-c9.json" --save
High passives: C9 London May 20-21, 2026
Passive rate: 46%
cd "$REPO" && python3 _scripts/ask.py --question "What is driving the high passive rate in C9 London May 20-21, 2026 — what do the verbatims say and what would convert them to promoters?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c6-c9/insights-data-c6-c9.json" --save
Promoter vs passive — what separates them
NPS verbatim analysis — highest signal for passive conversion
python3 _scripts/ask.py --question "What do promoters and passives say about the programme, and what specifically separates them?" --cache "/Users/edward.whittall/Library/CloudStorage/Box-Box/Anthropic/Phase II/Partner Enablement/Partner Basecamp v2/Partner Basecamp — Survey Pipeline/findings/insights/c6-c9/insights-data-c6-c9.json"

Investigation log · 5 conclusions saved · 5 open queries

Conclusions committed via ask.py --save, open signals from Tab 06 patterns, and pre-written queries.5 conclusions saved

Saved conclusions · 5 from ask.py --save

Q: Why does Architect consistently score +28 pts above programme NPS across 4 cohorts — is this audience fit, content relevance, or delivery?
The data points to audience fit as the primary driver, but content relevance is a co-factor — delivery cannot be assessed from available data.
Architects score +67 (C6), +38 (C7), +88 (C8), and +75 (C9) versus programme NPS of +43, +32, +43, and +38 respectively — a consistent gap averaging approximately +28 pts. The most plausible explanation is audience fit: Architects are pre-selected for system-design thinking and arrive with sufficient technical grounding to engage with content pitched at an 'Applying in practice' to 'Delivering independently' level, whereas Transformation Leads and Developers show more variance (Transformation Lead ranges from +25 to +80; Developer from +17 to +62). Content relevance is a co-factor: the single highest Architect verbatim explicitly cites 'well matched against the product capabilities and how to think about the larger set of questions for clients' (C8 Architect, frontier proficiency). Detractor verbatims from non-Architect personas repeatedly cite the programme being 'too foundational' or 'not beginner friendly,' implying the calibration suits Architects better than other groups. Delivery as a distinct driver cannot be isolated — no facilitator ratings, session-level scores, or delivery-specific survey items are present in the data. Key data points: · Architect NPS by cohort: C6 +67, C7 +38, C8 +88, C9 +75 — all above cohort programme NPS · Architect n is small across all cohorts: C6 n=6, C7 n=8, C8 n=8, C9 n=4 — findings are directionally consistent but not statistically robust · Key Architect promoter verbatim (C8): 'Well matched against the product capabilities and how to think about the larger set of questions for clients' — directly citing content-to-role fit Caveats: Architect n ranges from 4 to 8 per cohort — below the 20-respondent threshold for confident segment conclusions; treat as directional signal only. To distinguish audience fit from content relevance from delivery, you would need session-level ratings broken out by persona, facilitator scoring, and a pre-programme role-relevance self-assessment.
2026-07-28 18:20 UTC
Q: Why do Delivering independently AI proficiency participants rate the programme +17 pts above average — what does the D1 calibration data tell us?
The D1 calibration data does not include NPS broken out by AI proficiency segment, so the +17 pt advantage cannot be directly explained from the available data.
The data brief confirms that 'Delivering independently' participants rate the programme +17 pts above the programme average NPS of +37, but NPS scores are not disaggregated by AI proficiency band in any cohort — only headcounts per band are provided (C6: n=8, C7: n=14, C8: n=11, C9: n=13, totalling n=46 across four cohorts). D1 calibration scores are available at cohort level only (ranging from 3.95 in C9 to 4.08 in C7), not segmented by proficiency. Verbatim evidence points in a consistent direction: detractors and passives are disproportionately advanced practitioners frustrated by content pitched too foundationally, while 'Delivering independently' participants may sit in a sweet spot — experienced enough to apply the material immediately, but still gaining structured frameworks they lack. The one 'Delivering independently' promoter verbatim explicitly values 'fundamental AI engineering principles,' suggesting the programme's technical grounding resonates at this level without feeling remedial. Key data points: · 'Delivering independently' n across C6–C9: 8, 14, 11, 13 — total n=46, sufficient for a segment-level cut but not currently reported · D1 confidence scores range 3.95–4.08 across cohorts, but are not broken out by proficiency band — no D1 calibration comparison is possible by segment · Detractor verbatims skew toward 'Operating at the frontier' (e.g., valantic Architect, nps=6; Horváth Developer, nps=4) and passives toward 'Applying in practice', suggesting 'Delivering independently' avoids both ceiling and floor dissatisfaction effects Caveats: To answer this question properly, NPS and D1/D2 confidence scores need to be cross-tabulated by AI proficiency band. Specifically: NPS by proficiency segment per cohort, and mean D1 confidence score and D1→D2 confidence delta by proficiency band would isolate whether the effect is driven by pre-existing confidence level, confidence gain, or content-fit perception.
2026-07-28 18:20 UTC
Q: What explains PwC's persistent below-programme NPS score across 2 cohorts, and what would change it?
PwC's NPS averaged -23 pts across C7 (-45, n=11) and C8 (+0, n=5), driven by a consistent signal that the programme is perceived as too basic for their attendees' existing skill levels.
In C7, PwC scored -45 vs. a cohort NPS of +32 — a 77-point gap — and in C8 scored +0 vs. a cohort NPS of +43, a 43-point gap. Verbatims from PwC participants point to a single recurring theme: the content is pitched below their experience level. C7 PwC detractors explicitly said 'good for entry level with no Claude code experience' and called for 'more dialogue and discussion' rather than heads-down coding they felt could be done independently. The C8 PwC detractor felt 'lost' and 'behind' — the opposite direction — suggesting PwC may be sending a mixed-seniority group without sufficient pre-segmentation. Notably, the one C7 PwC promoter ('very helpful for a beginner') was a Practitioner-level Transformation Lead 'Applying in practice', confirming the content lands well for less experienced attendees but not for more seasoned ones. To change this, PwC would need to either send attendees better matched to the programme's current level, or Anthropic would need to create a streamed or advanced track for participants already delivering independently. Key data points: · PwC C7 NPS: -45 vs. cohort +32 (77-point gap), n=11 · PwC C8 NPS: +0 vs. cohort +43 (43-point gap), n=5 · PwC C7 detractors (3 verbatims) all cited content being too basic or format mismatched to in-person value · Only PwC promoter in C7 was entry-level ('Applying in practice', Practitioner seniority) — confirming the content works for newer practitioners · PwC is absent from C6 and C9 org-level data, so the pattern is confined to two cohorts Caveats: C8 PwC n=5 is well below the 20-respondent threshold for confident conclusions — treat as directional only. A breakdown of PwC attendees' AI proficiency levels across cohorts would confirm whether PwC consistently sends more experienced practitioners, which is the most actionable diagnostic available.
2026-07-28 18:20 UTC
Q: What is driving the high passive rate in C9 London May 20-21, 2026 — what do the verbatims say and what would convert them to promoters?
C9 London's 45.8% passive rate is driven by experienced participants finding content insufficiently advanced — verbatims point to depth and instructor capability as the two conversion levers.
C9 London has the highest passive rate across all four cohorts at 45.8% (n=24), compared to 25–35% in the San Francisco cohorts. Three passive verbatims are available and all score 7–8; none express strong dissatisfaction, but none articulate a clear reason to recommend. The detractor verbatims are more revealing: a frontier-level Developer from Horváth (NPS 4) explicitly states 'Few new things but mainly existing topics you mostly know when working with claude. Instructors did not seem to be capable of answering deeper technical questions.' A second detractor (NPS 5) notes the content is 'More for less experienced recipients.' This pattern mirrors C6 London passives, where a frontier-level SFEIR Developer (NPS 7) said content 'was already kind of known' for advanced users. C9's cohort skews experienced: 13 participants are 'Delivering independently' and 13 are 'Operating at the frontier' out of 55 day-one attendees, meaning roughly half the room may have outgrown the current content level. Converting passives to promoters likely requires either a streamed advanced track or deeper technical modules — and demonstrably stronger instructor capability on complex questions. Key data points: · C9 passive rate: 45.8% — highest across C6–C9 (next highest is C8 at 35.1%) · 26 of 55 C9 day-one participants (47%) are at 'Delivering independently' or 'Operating at the frontier' proficiency · Detractor NPS 4 verbatim explicitly cites shallow content depth and instructor technical limitations as the failure points Caveats: Only 3 passive verbatims are available for C9 (n=24 NPS respondents), which is insufficient to generalise with confidence. The passive verbatims themselves are thin ('Great content', 'It helped a lot') and do not explain the 7–8 scores — a follow-up open question targeting passives specifically would sharpen the conversion diagnosis considerably.
2026-07-28 18:21 UTC
Q: What do promoters and passives say about the programme, and what specifically separates them?
Promoters value practical depth and clear applicability; passives liked the content but felt it was too broad or too introductory for their level — the gap is calibration to experience, not content quality.
Promoters consistently cite specific, actionable gains: technical depth on Claude ('very useful technical dive into Claude'), foundational AI engineering principles, client framing ('well matched against product capabilities and how to think about larger questions for clients'), and structured coverage of important topics. Their language signals confidence and utility. Passives, by contrast, express general satisfaction — 'great content,' 'good course,' 'it was very good' — but their criticism, where present, centres on level-fit: one C6 passive (Operating at the frontier, Developer, SFEIR) explicitly noted 'most of the content was already kind of known,' and a C7 passive (PwC) wanted 'more build guidance instead of working off pre-built plumbing.' The separating factor is not whether participants enjoyed the programme, but whether it delivered new capability or stretch relative to their existing proficiency. Detractors reinforce the same pattern at greater intensity: advanced participants across C6, C7, and C9 flag insufficient depth, while less experienced participants in C8 flag being left behind — confirming a level-calibration problem in both directions. Passives sit in the middle: satisfied enough not to detract, but not stretched enough to advocate. Key data points: · Passives represent 31.7% of all respondents across C6–C9 (n=142); C9 London has the highest passive rate at 45.8% (n=24), flagged as high-risk for churn · Promoter verbatims consistently reference specific content value: 'technical dive into Claude,' 'fundamental AI engineering,' 'how to think about larger questions for clients' — all outcome-oriented · Passive verbatims where substantive (C6 SFEIR, C7 PwC) cite level-mismatch: content already known to more advanced participants, or desire for more hands-on building vs. pre-built scaffolding — not dissatisfaction with delivery Caveats: Verbatim coverage is sparse — only 3 promoter, 3 passive, and 3 detractor quotes per cohort are available, limiting confidence in thematic conclusions. A full verbatim export with NPS scores and proficiency tags would allow quantitative theme coding to validate whether level-calibration is the dominant passive driver or one of several.
2026-07-28 18:21 UTC

Open signals

Systematic patterns
5
consistent across ≥2 cohorts
Outlier flags
1
anomalies flagged
Conclusions saved
5
from ask.py --save
Suggested queries
5
pre-written in Tab 06

Patterns not yet addressed by a saved conclusion:


Pre-written queries → Tab 06 · Patterns

Tab 06 contains pre-written ask.py commands for each pattern and flag detected. Run them from the Partner Basecamp/ folder, review the output, then re-run with --save to commit the conclusion here.

Data Quality · survey compliance and completeness

Issues flagged for transparency and database migration. Assessment and remediation tracked with delivery team.

Programme Summary · Survey Compliance
Total Day 2 responses 142
Matched to Day 1 125 (88.0% of Day 2)
Day 2-only respondents 17 (12.0%) — no Day 1 data, excluded from persona & confidence analysis
NPS impact of D2-only respondents suppresses programme NPS by 5 points