A Real Estate Platform Folded an Acquired Mortgage Business Into Its Files.com Site—Without Centralizing Administration

A North American real estate platform company supplies real estate teams with their technology platform and the back office around it, from CRM, transaction management, and marketing through accounting, legal, HR, recruiting, and training.

The strategy is to bring the whole homeownership journey onto one platform: brokerage, mortgage, title, insurance, and home services. A company built that way keeps adding businesses. And each business it adds arrives with its own counterparties, its own regulated file flows, and its own IT team.

An Acquisition Arrives With Its Own Counterparties

The company acquired a mortgage business that trades loan files with institutional counterparties, among them some of the largest fixed-income asset managers in the market, a major insurer, and a loan-trading platform. That exchange is the acquired business’s day-to-day work, and folding it in posed a structural question rather than a technical one. Let the acquired business run its own transfer infrastructure, and the parent accumulates a separate estate with every deal it closes, each with its own credentials, keys, and audit story. Pull the work into the parent, and a small central IT team becomes the administrator of another company’s daily counterparty exchange, standing in the path of every folder change and every new counterparty.

The parent was already running its counterparty file exchange on Files.com, including an automated pipeline that pulls PGP-encrypted financial files from a major banking counterparty’s SFTP server into the company’s ERP every night.

The fix had to give the acquired business’s own IT team real administrative control over its own counterparty folders, under the parent’s security policy, without handing it the run of the parent’s site. The parent extended the Files.com site it already governed rather than standing up anything new.

A Walled Section of the Parent’s Site, Run by the Acquired Business’s Own IT

Using Files.com’s Partner capability, the parent carved out a scoped space on its existing site for the acquired business. Inside it, the acquired business’s IT team administers its own client folders, one per counterparty, alongside an inbox where valuation documents are uploaded. The loan-file exchange runs over SFTP, the protocol its institutional counterparties already speak.

The administration is scoped in both directions. The acquired team creates and manages folders within its own space and nothing beyond it. The parent keeps site-wide governance, with every entity’s files encrypted in transit and at rest and retained under the same policies as the parent’s own counterparty pipelines.

Files.com became the boundary layer: one platform and one set of controls, with administration delegated along the corporate structure instead of concentrated in the middle.

The Next Acquisition Is a Partner Space, Not a Platform Project

With the acquired business live, the parent replaced the choice between a second transfer estate and a central-IT bottleneck with a delegated section of the platform it already ran.

• The acquired business’s counterparty loan-file exchange runs on the parent’s Files.com site, administered end to end by its own IT team. The parent’s central team is not in the path of its folder changes or its counterparty onboarding.
• The acquired business’s loan files move to and from asset managers, an insurer, and a trading platform, while valuation documents arrive through a governed inbox.
• Both entities’ exchanges sit under one security posture, encrypted in transit and at rest, with transferred records retained on the platform.

File Transfer That Moves With the Org Chart

The parent’s whole model is absorbing more of the homeownership journey, and before Files.com, every absorption carried a file-transfer cost paid by hand. Now the platform boundary moves with the company. An acquired business gets a scoped section of the parent’s Files.com site, its own administrators, and the parent’s governance, and its counterparty exchange stays its own team’s work instead of becoming central IT’s.

Folding an acquisition into the parent’s file transfer did not mean migrating its work into a central team. It meant giving the acquired team its own room on the parent’s platform, with administration delegated to where the work is and governance kept where the accountability is.