We built this because we were the ones sending the chase emails.
Clivanta started as an internal tool in a working professional practice, where the team spent more hours reconciling a request tracker than reviewing the evidence it tracked.
Three principles we won't trade away
The request is the record
If it isn't attached to a request item, it didn't happen. One object carries the ask, the evidence, the conversation and the decision.
The client is a participant
Portals fail when they're built as a wall. Clivanta's client side is designed to be the easiest path, not the mandatory one.
Nothing is silently overwritten
Versions, not replacements. Reasons, not rejections. A reviewer in eighteen months should be able to reconstruct the whole story.
How we got here
- Before 2024
A spreadsheet nobody trusted
Every year-end became a second job — chasing documents, reconciling who-sent-what, re-explaining the same request for the third time.
- 2024
The first build
We built the first version inside a working practice to survive one brutal year-end. It was rough, but it held.
-
It survived the year
It got the practice through the year-end it was built for. Nothing fell through the cracks — and we knew we had something worth rebuilding properly.
- 2025
The rewrite
We rewrote it around request items and packs, after watching real firms live in the early build and hit its edges.
-
The client comes in
We opened it to the other side: a portal where clients and counterparts upload directly and see exactly what's outstanding, instead of living in your inbox.
-
It learned to chase
Automatic reminders meant the tool did the follow-up — the exact job that started all of this.
- 2026
Clivanta
The internal tool became a product. It opens to teams across industries — legal, finance, HR, insurance and more — with multilingual portals.