Case study / Financial services

An investor book moved off spreadsheets, to the penny

An investment firm's whole book of investors, brokers and trades moved off spreadsheets and a legacy platform into a CRM built around how a trade happens, with every figure reconciled to the penny.

Industry
Fixed-income investment
Used by
Operations, finance and sales
Our part
Advise, design, build and manage
Built with
Zoho CRM, Python, Microsoft 365
Status
Live, in daily use

01 / The industry

A book of investors, in several currencies

Some investment firms raise money by issuing bonds, sold to investors through networks of independent brokers. Each investment is a trade with its own currency, rate and term. Every investor has identity and anti-money-laundering checks to record, and every broker has commission terms to honour.

At any moment the business has to know who holds what, in which currency and through whom, and be able to prove it.

02 / The problem

Two spreadsheets and a platform it barely used

The firm paid for a specialist servicing platform it barely used. The real records lived in two large spreadsheets, and they had grown messy over the years: investor counts that disagreed between sources, joint and corporate holders packed into single cells, near-duplicate names, missing bank details, and mistyped codes that would silently break any import.

The brief was one system that:

  • holds investors, brokers and trades, and the people behind each;
  • takes every trade through the same steps, in the same order;
  • reports each bond in its own currency;
  • arrives with every record from the old sources, proven, not assumed.

03 / What we built

A CRM shaped around the trade

  • Investors as legal parties. Sole, joint and corporate holders, each with the people behind them, their check dates and their contact preferences.
  • Brokers and their terms. Commission terms, including sliding scales, and a restricted role for the sales team that sees only the brokers.
  • A trade workflow with gates. Eight stages from enquiry to settled. Bank details come before compliance review, identity and anti-money-laundering checks are recorded before clearance, trades outside the limits need a director's override, and nothing can change once a trade settles.
  • Bonds and their rates. Rate schedules for each bond, with nightly jobs that keep each trade's current rate, and each investor's and broker's status, up to date.
  • Reporting and email. Dashboards for operations, finance and sales, and email connected to each person's Microsoft 365 mailbox.

The team was handed a user guide, a training pack and a recorded walkthrough.

04 / How it works

A migration you can prove

  • A pipeline with a hard gate. Python scripts profile the data, clean it and validate it before anything is imported, and the run stops on any failure. The validator caught a renamed column that would have detached every trade from its investor, and a stray space that would have dropped most of the bank details.
  • Check the live system, not the import report. On one load the import reported complete while skipping more than half the trades. A check against the live data caught it within minutes.
  • A control copy. The old platform was archived read-only before the move, so three separate sets of totals could be compared.
  • Money modelled once. Face value, cash received and accrued interest are kept apart, and totals stay in each bond's own currency rather than being converted to sterling.
  • References that give nothing away. Trade references combine the date with letters from an alphabet that avoids look-alike characters, with no running counter to reveal volumes.

05 / Where it is now

Live, reconciled and in daily use

The CRM went live about ten weeks after the first call, and the old platform was retired. Every trade from the spreadsheets and every reference from the old platform is in the new system. Every bond but one matched the old platform to the penny; the exception was a single trade that had been paid but not yet settled. Every difference found along the way is named and explained in the reconciliation.

  • 10 weeksfrom first call to go-live
  • 100%of trades accounted for, by reference
  • 0ptolerance in the reconciliation
  • 8trade stages, each with its own gate

It is now on a monthly support plan.

06 / More work

Other case studies

Manufacturing

Keeping machine know-how when engineers move on

Machine knowledge lived in manuals nobody could search and in a few senior engineers' heads. We built an assistant that answers from the manuals and breakdown history, cites the exact page, and refuses rather than guesses.

AI · Search · AWS

Vehicle leasing

Salary sacrifice car leasing, joined up end to end

A vehicle leasing provider ran salary sacrifice schemes on a CRM, with manual steps at every stage. We built the pricing engine, portal, partner integrations and automation that take a deal from first quote to monthly mileage.

Platform · Integration · AWS

Commercial fit-out

Live dashboards from a decade-old project system

A commercial fit-out contractor's project and finance data sat in a decade-old system with fixed reports. We built live dashboards into it for forecasting, work in progress and daily changes, plus wallboards in its offices.

Data · QuickSight · SQL

07 / Contact

Running the business from spreadsheets?

Tell us where your records live today, and what has to be true once they have moved. We will tell you how we would prove it.