Enterprise Coopetition

Partnering with the companies you appear to compete with

"People talk about the office of the CFO, but the reality is the office of the CFO doesn't exist," Pedro Franceschi says.¹ He contrasts the sell side, where a chief revenue officer has "an ivory tower called RevOps" that aggregates revenue-tool decisions under one umbrella, with finance, which has no equivalent. Procurement, FP&A, accounting, and treasury make decisions in isolation from one another, so a vendor cannot walk in and tell a buyer to rip out the travel system and the procurement system at once. The buyer already runs systems, chosen by different silos, that any new tool has to play well with, and that is the argument for cooperating with the firms you appear to compete with: the enterprise buyer is served better by two integrated products than one monolithic one.

The one plus one equals three move

Franceschi frames Brex's response as partnerships with the incumbents of adjacent workflows. He describes a travel and expense partner where a shared customer already has a card on file: making that a Brex card and integrating the two products means "100% of travel spend reconciles automatically," with a single virtual card per booking mapped to the right general-ledger account, department, and trip, and "no accounting work for you." He describes a comparable procurement partnership that combines card provisioning, contracts, and reviews into one purchasing experience for customers with complex procurement flows.

The division of labor is the load-bearing part of his account. Brex owns the financial infrastructure, which he lists as underwriting, risk management, card back-office, settlement, payments, treasury, capital markets, and global issuing, and offers it to the partner, while the partner owns the workflow it does best. His stated reason is that "you can't assume a single company does it all given the complexity of Fortune 500 buyers." He also presents the posture as hard-won rather than obvious, saying it "took years" to accept being "stronger together than competing" on the bounds where the products overlap.

Where the pattern is unstable

Franceschi is direct about the tensions in his own account. He notes that coopetition is unstable because a partner with overlapping native capability is "tomorrow's overlap," so the arrangement holds only while the shared-customer win outweighs the incentive to grab the whole account. The approach also sits in tension with the opposite bet, the compound or single-vendor thesis that argues the integrated company wins on exactly the reconciliation seams coopetition has to engineer around. The mechanism connects to the forward-deployed engineer model in that the defensible asset is the owned infrastructure and the customer relationship rather than the workflow software any partner could build, positioning Brex as the financial substrate under other companies' products rather than a single product competing feature for feature.