DISPATCH ·

LP procurement evaluation toolkit (Phase 4 per-pillar artefact)

Thirtieth dispatch. Fourth per-pillar Phase 4 evaluation toolkit. Operationally-actionable artefact for Chapter VIII liquidity provider procurement covering the unique characteristics of LP procurement that distinguish it from other Phase 4 toolkits: 12-18 month establishment cycles for tier-1 prime broker access, bidirectional credit assessment (operator assesses LP creditworthiness while LP assesses operator), multi-LP relationship as procurement norm rather than exception, and FIX-API engineering-heavy integration testing that typically takes 3-6 months for institutional deployments. The toolkit provides procurement-stage questionnaire (34 questions structured for tier-1 prime brokers, PoP layer, regional LPs, and crypto LPs separately), reference customer questions (16 questions covering bilateral LP-operator operational reality), demo evaluation rubric (12 tests including live FIX-API connectivity and spread testing), integration testing protocol (12 pre-go-live tests), and decision documentation template.

tags · phase-4 · lp-procurement · prime-broker · evaluation-toolkit · operational-artefact

Why this dispatch exists

This is the thirtieth dispatch and the fifth in the Phase 4 operationally-actionable artefact sub-series opened by the RFP scoring framework dispatch and continued through the KYC evaluation toolkit, RegTech evaluation toolkit, and broker CRM evaluation toolkit. This dispatch covers the fourth per-pillar evaluation toolkit: liquidity provider procurement.

LP procurement is structurally distinct from the three prior toolkits because the procurement timeline, evaluation criteria, and operational characteristics differ materially from vendor product procurement. The LP procurement deep dive covered the tier-1 prime broker access gates (50-100 million USD AUM threshold range), the prime-of-prime (PoP) layer that mid-market operators procure through, regional MENA and APAC LP procurement, crypto LP procurement under MiCAR, and the six procurement decision dimensions (counterparty creditworthiness, spread competitiveness, last-look policies, multi-asset depth, API and execution venue, regulatory disclosure).

Four characteristics distinguish LP procurement from other Phase 4 toolkit coverage:

Procurement cycles are materially longer. Tier-1 prime broker establishment cycles run 12-18 months including operational due diligence, credit line establishment, and FIX-API integration. PoP procurement runs 6-12 weeks but with similar engineering integration complexity. Crypto LP procurement runs 4-8 weeks because the relationships are typically less formal than tier-1 prime brokerage. The Phase 4 toolkit timing assumptions for KYC (3-5 weeks) or CRM (4-6 weeks) do not apply.

Credit assessment is bidirectional. The LP assesses the operator’s creditworthiness, operational profile, and regulatory positioning before establishing the relationship. The operator should assess the LP’s counterparty creditworthiness, financial stability, and operational continuity before committing trade flow. The post-Credit Suisse 2023 environment makes counterparty creditworthiness the highest-weight procurement dimension; operators should evaluate LP creditworthiness with the same rigour the LP applies to operator creditworthiness.

Multi-LP relationships are the procurement norm. Operators procure at least two LP relationships for redundancy from the LP deep dive’s procurement-relevant framing. The procurement decision is therefore which combination of LPs rather than which single LP. The toolkit below assumes multi-LP procurement evaluation.

FIX-API integration is engineering-heavy. FIX-API integration with tier-1 prime brokers and institutional PoPs typically takes 3-6 months for full production deployment including market data integration, order routing, post-trade reconciliation, and risk integration. The integration testing protocol below structures the engineering work that precedes go-live.

This toolkit provides operationally-actionable artefacts that operators apply directly during LP procurement processes.

LP procurement scope recap

The LP procurement scope spans four distinct LP categories with materially different procurement characteristics:

Tier-1 FX prime brokers (Goldman, Morgan Stanley, Citi, JPMorgan, Barclays, UBS, BNP Paribas, HSBC). Direct prime brokerage relationships requiring 50-100 million USD AUM threshold, segregated client funds, institutional-grade operational profile, and tier-1 regulatory positioning (FCA, SEC, CySEC, DFSA preferred over CASP-only or smaller jurisdictions). Procurement cycles 12-18 months.

Prime-of-prime (PoP) layer (LMAX, FXCM Pro, Saxo Markets, ATC Brokers, IS Prime, Sucden Financial, Tickmill Pro, ADSS, Swissquote). Intermediated FX liquidity for operators below tier-1 AUM threshold. Procurement cycles 6-12 weeks. Broker-stack-bundled options (B2Prime, Leverate Prime) are subset.

Regional MENA and APAC LPs (Equiti, GFM, ATC MENA, Saxo Markets Asia, Swissquote Hong Kong). Currency pair coverage and time zone alignment for jurisdiction-specific operations. Procurement-relevant for Archetypes B (DMCC plus VARA), F (APAC), and H (ADGM institutional).

Crypto LPs (Cumberland, Wintermute, GSR, Falcon X, Galaxy Digital Trading) plus broker-stack-bundled (B2Prime crypto) plus CEX institutional access (Binance Institutional, Coinbase Institutional, Kraken Pro). Institutional crypto liquidity for crypto-touching archetypes (B, D, E, H). Procurement cycles 4-8 weeks. Per the LP deep dive the segment crystallised under MiCAR around five institutional vendors.

The toolkit below covers all four LP categories with separate procurement-stage questions and evaluation criteria.

Procurement-stage questionnaire template

The questionnaire template includes 34 specific RFP questions structured by LP category and framework dimension.

Universal dimensions (5 questions per the Phase 4 opener)

  1. Provide your pricing structure including spread structure, commission structure, settlement fees, and any per-volume rebate arrangements.
  2. List your regulatory authorisations and certifications including specific regulator status, FCA RTS 27 disclosure compliance, ESMA equivalent disclosure compliance, and jurisdiction-specific certifications.
  3. Describe your customer support structure including dedicated relationship management, support response SLAs, escalation paths, and operational issue handling.
  4. Provide your most recent financial position disclosure including audited financials, parent company disclosure framework, and credit rating if applicable.
  5. Describe your product roadmap including new instrument additions, technology investments, and forward operational commitments.

Tier-1 prime broker dimensions (8 questions)

  1. Confirm your AUM threshold for new prime brokerage relationships and your operational profile requirements for the operator’s specific size.
  2. Describe your credit line establishment process including credit assessment methodology, credit line sizing principles, and ongoing credit line review cadence.
  3. Provide your settlement terms including settlement schedule (T+0 for FX spot typical), credit terms, margin requirements, and intraday credit management.
  4. Describe your execution mechanics including last-look policy across instrument groups, execution venue, latency characteristics, and order rejection handling.
  5. List your FX prime brokerage product set including FX spot, FX forwards, NDFs, FX options, precious metals, and crypto-asset access if applicable.
  6. Describe your operational due diligence framework including operator-side compliance reviews, ongoing supervisory relationship, and operator-side notification obligations.
  7. Describe your operator-side reporting including end-of-day reconciliation files, FIX message logs, settlement reports, and supervisory examination support.
  8. Provide reference operators in similar archetype with prime brokerage relationship tenure and operational profile.

PoP layer dimensions (6 questions)

  1. Describe your PoP positioning including tier-1 prime broker relationships you aggregate, spread mark-up structure, and operator-side spread transparency.
  2. Describe your liquidity aggregation methodology including specific LPs aggregated, weighted contribution per LP, and operator-side LP transparency.
  3. Describe your last-look policy including specific instrument groups under last-look versus no-last-look, last-look duration, and operator-side disclosure.
  4. Provide spread analysis at the operator’s expected trade size distribution including FX majors, FX minors, exotics, indices, and commodities.
  5. Describe your CFD broker counterparty experience including operator-archetype-specific positioning and reference operators.
  6. Describe your integration architecture including FIX-API support, bridge plug-in compatibility (MT4 server bridge, MT5 server bridge), and operator-side integration timeline.

Regional LP dimensions (4 questions)

  1. (Regional MENA + APAC) Describe your regional currency pair depth including specific currency pairs covered (AED, SAR, KWD, EGP for MENA; HKD, SGD, JPY, AUD, NZD for APAC) and spread competitiveness.
  2. Describe your time zone alignment including specific operating hours, regional support presence, and operator-side coordination during regional market events.
  3. Describe your regional regulatory positioning including specific jurisdictional authorisations relevant to operator’s archetype.
  4. Provide reference operators in the operator’s regional client geography with relationship tenure.

Crypto LP dimensions (6 questions)

  1. (Crypto-touching archetypes) Describe your MiCAR-aligned positioning including specific authorisation status, EU passport positioning, and MiCAR Title VI compliance.
  2. List your crypto-asset coverage including supported tokens, derivatives access, OTC capability, and stablecoin rail integration.
  3. Describe your liquidity sourcing including primary venues, market-making infrastructure, and DeFi liquidity integration if relevant.
  4. Describe your settlement and credit terms including stablecoin settlement, fiat settlement, credit line establishment for institutional counterparties, and ongoing credit management.
  5. Provide your counterparty failure protection including segregation of operator funds, insurance coverage, and operator-side risk mitigation framework.
  6. Describe your post-Genesis Trading 2023 operational positioning including risk management framework changes, counterparty exposure management, and operator-side transparency.

Integration and operational dimensions (5 questions)

  1. Describe your FIX-API architecture including supported FIX versions (4.4, 5.0), market data feeds, order entry sessions, drop copy sessions, and post-trade integration.
  2. Describe your colocation availability including specific IBX presence (LD4, NY4, TY3, FR2, AM3, DX1, SY3) and cross-connect provisioning timeline.
  3. Describe your operator-side integration timeline including specific milestones (test environment, conformance testing, production go-live) and engineering coordination requirements.
  4. Describe your incident response framework including outage notification timing, market data feed redundancy, and operator-side communication during incidents.
  5. Describe your post-integration ongoing relationship including dedicated relationship management, quarterly business reviews, and operator-side issue escalation.

Reference customer questions

LP procurement reference customer diligence requires conversations with other operators with similar size and archetype rather than vendor-curated reference list. The 16 questions structure operator-side reference conversations:

Operational reality (6 questions)

  1. How long has your operation been using this LP and at what trade volume?
  2. What is your actual execution quality versus the LP’s pre-contract positioning? Specifically: average spread captured, slippage characteristics, order rejection rate.
  3. (Tier-1 prime brokerage) How responsive is the LP to credit line review requests? Has credit line sizing kept pace with your operational growth?
  4. (PoP layer) How transparent is the LP’s spread mark-up structure in operational reality? Are spread quotations reliable across instrument groups?
  5. How frequently do you encounter operational issues requiring LP intervention? What is the typical resolution time?
  6. How responsive is the LP’s relationship management to operational concerns? Are dedicated relationship management arrangements honoured?

Procurement specifics (5 questions)

  1. How long did your procurement cycle actually take versus the LP’s pre-contract estimate?
  2. How rigorous was the LP’s operational due diligence? Did they request information your team did not expect?
  3. What contract terms did you actually achieve versus the LP’s positioning? Specifically: pricing, credit terms, settlement schedule, termination provisions.
  4. (Tier-1 prime brokerage) Did the LP honour credit line commitments during operational reality including during fast-market conditions?
  5. Did you encounter situations where the LP’s regulatory positioning was inadequate for your operational context?

Counterparty assessment (5 questions)

  1. How transparent is the LP about their financial position and counterparty exposure during ongoing operational relationship?
  2. Have you observed the LP’s response during market stress events (fast-market conditions, regulatory shifts, counterparty failure events)?
  3. (Tier-1 prime brokerage) How does the LP manage operator credit exposure during operational stress? Is operator-side communication transparent during credit decisions?
  4. (Crypto LP procurement) How did the LP respond during the Genesis Trading 2023 event or similar institutional crypto LP failures?
  5. Would you procure this LP again given the same procurement decision context? Why or why not?

Demo evaluation rubric

LP procurement demos differ from product vendor demos because the demonstration involves live market data, FIX-API connectivity, and actual order placement against the LP’s production infrastructure. The 12-test rubric structures operator-side demo evaluation:

Demo Test 1: Live FIX-API connectivity from operator-provided test environment.

Pass criteria: LP demonstrates FIX-API connection establishment, market data feed activation, and order entry session activation from operator-provided test environment with explicit message flow visibility. Fail criteria: connectivity gaps; market data feed unavailable; order entry session not established.

Demo Test 2: Spread testing at operator’s expected trade size across major instrument groups.

Pass criteria: LP demonstrates competitive spread at operator’s expected trade size across FX majors, FX minors, indices, commodities relevant to operator’s product set. Spread characteristics consistent across market conditions. Fail criteria: spread degradation at operator’s expected trade size; spread characteristics inconsistent; spread positioning at smaller trade sizes only.

Demo Test 3: Last-look policy demonstration with operator-provided test order sequence.

Pass criteria: LP demonstrates last-look policy with explicit operator-side disclosure including instrument groups under last-look, last-look duration, and last-look rejection rate. Fail criteria: last-look policy non-transparent; rejection rate undisclosed; last-look applies across all instrument groups without disclosure.

Demo Test 4: Order execution latency testing from operator’s expected colocation.

Pass criteria: LP demonstrates order execution latency from operator-specified colocation (LD4, NY4, TY3) with explicit latency metrics and consistency under load. Fail criteria: latency characteristics non-transparent; latency degrades under load; colocation cross-connect not provisioned for testing.

Demo Test 5: Market data feed quality testing.

Pass criteria: LP demonstrates market data feed including tick-by-tick depth, market depth visibility, and feed redundancy with explicit failover demonstration. Fail criteria: market data feed shallow; market depth absent; feed redundancy not demonstrated.

Demo Test 6: Post-trade reconciliation demonstration.

Pass criteria: LP demonstrates end-of-day reconciliation file generation including FIX message logs, settlement reports, and operator-side integration support. Fail criteria: reconciliation files limited; integration support absent; settlement reports incomplete.

Demo Test 7: Credit line management walkthrough (tier-1 prime brokerage).

Pass criteria: LP demonstrates credit line establishment process, ongoing credit line review methodology, and operator-side credit line monitoring. Fail criteria: credit line process opaque; credit assessment methodology absent; operator-side monitoring not demonstrated.

Demo Test 8: Operational due diligence framework walkthrough.

Pass criteria: LP demonstrates operator-side due diligence requirements including specific information requirements, review timeline, and operator-side preparation guidance. Fail criteria: due diligence framework opaque; information requirements not specified; timeline estimate absent.

Demo Test 9: Multi-asset depth demonstration.

Pass criteria: LP demonstrates depth across operator’s specific instrument set including FX, CFDs on indices, commodities, single-stock CFDs if relevant, options if relevant. Fail criteria: multi-asset coverage shallow; specific instruments not supported; spread characteristics inconsistent across asset classes.

Demo Test 10: Crypto LP infrastructure demonstration (crypto-touching).

Pass criteria: LP demonstrates institutional crypto trading infrastructure including spot, derivatives, OTC capability, stablecoin rail integration, and settlement demonstration. Fail criteria: crypto infrastructure shallow; OTC capability absent; settlement integration not demonstrated.

Demo Test 11: Regional LP demonstration (regional procurement).

Pass criteria: regional LP demonstrates regional currency pair coverage with competitive spread, time zone alignment, and regional regulatory positioning. Fail criteria: regional coverage shallow; spread characteristics not competitive; time zone alignment inadequate.

Demo Test 12: Counterparty failure protection demonstration.

Pass criteria: LP demonstrates operator funds segregation, insurance coverage, and operator-side risk mitigation framework with explicit documentation. Fail criteria: segregation framework absent; insurance coverage undisclosed; operator-side framework not demonstrated.

Integration testing protocol

LP integration testing is the most engineering-heavy of the Phase 4 toolkits because FIX-API integration with tier-1 prime brokers and institutional PoPs typically takes 3-6 months for full production deployment. The 12-test protocol structures operator-side pre-go-live testing:

  1. FIX-API conformance testing. Operator integration team tests FIX-API conformance against LP specification including all required message types, session management, and recovery scenarios.
  2. Market data feed integration testing. Test market data feed integration including tick-by-tick processing, market depth handling, and feed failover scenarios.
  3. Order routing integration testing. Test order entry, modification, cancellation, and execution flow including order rejection handling.
  4. Drop copy session integration testing. Test drop copy session integration for risk management and post-trade reporting.
  5. Post-trade reconciliation integration testing. Test end-of-day reconciliation file processing including FIX message log handling and settlement report ingestion.
  6. Risk management integration testing. Test integration with operator’s risk management infrastructure including credit line monitoring, exposure aggregation, and margin call flow.
  7. Multi-LP aggregation testing (if multi-LP procurement). Test cross-LP exposure aggregation, cross-LP spread comparison, and cross-LP execution routing if operator runs multi-LP architecture.
  8. Colocation cross-connect testing. Test cross-connect provisioning including latency characteristics, redundancy, and cross-IBX connectivity if multi-IBX deployment.
  9. Disaster recovery testing. Test LP failover scenarios, market data feed redundancy, and operator-side recovery procedures.
  10. Performance testing at expected production volume. Test FIX-API performance at expected production trade volume including peak load handling.
  11. Compliance reporting integration testing. Test integration with operator’s RegTech infrastructure including transaction reporting (MiFIR), trade surveillance, and best execution reporting.
  12. End-to-end production simulation. Simulate full production trading day including pre-market, market opening, intraday trading, and end-of-day reconciliation.

The integration testing protocol typically takes 3-6 months for tier-1 prime broker integration and 6-12 weeks for PoP integration. Operators should staff the engineering work appropriately and treat integration testing as the critical path for go-live.

Decision documentation template

The decision documentation template structures the operator-side LP procurement record:

Section 1: Procurement context

  • Operator regulatory positioning and archetype identification
  • LP procurement scope (number of LPs procured, LP category breakdown)
  • Multi-LP architecture decision (primary plus secondary, or balanced multi-LP)
  • Procurement timing and decision process
  • Procurement team and roles

Section 2: LP shortlist

  • List of LPs evaluated per category
  • Initial screening criteria including operator-side credit assessment of LPs
  • RFP distribution and response timing per category
  • LPs disqualified at initial screening with counterparty creditworthiness reasoning

Section 3: RFP evaluation

  • Universal dimensions scoring per LP
  • Per-category dimensions scoring (tier-1 prime broker, PoP, regional, crypto)
  • Counterparty creditworthiness scoring as highest-weight dimension
  • Disqualification thresholds applied with specific dimension failures noted

Section 4: Reference customer diligence

  • Reference operator list per shortlisted LP (operators in similar archetype)
  • Reference operator responses summarised
  • Counterparty assessment documentation including post-Credit Suisse and post-Genesis Trading event responses
  • Reference diligence-driven scoring adjustments

Section 5: Demo evaluation

  • Demo dates and participants per shortlisted LP
  • Demo evaluation rubric results across 12 tests
  • Spread analysis at operator’s expected trade size documentation
  • Last-look policy documentation
  • Latency characteristics documentation
  • Demo-driven scoring adjustments

Section 6: Integration testing

  • Integration testing dates and scope per selected LP
  • Integration testing protocol results across 12 tests
  • Engineering work documentation including timeline, milestones, and resource allocation
  • Multi-LP aggregation testing documentation if applicable
  • Capability gaps identified with LP remediation commitments

Section 7: Procurement decision

  • Final LP selection per category with weighted total scoring
  • Multi-LP architecture decision documentation
  • Contract terms per LP including pricing, credit terms, settlement schedule, termination provisions
  • Counterparty creditworthiness ongoing monitoring framework

Section 8: Ongoing monitoring

  • Operator-side LP performance monitoring framework including execution quality metrics
  • Counterparty creditworthiness ongoing assessment including periodic financial review
  • LP relationship review cycle (quarterly business review, annual relationship review)
  • LP procurement review triggers (counterparty creditworthiness deterioration, execution quality degradation, regulatory positioning shifts, market stress event responses)

What comes next in Phase 4

This dispatch provides the fourth per-pillar evaluation toolkit. Future Phase 4 artefacts will extend coverage:

  • Additional per-pillar evaluation toolkits. Broker analytics, copy trading, IB management, payments, brokerage hosting, trading platform, prop firm tech, alt-WL platforms, crypto exchange WL, risk management, turnkey suites toolkits.
  • Per-archetype RFP templates. Complete RFP templates customised per archetype combining the universal dimensions plus relevant per-pillar dimensions plus per-archetype customisation.
  • Vendor evidence library. Aggregated evidence on specific vendors against framework dimensions sourced from public information and operator ground-truth contributions.
  • Institutional procurement toolkit (Archetype H specific). The Phase 4 toolkits cover retail and mass-market broker procurement; institutional Archetype H procurement requires structurally different toolkit coverage that future Phase 4 artefact will provide.

Phase 4 corpus state after this dispatch:

  • 25 Phase 3 synthesis dispatches
  • 5 Phase 4 operationally-actionable artefacts (RFP scoring framework opener, KYC toolkit, RegTech toolkit, broker CRM toolkit, this LP toolkit)
  • TOTAL: 30 dispatches

If you operate a broker stack with active LP procurement consideration and the toolkit 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.