Legal AI implementation timelines in 2026: how long each tool really takes
Implementation time is the cost nobody quotes. It does not appear on a rate card, it is paid in your team's hours rather than the vendor's invoice, and it varies by more than two orders of magnitude across tools sold into the same department.
The spread
| Tool | Time to useful | What the time is spent on |
|---|---|---|
| GenieAI | Same day | Nothing; it works on a document you upload |
| Spellbook | Same day | Installing a Word add-in |
| Termly | Under an hour | Answering a questionnaire |
| Xakia | Days | Loading matters and setting intake fields |
| Contractbook | Days | Uploading agreements and setting renewal dates |
| SpotDraft | 2 to 4 weeks, reported, often included | Templates and approval routing |
| HotDocs | Weeks | Building and testing templates |
| Juro | Weeks | Templates, approval rules, integrations |
| Luminance | Weeks | Loading and tuning against a document estate |
| Ironclad | Months | Workflow configuration, with an internal owner |
| Agiloft | Months | Configuration, charged separately |
| Onit | Months | Matter, spend and workflow across a department |
| Icertis | Months | Sourcing workflow, supplier data, ERP integration |
| Anaqua | Months | Portfolio migration and prosecution workflow |
| Harvey | Months | Deployment consuming partner time before delivery |
The pattern: configuration is the cost
Tools that work on a document you hand them start same-day. Tools that encode your process need that process described, agreed and built, and the description is the slow part rather than the building.
This is why the length tracks the invoice so closely. Agiloft charges configuration separately and it is usually the larger half of the first year. Anaqua's total cost of ownership is reported to add 40 to 60% on top of the licence. Neither figure appears in a price comparison, and both are real money.
SpotDraft is the useful counter-example. Implementation is reported at two to four weeks and often included, against configuration charged separately and measured in months elsewhere in its category. Where a vendor includes implementation, it usually means the tool has fewer decisions to make, which is a capability statement as much as a commercial one.
What actually delays a deployment
- Not having written down the positions the tool is meant to enforce. Most playbook and approval-routing projects stall here, and no vendor can supply this for you.
- No named internal owner. A configurable platform without one produces a half-built system nobody trusts, which is worse than the spreadsheet it replaced.
- Data migration from whatever holds the agreements now, which is usually worse than expected because nobody has audited it.
- Integration sign-off from IT and security, which runs on its own calendar rather than the project's.
- Agreeing who approves what. This is an organisational question wearing a software costume, and it takes as long as the organisation takes.
Questions worth asking before signing
- Is implementation included, or quoted separately? Ask for the figure in writing either way.
- How many hours of our time does it assume, and from whom? A number that assumes a full-time owner for eight weeks is a different purchase from one that does not.
- What is the date we can do the first real piece of work on it, rather than the go-live date?
- Which named customer of yours, at our size, went live in the time you are quoting? Ask to speak to them.
- What happens to the timeline if our templates are not ready? This is the most common cause of overrun and the one vendors price around rather than solve.
Method
Timings are taken from vendor statements and reported deployments, cross-checked against the same assessments behind our guides, and checked in September 2026. "Time to useful" means the point at which the tool does a real piece of work, not the contract start date or the kickoff call. Where a vendor publishes no figure and we could source none, the tool is left out rather than estimated.