Engineering · Custom business platform
Tender dossiers assembled from a repository, not by copy-paste
Responding to a tender means assembling an administrative, technical and financial dossier from scattered assets: expert CVs, project references, certificates. We replaced copy-paste assembly with a platform where each dossier is built from a document repository kept up to date once.
0
fake formats accepted: checks read the file content, not its extension
3
automated checks before every release
1×
experts, references and documents entered once, reused every dossier
GDPR
register, retention periods and handover documentation delivered
Before
- ✕A document estate scattered across office files, copied from one dossier to the next
- ✕Four versions of the same CV, with no way to know which one is current
- ✕A list of required documents never certain to be complete
- ✕Hours before a deadline, uncertainty becomes a risk of disqualification
After
- →The estate entered once: experts, references, projects, with their roles and specialities, reused for every dossier
- →Step-by-step assembly: required documents and the status of each one, so an omission is visible before the deadline, not after
- →Real format checks, on the content of the file rather than its extension: a renamed document does not pass
- →Business repositories administered by the client, with no developer involved
- →Every upload timestamped and attributed: a traceability no office folder ever had
- →Every business rule declared once, with the database as the authority: adding a category or a document type does not mean hunting down five copies of it
- →Permissions enforced by PostgreSQL itself, versioned migrations that verify their own result, three automated checks before every release
- →Security audit, full GDPR file and handover documentation: the client can take over, including without us
Next.jsReactTypeScriptSupabase/PostgreSQLSupabase StorageSupabase VaultPythonpandasClaude APIVercel
Entered once, reused everywhere