Why this dispatch exists
This is the twenty-sixth Phase 3 dispatch and the opener for Phase 4. The Phase 3 corpus closed with the cross-archetype matrix refresh at twenty-five dispatches covering eight operator archetypes, fourteen per-pillar deep-dives, vendor refresh maintenance, and the cross-archetype synthesis. The corpus reached comprehensive coverage of the broker tech procurement landscape at synthesis level: operators can read the relevant archetype dispatch plus relevant per-pillar dispatches plus the cross-archetype matrix and understand the procurement landscape they face.
What the Phase 3 corpus did not provide was operationally-actionable artefacts that operators can use directly when running vendor procurement processes. Reading the archetype dispatches helps an operator understand what their procurement context looks like; it does not help the operator score a specific vendor’s RFP response against a specific procurement decision. Reading the per-pillar deep-dives helps an operator understand the vendor landscape within a pillar; it does not produce a procurement-stage RFP framework that the operator can adapt for their specific procurement process.
Phase 4 pivots from synthesis dispatches to operationally-actionable artefacts. This dispatch establishes the foundation: a vendor RFP scoring framework with universal scoring dimensions, per-pillar weighted criteria, per-archetype customisation layer, and explicit guidance on how operators apply the framework at RFP stage. Future Phase 4 artefacts will extend the framework with per-pillar evaluation toolkits, per-archetype RFP templates, and operationally-actionable artefacts that operators can use directly in their procurement processes.
The RFP scoring framework structure
The framework has three layers:
Layer 1: Universal scoring dimensions. Five dimensions that apply to every vendor procurement regardless of pillar or archetype. Operators score every vendor on these dimensions during the RFP evaluation.
Layer 2: Per-pillar weighted dimensions. Three to seven dimensions per pillar that operators score in addition to the universal dimensions. The dimensions vary by pillar; the weights vary by pillar.
Layer 3: Per-archetype customisation. Weight modifiers that operators apply on top of the universal plus per-pillar scoring based on the operator’s specific archetype. The customisation reflects archetype-specific procurement priorities that the per-archetype dispatches surfaced.
Each dimension is scored on a 1-5 scale against the vendor’s RFP response plus product demo plus reference customer evidence. Universal dimensions carry equal weight (5 dimensions x 20% = 100% weighted total at Layer 1). Per-pillar dimensions extend the total with per-dimension weights summing to 100% within the per-pillar layer. The per-archetype customisation applies multipliers (1.0x to 2.0x) to specific dimensions reflecting archetype-specific priorities.
Vendor ranking is the weighted total across all dimensions. Disqualification thresholds apply at the dimension level rather than the total level: a vendor scoring below 2 on any critical dimension is automatically disqualified regardless of total score because critical dimension failures cannot be compensated by strength elsewhere.
The five universal scoring dimensions
The universal dimensions apply to every vendor procurement regardless of pillar or archetype:
Dimension U1: Pricing transparency. How clearly does the vendor disclose pricing structure including base pricing, per-unit pricing, optional modules, integration costs, and ongoing support costs? Score 5 = published pricing with concrete numerical disclosure (rare in the corpus; Spotware Store pricing covered in the trading platform deep dive is the benchmark). Score 4 = quote-based but with concrete pricing ranges in the RFP response. Score 3 = quote-based with general pricing structure description. Score 2 = quote-based with no pricing disclosure pre-contract. Score 1 = pricing structure varies by client with no disclosure.
Dimension U2: Regulatory positioning and certifications. Does the vendor hold the certifications and regulatory positions relevant to the operator’s procurement context? Score 5 = ISO 27001 plus SOC 2 Type II plus relevant jurisdiction-specific certifications plus active regulator engagement disclosed. Score 4 = ISO 27001 plus SOC 2 Type II plus jurisdiction-specific certifications. Score 3 = ISO 27001 plus jurisdiction-specific certifications. Score 2 = ISO 27001 only. Score 1 = no relevant certifications disclosed.
Dimension U3: Customer support quality. How does the vendor structure customer support including dedicated technical account management, SLA-backed support response times, and operator-side escalation paths? Score 5 = dedicated TAM plus 24/7 support plus operator-specific SLAs in contract. Score 4 = dedicated TAM plus business-hours support plus general SLAs. Score 3 = shared account management plus business-hours support. Score 2 = shared account management plus standard ticketing support. Score 1 = standard ticketing support only.
Dimension U4: Vendor financial stability. Does the vendor demonstrate sustainable financial position through public-company disclosure, sustained customer base, or recent capital position? Score 5 = public-company filings disclosed (Equinix NASDAQ, Beeks LSE AIM, S&P Global parent for Cappitech, BGC Group parent for Lucera). Score 4 = private with sustained 5+ year operating history and stable customer base. Score 3 = private with recent capital position and growing customer base. Score 2 = private with limited public financial information. Score 1 = recent vendor with unclear financial position.
Dimension U5: Product roadmap visibility. How transparently does the vendor disclose product roadmap and forward investment trajectory? Score 5 = public quarterly roadmap with operator-specific advisory input on roadmap priorities. Score 4 = annual roadmap shared with customers plus quarterly update calls. Score 3 = roadmap shared on request plus periodic update calls. Score 2 = roadmap not shared but reactive feature delivery. Score 1 = no roadmap visibility.
The five universal dimensions produce a baseline vendor score that operators can compare across any vendors in any pillar. Vendor scoring below 3 average on the universal dimensions is procurement-disqualifying for most procurement contexts; the operator should evaluate whether the per-pillar strength compensates for universal weakness or whether the vendor procurement should be deprioritised.
Per-pillar weighted dimensions
Per-pillar dimensions extend the universal scoring with pillar-specific evaluation criteria. The dimensions and weights for each Phase 2 chapter:
Chapter XIV - Brokerage hosting (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| H1: Per-jurisdiction data residency support | 25% | Yes |
| H2: IBX presence at procurement-relevant locations | 25% | Yes |
| H3: Latency-to-LP testable against operator’s specific LP infrastructure | 20% | No |
| H4: Disaster recovery + business continuity SLAs | 15% | Yes |
| H5: Multi-IBX connectivity costs and provisioning timelines | 15% | No |
Critical dimensions are H1, H2, H4. Vendor scoring below 2 on any critical dimension is procurement-disqualifying.
Chapter II - Alternative white-label platforms (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| P1: Per-jurisdiction leverage cap configurability | 20% | Yes |
| P2: Multi-asset depth across operator’s product set | 20% | Yes |
| P3: Customisation envelope (branding + UX + workflow) | 20% | No |
| P4: CRM integration tightness (vs operator’s CRM procurement) | 15% | No |
| P5: Multi-language localisation depth | 15% | Conditional |
| P6: Native copy trading capability | 10% | No |
P5 is critical for operators with multi-language client geography. P1 and P2 are critical for all operators.
Chapter X - Crypto exchange white-label (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| CX1: MiCAR / VARA / FSRA Virtual Asset Framework alignment | 25% | Yes |
| CX2: Custody integration architecture (bundled vs delegated) | 20% | Yes |
| CX3: Travel Rule infrastructure integration | 15% | Conditional |
| CX4: Liquidity provider integration depth | 15% | No |
| CX5: Multi-asset support across listed tokens | 15% | No |
| CX6: Operator branding + customisation envelope | 10% | No |
CX3 is critical for archetypes with regulated Travel Rule obligations (CASP under MiCAR, EU dual-licensed, FSRA VAF if in scope). The Phase 2 chapter LIMITED verdicts (Match-Trade Crypto, ETNA Software) score below 2 on CX1 making them procurement-disqualifying.
Chapter VIII - Liquidity providers (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| LP1: Counterparty creditworthiness | 25% | Yes |
| LP2: Spread competitiveness at operator’s expected trade size | 20% | Yes |
| LP3: Last-look policy disclosure (FX-specific) | 15% | Conditional |
| LP4: Multi-asset depth | 15% | No |
| LP5: API quality + execution venue | 15% | No |
| LP6: Regulatory disclosure quality | 10% | No |
LP1 and LP2 are universally critical. LP3 is critical for FX-touching procurement; not relevant for crypto-only procurement.
Chapter IX - Risk management (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| R1: Pre-trade controls with per-regulatory-regime configurability | 25% | Yes |
| R2: Multi-LP exposure aggregation | 20% | Yes |
| R3: VaR methodology + operator calibration | 15% | No |
| R4: P&L attribution across execution paths | 15% | No |
| R5: Execution quality reporting (RTS 27 / equivalent) | 15% | Conditional |
| R6: Broker-ID-level segmentation (hybrid-specific) | 10% | Conditional |
R6 is critical for hybrid Archetype C. R5 is critical for archetypes with explicit best execution reporting obligations.
Chapter III - KYC + AML (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| KYC1: Document verification depth (per-jurisdiction document support) | 25% | Yes |
| KYC2: Biometric liveness check robustness | 20% | Yes |
| KYC3: Ongoing screening data set coverage | 15% | Yes |
| KYC4: Manual case management integration | 15% | No |
| KYC5: Travel Rule integration (CASP-specific) | 15% | Conditional |
| KYC6: KYB plus UBO verification depth (institutional-specific) | 10% | Conditional |
KYC1, KYC2, KYC3 are universally critical. KYC5 is critical for CASP-touching procurement. KYC6 is critical for institutional Archetype H.
Chapter XIII - RegTech and compliance reporting (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| RT1: Per-regulatory-framework rule library calibration | 25% | Yes |
| RT2: Comms surveillance channel coverage breadth | 20% | Yes |
| RT3: Transaction reporting accuracy + flexibility | 15% | Conditional |
| RT4: Chain analytics integration (crypto-touching) | 15% | Conditional |
| RT5: Multi-jurisdiction regulatory horizon scanning | 15% | No |
| RT6: Operator-side audit trail completeness | 10% | Yes |
RT3 is critical for archetypes with transaction reporting obligations (A, C, E, F, G, H with EU-passport client segments). RT4 is critical for crypto-touching archetypes.
Chapter IV - Broker CRMs (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| CRM1: Multi-tenant configuration capability | 25% | Conditional |
| CRM2: Platform integration tightness | 20% | Yes |
| CRM3: Multi-language client cabinet depth | 15% | Conditional |
| CRM4: Multi-currency wallet structure | 15% | Yes |
| CRM5: KYC handoff design quality | 15% | Yes |
| CRM6: CASP-specific extensions (wallet attribution, blockchain hash, asset config per jurisdiction) | 10% | Conditional |
CRM1 is critical for hybrid Archetype C and EU dual-licensed Archetype E. CRM3 is critical for APAC Archetype F, LATAM Archetype G. CRM6 is critical for crypto-touching archetypes.
Chapter VI - Payments (per-pillar)
Payment procurement scoring is necessarily operator-specific because PSPs underwrite per-merchant and the relevant procurement is operator-specific banking and rail relationships. The universal dimensions apply; per-pillar dimensions reduce to two:
| Dimension | Weight | Critical |
|---|---|---|
| PMT1: Per-jurisdiction rail coverage matching operator’s client geography | 60% | Yes |
| PMT2: Reconciliation flow integration with operator’s CRM and back-office | 40% | Yes |
Both dimensions are universally critical.
Chapter VII - IB management (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| IB1: Multi-tier attribution depth | 25% | Conditional |
| IB2: Commission structure flexibility (CPA + revshare + hybrid + MTV) | 20% | Yes |
| IB3: Four-stage hybrid attribution capability | 20% | Conditional |
| IB4: Per-jurisdiction tax disclosure handling | 15% | Conditional |
| IB5: IB material approval workflow | 10% | No |
| IB6: Client cabinet IB disclosure integration | 10% | No |
IB1 is critical for operators with multi-tier IB networks. IB3 is critical for hybrid Archetype C. IB4 is critical for LATAM Archetype G with Brazil-specific tax handling.
Chapter V - Turnkey suites (per-pillar)
Turnkey procurement scoring extends the per-pillar dimensions for the component pillars the turnkey suite bundles. Operators procuring turnkey should weight the lean-scale-tier-specific factors:
| Dimension | Weight | Critical |
|---|---|---|
| TK1: Component completeness across operator’s required scope | 25% | Yes |
| TK2: Integration tightness across bundled components | 20% | Yes |
| TK3: Customisation envelope at lean-scale-tier | 20% | Yes |
| TK4: Graduation friction (per the turnkey suite deep dive) | 20% | Yes |
| TK5: UAE-tested or jurisdiction-tested deployment evidence | 15% | Conditional |
Chapter XI - Broker analytics and market signals (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| AN1: Content quality + accuracy + update frequency | 25% | Yes |
| AN2: Per-language content depth | 20% | Conditional |
| AN3: Platform integration tightness | 20% | No |
| AN4: Per-seat pricing transparency | 15% | No |
| AN5: API and data feed integration | 10% | Conditional |
| AN6: CASP-specific analytics extension (Glassnode + Messari Pro + CoinGecko Terminal) | 10% | Conditional |
AN2 is critical for multi-language client geography operators. AN6 is critical for CASP-touching archetypes.
Chapter XII - Copy and social trading (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| CT1: Signal-provider vetting depth | 25% | Yes |
| CT2: MiFID II copy-as-portfolio-management positioning | 20% | Yes |
| CT3: Toxic-signal-provider clawback policy | 20% | Yes |
| CT4: Cross-broker network depth (independent network vs platform-native) | 15% | Conditional |
| CT5: Architectural fit (broker-stack-bundled / platform-native / plugin / independent) | 15% | Yes |
| CT6: Regulatory positioning of independent networks | 5% | Conditional |
CT1, CT2, CT3, and CT5 are universally critical. The Phase 2 LIMITED verdict for FXJunction reflects score-below-2 on CT6 because the Comoros registration disqualifies the vendor for regulated operator procurement.
Chapter I - Prop firm technology (per-pillar)
| Dimension | Weight | Critical |
|---|---|---|
| PF1: Challenge management infrastructure | 20% | Yes |
| PF2: Payout processing infrastructure | 20% | Yes |
| PF3: Simulated execution mechanics | 25% | Yes |
| PF4: Prop firm CRM distinct from broker CRM | 15% | Yes |
| PF5: Forward-compatible architecture for 2026-2028 regulation | 20% | Yes |
All dimensions critical for hybrid Archetype C prop firm vertical procurement.
Per-archetype customisation layer
The per-archetype customisation applies weight multipliers to specific dimensions reflecting archetype-specific priorities:
Archetype A (CySEC CFD broker). RT3 (transaction reporting) x 1.5; KYC3 (ongoing screening) x 1.5 reflecting August 2025 CySEC sanctions regime; H1 (data residency) x 1.3 for EU AMLR transition.
Archetype B (DMCC plus VARA UAE broker). P5 (multi-language) x 1.5 for Arabic plus Hindi; CX1 (MiCAR/VARA alignment) x 1.5 for VARA crypto venue; KYC1 (UAE Cabinet Resolution) x 1.3.
Archetype C (hybrid prop firm plus broker). IB3 (four-stage hybrid attribution) x 2.0; R6 (broker-ID segmentation) x 2.0; CRM1 (multi-tenant) x 1.5; PF1 through PF5 all x 1.5 for prop firm vertical.
Archetype D (CASP under MiCAR). CX1 (MiCAR alignment) x 2.0; CX2 (custody architecture) x 2.0; CX3 (Travel Rule) x 2.0; RT4 (chain analytics) x 1.5; KYC5 (Travel Rule integration) x 1.5.
Archetype E (EU dual-licensed CASP plus CFD broker). All Archetype A multipliers plus all Archetype D multipliers plus CRM1 (multi-tenant) x 1.5 for cross-vertical infrastructure sharing.
Archetype F (APAC CFD broker). R1 (leverage cap configurability) x 1.5 for per-jurisdiction caps; P5 (multi-language) x 1.5 for Mandarin/Cantonese/Japanese/Korean depth; KYC1 (per-APAC documents) x 1.5; PMT1 (APAC rail coverage) x 1.5.
Archetype G (LATAM CFD broker). P5 (Spanish + Portuguese distinct) x 1.5; PMT1 (Pix integration plus LATAM PSPs) x 1.5; KYC1 (LATAM documents) x 1.3; IB4 (Brazil tax handling) x 1.5.
Archetype H (ADGM FSRA institutional broker). U2 (institutional certifications) x 1.5; KYC6 (KYB plus UBO) x 2.0; LP1 (counterparty creditworthiness) x 1.5; H2 (multi-IBX from Day 1) x 1.5; AN1 (institutional data feed quality) x 1.5.
How operators actually use the framework
Five operational steps for applying the framework at vendor procurement:
Step 1: Identify the procurement scope. Determine which Phase 2 chapter the vendor procurement falls under. For multi-chapter procurement (turnkey suites spanning CRM plus platform plus payments plus LP) apply each chapter’s per-pillar dimensions to the relevant component plus the turnkey-specific dimensions.
Step 2: Identify the operator’s archetype. Match the operator’s regulatory positioning and operating model to one of the eight archetypes covered in the synthesis sub-series. For operators that span multiple archetypes (rare but real) apply the strictest per-archetype customisation across the multi-archetype scope.
Step 3: Construct the RFP scorecard. Combine the five universal dimensions plus the relevant per-pillar dimensions plus the per-archetype weight multipliers into a single scorecard. The scorecard should be shared with the vendor before the RFP response so the vendor can address the dimensions explicitly.
Step 4: Score the vendor against the scorecard. Score each dimension on the 1-5 scale against the vendor’s RFP response plus product demo plus reference customer evidence. Apply disqualification thresholds: any critical dimension scoring below 2 produces automatic disqualification regardless of total score.
Step 5: Rank vendors and document the procurement decision. Calculate weighted totals across dimensions. The ranking produces the procurement shortlist. Document the scoring including the specific evidence for each dimension to produce an audit trail that supports supervisory examination of the procurement process.
The framework is iterative. Operators should refine the per-pillar weights and per-archetype multipliers based on their procurement experience over time; the framework above provides starting weights and dimensional structure but operators should adapt to their specific procurement context.
What comes next in Phase 4
This dispatch opens Phase 4 with the foundational RFP scoring framework. Future Phase 4 artefacts will extend the framework:
- Per-pillar evaluation toolkits. Operationally-actionable toolkits for specific pillar procurement including questionnaire templates, reference customer questions, demo evaluation rubrics, and integration testing protocols.
- Per-archetype RFP templates. Complete RFP templates customised per archetype that operators can adapt directly for their procurement processes.
- Vendor evidence library. Aggregated evidence on specific vendors against the framework dimensions sourced from public information plus operator ground-truth contributions.
- Procurement decision documentation templates. Templates for documenting procurement decisions supporting supervisory examination and operator-side governance.
The Phase 4 corpus state begins at:
- 25 Phase 3 synthesis dispatches
- 1 Phase 4 opener (this dispatch)
- TOTAL: 26 dispatches
The Phase 3 synthesis sub-series is closed; Phase 4 operationally-actionable artefacts begin with this dispatch. The forward roadmap will be shaped by which artefacts produce the most operator-actionable value rather than by additional synthesis coverage.
If you operate a broker stack and the framework above does not match your procurement process reality, that is the editorial signal we are looking for. The corpus improves through ground-truth from operators.