From first contact to legal operations.
Contextual proposals, human review, approval, and documents connected to the CRM.
Explore the full demo ↗
What needed to work
Preparing proposals and converting a lead into actionable work requires consistent context across sales and operations.
My contribution
CRM, proposal, document, and operations interfaces assembled into an anonymized demo. Source contribution and portfolio adaptations are recorded in the source inventory.
How the pieces connect
- 01Full CRM interface
- 02Original API contracts
- 03Isolated PostgreSQL state
- 04Validated inference + approval
- 05PDF from current state
Engineering choices
- Explicit approval before the final document.
- One repository serves server pages and APIs.
- Legal data, companies, and amounts are entirely synthetic.
Two ways to explore
1Lead → proposal → review → approval → PDF.
2Conversion → customer → work order → tasks → Kanban.
What the demo demonstrates
Original: Legal CRM, proposals, tasks, and operations. Original client identity and data were removed.
Demo: Fixtures, visitor isolation, reset, translation, demo generation, and inference adapter.
GitHub · source repositories may be private ↗Clear boundaries
The demo provides no legal advice. Simulation is the default; live inference requires an authorized session. Integrations and external acceptance are simulated.
State belongs to your visitor session. Restart from the demo bar.