What our first 100 firms taught us about document collection

The first time we watched a real firm use Clivanta, a manager in Limassol sent a client a request for a bank confirmation and a signed representation letter, then sat back to see what came in. Twenty minutes later the client had uploaded a scan of last year’s letter to the wrong item. Not a bug. Not a training gap. The ask simply wasn’t clear enough, and the client did the reasonable thing with the information in front of them.

That small moment contained most of what we’ve since learned. As more firms came onto the product and the volume of requests grew, the same lessons kept surfacing. None of them were surprising in hindsight. All of them changed the product.

The ask has to explain itself

A firm knows exactly what “the VAT reconciliation” means. The Client, uploading twice a year under time pressure, does not. Left to guess, they send something adjacent and plausible, and you’ve spent a round-trip discovering it’s wrong.

The pattern was consistent enough that we stopped treating instructions as optional. Every Request Item carries its own instructions and, where it helps, a sample format — the exact layout you expect, the entity it should cover, the period it belongs to. A well-written ask removes an entire cycle of back-and-forth before it starts.

This is also why the Pack matters more than we first thought. A Pack is your firm’s reusable standard procedure for a service type — the set of Request Item templates, written once. When you write good instructions into the Pack, every Period inherits them. You’re not being clearer one email at a time. You’re being clear by default.

”Outstanding” has to be a stored fact

Early on we assumed firms would mostly care about what had arrived. They didn’t. The number that governs a partner’s week is what’s still missing, and we watched teams derive it by hand — cross-referencing an inbox against a folder against a spreadsheet, each of which told a slightly different story.

Derived state drifts. A file lands in a folder but nobody marks the tracker, so the item looks open when it’s satisfied. Or the reverse: a client is chased for something they sent last week. Both failures come from asking “does a file exist here” instead of “what did we decide about this item.”

So outstanding is read from the stored, audited status of each Request Item — outstanding means requested or needs revision, nothing else. The worklist, the client’s portal, the reminders and the exports all read the same status. One source of truth, and no reconciling two systems that were never going to agree.

Clients bulk-dump, so matching has to be easy

We designed for the tidy client who answers one item at a time. Plenty of clients don’t. They wait, then reply to ten requests with a single zip of forty files, half of them named some variation of final.

In email that’s a sorting nightmare that lands on your most expensive people. So we built for the dumper directly. Bulk uploads go into an unassigned pool, and the AI pre-checks suggest which Request Item each Document likely belongs to, using document type, date and entity name, with duplicates flagged by file hash. The Firm confirms or overrides — the AI never assigns anything as final on its own. The pile still arrives. It just doesn’t have to ruin an afternoon.

Reminders only work if they read live status

The first version of any reminder is “please send your documents.” It gets ignored, because it asks the client to do the firm’s bookkeeping — to work out what’s still needed and act on it.

The reminders that get acted on name the specific items still outstanding, because they read from live per-item status. They chase what’s genuinely missing and nothing else. We added a deterministic cadence — a nudge on Day +2, then +5, then +12, then weekly — that escalates and CCs the Client Owner, and, importantly, a way for a client to pause a reminder with a logged acknowledgment. The cadence quiets, the item stays open, and it comes back on its own. Chasing that respects the relationship gets tuned in, not out. We wrote more about that in reminders that chase for you.

Firms want the record to be defensible, not just tidy

We thought we were building a faster way to collect documents. We were, but the feature firms kept pointing at was the trail. When a file is questioned months later, “it’s in the email somewhere” is not an answer. Partners wanted to show who asked, who sent, who reviewed and who accepted, each with a timestamp.

That reshaped the core distinction in the product. A Document is a raw file a client uploaded. Evidence is a Document the Firm has accepted against a Request Item — permanent, attributed, timestamped. Acceptance is a decision with a name on it, superseded files are retained as previous attempts rather than deleted, and every action lands in an immutable activity log. Tidy is a side effect. Defensible is the point, and it’s the theme running through the audit evidence problem every Cyprus firm knows.

Passwordless wins adoption, quietly

The last lesson was the least glamorous and possibly the most important. A portal that asks an occasional user to create and remember a password loses them. They forget it, the reset fails the evening before a deadline, and they retreat to email — at which point none of the structure above exists.

Passwordless magic-link access removed the single biggest reason clients abandoned the portal. There’s nothing to reset at 9pm. The client clicks a link, sees exactly what’s needed, and uploads. Adoption isn’t won with a clever dashboard. It’s won by removing the small frictions that send people back to their inbox.

What the pattern adds up to

Read together, these lessons point the same direction. The system works when the occasional user at the Client can succeed without help, and when the firm’s record survives scrutiny without reconstruction. Every decision we’ve made since has been in service of those two things.

You can see the whole model in the product. But the summary is simpler than the feature list: make the ask clear, make the status true, and make the record hold.

Build for the client who logs in twice a year, and the firm gets its evenings back.