DISPATCH ·

Copy + social trading procurement evaluation toolkit (Phase 4 per-pillar artefact)

Thirty-fifth dispatch. Ninth per-pillar Phase 4 evaluation toolkit. Operationalises the copy trading deep dive's procurement filters: the four architectural archetypes (broker-stack-bundled / platform-native / plugin / independent network), the signal-provider vetting depth as procurement filter with five evaluation dimensions, the MiFID II copy-as-portfolio-management classification as procurement-stage compliance question requiring operator compliance counsel evaluation before signature, the toxic-signal-provider clawback as explicit RFP filter that disqualifies vendors who cannot answer in concrete operational detail, and the FXJunction LIMITED durable verdict as automatic disqualifier for any of CySEC, FCA, DMCC, or ASIC-regulated operator procurement. Operators apply directly during copy trading vendor procurement processes.

tags · phase-4 · copy-trading · signal-providers · evaluation-toolkit · operational-artefact

Why this dispatch exists

This is the thirty-fifth dispatch and the tenth in the Phase 4 operationally-actionable artefact sub-series. The earlier Phase 4 dispatches covered the RFP scoring framework opener plus eight per-pillar toolkits (KYC, RegTech, broker CRM, LP, payments, hosting, risk management, trading platform). This dispatch covers the ninth per-pillar toolkit: copy and social trading procurement.

The copy trading deep dive covered the four architectural archetypes (broker-stack-bundled with dual lock-in, platform-native with platform lock-in, plugin with platform flexibility, independent network with regulatory complexity), the signal-provider vetting depth evaluation, the MiFID II copy-as-portfolio-management classification question with material operator-side cost of misclassification, the toxic-signal-provider clawback procurement question with per-architecture liability allocation differences, and the FXJunction LIMITED durable verdict as procurement disqualifier for any operator regulated under CySEC, FCA, DMCC, or ASIC.

The 2026 procurement-relevant question is concrete RFP filter application at vendor selection. Most mid-market operators procure across two architectural archetypes (one bundled or platform-native primary plus one independent network for signal provider depth); the procurement decision combines per-archetype evaluation with per-vendor diligence on signal-provider vetting depth, MiFID II classification positioning, and toxic-signal-provider clawback policy.

This toolkit provides operationally-actionable artefacts that operators apply directly during copy trading vendor procurement.

Copy trading procurement scope recap

The copy trading procurement scope spans the four architectural archetypes with distinct evaluation criteria:

Broker-stack-bundled. B2Copy (B2Broker), Match-Trade Copy, Leverate Copy (PARTIAL FIT with Sirix lock-in), UpTrader Copy (PARTIAL FIT with CRM-first opacity). Procurement-appropriate for operators committed to the broader stack vendor. Dual lock-in implications.

Platform-native. cTrader Copy (STRONG PICK with Spotware Store published pricing, tier-1 CySEC reference deployments). Procurement-appropriate for operators on cTrader or willing to add cTrader as parallel platform.

Plugin. Brokeree Social Trader (SOLID, server-side plugin operating across MT4/MT5/cTrader with consistent product capability). Procurement-appropriate for operators wanting platform flexibility with specialist copy product depth.

Independent network. ZuluTrade (SOLID, 80+ broker integrations, HCMC-regulated), DupliTrade (SOLID, only directly CySEC-regulated independent network), Pelican Trading (SOLID, FCA-authorised), FXJunction (LIMITED, Comoros registration with no recognised financial services authorisation; procurement-disqualified for CySEC, FCA, DMCC, ASIC-regulated operators). Procurement-appropriate for additional signal provider depth alongside primary archetype.

Most mid-market operators procure across two archetypes (one bundled or platform-native primary plus one independent network); operators rarely select a single archetype.

Procurement-stage questionnaire template

The questionnaire template includes 32 specific RFP questions structured by dimension.

Universal dimensions (5 questions per the Phase 4 opener)

  1. Provide your pricing structure including base pricing, per-account-pair pricing if applicable, signal provider revenue share structure, follower fees, and operator-side commercial economics.
  2. List your relevant certifications including ISO 27001, SOC 2 Type II, jurisdiction-specific certifications, and operator-relevant regulatory authorisations.
  3. Describe your customer support structure including dedicated TAM availability and operator-side escalation paths.
  4. Provide your most recent financial position disclosure.
  5. Describe your product roadmap including feature commitments and regulatory readiness investments.

Architectural archetype dimensions (6 questions)

  1. Confirm your architectural archetype positioning (broker-stack-bundled / platform-native / plugin / independent network). Describe the operator-side procurement implications including lock-in characteristics and integration framework.
  2. (Broker-stack-bundled) Describe your dual lock-in implications including operator-side commitment to broader stack vendor and operator-side flexibility limitations if stack replacement is considered.
  3. (Platform-native) Describe your platform lock-in implications including operator-side procurement framework for operators on different platforms.
  4. (Plugin) Describe your platform flexibility including specific supported platforms (MT4 / MT5 / cTrader), plugin maintenance overhead, and operator-side integration cost.
  5. (Independent network) Describe your network depth including specific broker integrations count, signal provider count, and operator-side partnership economics.
  6. Describe your typical procurement combination with operator’s existing primary architecture (e.g. if independent network procurement, describe primary architecture procurement pattern operators typically combine with).

Signal-provider vetting depth dimensions (5 questions)

  1. Describe your signal-provider identity verification depth including verification beyond standard KYC, source-of-funds verification, source-of-wealth verification, and ongoing professional qualification verification.
  2. Describe your signal-provider trading history depth requirement including minimum history requirement (90-day / 12-month / none), history verification methodology (vendor-platform-verified versus self-reported), and operator-side transparency.
  3. Describe your signal-provider strategy disclosure framework including instrument set disclosure, risk profile disclosure, leverage usage disclosure, position holding periods, drawdown tolerance, and disclosure update cadence requirements.
  4. Describe your signal-provider conflict of interest screening including specific relationships flagged (broker relationships, LP relationships, counterparty relationships) and operator-side transparency.
  5. Describe your ongoing signal-provider performance monitoring including specific thresholds (performance degradation, drawdown excursions, behavioural shifts), suspension triggers, and removal triggers.

MiFID II copy-as-portfolio-management classification (4 questions)

  1. Describe your MiFID II classification positioning including specific positioning (automated trading / social trading / portfolio management) and rationale.
  2. Provide regulatory positioning documentation including specific regulator engagement, classification confirmation from operator-relevant regulators, and operator-side legal opinion support.
  3. Describe your operator-side compliance counsel framework including specific documentation provided to operator compliance counsel for classification evaluation before contract signature.
  4. (Per-architecture implications) Describe how your architectural archetype affects MiFID II classification positioning. Bundled and platform-native easier to position as automated trading; independent networks harder.

Toxic-signal-provider clawback dimensions (5 questions)

  1. Describe your toxic-signal-provider policy including specific risk scenarios covered (deliberate grid trading, undisclosed conflicts of interest, copy-trading flow feeding own counterparty positions, similar).
  2. Describe your liability allocation framework including vendor-side liability, operator-side liability, and signal-provider-side liability in the event of misconduct causing follower account harm.
  3. Describe your clawback mechanism including operator-side claim process, vendor coverage thresholds, audit trail requirements, dispute resolution mechanism, and historical clawback claim experience.
  4. Describe your follower account harm coverage including specific coverage limits, coverage exclusions, and operator-side coverage activation process.
  5. (Per-architecture implications) Describe how your architectural archetype affects liability allocation. Bundled and platform-native typically place primary liability on operator; independent networks typically retain primary liability for signal provider conduct.

Regulatory positioning dimensions (4 questions)

  1. (Independent network) Describe your network regulatory positioning including specific authorisation status, jurisdiction-specific regulatory positioning, and operator-side regulatory framework alignment.
  2. Confirm your network is procurement-eligible for the operator’s specific regulatory framework. For CySEC, FCA, DMCC, ASIC-regulated operators specifically, confirm regulatory positioning satisfies operator’s regulatory requirements.
  3. (FXJunction-equivalent positioning) For vendors with Comoros registration or similar non-FSA-authorised positioning, acknowledge LIMITED procurement positioning and operator-side procurement disqualification for CySEC, FCA, DMCC, ASIC-regulated operations.
  4. Describe your operator-side regulatory disclosure support including specific disclosures provided to operator regulators and operator-side regulator examination support.

Phase 4 framework alignment (3 questions)

  1. How does your product align with the per-archetype procurement pattern (most mid-market operators procure across two architectural archetypes)? Specifically: integration with operator’s primary architecture if your product is secondary.
  2. How does your product handle the operator’s specific archetype context including per-archetype customisation weight multipliers from the Phase 4 opener?
  3. Describe your contract terms including pricing escalation methodology, contract length, data portability provisions on termination, and operator-side switching cost mitigation.

Reference customer questions

The 16 reference customer questions structure operator-side diligence:

Operational reality (6 questions)

  1. How long has your operation been using this vendor and at what active follower account scale plus signal provider count?
  2. Did the vendor’s RFP-stage capability disclosure match operational reality post-deployment? Specifically: signal-provider vetting depth gaps, MiFID II classification handling, toxic-signal-provider clawback experience.
  3. How does the vendor’s product perform at production scale including copy execution latency, follower account synchronisation, and operator-side risk management integration?
  4. (Independent network) How accurate is the vendor’s network depth positioning in operational reality? Have you encountered signal provider quality gaps?
  5. (For toxic-signal-provider scenarios) Has your operation encountered signal provider misconduct scenarios? How did the vendor handle clawback or coverage?
  6. (For MiFID II positioning) How did the vendor’s classification positioning hold up during regulator engagement?

Procurement specifics (5 questions)

  1. How did the vendor handle the procurement decision process? Were they responsive to RFP iterations including signal-provider vetting testing and toxic-signal-provider clawback policy discussion?
  2. What contract terms did you actually achieve versus the vendor’s positioning? Specifically: pricing, revenue share, contract length, termination provisions.
  3. (Bundled procurement) How did the dual lock-in between copy trading and broader stack affect operational flexibility?
  4. (Platform-native procurement) How did the platform lock-in affect operator-side platform strategy?
  5. Has the vendor’s roadmap delivery matched the roadmap visibility provided during procurement?

Operational quality (5 questions)

  1. How accurate is the vendor’s signal-provider vetting in operational reality? Specifically: identity verification depth, trading history verification, strategy disclosure currency.
  2. How responsive is the vendor’s signal-provider monitoring? Specifically: performance degradation detection, drawdown excursion detection, behavioural shift detection.
  3. (Independent network) How did the vendor’s regulatory positioning hold up across regulator engagement? Specifically: CySEC, FCA, DMCC, or ASIC-specific positioning depending on operator’s jurisdiction.
  4. How responsive is the vendor to regulatory developments including ESMA copy-as-portfolio-management positioning evolution, CySEC enforcement, FCA consultations, or jurisdiction-specific regulatory shifts?
  5. Would you procure this vendor again given the same procurement decision context? Why or why not?

Demo evaluation rubric

The 12-test rubric structures operator-side demo evaluation:

Demo Test 1: Architectural archetype demonstration with operator’s primary platform integration.

Pass criteria: vendor demonstrates architectural archetype operationalisation with operator’s specific primary platform (MT5, cTrader, Match-Trader, B2BX) including integration depth and operator-side procurement consolidation. Fail criteria: integration shallow; primary platform not supported; procurement consolidation absent.

Demo Test 2: Signal-provider identity verification demonstration.

Pass criteria: vendor demonstrates signal-provider identity verification depth including verification beyond standard KYC, source-of-funds verification, and ongoing verification methodology with operator-provided test signal provider scenarios. Fail criteria: identity verification at standard KYC level only; source-of-funds verification absent; ongoing verification methodology shallow.

Demo Test 3: Signal-provider trading history depth demonstration.

Pass criteria: vendor demonstrates trading history verification including minimum history requirement enforcement, vendor-platform-verified versus self-reported distinction, and operator-side transparency. Fail criteria: history requirement absent; verification methodology opaque; operator-side transparency limited.

Demo Test 4: Signal-provider strategy disclosure demonstration.

Pass criteria: vendor demonstrates strategy disclosure framework including specific disclosure dimensions, disclosure update cadence enforcement, and operator-side disclosure access. Fail criteria: strategy disclosure shallow; disclosure update enforcement absent; operator-side access limited.

Demo Test 5: Signal-provider conflict of interest screening demonstration.

Pass criteria: vendor demonstrates conflict of interest screening including specific relationships flagged and operator-side transparency. Fail criteria: conflict screening shallow; relationship flagging limited; operator-side transparency absent.

Demo Test 6: Ongoing performance monitoring demonstration.

Pass criteria: vendor demonstrates performance monitoring including specific thresholds (performance degradation, drawdown, behavioural shifts), suspension triggers, and operator-side monitoring access. Fail criteria: monitoring thresholds opaque; suspension triggers absent; operator-side access limited.

Demo Test 7: MiFID II classification documentation walkthrough.

Pass criteria: vendor demonstrates classification positioning including specific regulator engagement, classification confirmation documentation, and operator-side compliance counsel support framework. Fail criteria: classification documentation absent; regulator engagement opacity; compliance counsel support limited.

Demo Test 8: Toxic-signal-provider clawback policy walkthrough.

Pass criteria: vendor demonstrates toxic-signal-provider policy including specific risk scenarios covered, liability allocation framework, clawback mechanism, and historical clawback claim experience. Fail criteria: clawback policy absent; liability allocation opaque; historical experience limited; vendor cannot answer in concrete operational detail.

Demo Test 9: Live copy execution demonstration.

Pass criteria: vendor demonstrates copy execution including signal-provider trade replication, follower account synchronisation, and execution latency metrics. Fail criteria: copy execution shallow; synchronisation gaps; execution latency opaque.

Demo Test 10: Network depth demonstration (independent network procurement).

Pass criteria: independent network vendor demonstrates network depth including specific broker integrations, signal provider count, and operator-side partnership economics. Fail criteria: network depth shallow; broker integrations limited; partnership economics opaque.

Demo Test 11: Regulatory positioning verification.

Pass criteria: vendor demonstrates regulatory positioning including specific authorisation status, jurisdiction-specific positioning, and operator-side regulatory framework alignment confirmation. Fail criteria: regulatory positioning opaque; jurisdiction-specific support limited; operator-side framework alignment absent.

Demo Test 12: Integration with operator’s risk management and compliance framework.

Pass criteria: vendor demonstrates integration with operator’s risk management vendor, KYC vendor, and compliance reporting framework including alert handover and case management coordination. Fail criteria: integration gaps; operator-side framework alignment limited; compliance reporting absent.

Integration testing protocol

The 10-test protocol structures operator-side pre-signature integration testing:

  1. Platform integration testing. Test vendor product integration with operator’s specific primary platform including signal-provider trade flow, follower account synchronisation, and operator-side risk management integration.
  2. Multi-platform integration testing (if applicable). Test integration across operator’s multi-platform configuration (e.g. MT5 primary plus cTrader secondary) including consistent signal-provider visibility.
  3. Signal-provider vetting workflow testing. Test end-to-end signal-provider vetting workflow including identity verification, history verification, strategy disclosure, and operator-side transparency access.
  4. Ongoing monitoring integration testing. Test ongoing signal-provider performance monitoring integration with operator’s risk management framework including alert generation, suspension triggers, and removal workflow.
  5. Follower account management integration testing. Test follower account lifecycle integration with operator’s CRM including account creation, copy allocation, and follower-side risk controls.
  6. Toxic-signal-provider clawback workflow simulation. Simulate signal provider misconduct scenario and test clawback workflow including operator-side claim submission, vendor-side coverage activation, and dispute resolution.
  7. MiFID II compliance documentation review. Review vendor compliance documentation including classification positioning, regulator engagement evidence, and operator-side compliance counsel support framework.
  8. Performance testing at expected production scale. Test vendor performance at operator’s expected production scale including copy execution latency under peak load and synchronisation accuracy.
  9. Regulatory reporting integration testing. Test integration with operator’s RegTech infrastructure including trade surveillance, transaction reporting, and operator-side regulator engagement support.
  10. End-to-end production simulation. Simulate full production copy trading scenarios including signal-provider onboarding, follower account onboarding, copy execution, performance monitoring, and operator-side risk team workflow.

Integration testing typically takes 4-8 weeks for copy trading vendor deployments.

Decision documentation template

Section 1: Procurement context

  • Operator regulatory positioning and archetype identification
  • Copy trading procurement scope (primary architecture + secondary architecture if applicable)
  • Two-architecture procurement pattern rationale
  • Procurement timing and decision process

Section 2: Vendor shortlist

  • List of vendors evaluated per architectural archetype
  • Initial screening criteria including regulatory positioning filter (FXJunction-equivalent positioning automatic disqualification for CySEC, FCA, DMCC, ASIC operators)
  • RFP distribution and response timing
  • Vendors disqualified at initial screening with reasoning

Section 3: RFP evaluation

  • Universal dimensions scoring per vendor
  • Architectural archetype dimensions scoring
  • Signal-provider vetting depth scoring
  • MiFID II classification positioning scoring
  • Toxic-signal-provider clawback policy scoring
  • Regulatory positioning scoring with explicit FXJunction-equivalent disqualification documentation
  • Per-archetype customisation applied
  • Disqualification thresholds applied

Section 4: Reference customer diligence

  • Reference customer list per shortlisted vendor including operators with toxic-signal-provider scenario experience if available
  • Reference responses summarised
  • Signal-provider vetting operational reality documentation
  • MiFID II positioning operational reality documentation
  • Toxic-signal-provider clawback claim experience documentation if applicable
  • Reference diligence-driven scoring adjustments

Section 5: Demo evaluation

  • Demo dates and participants per shortlisted vendor
  • Demo evaluation rubric results across 12 tests
  • Toxic-signal-provider clawback policy demonstration documentation (vendor’s ability to answer in concrete operational detail)
  • MiFID II classification documentation walkthrough documentation
  • Demo-driven scoring adjustments

Section 6: Integration testing

  • Integration testing dates and scope per shortlisted vendor
  • Toxic-signal-provider clawback workflow simulation documentation
  • Capability gaps identified with vendor remediation commitments

Section 7: Procurement decision

  • Final vendor ranking with weighted total scoring per architectural archetype
  • Selected primary architecture vendor with explicit decision rationale
  • Selected secondary architecture vendor if applicable with rationale
  • MiFID II classification evaluation outcome with operator compliance counsel sign-off
  • Contract terms summary including pricing, revenue share, and toxic-signal-provider clawback commitment documentation

Section 8: Ongoing monitoring

  • Operator-side vendor performance monitoring framework
  • Signal-provider performance monitoring framework
  • MiFID II classification ongoing review framework
  • Vendor review cycle (quarterly business review, annual relationship review)
  • Procurement decision review triggers (regulatory shifts, vendor M&A, toxic-signal-provider scenario emergence, capability gaps)

What comes next in Phase 4

Future Phase 4 artefacts will extend coverage:

  • Additional per-pillar evaluation toolkits. Broker analytics, IB management, prop firm tech, alt-WL platforms, crypto exchange WL, turnkey suites toolkits.
  • Per-archetype RFP templates.
  • Vendor evidence library.
  • Institutional procurement toolkit (Archetype H specific).

Phase 4 corpus state after this dispatch:

  • 25 Phase 3 synthesis dispatches
  • 10 Phase 4 operationally-actionable artefacts
  • TOTAL: 35 dispatches

If you operate a broker stack with active copy trading 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.