01 LegalTech / AI / Product
Pravo365
Drafting contracts for a jurisdiction, not for a template gallery.
How can the creation of a complex legal document become a usable digital product?
Overview
Pravo365 is a digital product for drafting contract proposals in the Czech legal environment. It takes structured input from someone who knows what they need and returns a draft they can read, check and take further.
It is deliberately not an "AI lawyer". The product does not give legal advice and nothing in it suggests the draft is final.
Context
Contract drafting is document work: precise, repetitive, and unforgiving of small mistakes. It is also bound to a jurisdiction — a template written for one legal environment is not merely less useful in another, it can be wrong.
Most general-purpose document tools solve the formatting problem and leave the jurisdiction problem to the user. That is the wrong way round.
Idea
Narrow the product until it can actually be trusted. One legal environment, Czech. One language, Czech. A defined set of document types rather than an open text box.
The constraint is the feature. A system that only tries to produce Czech contract proposals can be checked against Czech expectations.
Process
The work splits into three parts that stay separate on purpose: collecting structured input, generating the document, and presenting the result for review.
Structured input matters most. A form that asks the right questions in the right order does more for output quality than any amount of post-processing.
The review step assumes the draft will be edited. Nothing in the interface performs finality it has not earned.
Technology
A generation pipeline behind a structured web interface, with the document assembled from validated inputs rather than from free-form prompting.
Reliability work — confirming that the same input produces the same shape of document — matters more here than model sophistication. A legal draft that varies unpredictably between runs is unusable regardless of how good any single run looks.
Current state
Live at pravo365.cz, in Czech. The scope is intentionally narrow and is extended one document type at a time.
What I learned
In this category, trust is built by what a product refuses to do. Every place the interface declines to sound authoritative makes the parts that do work more believable.
The narrow scope also made the engineering tractable. A general-purpose contract generator would have been easier to describe and far harder to verify.
Evidence
