Part 8: Capstone

Putting It All Together

The preceding thirty-nine chapters have built a comprehensive understanding of regulatory technology — its history and foundations, its specific applications across identity verification, financial crime prevention, risk management, trading compliance, and emerging technology, and its strategic, organizational, and ethical dimensions.

The capstone section brings this knowledge to bear on realistic, integrated problems that do not fit neatly into any single chapter's scope. Real RegTech challenges are not chapter-sized. They require the simultaneous application of technical understanding, regulatory knowledge, strategic judgment, and implementation skill. The capstone projects are designed to develop and assess precisely this integration.

Chapter 40: The Integration Chapter

Chapter 40 provides a synthetic overview of how a complete RegTech stack — KYC, AML, regulatory reporting, market surveillance, and the governance layer that sits above them — fits together as an integrated system. It addresses the integration challenges that do not arise when studying each component in isolation: data sharing across systems, alert correlation across domains, unified audit trails, consolidated management information, and the organizational design questions that determine whether a sophisticated technology stack functions as a coherent compliance program or as an expensive collection of disconnected tools.

Chapter 40 also provides the final development of the three characters whose journeys have run through the book. Maya, Rafael, and Priya have each reached a different kind of maturity by the end of the text — not conclusions, because compliance programs are never finished, but recognizable moments of synthesis.

The Three Capstone Projects

The capstone projects are extended, integrative assessments designed for graduate-level or professional development programs. Each project requires substantial independent work — research, analysis, design, and written communication — and is calibrated for approximately 15–25 hours of effort.

Capstone Project 01: Design a KYC/AML RegTech Program for a Fintech Startup

You are Priya Nair, engaged as a RegTech consultant by a UK-licensed fintech startup preparing to launch a consumer payments product. The firm has a payment institution license from the FCA, 40 employees, no existing compliance infrastructure, and a plan to onboard 50,000 customers in its first year. Your task is to design its complete KYC/AML RegTech architecture — from customer identity verification through transaction monitoring to SAR filing capability — within a £250,000 first-year technology budget.

This project draws on Parts 1, 2, and 3 of the textbook and requires integrating knowledge across Chapter 6 (KYC), Chapter 7 (AML transaction monitoring), Chapter 8 (sanctions screening), Chapter 10 (customer risk rating), Chapter 11 (SAR case management), Chapter 35 (program strategy), and Chapter 36 (vendor selection).

Capstone Project 02: Build a Regulatory Reporting Pipeline

You are a regulatory technology lead at Cornerstone Financial Group, tasked with designing and partially implementing a regulatory reporting pipeline for MiFIR transaction reporting. The pipeline must extract transaction data from three source systems, transform it to conform to the MiFIR XML schema, validate it against regulatory rules, and generate the submission file for daily delivery to ESMA's reporting infrastructure. Using Python, you will build the core components of this pipeline and document its design for governance and audit purposes.

This project draws on Parts 1, 3, and 5 of the textbook and requires integrating knowledge across Chapter 5 (data architecture), Chapter 13 (regulatory reporting), Chapter 18 (MiFID II requirements), and Chapters 23 and 26 (NLP and explainability for data quality monitoring).

You are Maya Osei, conducting a formal vendor evaluation for Verdant Bank's next-generation AML transaction monitoring platform. Your task is to design and execute the complete evaluation process — from requirements definition through market assessment, RFP scoring, due diligence, and final recommendation — and to present your recommendation to Verdant's Board with a supporting business case.

This project draws on Parts 2, 6, and 7 of the textbook and requires integrating knowledge across Chapter 7 (AML transaction monitoring), Chapter 29 (algorithmic fairness), Chapter 35 (program strategy), Chapter 36 (vendor selection), Chapter 37 (change management), and Chapter 38 (ROI).

Using the Capstone Projects

The capstone projects are designed for multiple learning contexts:

Self-directed learners can work through the projects independently, using the detailed briefs and deliverable specifications to structure their work. Each project includes suggested research sources and self-assessment rubrics.

Academic programs can use the projects as major assessments, with instructors using the assessment rubrics provided. The projects are designed to be genuinely differentiated at the graduate level — there is no single "right" answer, but there are demonstrably stronger and weaker responses.

Corporate learning programs can use the projects as team exercises — each project can be completed by a small group with different members taking ownership of different workstreams — or as individual assessments within compliance professional development programs.

Professional development contexts can use the projects as frameworks for real-world work: Capstone 01 maps directly to the experience of a consultant designing a startup compliance program; Capstone 02 maps to a regulatory reporting transformation project; Capstone 03 maps to a formal vendor procurement process.

A Final Note

The RegTech field will continue to evolve after this text was written. Regulations will change. New technologies will emerge. The specific details of particular frameworks — the notification timelines, the model risk guidance, the fairness testing requirements — will be updated and refined. What will not change is the need for compliance professionals who can think across the technical, regulatory, ethical, and organizational dimensions of this work simultaneously.

That integrative capability — the capacity to hold all these dimensions together and make good judgments in complex, ambiguous, high-stakes situations — is what the thirty-nine chapters of this book have tried to develop. The capstone projects are the test of whether it worked.

Good luck.