AlphaStack
Score AI maturity against the actual service blueprint. Two stages: evaluate the gap, then close it.
This is the AlphaStack methodology pack: what the SKU is, how the rubric works, and what Stage 1 intake produces. Not a live assessment.
AlphaStack is a productised AI-stack maturity assessment with two stages. Stage 1 (Evaluate) scores AI maturity against the subject's actual service blueprint and produces a band rating (AAA–CCC), a 10-axis scorecard, and an opportunity matrix. Stage 2 (Enable) builds workflow products that directly address the highest-leverage gaps Stage 1 identifies. A downstream re-score closes the loop with a quantified uplift.
The scoring mechanic is inherited verbatim from AlphaRating v1.3: 10 axes, 0–1,000 scale, two weight profiles (GP-PE and GP-VC), AAA–CCC band breakpoints, Signal + Score + Gap output per axis, atom-backed evidence. What changes is the subject matter: AlphaStack axes score AI-stack maturity as it operates against the actual service delivery blueprint, not company health broadly.
Primary buyer: VC/PE GPs commissioning assessments of portfolio companies for pre-investment AI diligence, value-creation review, or M&A target evaluation. The external sales partner (identity TBD) owns Phase 0 (C-suite education). AlphaStack scope begins at Phase 1 (Evaluate) and Phase 2 (Enable).
This pack is an internal strawman awaiting Ant review. Rubric axes are candidates, not calibrated against a live engagement. The scoring mechanic is correctly inherited; axis definitions require first-engagement validation before external use.
Five things that are true about AlphaStack that are not true of commodity AI assessment tools.
For each step in how the subject delivers value, AlphaStack asks whether AI is deployed and how effectively. The output maps AI gaps to real workflow steps, which means the opportunity matrix is directly actionable rather than a generic recommendation list. No commodity tool does this.
The opportunity matrix is the build brief. Workflow products in Stage 2 directly address the Priority 1–2 gaps identified by the scorecard. The re-score at 3–6 months closes the commercial loop with a quantified uplift number, not a consulting summary. GP gets a before-and-after with a score delta.
Every score traces to evidence atoms from the intake corpus. Inferred claims are explicitly flagged as INFERENCE with a confidence score below 0.7. The Signal + Score + Gap format per axis provides a structured output that can be cited, not a narrative summary that cannot.
Most assessment tools measure current state. AlphaStack Axis 10 measures the forward-looking ROI of closing identified gaps: a company with 30% AI coverage of highly addressable workflows scores higher on Axis 10 than one with 90% coverage and few remaining high-leverage gaps. This is the direct feed for Stage 2 scoping and pricing.
The intake is one structured Zoom (60–90 min), a pre-session questionnaire, and targeted document uploads. No system installs, no 6-week engagement, no client-side burden beyond the session and uploads. The lean mandate is locked and enforced: if Stage 1 expands, it surfaces to Ant immediately.
"AlphaStack scores AI maturity against the actual service blueprint, not an abstract capability checklist. The output is an opportunity matrix grounded in real workflows."
10 axes. Two weight profiles. Seven bands.
The scoring mechanic is inherited verbatim from AlphaRating v1.3. What changes is the subject matter: AI-stack maturity, grounded in the service blueprint.
| # | Axis | What it measures | Wedge |
|---|---|---|---|
| 01 | AI-Workflow Integration | AI coverage and depth across each step of the service delivery blueprint. The primary differentiator axis. | Wedge |
| 02 | Data Infrastructure & Moat | Data quality, labeling discipline, governance, and proprietary training advantage over competitors. | Wedge |
| 03 | AI Stack Architecture | Model layer choices, build vs. buy strategy, infrastructure maturity, vendor lock-in risk. | |
| 04 | Team AI Fluency | Adoption breadth and depth across the organisation; AI ownership structure; upskilling maturity. | |
| 05 | AI Velocity | Iteration speed, experimentation cadence, time from identified opportunity to live deployment. | |
| 06 | AI Governance & Risk | Hallucination controls, data privacy posture, IP risk, regulatory exposure (AI Act, sector rules). | |
| 07 | Commercial AI Leverage | Measurable business impact: cost reduction, revenue enablement, quality improvement, throughput. | Wedge |
| 08 | AI Strategy Coherence | Coherent AI roadmap vs. opportunistic adoption; vision-to-execution gap. | |
| 09 | AI Durability | Structural defensibility of AI advantage against commoditisation and AI-native entrants. | |
| 10 | AI Opportunity Density | Forward-looking: how much unlocked AI value sits in identified workflow gaps, relative to capture effort. Stage 2 feed. | Wedge |
Definitions, scoring logic, and what good vs. weak evidence looks like per axis. All 10 axes shown. Status: strawman, awaiting first-engagement calibration.
The primary differentiator axis. For each step in the subject's service delivery blueprint, is AI deployed and how effectively? Scores breadth (what percentage of workflow steps have AI embedded), depth (peripheral/experimental vs. optimised/measured), and evidence of actual productivity or quality impact. Level 0 = no AI. Level 4 = AI is the delivery mechanism for that step.
Self-reported claims discounted; verifiable artefacts (toolchain inventory, workflow docs, sample outputs) weighted up. Stage 1 lean: infer from interview + uploads.
Data quality, labeling discipline, governance maturity, and availability for model training or retrieval. A strong data moat = historical, proprietary, clean data that creates an AI training advantage competitors cannot replicate. Gaps weighted by how AI-addressable the workflows are: a data-poor company in a high-AI-leverage workflow is a structural risk.
Model layer choices (frontier API vs. fine-tuned vs. local), build vs. buy strategy, infrastructure maturity (observability, CI/CD for model updates, evaluation rigor, cost controls). Vendor lock-in risk. Is the architecture aligned with the subject's workflow requirements (latency, privacy, scale) or generic/accidental?
For lean Stage 1: inferred from toolchain list and workflow description. Flag as low-confidence if not verifiable from uploads.
Who uses AI tools, how deeply, and at what levels of the organisation. Adoption breadth (across functions) and depth (beyond chat interfaces into embedded workflows). AI ownership and accountability structure. Upskilling and onboarding maturity. C-suite AI literacy signals. Score reflects the gap between AI capability available and AI capability actually absorbed.
How fast is the subject iterating on AI deployments? Learning cycles, experimentation cadence, time from identified opportunity to live deployment. Evaluation discipline: are they measuring whether AI is working? Leading indicator: a named process for trialling and retiring AI tools vs. ad hoc adoption.
For lean Stage 1: inferred from team description and workflow documentation. Flag as low-confidence if not verifiable.
AI-specific risk management: hallucination controls and output validation processes, data privacy posture (PII in prompts, vendor data-handling terms), IP and confidentiality risk, regulatory exposure (EU AI Act, sector-specific rules). Vendor concentration risk. Score reflects maturity of the governance layer: policies exist vs. policies are enforced vs. policies are tested.
Is AI measurably moving business metrics: cost reduction, revenue enablement, quality improvement, throughput increase? Evidence: unit economics (cost-per-task AI vs. human), documented time savings, customer-facing AI features with adoption data. Scores based on verifiable commercial impact. Zero-impact deployments (AI running but not moving a metric) score below baseline.
Stage 1 lean: inferred from workflow description and any metrics shared. Flag as low-confidence if purely self-reported with no documentation.
Is there a coherent AI roadmap grounded in the service blueprint, or is AI adoption opportunistic and uncoordinated? Vision-to-execution gap: stated AI ambitions vs. observable evidence of progress toward them. C-suite alignment vs. ground-truth reality. Score discounts visions not supported by verifiable execution signals, same mechanic as AlphaRating v1.3 Vision & Feasibility axis.
Will the subject's AI advantage survive the next wave of AI commoditisation? Data moat quality, proprietary model investments, workflow lock-in from AI integration, defensibility against AI-native entrants. Model-layer independence vs. fragile dependency on a single vendor's capability cliff. Score reflects structural defensibility, not current capability.
The forward-looking axis. How much unlocked AI value sits in identified workflow gaps, relative to the effort to capture it? A company with 30% AI coverage of highly AI-addressable workflows scores high (dense opportunity). A company with 90% coverage and few remaining high-ROI gaps scores lower. Directly feeds the Opportunity Matrix and Stage 2 scoping.
This is the only forward-looking axis. Validity requires calibration across live engagements: confirm Axis 10 can be scored consistently without becoming subjective.
One Zoom. Two weeks. A scored pack.
The lean mandate is locked. Stage 1 is not a 6-week engagement. If it expands beyond the parameters below, it surfaces to the orchestrator immediately.
- Process or workflow documentation
- Toolchain inventory (AI tools in use, where, by whom)
- Team structure and AI ownership
- Sample workflow artefacts (optional, highest value if available)
- AlphaStack band: AAA–CCC
- 10-axis scorecard: Signal + Score + Gap per axis
- Per-axis colour: Blue / Green / Amber / Red
- Opportunity matrix: gaps ranked by uplift ROI
- Delivery: password-gated pack subdomain
Decisions required before any external use.
The following variables are open. None of these are resolved by this pack. AlphaStack cannot be presented to a partner or prospect until these are Ant-reviewed and confirmed.
| Variable | Status | Notes |
|---|---|---|
| Final SKU name | TBD | Working name "AlphaStack" not locked. Ant decides. |
| Subdomain slug | TBD | Do not auto-pick. Awaiting Ant. |
| Brand house | Deferred | Alpha Suite is working housing. Alpha Suite vs. FullyBaked decision deferred until post-v0 one-pager. |
| Pricing model | TBD | Not defined. Ant + partner decision. |
| External partner identity | TBD | Not disclosed. Partner owns Phase 0 (C-suite education). |
| Weight profile selection logic | TBD | GP-PE vs. GP-VC decision at kickoff. Third profile possible based on partner buyer context. |
| Stage 1 timeline (2-week estimate) | Strawman | Confirm with Ant before first engagement. |
| Axis 10 validity | Unvalidated | Forward-looking axis. Confirm it can be scored consistently without becoming subjective across live engagements. |
| Intake fallback (no service blueprint) | Undefined | What happens when the subject has no documented service blueprint? Define the intake fallback before first engagement. |