MCO and the expensive art of joining the dots

The bank had a system for tracking licences. It also had emails, spreadsheets, PDFs and Word documents. According to MCO’s account of the project, the internal system amounted to a “glorified spreadsheet”. A new employee arrived; somebody needed to identify the licensing requirements. An employee moved; somebody needed to do it again. The information existed. Keeping it useful required a small procession of people.

There is something wonderfully familiar about this predicament. An institution can have an abundance of information and an acute shortage of answers. The documents are present. The handoffs are the problem. MCO, short for MyComplianceOffice, sells software for this gap between knowing something and doing something about it.

The spreadsheet that knew too little

In the Australian bank’s published case study, the change was practical. MCO connected licensing management to HR data. New hires, transfers and departures could trigger notifications automatically. Stakeholders gained a dashboard of licensing status, updated daily. The company describes the result as hours saved each day.

This is a vendor-authored, anonymous account, so the reported benefit deserves that qualification. Still, it explains the product more clearly than a parade of adjectives. Instead of asking a person to discover that something had changed, the workflow began with the change itself. A licence record became part of a process.

That distinction matters for MCO’s customers: banks, asset managers, investment firms, insurers and private funds operating under demanding oversight. The daily work includes employee trade requests, gifts, outside business interests, counterparty checks and evidence for reviewers. A beautifully arranged archive cannot, by itself, make those tasks happen.

A platform born from the handoff

Brian Fahey had seen this pattern from inside financial services. In a 2020 RegTech Insight interview, he described teams receiving a budget and a short deadline to address a regulation. They built a solution. Another issue produced another solution. Integration became tomorrow’s project, and tomorrow proved remarkably elusive.

“never really a project or a budget to integrate them later”

Brian Fahey · RegTech Insight interview, 2020

The company’s official history traces MyComplianceOffice’s lineage to TerraNua, a Fidelity Investments division, in 1998. It identifies 2008 as the year MCO moved out of Fidelity under Fahey’s guidance. Its early independent focus was affordable SaaS employee compliance for small and mid-market American firms. The ambition widened to third parties and transactions as the platform and customer base grew.

MCO’s expertise sits where financial conduct and software design meet. A trade record, an employee disclosure and a business relationship need consistent identities before a reviewer can sensibly connect them. Shared data is the unglamorous premise behind its platform. Anyone who has reconciled two lists of supposedly identical customers will appreciate the ambition.

Four questions, one working record

MCO now organizes its offering into four suites. Know Your Employee handles conduct matters such as personal trading, gifts, political contributions, outside business activities and communications. Know Your Transactions covers surveillance, deal review, insider information and financial-crime monitoring. Know Your Third Party addresses screening, assessment and relationship management. Know Your Obligations ties requirements to policies, controls and assurance.

Consider an illustrative situation: an employee asks permission to buy a security while the firm is handling a sensitive engagement involving its issuer. The useful question is whether the employee’s request can be checked against relevant restrictions. MCO’s Personal Trade Manager describes precisely this sort of machinery: configurable pre-clearance, watch and restricted lists, post-trade rules and recorded workflow actions.

Its capture methods include direct broker feeds, online account access, manual entry and optical character recognition of statements. That variety reveals a stubborn reality of automation. The world does not supply every record in the format your system prefers. Coverage requires several routes in, followed by checks that the information arrived.

The same logic extends beyond trading. Third-party onboarding needs follow-up as relationships change. Obligations management needs a connection between a requirement, the policy addressing it and the evidence that the control operated. MCO is selling the ability to keep those relationships visible over time.

Buying the missing pieces

Expansion has included acquisitions. Governor Software joined in 2021, bringing governance oversight and visual mapping of regulations. MCO completed its acquisition of Schwab Compliance Technologies in May 2022, adding employee trading and code-of-ethics expertise. The acquired product became MyComplianceTechnologies.

Fairwords followed in 2023, adding communications protection technology, including proactive policy guidance while employees type. In August 2024, Swiss provider Pythagoras Solutions extended MCO’s KYC and anti-money-laundering capabilities. Each purchase addressed a different stretch of the compliance map.

The distinction MCO asks buyers to notice is its shared infrastructure across that breadth. It is a proposition about architecture, rather than proof that every function beats every rival. StarCompliance competes in employee conflicts, trading and accountability. COMPLY offers employee and firm compliance, alongside services. Behavox concentrates on AI compliance and conduct surveillance. A buyer’s shortlist depends on the actual work to be done.

An anonymous Dublin proprietary-trading customer offers a small example of MCO’s expansion model. Already using employee compliance, it wanted fewer systems and stronger regulatory-change capabilities. MCO’s case study says the ability to add obligations management to the existing platform helped settle the choice. The appeal was continuity of work, not merely another purchase.

The cost of connecting everything

MCO sells B2B SaaS through tailored demonstrations and commercial scoping. Firms can buy individual modules or combinations and add capabilities as their needs change. That makes the relevant buying question a specific one: which workflows, users, jurisdictions and connections are in scope?

The price of the platform is negotiated. A useful evaluation therefore needs to count implementation work as well as the subscription: data preparation, integration, rule configuration, training and ongoing review. Those are buying considerations, not a published MCO fee schedule. The company’s buyer FAQ recommends clarifying scope, implementation and commercial packaging.

At company level, the sums are more visible. On September 23, 2026, MCO announced more than $100 million in strategic growth financing from Accel-KKR Credit Partners. This is debt financing. The stated uses include expanding the technology team, developing products and AI capabilities, and extending market reach. It is not a disclosed equity valuation.

Six days later, MCO appointed former RegEd co-founder and CEO John Schobel as President. The announcement also reported 22% revenue growth from 2024 to 2025 and more than 100 new client firms over that period. Those figures suggest demand for the proposition; they do not measure an individual buyer’s return.

A useful alert needs a human

The first thing to fail need not be data capture. Sometimes it is the reviewer’s patience. In another MCO customer account, an American asset-management business wanted to replace an expensive communications provider with limited surveillance and too many false positives. MCO says it presented the solution, answered technical questions and began implementation within three weeks. That is a reported start, not a promise of a three-week completed deployment.

MCO’s recent AI work includes intent-based communications monitoring, trade-alert summaries and policy assistance. Its September financing announcement also describes digital-asset and prediction-market personal trading capabilities. These extend the questions a compliance team can ask. Their usefulness still depends on capture, configuration and the decisions that follow.

The lesson a reader can copy is modest: follow one real case through a demonstration. Start with the event. Check the identity, the rule, the escalation, the reviewer and the retained evidence. See where someone must re-enter information. See whether the outcome can be explained later.

Connected software has less value when the underlying records are incomplete, ownership is unclear or nobody has time to investigate. A firm with a narrow requirement may prefer a specialist tool. MCO’s case becomes stronger when several compliance processes share people, entities and decisions. The dots already exist. The work is making their connections useful.