Company
DocumentMS leadership team
This page names the people accountable for DocumentMS product, engineering, information security and customer delivery. It also serves as the author reference for our guides: each byline on the site links to the profile of the person who wrote and reviewed it.
Why this page exists
Two reasons, and only one of them is conventional. The first is the ordinary one: enterprise buyers want to know who is accountable for the product they are about to depend on, and during a security review or an escalation the useful question is not who the founders are but who owns the decision you need made.
The second is that this page is the authorship backbone for everything published under Resources. A guide on electronic signature legality or GxP retention is written and reviewed by whoever holds the relevant accountability below, and is published under an organisational byline because that is what it actually is — reviewed work, not one person’s opinion. If you want to speak to the individual behind a particular piece, ask and we will introduce you.
Where accountability sits
- Product
- Owns what the product does and, more usefully, what it does not. Decides the roadmap, and is the person who will tell you plainly during an evaluation that a capability you need is not there rather than describing it as planned.
- Engineering
- Owns how the product is built and operated: the availability commitment, the release process, the recovery objectives and the restore tests behind them. Answers for the uptime figure published in the terms of service.
- Information security
- Owns the information security management system, the control evidence, vendor security questionnaires and incident response. This is the accountability a customer security team will want on the call, and the one that signs the answers you are given.
- Customer delivery
- Owns implementation, migration and support outcomes — including the scoping of a migration before it is sold, which is where most document management projects are won or lost.
- Information governance / records
- Owns the retention schedules, record classes and disposition logic in the product, and reviews the compliance and records content published on this site before it goes out.
Última revisión: 2026-09-01