The least glamorous object in finance may be the spreadsheet that quietly became a trading system. It begins as a helpful grid. Then someone adds a macro, another desk copies the file, a third person becomes the only human who knows which tab matters, and suddenly millions of dollars are passing through a tool that was never asked to be infrastructure. Genesis Global has built a serious business around that familiar little horror story.
Founded by former investment-bank technologists Stephen Murphy and James Harrison, Genesis makes an application-development platform for financial markets. The company is easy to misread as a generic low-code vendor with sharper suits. It is more specific than that. Genesis supplies the repetitive parts of financial software - data models, permissioning, audit trails, messaging, reporting, monitoring and interfaces - along with ready-made market components and people who know why a bond workflow behaves nothing like an online shopping cart.
Its customers include banks, asset managers, broker-dealers, exchanges, clearing houses, data networks and fintechs. Public names include Citi, ING, StoneX, Itaú Securities, B3, LCH, Neptune Networks and T. Rowe Price. In 2022, when the company announced its $200 million Series C, it said it had 50 customers and thousands of developers using the platform. It does not publish a current customer count.
Two bad choices, plus a third door
Financial institutions traditionally face a grim menu. Buy a large vendor package and accept its opinions about how the business should work. Or build a custom system, hire a small civilization of engineers and spend years maintaining every entitlement screen and data connector. The first route creates vendor dependence. The second creates a private museum of technical debt.
Fast start, fixed shape
Packaged software brings proven functions but can make differentiation, integration and upgrades awkward.
Perfect fit, long bill
Custom code gives control, while the institution owns every test, upgrade and midnight incident.
Buy to build
Reuse the regulated plumbing, then customize the workflow and interface where the business has an edge.
Genesis calls its answer “buy to build.” The phrase is marketing, but unusually useful marketing. Developers assemble applications from reusable services and can extend the generated code rather than being trapped inside a visual editor. The architecture is event-driven, the deployment can run across cloud environments, and the platform is tuned for jobs where both latency and auditability matter. Generic low-code products such as Mendix, OutSystems and Microsoft Power Apps compete for broad enterprise workflows. Packaged capital-markets systems from firms including Murex, Broadridge and Nasdaq Calypso solve established industry problems. Genesis occupies the gap: a specialist kit for making software that is custom without being completely handmade.
“The platform eliminates repetitive, non-differentiating work core to many financial industry applications.”Nikhil Joshi, Citi, on the bank’s 2022 strategic investment
A billion-message reference call
The cleanest evidence comes from Neptune Networks, a fixed-income data distributor connecting more than 30 dealers with more than 80 buy-side firms. Neptune’s earlier core technology had become the first thing to fail: it lacked the features and scale needed for new datasets and analytics. Genesis rebuilt the platform from the ground up in six months. According to the companies, the resulting system has processed roughly one billion messages a day since launch and can exceed 18,000 FIX messages a second.
The delivery method is less cinematic and more copyable. The Genesis and Neptune teams held daily stand-ups, refined the backlog every other day and kept design conversations frequent enough to catch wrong assumptions early. The platform supplied the reusable structure; capital-markets specialists supplied the questions. Since the first release, Neptune has added API access, portfolio trading, credit-default-swap coverage and real-time analytics. This is the platform thesis in miniature: speed on day one matters, but inexpensive change on day 600 matters more.
send axe data
normalizes + streams
analyze in real time
The product shelf is really a set of clues
Genesis sells the underlying Application Platform, but its named solutions reveal the work clients actually pay to fix. Trade Allocation Manager handles the unlovely minutes after execution: capturing block trades, matching them, splitting allocations across accounts, calculating fees, resolving exceptions and sending clean records toward settlement. StoneX began using it in 2020 to connect front, middle and back offices across multiple asset classes. A web version arrived in 2024, aimed at easier deployment and maintenance.
The Credit Insurance Application replaced spreadsheet-heavy processes for ING in the United States, Hong Kong and Singapore. ING then reused parts of that application for a fund-finance system. Primary Bond Issuance addresses a different kind of speed. New corporate bond deals can move from announcement to pricing and allocation in as little as two hours, while managers juggle data from several providers, email, analytics, compliance and order systems. PBI puts those fragments in one live view. T. Rowe Price deployed a customized version in 2025, and the product won a TradingTech Insight award in 2026.
Then there is Genesis Create, the visual and AI-assisted builder. A user can define entities, fields, views, permissions, services and interfaces, generate a working project, and continue in a browser-based cloud workspace or a local development environment. This matters because Genesis does not pretend that visual assembly finishes the job. The generated project is inspectable and extensible. Its documentation even leaves “to do” markers for the human work still required. That small admission is more credible than another demo in which a prompt produces a bank by lunchtime.
The invoice nobody publishes
What does it cost? Genesis does not publish list prices or verified implementation fees. Enterprise contracts depend on scope, deployment, integrations, support and how much Genesis or a partner builds. Any neat dollar figure would be fiction. The visible price tag is the company’s own financing: about £3 million in Series A capital, a $1.8 million extension, $45 million in Series B funding, a $200 million Series C led by Tiger Global, then $20 million from Bank of America, BNY Mellon and Citi. In round numbers, roughly $270 million has funded the wager.
Not public. A buyer should compare the full contract with the avoided cost of custom infrastructure, legacy licenses, support staff, integration work and delayed launch. “Ten times faster” is a vendor claim; a signed scope and measured baseline are better procurement tools.
The business model appears to combine enterprise platform access, prepackaged applications, customization and delivery services. Systems integrators widen the labor pool. DXC provides developers and project specialists; Luxoft has adapted Genesis components for trade matching, reconciliation, bond portals and electronic trading. Cloud partners include AWS, Azure and Google Cloud, while HERE, formerly OpenFin, adds an enterprise browser and interoperability layer.
What changed the buyer’s mind
The conversion usually begins at a weak seam, not with a grand rewrite. At ING, it was spreadsheet risk across three regions. At Neptune, an aging core could no longer absorb richer products and higher volumes. At StoneX, separate post-trade systems did not talk cleanly to one another. At a large Japanese bank described by Genesis, Excel-based workflows created audit and authentication problems across a global securities operation.
Those failures change the calculation. A spreadsheet is cheap until it becomes a control problem. A legacy platform is stable until a new product requires six months of surgery. A vendor package is safe until its data model dictates the business. Genesis does not need customers to believe every system should be replaced. Its better argument is incremental: keep the settlement engine or market-data source that works, put a modern workflow over it, replace the risky end-user tool, then reuse the components elsewhere.
“The controls, auditability, and delivery speed were exactly what we needed.”Jean-Maurice Elkouby, ING
AI meets the compliance department
Genesis now describes its platform as AI-native, a fashionable adjective that deserves inspection. The useful pieces are more prosaic. Genesis Create uses focused agents inside a constrained component framework. Applications can expose approved operations through Model Context Protocol, with authentication and optional approval. The company’s pitch is that an AI model may help assemble logic or trigger a live workflow, while permissions, audit trails and deterministic services remain underneath.
That framing shows what changed inside Genesis, too. In 2021 the ambition included taking low code into fields such as healthcare and manufacturing. The current company has leaned hard into capital markets and the difficulty of moving AI from prototype to production. James Harrison, who became CEO in August 2025 after co-founder Stephen Murphy stepped down, has made production discipline part of the sales story. In 2026 Genesis reorganized product, engineering, delivery and sales leadership around that task.
The distinction is important. Code generation is becoming cheap. Knowing which code may touch a position, who may approve it, how it fails, and what an auditor can reconstruct is not. Genesis is betting that its decade of accumulated components becomes more valuable when AI makes the first 70 percent of an application easier and the final 30 percent more conspicuous.
The part worth copying
A bank cannot copy Genesis’s component library overnight. It can copy the order of operations. Start with one workflow whose failure is visible, expensive and measurable. Map the surrounding systems before choosing what to replace. Separate commodity plumbing from the small portion that creates an advantage. Put permissions, monitoring and audit into the foundation. Run short design loops with the people who do the work. Measure the second release, not only the first launch.
- Choose the weak seam. A spreadsheet, duplicate entry step or unscalable data feed makes a better first target than “digital transformation.”
- Keep the useful core. Wrap stable systems and replace risky workflows before attempting a wholesale platform migration.
- Standardize the boring parts. Identity, audit, messaging, deployment and observability should not be rebuilt for every desk.
- Demand an exit route. Generated code, APIs and cloud choice matter only if the client can operate and extend the result.
The approach is a poor fit when a standard package already matches the workflow, when transaction volume is modest and customization has little value, or when the institution lacks product owners who can make quick decisions with engineers. Component speed cannot rescue unclear ownership, bad source data or an integration nobody is authorized to change. Nor does “cloud agnostic” make migration free. Every environment still needs testing, security review and operations staff.
Genesis’s real competition, then, is not merely other software. It is the temptation to tolerate the spreadsheet for one more quarter, renew the inflexible vendor contract, or commission another blank-sheet build. The company’s most persuasive answer is not the $270 million it raised. It is the awkward financial workflow that went live in months, survived the morning rush and was easier to change the next time.
Keep clicking
See the platform, its documentation, company updates and working demonstrations.