FactSet Trading Solutions

Name: FactSet Trading Solutions
Brand: FactSet
Rating: 4.3 (76 reviews)

FactSet creates flexible, open data and software solutions for tens of thousands of investment professionals around the world, providing instant access to financial data and analytics that investors use to make crucial decisions

Est 1978|Valuation $9.2B|Raised $2.6B

LinkedIn 319K|Website|Web traffic 647K|FTEs 12,694|HQ Norwalk, Connecticut, US

MarketsOrder/Execution Management Systems (OMS/EMS)Transaction Cost Analysis (TCA)

01Competitive Landscape

Top competitors comparison (indicative, not exhaustive)

| Aspect | FactSet Trading Solutions (Portware + LiquidityBook) | SS&C Eze (Eze EMS/OEMS) | Bloomberg (EMSX + AIM ecosystem) | |---|---|---|---| | Starting Price | Quote-based; not publicly listed | Quote-based; not publicly listed | Terminal price more standardized; enterprise components quote-based | | Best For | Buy-side desks wanting configurable multi-asset EMS with embedded FactSet analytics; firms already standardized on FactSet data/workstation | Firms seeking an integrated OEMS-style approach across trading + OMS in one vendor family | Firms deeply embedded in Bloomberg ecosystem; traders valuing liquidity, messaging, and broad terminal adoption | | Key Strength | Configurability; multi-asset automation; integration with FactSet data/analytics; expanded OMS footprint via LiquidityBook | Strong OEMS narrative; broad trading workflow; vendor focus squarely on trading stack | Network effects, terminal ubiquity, and broad market ecosystem integrations | | Key Weakness | Market perception risk: Portware viewed by some as legacy; LiquidityBook perceived by some as a lower-end OMS; fewer public user reviews for EMS | Can be complex; pricing not transparent; integration-heavy deployments | Higher baseline costs for terminals; enterprise pricing opacity; may be Bloomberg-centric by design |

Narrative analysis

Where FactSet tends to perform strongly: - **Embedded analytics and content:** FactSet can integrate its broader data stack into pre- and at-trade decision support. - **Portware configurability:** Trade press coverage emphasizes workflow configurability and multi-asset coverage. - **Strategy to expand OMS/EMS footprint:** LiquidityBook acquisition is a strategic move to deepen front-office workflow coverage and reduce vendor sprawl. Where competitors can be stronger: - **Single-vendor OEMS maturity:** Some buyers prefer a more natively unified OEMS; Burton Taylor suggests many do not expect LiquidityBook and Portware to become fully integrated immediately. - **Perceived modernity/cloud-native:** LiquidityBook is cloud-native, while Portware is sometimes characterized as legacy in industry commentary. - **Terminal-based trader network effects:** Bloomberg’s ecosystem remains a differentiator for some trading workflows.

Market adoption signals

Burton Taylor indicates Portware is seen more frequently than LiquidityBook in some contexts, but both are less commonly encountered than CRD or Eze in OMS contexts—suggesting FactSet is not the dominant OMS incumbent.

01Competitive Landscape

Top competitors comparison (indicative, not exhaustive)

Aspect	FactSet Trading Solutions (Portware + LiquidityBook)	SS&C Eze (Eze EMS/OEMS)	Bloomberg (EMSX + AIM ecosystem)
Starting Price	Quote-based; not publicly listed	Quote-based; not publicly listed	Terminal price more standardized; enterprise components quote-based
Best For	Buy-side desks wanting configurable multi-asset EMS with embedded FactSet analytics; firms already standardized on FactSet data/workstation	Firms seeking an integrated OEMS-style approach across trading + OMS in one vendor family	Firms deeply embedded in Bloomberg ecosystem; traders valuing liquidity, messaging, and broad terminal adoption
Key Strength	Configurability; multi-asset automation; integration with FactSet data/analytics; expanded OMS footprint via LiquidityBook	Strong OEMS narrative; broad trading workflow; vendor focus squarely on trading stack	Network effects, terminal ubiquity, and broad market ecosystem integrations
Key Weakness	Market perception risk: Portware viewed by some as legacy; LiquidityBook perceived by some as a lower-end OMS; fewer public user reviews for EMS	Can be complex; pricing not transparent; integration-heavy deployments	Higher baseline costs for terminals; enterprise pricing opacity; may be Bloomberg-centric by design

Narrative analysis

Where FactSet tends to perform strongly:

Embedded analytics and content: FactSet can integrate its broader data stack into pre- and at-trade decision support.
Portware configurability: Trade press coverage emphasizes workflow configurability and multi-asset coverage.
Strategy to expand OMS/EMS footprint: LiquidityBook acquisition is a strategic move to deepen front-office workflow coverage and reduce vendor sprawl.

Where competitors can be stronger:

Single-vendor OEMS maturity: Some buyers prefer a more natively unified OEMS; Burton Taylor suggests many do not expect LiquidityBook and Portware to become fully integrated immediately.
Perceived modernity/cloud-native: LiquidityBook is cloud-native, while Portware is sometimes characterized as legacy in industry commentary.
Terminal-based trader network effects: Bloomberg’s ecosystem remains a differentiator for some trading workflows.

Market adoption signals

Burton Taylor indicates Portware is seen more frequently than LiquidityBook in some contexts, but both are less commonly encountered than CRD or Eze in OMS contexts—suggesting FactSet is not the dominant OMS incumbent.