DISPATCH ·

Hybrid prop firm + broker RFP template (Phase 4 per-archetype artefact)

Forty-fourth dispatch. Third per-archetype RFP template covering Archetype C: hybrid prop firm plus broker operators with two legally distinct entities under one operating brand.

tags · phase-4 · rfp-template · hybrid · archetype-c · operational-artefact

Why this dispatch exists

Third per-archetype RFP template covering Archetype C: hybrid prop firm plus broker operators per the hybrid archetype dispatch.

Section 1: Requirement overview

The requirement is the dual-vertical broker tech stack for an operator running two legally distinct entities: a regulated CFD broker (typically CySEC, DMCC, or both) plus an education-positioned prop firm vertical under common ownership.

Section 2: Vendor evaluation categories required

  • Brokerage hosting (single deployment with logical separation between prop firm and broker MT5 instances)
  • Trading platforms (shared MT5 with broker-ID separation; separate prop firm tech vendors for challenge management + payout + simulated execution)
  • LP procurement (broker side only; prop firm side simulated execution)
  • Risk management (specialist with broker-ID-level segmentation as critical procurement requirement)
  • KYC + AML (two distinct flows: lightweight prop firm KYC + full broker KYC; two-vendor pattern recommended)
  • RegTech (Eventus Validus for combined CFD + proactive prop firm surveillance; Cappitech for broker-side MiFIR; Behavox or Smarsh for both entities)
  • Broker CRM (multi-tenant configuration Pattern 3 from broker CRM deep dive: one tenant per entity with shared parent visibility)
  • Prop firm tech (specialist vendors for challenge management + payout + simulated execution)
  • IB management (four-stage attribution capability required: challenge purchase → challenge pass → broker FTD → ongoing broker revenue)
  • Broker analytics (broker side only)
  • Copy trading (broker side only; cTrader Copy or Brokeree Social Trader)
  • Payments (two distinct PSP stacks for prop firm + broker)

Section 3: Universal vendor requirements

Apply the five universal dimensions from the RFP scoring framework opener.

Section 4: Per-pillar requirements

Per-pillar requirements with hybrid-specific emphasis:

  • Risk management: broker-ID-level segmentation demonstrated on operator’s specific MT5 instance configuration before signature (broker-IDs 1-100 prop firm vs 101-500 broker with separate VaR limits + separate pre-trade controls per group)
  • Broker CRM: multi-tenant Pattern 3 with parent organisation visibility
  • IB management: four-stage attribution test on operator’s specific test client introduction sequence (challenge purchase → challenge pass → 90-day broker FTD → 12-month ongoing broker revenue tracking)
  • KYC: two-vendor approach OR one-vendor-with-two-configurations approach (Pattern 1 vs Pattern 2 architectural decision per broker CRM deep dive)
  • Prop firm tech: forward-compatible architecture for 2026-2028 regulatory environment (FCA consultation, CySEC enforcement, DMCC framework, ASIC + US CFTC parallel activity)

Section 5: Hybrid archetype customisation (weight multipliers)

Per the Phase 4 opener customisation layer:

  • IB3 (four-stage hybrid attribution) x 2.0
  • R6 (broker-ID segmentation) x 2.0
  • CRM1 (multi-tenant) x 1.5
  • PF1-5 (prop firm tech) x 1.5

Section 6: Disqualification thresholds checklist

Vendor automatic disqualification if score below 2:

  • ☐ Broker-ID-level segmentation for risk management vendor
  • ☐ Four-stage attribution capability for IB management vendor
  • ☐ Multi-tenant Pattern 3 for CRM vendor
  • ☐ Forward-compatible regulatory architecture for prop firm tech vendor
  • ☐ Match-Trade Crypto / ETNA Software / FXJunction automatic disqualifications carry through

Section 7: Vendor scoring rubric reference

Hybrid-specific demo emphasis:

  • Broker-ID segmentation demonstration on operator’s MT5 (concrete demonstration before signature)
  • Four-stage attribution demonstration on operator’s specific test client introduction sequence
  • Multi-tenant CRM demonstration with parent organisation visibility

Section 8: Reference customer validation

Required hybrid operator reference customers:

  • Risk management: minimum 2 hybrid operators with broker-ID segmentation deployment
  • IB management: minimum 2 hybrid operators with four-stage attribution deployment + 12-month-plus tenure
  • CRM: minimum 2 hybrid operators with multi-tenant Pattern 3 deployment
  • Prop firm tech: minimum 2 hybrid operators with simulated execution layer operational tenure

Section 9: Integration testing scope

Hybrid-specific integration testing:

  • Broker-ID segmentation end-to-end testing on operator’s specific MT5 instance configuration
  • Four-stage attribution end-to-end testing on operator’s specific test client introduction sequence
  • Multi-tenant CRM testing with cross-entity workflow validation
  • Prop firm tech simulated execution layer testing under fast-market scenarios

Section 10: Decision documentation references

Hybrid-specific documentation:

  • Two-architecture procurement pattern rationale (broker-side turnkey or unbundled + separately procured prop firm vendors)
  • Legal entity separation framework documentation
  • Multi-tenant CRM pattern selection rationale (Pattern 1 vs 2 vs 3)
  • KYC architecture decision rationale (two-vendor vs one-vendor-two-configurations)