About Repovyn

Built by someone who watched attorneys spend their time on the wrong work

Most legal review bottlenecks are not judgment problems. They are comparison problems — and comparison is something a well-defined rule set handles better than a paralegal with a 40-page playbook.

Why Repovyn exists

Luca Bertrand spent several years in legal operations at a mid-size software distributor in Kansas City. The company processed several hundred commercial agreements a year — NDAs, vendor MSAs, SaaS subscription terms — and the legal team was consistently the bottleneck on deal close.

The problem was not attorney capacity. It was that 70-80% of each review was clause-matching against a playbook: checking whether the indemnity cap was above the fee-paid threshold, confirming governing law, flagging auto-renewal notice windows below 90 days. Predictable, rule-based work that consumed the same attorney hours whether the contract was routine or genuinely complex.

Luca built the first version of Repovyn in early 2025 to handle that comparison work internally. After seeing it reduce first-pass review time from several hours to under 10 minutes on the same agreement types, he turned it into a product other legal teams could use. Repovyn is built and operated in Kansas City, MO.

Luca Bertrand, Founder and CEO of Repovyn

Luca Bertrand

Founder & CEO

Desk workspace with stacked contract documents and annotation tools
Our approach

What we believe about legal tools

Specific beats general

A system that knows NDA deviation patterns, MSA indemnity structures, and SOW acceptance criteria specifics is more useful than one that "understands contracts broadly." Repovyn is trained on commercial agreement types specifically — not general legal language.

Your playbook is the ground truth

We do not impose a generic risk framework. If your playbook accepts Delaware governing law for vendor contracts, that is not a flag. Repovyn applies the rules your legal team has defined — nothing more, nothing less.

Reports for attorneys, not data scientists

Output should be actionable the moment the attorney opens it: clause text, the specific rule it deviates from, and a suggested negotiation note. No score dashboards, no heatmaps, no AI summaries to interpret. The report is a work product, not an analytics view.

If your legal team reviews 200+ contracts a quarter, this was built for you.