illustrative use case, not a specific client
Which one is the final version?
Important documents lived in email attachments and shared folders with names like final_v3_REAL. Now each one has a history, an owner and clear access.
Documents & access control · the kind of thing I build
Contracts, quotes, SOPs, certificates. Most businesses have a handful of documents that really matter, and they usually live in email threads and shared folders where the naming convention is “add another _final”.
Before
Someone asks for the latest version of a contract. Three people send three different files. One of them has edits nobody remembers making. An important file gets overwritten, and the only backup is an old email attachment. Anyone with the folder link can see everything, including things they shouldn’t.
What the system does
- Versions, not copies: a document is uploaded once, and every update becomes a new version on top of the old ones.
- A clear history: each version records who changed it and when, so “who touched this?” has an answer.
- Undo for mistakes: deleting is soft, so anything removed by accident can be brought back.
- Access by role: finance sees finance documents, the warehouse sees warehouse documents, and the owner sees everything.
- Search: find a document by name, type or customer instead of digging through folders.
What changes day to day
There’s one place to look and one current version. Mistakes are recoverable instead of scary. And when a customer or an auditor asks for a document and its history, it takes a minute, not an afternoon.
How I’d build it
I’d start with the one type of document that causes the most pain, often contracts or quotes, and move just those into the system. Once people trust it, the rest follows.
Does this sound like your business? Tell me about it.
next story: The booking diary that stopped losing people