Financial-services marketing
A compliance-gated export CRM
A list-export CRM for a financial-services marketing business, where every export has to clear a compliance gate first.
- Services
- App or CRM
- Stack
- CRM chassis, Record completion, Export gate
- Updated
The export is the risky moment
This one is for a financial-services marketing business of our own. It needed a CRM for its records whose exports can only leave once they clear its compliance rules. The business stays unnamed here, and the picture above is a sketch rather than a screenshot.
In this line of work the export is the risky moment. Once a list leaves the system, anything wrong with it has left too.
Tiers, and one spelling for every name
The records also differ in how useful they are, so they needed tiers, and names that recur across the records needed one consistent spelling. So we built tiered records, a dictionary that keeps recurring names spelled one way, and a step that fills the gaps in a record before it can leave.
Features
What it does
Records sit in tiers by how useful they are.
A dictionary keeps the names that recur across the records spelled one way everywhere.
A list leaves only once it clears the compliance checks, and the gate is part of the export itself, not a step someone can skip on a busy afternoon.
It stood up on our CRM chassis first, so the build went into the parts only this business needed.
The gate is the export
Exports are gated. A list only leaves once it clears the compliance checks, and the gate is part of the export itself, not a step someone can skip on a busy afternoon.
Below, a replica over made-up records: the filters are the selection, a row can be left out by hand, and the export button stays locked until you have ticked every check.
Sample
Click through a sample
The app on its own screens, with made-up data. On a computer, the controls work.
| Name | Tier | Complete | Updated | Owner | Leave out |
|---|---|---|---|---|---|
| Orin Blakely | A | Yes | Today | Kim | |
| Sela Marchetti | A | Yes | Yesterday | Lee | |
| Dario Quintrell | A | Gaps | Monday | Kim | |
| Wren Castellano, on hold | B | Yes | Today | Lee | |
| Ines Halloran | B | Yes | Last week | Kim | |
| Tobias Renard | C | Gaps | Last month | Lee | |
| Maren Solberg | A | Yes | Tuesday | Lee | |
| Cyrus Adebayo | B | Gaps | Today | Kim | |
| Lior Benatar, on hold | A | Yes | Today | Kim | |
| Petra Vasquez | C | Yes | Last week | Lee | |
| Anouk Reyes | B | Yes | Monday | Kim | |
| Hale Okonkwo | A | Gaps | Last week | Lee |
The chassis did its job
We stood it up on our CRM chassis and built what this business needed on top. The chassis did the job it was built for: the base of the CRM was there from the start, with the rest of the build spent on the parts only this business needed.
Stack
- CRM chassisthe codebase behind the Tidewater sales desk
- Record completionfills the gaps before an export
- Export gatecompliance checks before any list leaves
Tell us what you are working on.
A few lines about your business is enough to start. We reply with questions and a plain next step.