Skip to main content
A workflow takes a pile of documents and a handful of answers about your situation, runs a multi-step pipeline over them, and hands back finished work product: a DOCX memo, an XLSX log, a scored redline package, a draft motion. Everything in between (retrieval, extraction, scoring, synthesis, citation verification, rendering) runs unattended. You launch it and come back to the artifacts.

New here? Run one in ten minutes

A folder of NDAs to a finished review memo, start to finish.
There are two ways to get one.

Built-in workflows

25 pre-built pipelines maintained by Vaquill. Pick one, upload documents, answer a short form, launch. No configuration.

Workflow Builder

Chain 25 typed step types into your own pipeline, or describe it in plain English and let Vaquill draft the chain for you.
Screenshot of the Workflows gallery showing the built-in workflow catalogue grouped by category

The Workflows gallery: built-in catalogue and your custom workflows

​
Which one do I want

Use a built-in workflow when

The job is a recognizable legal task: reviewing a batch of NDAs, building a privilege log, drafting a motion, auditing vendors for privacy compliance. Someone has already thought hard about the prompts, the scoring rubric, and the output format.

Use the builder when

Your job is specific to your organization: a custom intake sequence, a firm-specific scoring pass, a chain that ends in your own DOCX template. Or you want to run a built-in-style pipeline with your own steps swapped in.
The two are not exclusive. A common pattern is to run a built-in workflow to see the shape of the output, then build a custom one that does the same thing against your own playbook and your own export format. Neither kind is billed per run. Both are covered by your subscription; see Plans, trial, and limits.

​
How they differ

​
What a run looks like

Both kinds share the same run machinery.
1

Launch

Pick the workflow, attach documents to its slots, fill in the inputs, and optionally scope the run to a matter.
2

Watch

The run streams progress: which step is executing, a percentage, and an audit event for every step start, completion, document processed, and artifact rendered. Cancel at any point.
3

Collect

Completed runs expose their artifacts as signed downloads, plus an on-screen results panel. Runs persist in your run history, so the work product stays retrievable.
Read Running a workflow for the mechanics that apply to every workflow, and Results and artifacts for what comes out the other end.

Agent Mode

One-shot autonomous research that picks its own tools. A workflow is the repeatable, auditable version.

Document Matrix

Several built-in workflows run a matrix under the hood. This is that engine on its own.

Playbooks

Negotiation playbooks feed the Contract Playbook Review workflow.

Matters and workspaces

Runs scoped to a matter save their output back into it.