About Legarch
The structure should survive the signature.
Legarch is built around a single position: an agreement is data. That it also reads as text is a consequence, not the point.
Why we built it
Existing tools end at the signature
E-signature tools are built to get a signature in place. Once it exists the work is done, and the result is a PDF.
That is where the information stops being usable. The amount, the notice period and the revenue share are in the file, but only as text on a page. To learn which agreements carry more than three months' notice, someone has to open them and read.
We built the opposite. The agreement is assembled from versioned clauses and typed fields, and that structure remains after signing.
What we believe
An agreement is data that happens to be readable by people
Not a document that happens to be stored. The difference decides what you can ask afterwards.
We also believe negotiation should mean choosing among terms someone already approved — not rewriting paragraphs under time pressure. The chosen variant is recorded, not reworded.
Fulfilment of an obligation is asserted by a person. The system never guesses that something is done.
Where we are
Early, but in production
We are early. The system runs in production on real agreements, and we build on it every week.
We hold no certifications and claim none. The security page states a state per control — what exists, what is being drafted and what has not started.
Company details
- Legal name
- TODO_LEGAL_ENTITY_NAME
- Company number
- TODO_ORG_NUMBER
- Registered address
- TODO_REGISTERED_ADDRESS