Contract review by vertical.

Why now

Generic contract-AI loses to vertical depth. Industry-specific playbooks win.

What the signal looks like

Repos with vertical-specific playbook libraries, redlining models, and contract-management integrations.

Public examples

We name publicprojects + categories only, never founders we track inside the paid product. The buyer’s edge stays inside the product.

• Spellbook for SaaS
• Lex Machina vertical shape
• Open-source legal-LLM libraries

What this displaces

A general-purpose AI tool that misses industry-specific risks.

How to validate it in an afternoon

Before committing build time or a thesis memo to contract review by vertical, run three cheap checks against public engineering activity. Each takes minutes and none require access to private data.

1. Count active builders. Search GitHub for repositories matching this category, then check how many accepted commits in the last 14 days. More than a handful of active teams means the category has energy, not just mentions.
2. Look for the hot, multiple deals per month pattern in funding. If funded companies keep appearing here, multiple funded companies are landing in this category per quarter right now. Cross-check the legal tech leaderboard to see whether any of the accelerators sit adjacent to this niche.
3. Test the one-quarter build cost assumption honestly: expect a quarter of sustained build time, usually two or three people, before first external users. If your calendar cannot absorb that, the opportunity is real but not yours yet.

The weekly signal feed tracks 10 Legal Tech sub-niches including this one, so the cohort side of this check can run continuously instead of manually.

Common questions about this niche

Buyer?

GC + legal ops at vertical-specific companies.

Pricing?

Per contract or per seat.

Defensibility?

Playbook + integration + reputation.