AGT-903 — Strategy Brain

Layer 9: Reasoning · Tier 2 Brain Agent · Multi-quarter horizon · Portfolio & segment-bet reasoning · LLM-native · Reads Tier 1 services · Never writes canonical data · Executive-invoked
L9 · Agent 03 Specced · v37 Tier 2 · Brain Agent CRO + RevOps
Long-horizon counterpart to AGT-901 and AGT-902. Where AGT-901 reasons across the current pipeline and AGT-902 reasons across a single account in the current state, AGT-903 reasons across multi-quarter trajectory and portfolio bets: ICP redefinition, vertical entry, pricing/packaging strategy, capacity reallocation, retrospective on prior strategic moves. Same architectural commitments — LLM-native, reads brain-ready views, never writes canonical data, executive-invoked. The CRO owns the strategic call; the brain assembles cross-functional, cross-quarter context faster than a planning cycle would.
Purpose

AGT-903 is the strategic-reasoning layer for portfolio and multi-quarter questions: are we making the right segment bets?, is our ICP still aligned with where the highest-LTV customers actually are?, did the bet we made last year work, and what's next?, if we have $X to deploy, where's the highest-leverage motion?. It reads multi-quarter cohort and trajectory views from Tier 1 services, optionally calls Tier 3 specialist tools (cohort retention, market sizing), and produces option-shaped strategic recommendations — not single answers — with full source-trace metadata for executive review. It is invoked rarely and per query is heavy: annual planning, board prep, mid-year inflection moments, strategic offsites. Never on cadence.

Scope — what AGT-903 answers, what it doesn't
In scopeOut of scope
"Should we expand ICP to fintech vertical?"Computing TAM/SAM for fintech (AGT-205 owns)
"Our top-decile NRR customers don't match our ICP — should we rewrite the rubric?"Editing the ICP rubric (AGT-201 owns; spec change required)
"Did the 2025 land-and-expand pivot work? What does the cohort data say?"Computing cohort retention numbers (Tier 1 service brain-ready view extensions own)
"If we add 10 reps, what's the highest-leverage segment to deploy them in?"Producing the capacity plan (AGT-105 owns)
"Are we leaving money on the high end of pricing? Underpricing the low end?"Pricing decisions or quote generation (AGT-406 owns CPQ)
"We're losing more deals to competitor X over 3 quarters. What's the strategic response?"Competitive battle cards or per-deal positioning (AGT-403 owns)
"Is our NRR trajectory durable, or held up by 5 accounts?"Computing NRR (AGT-702 owns)
Drafting strategic-recommendation memos with 2–4 viable options + tradeoffs + risk surfaceMaking the strategic call (executive decision; AGT-903 informs, never decides)
The hard line. AGT-903 never recomputes a Tier 1 number, and never proposes a direct edit to a canonical config — not the ICP rubric, not segment definitions, not quota models, not capacity plans, not pricing. It produces option-shaped recommendations that, if accepted, kick off a human-led planning workstream that goes through the relevant Tier 1 service's normal redesign cycle. The brain is a synthesis layer; strategic decisions remain with humans and remain subject to fiduciary deterministic processes.
How AGT-903 differs from AGT-901 and AGT-902
DimensionAGT-901 Pipeline BrainAGT-902 Account BrainAGT-903 Strategy Brain
Time horizonCurrent quarter / current periodCurrent state of one accountTrailing 4–12 quarters + forward 2–6 quarters
ScopeCross-account, segment / periodPer-account synthesisPortfolio / segment / vertical / motion
StakeholderRevOps, sales leadersAM, CSM, AE, RevOpsCRO, CFO, CEO, board prep
Decision impactPlays, cadences, coverage allocationPer-account next movesICP, segment definitions, quota model inputs, capacity bets, pricing, vertical entry
Output shapeDiagnosis + 1–3 candidate playsSynthesis + 1–3 proposed actions to existing leversStrategic memo: 2–4 options, tradeoffs, risk surface, assumptions-that-must-hold
Default modelSonnetSonnetOpus — multi-quarter cohort reasoning is the deep-analysis case
Invocation cadenceAd-hoc + WBR/MBR narrative + quarterly play refreshAd-hoc + AGT-603 QBR narrative + hand-off eventsAnnual planning, mid-year inflection, board prep — rare and heavy
A query that lands in the wrong brain produces low-quality output. The intake layer (operator interface) routes by horizon: current-period operational → AGT-901; named-account → AGT-902; multi-quarter or portfolio-bet → AGT-903. When ambiguous, AGT-903 may decline and route the operator to AGT-901 (or vice versa).
Read contract — Tier 1 services consumed (multi-quarter scoped)

AGT-903 reads strategy-scoped brain-ready view extensions: the same Tier 1 tables AGT-901 reads, but with longer time windows and cohort projections precomputed. The view extensions are owned by the underlying Tier 1 service. AGT-903 never extends the time window itself by re-aggregating raw rows — the view extension is the deterministic surface.

Tier 1 serviceStrategy brain-ready viewUsed for
AGT-702 GTM Health MonitorMetricsCalc.strategy_brain_view — Magic Number, NRR, GRR, R40, CAC Payback by segment / vertical / cohort across trailing 8–12 quartersLong-horizon trajectory diagnosis: durable trend or recent compression?
AGT-703 Win-Loss & Forecast AccuracyWinLossLog.strategy_brain_view — loss-reason evolution + competitive mention frequency + forecast-bias evolution by segment, trailing 8 quartersStrategic loss-pattern detection (multi-quarter, not week-over-week)
AGT-501 Customer Health MonitorCustomerHealthLog.cohort_brain_view — cohort retention curves by signup quarter / segment / vertical / ICP tierCohort-level retention bet evaluation: do customers we're winning today retain better or worse than 2 years ago?
AGT-201 ICP ScorerAccounts.icp_outcome_brain_view — correlation of 6-dimension ICP score to realized LTV / NRR / churn / win-rate, by cohort"Is the ICP rubric still predicting outcomes?" diagnosis
AGT-205 TAM/SAM SizingMarketAssumptions.strategy_brain_view — TAM / SAM / SOM by product family + vertical + segment, with current penetrationVertical or segment entry sizing — sized by AGT-205 hybrid methodology, not by AGT-903 estimation
AGT-604 Voice of CustomerVoCSynthesisLog.strategy_brain_view — trailing 8-quarter theme evolution + competitive theme evolutionStrategic shift in customer narrative
AGT-105 Sales Capacity PlanningCapacityPlan.strategy_brain_view — deployed eRep + ramp + utilization trajectory by segment, trailing 8 quartersCapacity-bet retrospective + reallocation modeling
AGT-101 Quota SettingQuotaPlanLog.strategy_brain_view — quota attainment distribution + bias by segment, trailing 8 quartersQuota-model strategic alignment (over/under-set by segment)
AGT-503 Expansion TriggerExpansionLog.strategy_brain_view — expansion realization rate + cohort upsell trajectory by segmentLand-and-expand bet retrospective
AGT-404 Top-Down ForecastTopDownForecast.strategy_brain_view — top-down vs bottoms-up reconciliation across trailing 4–8 quarters + segment-level decompositionMulti-quarter forecast bias and structural gaps
Strategy brain-ready view extensions are a new contract obligation on the listed Tier 1 services. They differ from AGT-901's brain-ready views by (a) longer time windows, (b) cohort axis where applicable, and (c) outcome-correlation projections (e.g., ICP score × realized LTV). View definition lives with the owning Tier 1 service; refresh cadence is at most quarterly. Where a strategy view does not yet exist, AGT-903 declines the query and surfaces the gap rather than estimating from raw rows.
Write contract — what AGT-903 may write
TargetWhat's writtenCanonical?
BrainAnalysisLogEvery query: question, scope, sources read with timestamps, narrative, proposed strategic actions, confidence flags, model used, token costNo — brain's own log, shared schema with AGT-901 / AGT-902
StrategyRecommendationLog (status: draft) — new table, schema doc separateStrategic recommendation memos: question, options enumerated (typically 2–4), per-option tradeoffs and risk surface, assumptions-that-must-hold, source-trace lineage, suggested human-led workstream ownersNo — drafts only. Promotion to under_review is a CRO pickup; promotion to endorsed kicks off a human-led planning workstream.
Annual planning narrative sectionsPer AGT-704 charter extension: AGT-903 may draft strategic narrative sections of the annual planning document (segment outlook, ICP review, competitive posture). Metric sections remain off-limits.No — written into BusinessReviewLog narrative fields, not metric fields.
What AGT-903 may NEVER write
SalesPlayLibraryAnything — play drafting belongs to AGT-901 / AGT-902. Strategic recommendations may suggest plays as a downstream consequence; AGT-901 actually drafts them after the strategic recommendation is endorsed.n/a
ICPRubric / SegmentDefinitions / QuotaPlans / CapacityPlan / PricingCatalogAnything — canonical configuration is Tier 1 only and changes go through the owning service's normal redesign cyclen/a
MetricsCalc / WinLossLog / ForecastAccuracyLogAnything — metric and pattern computation is Tier 1 onlyn/a
MarketAssumptions (AGT-205 owns)Anything — TAM/SAM input assumptions are governed by AGT-205's analyst-input processn/a
Promotion gate — from draft strategic recommendation to endorsed

Strategic recommendations have a higher human gate than play drafts. Endorsement does not change canonical state — it kicks off a human-led planning workstream that may, in turn, propose changes through the relevant Tier 1 service's normal redesign cycle.

StateWho can transitionWhat's required
draftAGT-903 (write)Brain produces a strategic memo with 2–4 options; lands in StrategyRecommendationLog for executive review
under_reviewCRO (manual pickup)CRO selects a draft to refine. May edit the option set, request additional analysis, narrow scope.
endorsedCRO + CFO + (CEO if scope warrants) joint approvalEndorsement triggers a planning workstream owned by the relevant Tier 1 service(s). For ICP changes → AGT-201 redesign cycle. For capacity reallocation → AGT-105 redesign. For quota model → AGT-101. For vertical entry → cross-functional motion-build. Endorsement does not directly modify any canonical table.
shelvedCRORecommendation set aside — not endorsed, not retired. Retained for historical retrospective.
retiredRevOpsRecommendation no longer relevant. Outcomes (if endorsed and acted on) recorded for retrospective.
Volume cap is enforced at endorsement. AGT-903 may produce many drafts — the human cost is in CRO pickup time, not in brain output. Endorsement is rare by design: a healthy cadence is 2–5 endorsed strategic recommendations per year, not per quarter. Strategy churn is a known anti-pattern; the brain produces options, not constant pivots.
Use case patterns
PatternTriggerSources readOutput
ICP fit retrospectiveCRO query: "Are our highest-LTV customers actually matching our ICP rubric?"AGT-201 icp_outcome_brain_view, AGT-501 cohort_brain_view, AGT-702 strategy_brain_viewStrategyRecommendationLog memo: ICP rubric correlation analysis + 2–4 options (keep, reweight dimensions, add a dimension, narrow ICP) + tradeoffs and assumptions
Vertical entry assessmentCRO/CFO query: "Should we invest in [vertical]?"AGT-205 strategy_brain_view (TAM/SAM), AGT-703 strategy_brain_view (win-rate in vertical), AGT-501 cohort_brain_view (vertical retention if any), AGT-604 strategy_brain_view (VoC themes), Tier 3 cohort/sizing tools where applicableMemo: vertical sizing + opportunistic-deals retrospective + 2–4 entry options (deprioritize, opportunistic continued, lightweight focus, full GTM motion build) + capacity implications
Strategic-bet retrospectiveCRO query: "Did the [Q1 last year] [pivot / launch / segment-bet] work?"Cohort views since pivot date + win-loss evolution + capacity utilization trajectory + outcome metricsMemo: bet vs. counterfactual, what worked, what didn't, what next quarter should change
Capacity reallocation modelingCRO query: "If I add N reps next year, what's the highest-leverage deployment?"AGT-105 strategy_brain_view + AGT-101 strategy_brain_view + AGT-205 TAM coverage + AGT-501 cohort_brain_view by segmentMemo: 2–4 deployment scenarios with projected attainment ranges + ramp risk + downside scenarios. Hard refusal to produce a single "best" answer.
Pricing/packaging strategic reviewCRO/CFO query: "Are we leaving money on either end of pricing?"UsageMeteringLog cohort distribution + win-rate by deal size + competitive loss-reason evolution + VoC pricing themesMemo: distribution analysis + 2–4 packaging options + revenue-impact ranges (with explicit assumption surface, not point estimates)
Strategic loss-pattern diagnosisCRO query: "We're losing more to [competitor] over 3 quarters. Strategic response?"AGT-703 strategy_brain_view (multi-quarter competitive evolution) + AGT-604 strategy_brain_view + AGT-403 competitive intelligenceMemo: pattern characterization + 2–4 strategic responses (product gap, positioning, packaging, segment-narrowing) + assumption surface
Annual planning narrativeAGT-704 invokes for annual planning narrative sections (segment outlook, ICP review, competitive posture)Strategy brain-ready views across services + prior-year endorsed StrategyRecommendationLog entriesNarrative content written to BusinessReviewLog narrative fields per AGT-704 charter extension
NRR durability assessmentCRO/CFO query: "Is our NRR durable, or held up by a few accounts?"AGT-501 cohort_brain_view + AGT-503 strategy_brain_view + concentration analysis from MetricsCalc.strategy_brain_viewMemo: concentration/durability decomposition + scenario range + 2–4 options to broaden expansion base
Every use case produces an options-shaped output, not a single recommendation. If the brain finds itself with one obvious answer, it is required to articulate at least one credible alternative and the conditions under which the alternative would be correct — the discipline is to widen the executive's frame, not narrow it.
Output structure — per-query StrategyRecommendationLog row + BrainAnalysisLog row

Every AGT-903 query produces both a BrainAnalysisLog row (shared schema with AGT-901 / AGT-902) and a StrategyRecommendationLog row (new schema, dedicated to strategic memos). See the StrategyRecommendationLog schema doc for field-level detail.

  1. Question — the executive query verbatim, or the AGT-704 narrative-job prompt.
  2. Scope tags — structured: which segments / verticals / time windows the analysis covers.
  3. Sources read — structured list of (table_name, view_name, last_refresh_timestamp, row_count_consumed). Every numerical claim ties back.
  4. Options enumerated — 2–4 options. Each option carries: hypothesis, rough projected impact range (not a point estimate), required investment, capacity implications, dependencies on other Tier 1 services.
  5. Tradeoffs matrix — per option: upside scenario, downside scenario, what has to be true for the option to work.
  6. Risk surface — structured enumeration: market risks, execution risks, capacity risks, model-assumption risks. Each risk carries a confidence flag.
  7. Assumptions-that-must-hold — the falsifiable assumptions underlying the analysis. If any assumption is brittle or based on stale data, surfaced explicitly.
  8. Confidence flags — per claim: high_confidence, multi_source, inference, speculation. AGT-903 is expected to use speculation more often than AGT-901 / AGT-902; multi-quarter strategic reasoning involves more legitimate uncertainty.
  9. Source freshness gate — if any strategy brain-ready view was stale, output flagged data_staleness_acknowledged and the staleness surfaced. Per AGT-704 staleness model.
  10. Suggested human-led workstream owners — if endorsed, which Tier 1 services or cross-functional groups own the resulting workstream.
  11. Cost metadata — (model, input_tokens, output_tokens, cached_tokens, cost_usd_estimate).
Proposed-action taxonomy

AGT-903's proposed actions are strategic-recommendation shaped, not play-shaped. Every action maps to a downstream human-led workstream, never to a direct table edit.

Proposed actionMaps to downstream workstreamApproval gate
propose_icp_revisionAGT-201 ICP rubric redesign cycleCRO + RevOps endorse; AGT-201 spec change is the canonical change
propose_segment_redefinitionAGT-201 segment-band redesign + AGT-202 routing alignment + AGT-101 quota alignmentCRO + RevOps + Finance endorse; cross-service spec change
propose_vertical_entryCross-functional motion-build: AGT-203 ABM target selection, AGT-205 sizing refresh, AGT-302 cadence orchestration, AGT-403 competitive prep, AGT-105 capacityCRO + CFO + (CEO if material) endorse; motion plan owned by RevOps
propose_capacity_reallocationAGT-105 capacity plan redesign + AGT-106 territory redesign + AGT-101 quota redesignCRO + Finance endorse; AGT-105 owns the plan change
propose_pricing_packaging_reviewCross-functional pricing committee — AGT-406 CPQ catalog change + AGT-802 billing alignment + AGT-101 quota model alignmentCRO + CFO + Product endorse; pricing committee owns
flag_strategic_riskn/a — the brain is naming a risk for executive attention without proposing actionNone — informational
recommend_market_research_queryn/a — the question cannot be answered from internal data; brain is recommending external researchNone — informational; may trigger external research engagement
recommend_human_queryn/a — the brain is saying "this is a judgment call, here's the framing"Human picks it up or doesn't
nonen/a — the brain found nothing strategically actionable; output is informationaln/a
No proposed action ever bypasses an existing approval gate. AGT-903 cannot directly modify ICP, segments, quotas, capacity, territories, or pricing — it can only propose redesigns through the owning Tier 1 service's normal cycle.
Cost guardrails

AGT-903 is rare-but-heavy — few queries per month, large input context, deep analysis. Sizing is unlike AGT-901 / AGT-902.

TacticImplementation
Default modelClaude Opus tier — multi-quarter cohort reasoning is the deep-analysis case where Opus IS the default, not the opt-in. Sonnet is only used for cheap retrospective lookups inside a session (e.g., "list the prior strategic recommendations on this segment").
Strategy brain-ready views, not full historical tablesCohort and trajectory projections precomputed by Tier 1 services. Without this contract, multi-quarter input would be prohibitive.
Prompt caching5-minute TTL cache on system prompt + strategy view bundle. Iterative follow-up questions in the same session pay the diff only.
Per-query budget capHard limit: 200K input + 20K output tokens per query. Queries exceeding the limit return a budget-exceeded result. Larger context window than AGT-901 / AGT-902 reflects the multi-quarter scope.
Monthly tier budget alertAlert at 75% of monthly budget (CRO-configurable, default $300/month for Strategy Brain). Hard stop at 100% requires manual override. Lower volume than 901/902 but higher per-query cost.
Sizing ballpark10–30 queries/month at 150K input + 10K output, Opus pricing. Annual planning weeks may concentrate usage; monthly average smooths out.
Refusal as cost controlIf a strategy brain-ready view is missing or stale, refusal is cheaper than estimation and is the correct answer. Refusal cost ≈ one tool-call's tokens, not a full analysis.
Eval criteria

Strategic recommendations have a longer feedback loop than play drafts — outcomes may take 2–6 quarters to validate. Eval design balances near-term proxies (option completeness, risk-surface coverage) with longer-horizon retrospective accuracy.

CriterionMeasurementPass threshold
Source citation rate% of numerical claims with valid source citation pointing to a real strategy brain-ready view row≥ 95%
Hallucination rate% of outputs containing claims not supported by cited sources≤ 2%
Staleness recognitionWhen a strategy view is stale, % of outputs that surface staleness vs. silently using stale data100% — hard requirement
Option completeness% of outputs that produce 2–4 viable options with distinct hypotheses (not minor variants of one option)≥ 90%
Risk-surface coverage% of outputs that enumerate market risk, execution risk, capacity risk, and model-assumption risk explicitly≥ 90%
Assumption-surface honesty% of outputs that explicitly list falsifiable assumptions underlying the analysis≥ 90%
Refusal correctnessFor queries where required strategy view is missing or stale: % of outputs that refuse and surface the gap vs. estimating100% — hard requirement
Retrospective accuracyFor past strategic recommendations where outcome is now known (4–6 quarters later): % where the brain's top option matched the path that produced best outcome≥ 50% — deliberately lower than 901/902 because strategic uncertainty is higher
Endorsement rate (calibration)% of drafts that reach endorsed state10–30% target band — too high suggests brain is reading leadership preference; too low suggests options are not credible
Decision-quality liftCohort comparison: outcomes following endorsed AGT-903 recommendations vs. comparable historical decisions made without the brainTrack annually; positive lift expected by Y+2 after launch
Failure modes
SymptomLikely causeAction
Brain produces a single "right answer" instead of optionsOver-confident synthesis; system prompt not enforcing options disciplineHard fail. Eval enforces option-count ≥ 2. Tune system prompt to require articulating credible alternatives.
Brain estimates a Tier 1 metric instead of refusing on stale viewRefusal discipline broken; strategy view assumed availableHard fail. Sev-2 incident treatment. Source-trace integrity is non-negotiable, same posture as AGT-901 / AGT-902.
Brain proposes an action that maps to direct edit of a canonical tableAction taxonomy violationHard fail. Eval enforces action enum + downstream-workstream mapping. Brain may never propose direct table edits.
Endorsement rate trending toward 0% over multiple quartersOptions not credible to executive review — brain is missing context the CRO has, or anchoring on stale strategic priorsQuarterly retrospective working session: refine system prompt, add few-shot examples from prior endorsed recommendations.
Endorsement rate > 50%Brain is reading leadership preference — producing options the CRO already wanted to hearTighten eval suite. Add adversarial fixtures where the strategically correct answer is one the operator did NOT prefer at intake.
Cost spikingLikely cause: queries that should have routed to AGT-901 (current-period operational) running on Opus context unnecessarily, or full historical tables read instead of strategy viewsAudit recent BrainAnalysisLog rows. Enforce strategy view requirement. Tighten intake-routing logic to short-circuit operational queries to AGT-901.
Strategy view missing for a Tier 1 service AGT-903 needsTier 1 service has not yet shipped the strategy_brain_view extensionAGT-903 declines + flags the gap to RevOps + the owning service. Not a brain failure — a contract gap. Track in upstream service backlog.
Invocation paths
PathFrequencyInitiated by
Executive query (chat-style interface)Ad-hoc, rare — concentrated around planning periodsCRO, CFO, CEO, RevOps strategic leads
Annual planning narrative jobOnce annually + mid-year refresh; AGT-704 calls AGT-903 for strategic narrative sections onlyAGT-704
Board prep batchPer board cycle (typically quarterly), initiated by CRO/CFOCRO or CFO (manual trigger)
Strategic-bet retrospective batchAnnual or per-major-pivot retrospectiveRevOps (manual trigger)
No cadence-driven invocation, ever. Strategy Brain runs only when explicitly invoked by an executive or by AGT-704 for a planning narrative job. This is the strongest invocation discipline of the three brains — reflects that strategic churn is a known anti-pattern and brain availability should not lower the cost of strategic second-guessing.
Dependencies and likely Tier 3 tool needs

AGT-903 cannot ship usefully until two contracts are in place: (a) strategy brain-ready view extensions on the Tier 1 services listed in the read contract, and (b) at least a minimal set of cohort/trajectory Tier 3 tools.

DependencyOwnerStatus
Strategy brain-ready view extensions on AGT-201, AGT-205, AGT-501, AGT-503, AGT-702, AGT-703, AGT-105, AGT-101, AGT-404, AGT-604Each owning Tier 1 serviceNew contract obligation as of v37 spec
StrategyRecommendationLog schema (separate doc)Schema team, parallels SalesPlayLibraryTo be drafted
Tier 3 cohort retention forecaster (e.g., TOOL-013)Tools team, analogous to TOOL-004 Consumption ForecastingLikely needed; not yet specced
Tier 3 segment-LTV decomposer (e.g., TOOL-014)Tools teamLikely needed for capacity-reallocation and ICP-revision use cases; not yet specced
AGT-704 charter extension to delegate annual planning narrative sections to AGT-903AGT-704Mirrors v26 charter pattern that delegated MBR/QBR narrative to AGT-901 / AGT-902; new addition for v37
Spec-first, build-later. AGT-903 is specced now to anchor the strategy brain-ready view contract obligations on Tier 1 services. Build follows once a critical mass of strategy views ships and at least one Tier 3 cohort tool exists.