About us

We've both spent time in medtech. We know the frameworks are rigorous for good reason, the standards exist to protect patients, and they deserve to be taken seriously. What we couldn't accept was how much friction the work accumulates. Documents live in disconnected silos. Knowledge sits in the heads of a few experts, or in the Dropbox of an expensive consultant. Every audit becomes archaeology. The rigour is real; the tooling around it lags behind.

Regulated teams work inside tools that rarely model the structure of this work. Most compliance software is a document store with approval routing attached. The actual structure, regulatory mandates, traceability chains, cross-references, applicability decisions, lives outside the tool, in spreadsheets, Word files, and the memory of the one person who last ran the audit. We built Lumidocs because the missing piece is structural. Speed and correctness stop trading against each other once the structure is modelled in the system.

The tooling had never caught up to that reality. Documents lived in folders. Version history told you a file had changed while the reason and dependencies stayed elsewhere. Knowing which regulations informed which paragraph, or what a guideline update touched across your QMS, was a manual exercise every time. That gap is where we saw the opportunity.

The rigour that makes AI trustworthy in software — every change tracked, every decision attributed, every dependency explicit — is exactly what was missing in compliance tooling. We built the same foundation into Lumidocs. The technical choices are a fair signal of how we think: carefully, from the ground up.

It took time to build this properly. Once the structure is in place, setup is fast, and what you get is a compliance system you can genuinely control while harnessing the power of AI.