← All case studies
CASE STUDIES · 2022

Bond Analytics Platform

Zero to enterprise-ready in two months. Multiple funding rounds followed.

An institutional analytics platform that scores bond issuance and stock debt health via a proprietary rating algorithm. Banks, asset managers, and enterprises use it to price corporate debt and run ex-post analysis against realised market outcomes. Multiple funding rounds closed.

ENTERPRISE 2022 Live
01 Overview

Overview

An institutional analytics platform that scores bond issuance and stock debt health via a proprietary rating algorithm. Banks, asset managers, and enterprises use it to price corporate debt and run ex-post analysis against realised market outcomes. Multiple funding rounds closed.

02 The Challenge

The Challenge

Two months, zero codebase, banks on the other end of the demo. The vendor API was out of budget, so the data path ran on quarterly Excel exports, manually downloaded, format-drifting, no API safety net. The proprietary rating logic had to be defensible enough for institutional buyers to stake decisions on, and ex-post analysis had to be first-class because that's what they actually buy.

03 The Call We Made

The data-vendor licence was the constraint that shaped the architecture.

The institutional data vendor was the source banks expected, and the licence was out of budget for a startup. Every downstream decision absorbed that. Quarterly Excel exports, manual downloads, schema drift between releases. We built around it: idempotent reruns, row-level validation that caught format drift before it corrupted ratings, and a snapshot-shaped Postgres schema so ex-post replay stayed audit-grade. The licence shaped the architecture, the architecture shaped what the platform could promise.
04 What We Did

What We Did

Constraint: institutional analytics on a startup's licence budget, with Excel as the only realistic source. The non-obvious call: design the data path around idempotent reruns and audit-grade ex-post replay, not streaming freshness, that's what banks actually use. Concretely: Excel ingestion with row-level schema validation that catches vendor format drift before it corrupts ratings, the proprietary bond and stock debt-health engines, NestJS API, React dashboard, JWT auth, Postgres schema built around quarterly snapshots. Test-driven end to end. The proprietary algorithms were complex enough that without the suite the platform wouldn't have been buildable, every new requirement could quietly break three others. What it bought: institutional buyers who could replay every rating call against realised outcomes.

05 Outcomes

Outcomes

Speed 2 months 0 to Enterprise
Business Multi-round Funded
Architecture & Flows

Production architecture

Three lanes. The institutional data vendor on the left, exported to Excel each quarter and immutable between releases. Wavect-built ingestion, schema validation, and the two proprietary rating engines in the middle, snapshotting into Postgres for ex-post replay. NestJS API and React dashboard on the right, delivering to banks, asset managers, and enterprises. Proprietary algorithm highlighted in yellow.

The diagram illustrates a simplified high-level architecture and omits confidential implementation and security details.

06 What We Learned

What We Learned

When the licence budget pins you to Excel and the cadence is quarterly, the architecture inverts. You stop optimising for streaming freshness and start optimising for idempotent reruns, schema-drift resilience, and audit-grade ex-post replay. That is what institutional finance actually runs on.

Tech Stack
Tags
FinTechTradFiData Analytics

Want outcomes like this?

Tell us what you're building. We'll tell you whether we're the right team for it.

 Book a call