The Situation
Drew is building an AI-powered legal tech product targeting law firms. He needed demo workflows to show prospective clients what automated legal intake looks like in practice. Something to screen share on sales calls, record into Looms for outreach, and use as proof of concept when pitching firms.
His product didn't exist yet in a demoable state. He needed working demos that looked and functioned like a real system, built fast enough to support an active sales pipeline, but robust enough to hold up under scrutiny from attorneys who are trained to poke holes in things.
He had two specific use cases: automated billing workflows (invoice generation, payment tracking, client notifications) and document automation (retainer agreements, engagement letters, NDAs, conflict checks populated with client data automatically).
What We Built
Two fully functional n8n demo workflows with supporting PDF templates.
The billing demo workflow triggers on a simulated new client event, generates an invoice with the correct matter details, sends a payment notification, and logs the transaction. Each step is visible in n8n's execution view so Drew can walk prospects through exactly what happens at each stage during a live demo.
The document demo workflow takes client intake data and automatically populates four legal document templates: a retainer agreement, an engagement letter, an NDA, and a conflict check form. Each template is a real PDF with proper legal formatting that fills dynamically based on the client record. Drew can show a prospect: "Your new client fills out the intake form, and 30 seconds later these four documents are generated, named correctly, and stored in the client's folder."
Both workflows were built as importable n8n JSON files so Drew could run them in any n8n instance, modify them for specific prospect demos, and hand them off to his development team as reference architecture for the actual product build.
Results
2 working demo workflows ready for sales conversations. 4 legal document templates (retainer, engagement letter, NDA, conflict check). Importable n8n JSON files for flexibility across demo environments. Full documentation for product development team. Demo assets delivered within days to support active sales pipeline.
Tech Stack
What Made This Work
Demo workflows for a product that doesn't exist yet require a different approach than building production systems. The goal isn't reliability at scale. The goal is making a prospect on a sales call say "I want that." Every node in the workflow needed to be visible and explainable. Every document template needed to look like something a real law firm would use. The execution needed to be fast enough to demo live without awkward loading screens.
Building the demos as n8n JSON files rather than hardcoding them into a specific environment meant Drew could customize each demo for different prospect types. A personal injury firm sees different document templates than a corporate law firm, but the underlying workflow architecture is the same.