[ DEBT_CAPITAL_MARKETS ]

Bond Issuance & Investor Platform

2026Finance & Capital MarketsIn-depth

What it is

Onboarding, deal workspace and investor portal for private debt issuance.

Client work is shown without identifying imagery

[ THE_PROBLEM ]

Why this existed

Private debt issuance runs on email attachments and spreadsheets. Nobody is certain which version of the term sheet is current, and an incorrectly onboarded issuer is a compliance problem rather than a bug.

[ WHAT_WE_BUILT ]

What we built

A multi-step onboarding wizard with draft persistence, field-level and cross-field validation, and a verification step — issuers and investors take different paths through it. From there a deal workspace for live issuances, an investor portal, and an admin panel over the whole platform. Auth and access rules are unit-tested, as is the onboarding state machine and its validators — a deliberate choice on a product where an incorrectly-onboarded issuer is a compliance problem, not a bug.

Multi-step onboarding wizard with draft persistence across sessions
Field-level and cross-field validation with a verification step
Separate onboarding paths for issuers and investors
Deal workspace for live issuances
Investor portal scoped to the investor's own deals
Admin panel across the platform
Unit-tested auth rules, onboarding state machine and validators

[ HOW_IT_IS_USED ]

How a company uses it

An arranger or trustee moves issuance off email and spreadsheets: issuers self-onboard with validation at the door, investors see only their own deals, and the audit trail exists by construction.

Built with

ConvexReactBetter AuthVitest

[ COMMON_QUESTIONS ]

Questions clients ask

Why unit-test the onboarding flow specifically?

Because of what it costs to get wrong. On most products a broken form is an annoyance. Here, an issuer who completes onboarding with invalid or unverified details creates a compliance exposure that surfaces much later and is expensive to unwind. Testing the state machine and the validators was proportionate to that risk.

How is investor data kept separate?

Scoping is enforced server-side rather than by hiding UI. An investor sees only their own deals because the query is bounded, not because the link is not displayed. For a platform handling private placements that distinction is the whole security model.

Can it fit our existing issuance process?

The onboarding wizard and the deal workspace are structured to be reconfigured — the steps, fields and validation rules are the parts that vary between arrangers. That is normally where the discovery work goes.

[ RELATED_WORK ]