Innovation June 2026 Book Extract

Data science and engineering: powering innovation in financial services

The institutions that will lead financial services in the next decade are not the ones with the most data. They are the ones that have learned to move from asking what happened to knowing what is about to happen. That shift is architectural, cultural, and strategic simultaneously.

Author: Declan Sheehy

Back to Insights

This is an adapted extract from Disruptive Innovation in Financial Services by Declan Sheehy (published April 2026, ISBN 978-1-919487-10-6). The full framework, including detailed treatment of operational architecture, regulatory strategy, and go-to-market execution, is available in the book. Available on Amazon.

Eighteen years at HSBC Alternative Investments taught me something that takes most institutions far longer to learn: data is not a byproduct of financial services operations. It is the raw material. The firms that treated it as an afterthought, something to be reported on quarterly and filed, were perpetually reactive. The ones that treated it as infrastructure, something to be engineered, governed, and deployed, were building genuine competitive advantage whether they knew it or not.

The digital revolution has made this distinction existential rather than merely strategic. Financial institutions now ingest vast volumes of structured and unstructured data across every function. The question is no longer whether to invest in data science and engineering. It is whether you are building the capability fast enough to use what you already have.

From hypothesis to product

The traditional model kept analytics at arm's length from operations. Insights arrived retrospectively, usually in a report that described what had already happened well enough to inform the next quarter's planning. That model is structurally broken in a market where the relevant signals are moving in real time.

Modern financial institutions have shifted to agile methodologies that treat a data hypothesis the same way a product team treats a feature: validate it quickly, deploy what works, discard what does not, and iterate. A commodities trading desk can hypothesise how weather patterns affect electricity markets, build that signal into a model using cloud data infrastructure, and have it running in production within weeks. That speed is not just a technical achievement. It is a commercial one. The hypothesis that takes six months to reach production has usually been arbitraged away by the time it arrives.

The innovation journey from hypothesis to commercial product follows a consistent arc. Collaborative ideation, ensuring the hypothesis is grounded in a real business problem rather than a technical curiosity. Rapid prototyping using real-world data, not sanitised test sets. Transition to minimum viable deployment via automated continuous integration and delivery pipelines. Continuous validation as market conditions change. And full industrialisation with appropriate governance once the model has proven its commercial value.

Each stage requires both data science capability and data engineering infrastructure. You cannot prototype rapidly without a well-architected data platform. You cannot industrialise without the governance processes already in place. The two disciplines are not sequential. They need to be built together.

The strategic case for in-house capability

There is a recurring temptation in financial services to buy analytical capability rather than build it. The vendor proposition is always compelling: faster to deploy, lower upfront cost, someone else's problem to maintain. The difficulty is that the most valuable analytical work in financial services is inseparable from proprietary data, and proprietary data is exactly what a vendor cannot replicate.

Institutions that have built internal data science teams have created something genuinely defensible. Proprietary datasets sourced from Bloomberg, MSCI, and global exchanges, enriched through careful integration with open-source and company data, become intellectual property that compounds over time. A model trained on ten years of your own client behaviour, transaction history, and market interaction is not something a competitor can acquire. It can only be built.

The close collaboration that in-house teams enable between data scientists and business units is also underestimated. An external vendor builds to a specification. An internal team builds to a conversation, iterating in real time as the business need evolves. The adoption rate and commercial relevance of analytical products that emerge from that kind of collaboration is consistently higher than those delivered against a fixed brief from outside.

That said, not every institution has the scale, budget, or talent pipeline to build a full data science function internally. This is where Data Science as a Service has emerged as a credible complement. A DSaaS model provides the analytical infrastructure, ML pipelines, and model management tooling as a managed service, deployed within the firm's own cloud environment so proprietary data never leaves the perimeter. The firm retains ownership of the data and the models. The service provider handles the engineering, the tooling, and the iteration cycle.

For those with genuine analytical ambition but without the headcount or expertise to sustain a dedicated team, DSaaS closes the gap between intent and capability without requiring the firm to build everything from scratch. The strongest implementations combine this external infrastructure with a small internal team that owns the business questions and validates the outputs, preserving the collaboration that makes analytical products commercially relevant while removing the engineering burden that most firms underestimate until they are already committed to it.

Where data science is changing the outcome

The use cases now span every segment of financial services, and the common thread is the shift from description to prediction.

Trading desks employ machine learning algorithms on enriched proprietary datasets to uncover market opportunities that fundamental analysis misses. In energy commodities, for example, the relationship between weather, grid infrastructure, and spot pricing contains signal that rules-based systems cannot fully capture. Advanced analytics also optimise execution strategies: reducing transaction costs, improving timing, and contributing to risk-adjusted returns in ways that are measurable and attributable.

Institutional investors are integrating alternative datasets into the investment process at a pace that would have been operationally impossible five years ago. ESG ratings, satellite imagery, climate data, and shipping traffic all inform asset allocation decisions for pension funds and asset managers willing to build the infrastructure to ingest and process them. For limited partners evaluating private equity and infrastructure investments, advanced forecasting tools are beginning to change how liquidity events are anticipated and how secondary market activity is timed.

In wealth and asset management, AI-driven portfolio construction is moving personalisation from a marketing concept to an operational reality. Investment strategies tailored to a client's goals, life stage, and risk preferences, updated dynamically as circumstances change, are no longer the exclusive domain of ultra-high-net-worth relationships. Predictive analytics is making them scalable.

Retail platforms and digital banks are using behavioural analytics to deliver financial guidance that is genuinely responsive to how individual customers actually manage money, not how a product team assumed they would. Real-time credit scoring using machine learning has expanded access to lending for customers who would previously have been declined by models built on thin or non-standard credit histories. Explainable AI is making these decisions transparent enough to meet regulatory standards without sacrificing the precision that makes them valuable.

Across all of these, generative AI is beginning to change how institutional knowledge is accessed and how client reporting is produced. Large language models applied to comprehensive data lakes can surface relevant analysis in seconds that would previously have required hours of manual research. The speed gain is real. So is the governance challenge that comes with it.

Engineering: the part that makes it real

Every data science capability described above depends on data engineering infrastructure that most institutions significantly underinvest in. The model is only as good as the pipeline that feeds it, and pipelines built on fragile, inconsistently governed data foundations produce results that cannot be trusted in production.

Centralised data management solutions, Azure and Delta Lake being the most widely adopted in financial services, combined with orchestrated pipelines, provide the scalability and flexibility that serious analytical work requires. Rigorous continuous integration and delivery practices ensure that models can be deployed, updated, and rolled back without disrupting the operational systems they feed. These are not glamorous capabilities. They are the difference between a proof of concept that impresses in a demo and a model that is still running reliably eighteen months after deployment.

DataOps, MLOps, and responsible AI frameworks are increasingly the vocabulary of the regulatory conversation as well as the technical one. The EU AI Act, the FCA's evolving expectations, and the PRA's model risk management supervisory statement all reflect a regulatory direction that assumes institutions can explain, audit, and intervene in the AI-driven decisions that affect customers and markets. Building that capability after the fact is significantly harder and more expensive than building it in from the start.

What this requires beyond technology

The institutions that are genuinely succeeding with data science and engineering share characteristics that go beyond their technical stack. They have built cultural alignment between research, engineering, and business domains so that analytical products are built to solve real problems rather than demonstrate capability. They treat data as a managed asset with governance, lineage, and quality standards, not as a byproduct to be warehoused. And they have leadership that understands the difference between a data strategy and a data science team, and has invested accordingly in both.

The firms still approaching this as a technology procurement exercise, buying tools and hoping the insight follows, are consistently disappointed. The ones treating it as an organisational capability to be built over time, with the patience to do it properly and the discipline to govern it well, are creating advantages that compound.

Data science and engineering have become core strategic pillars in financial services. The shift from reactive reporting to proactive, real-time decision-making is not a future state to plan towards. For the leading institutions, it is already the present. The question for everyone else is how much of that distance is still closeable, and how quickly.

Adapted from Chapter: Data Science and Engineering: Powering Innovation in Financial Services

Book: Disruptive Innovation in Financial Services by Declan Sheehy BSc CFA (April 2026)

Foreword by Graham Rodford, CEO, Archax. ISBN 978-1-919487-10-6.