Audit trails as a competitive moat for fiduciaries.

A pattern we've watched develop with our fiduciary customers, anonymised and condensed: the firms who win the long, complex mandates aren't necessarily the ones with the best advisors — they're the ones whose advisors can show, in a sentence, exactly what was done with each document and when.

The shift in what clients ask for

Five years ago, a sophisticated client asking about your record-keeping might have wanted to see your engagement letter and a signed NDA. Today the question is different: how would you reconstruct the file if you had to, and how quickly? The implicit follow-up — whom you'd be reconstructing it for — is rarely the firm itself.

We hear three triggers behind the shift. Family-office succession committees vetting custodians for a generational handover. Audit committees at corporate clients formalising vendor due-diligence questionnaires. Regulators, in some cantons, sending more pointed questions about how mandates are documented.

What an audit trail actually has to prove

A useful audit trail isn't a log file. It's an answer to four questions, in order:

1. Who created or last modified each record? By name, by role, with cryptographic attestation that the identity wasn't spoofed.
2. Who has accessed it, and when? Including read access, including failed attempts.
3. What was changed, in what order? Versioned diffs, not "last edited 12 March".
4. Can the chain of custody be exported? In a format that someone outside your firm — an auditor, a regulator, a successor — can read without your help.

The moat isn't keeping the records. It's being able to prove, at any moment, exactly what happened to each one.

Why most legacy DMS vendors can't answer

Document management systems built before 2018 were built around a different premise: keep documents safe, version them, share them. Most don't have an immutable audit log — they have a database table that an admin can edit. Most don't have a chain-of-custody export — they have a screenshot of a "history" tab. The gap shows up the moment a real audit requests an answer.

What we built, and how

Every action inside My Swiss Keeper writes to an append-only log signed by the user's hardware-bound key. The log itself is anchored every 24 hours to a public time-stamping authority, so neither us nor anyone else can rewrite the past without it being detectable. When a fiduciary needs to produce a custody chain — for an audit, a handover, a court — it's a one-click export, with cryptographic proofs included.

We didn't build this because clients asked for it line-by-line. We built it because the firms that we admired in the early customer interviews were already keeping a manual version, by hand, in a spreadsheet they showed us in confidence. The product is just an honest version of what serious firms were already doing badly.