The boxed CRM couldn't pass regulator requirements.
A leasing company ran on a boxed CRM that failed central-bank requirements: lease documents were assembled by hand and monthly reporting was compiled from spreadsheets.
We built a custom CRM on the client's own cloud, on PostgreSQL, with a compliance matrix at the core: the regulator's requirements are built into the data model and the processes, so the system is inspection-ready by design. Lease documents are assembled from templates using deal data, recurring reports are produced without manual spreadsheets, and the existing leasing calculator is integrated so calculations live in one loop with the deals.
The data was fully migrated off the boxed system. Before, the platform and the data belonged to the box vendor and compliance was patched around the tool; now the system runs on the client's cloud and is fully theirs, documents are generated rather than assembled, and monthly reporting is produced automatically instead of being a monthly manual job.
What was in the way
- ✗The boxed CRM failed central-bank requirements
- ✗Lease documents were assembled by hand
- ✗Monthly reporting was compiled from spreadsheets
- ✗The system and the data lived on someone else’s platform
What the system does
Compliance matrix
Regulator requirements are built into the data model and processes — the system is inspection-ready.
Document generation
Lease documents are assembled from templates using deal data.
Automated reporting
Recurring reports are produced without manual spreadsheets.
Leasing calculator
The existing calculator is integrated — calculations live in one loop with the deals.
How it fits together
The engineering behind it.
Compliance as the data model
Regulator requirements are the structure of the data and processes — not a checklist bolted on top.
Migration off the box
Historical data was carried over from the boxed CRM into the new system.
The client's cloud
Deployed on the client’s infrastructure — the code and data are theirs.