Alquimia Tech / OmniLex
End-to-end SaaS with AI-assisted engineering
How Paulo built a legal-document automation SaaS from concept through production while using AI coding agents as implementation support.
Useful for teams evaluating engineers who can combine product ownership, architecture, implementation, testing, and practical AI-assisted delivery.
- Source review
- Approved resume and experience notes supplied on 2026-08-28
- Confidentiality
- Generalized for public professional use
Context
OmniLex is a legal-document automation SaaS built through Alquimia Tech. The product focused on reusable smart templates, structured document generation, optional blocks, placeholders, mappings, calculations, and generated DOCX/XML output.
Paulo’s role
Paulo took the product from concept through production. He owned architecture, requirements, decomposition, review, debugging, validation, tests, and acceptance while using AI coding agents as implementation support.
Constraints and risks
- The product had to turn legal-document structure into maintainable software behavior.
- Template logic needed to remain understandable as document complexity increased.
- AI assistance could speed implementation, but Paulo remained responsible for correctness and production quality.
- The result had to be usable as a real product, not only a prototype.
Decisions and trade-offs
The implementation treated AI-assisted development as an execution multiplier, not as a substitute for engineering judgment. Paulo kept responsibility for breaking work down, reviewing generated code, debugging failures, and validating behavior against acceptance criteria.
The trade-off was that review and test discipline remained non-negotiable. That made AI assistance useful without letting generated code become an unowned risk.
Outcome and evidence
The approved source material states that Paulo built OmniLex from concept through production and used AI coding agents while retaining ownership of architecture, requirements, review, testing, and production validation.
Evidence limits
This page avoids private product details, legal-domain specifics, and unpublished implementation internals. It is based on the approved resume and experience notes supplied on 2026-08-28.
