Shape 01
Solutions
Agreements differ less between departments than between shapes.
A procurement agreement and a creator agreement can look nothing alike and still need exactly the same thing from the system. So we organise by what the agreement has to do, not by which team sends it. Three shapes, three different demands.
Shape 01
Recurring agreements with variants
The same agreement sent many times, where a few terms differ each time: creator agreements, consultancy agreements, supplier terms.
This is what clause variants exist for. The operator opens only the variants that are acceptable for that particular send. What comes back can therefore differ without anyone rewriting a paragraph.
All three agreements below trace back to the same template version. The difference is which variant was picked.
Shape 02
Agreements that require the right signatures
Board resolutions, powers of attorney, minutes. What matters is not how many people sign but which roles do.
A chair, a minute-taker, an adjuster, every board member. Legarch names the required roles and will not conclude the agreement until each named role has signed. A signature from someone outside the roster moves nothing.
The role is the requirement. The person is filled in against the role, not instead of it.
Shape 02
Agreements that require the right signatures
styrelsebeslut · ALMTRA-00073 / 5
ChairElvira Sandström2026-03-04 09:12signed
Minute-takerOskar Lindqvist2026-03-04 09:18signed
AdjusterMalin Ferrand2026-03-04 09:31signed
Board memberNils Aspegrenwaitingpending
Board memberSiri Wallmarkwaitingpending
Cannot conclude — two roles are emptyawaiting signature
Shape 03
Agreements that create obligations
Agreements where signing is the beginning, not the end: deliverables, payment terms, notice periods.
What each side undertook is registered separately from the text and carries its own state. Fulfilment is asserted by a person; it is never assumed by the system because a date has passed.
An obligation past its date changes state. It does not disappear and it does not fulfil itself.
Shape 03
Agreements that create obligations
In practice
What this means in practice
Four recurring situations, and which part of the system handles them. The entry points differ; the parts do not.
01
Creator agreements sent at volume
The form of payment differs per engagement: fixed fee, variable per job, or a share of revenue. Without variants the text is rewritten on every send, and three months later the amounts cannot be compared. With variants the choice stays a choice, and the payment sits in a typed field.
- Clause variants
- Typed fields
02
Board resolutions needing the right signatories
A resolution missing the adjuster's signature is not a half-finished resolution; it is not a resolution. The roles are named before the send, and the agreement cannot reach the active state while a role sits empty.
- Signatory roles
03
Consultancy agreements with varying notice periods
The notice period is set per engagement and has to be queryable later, not hunted for in a PDF. It sits in a typed field, and the obligation it creates carries its own state and its own follow-up.
- Typed fields
- Obligations
04
Powers of attorney other agreements point to
A power of attorney is itself an agreement in the system, with a reference code and a lifecycle. When someone concludes an agreement under it, that signature points at the power's reference, so authority can be traced afterwards without digging through an email thread.
- Signatory roles
- Audit log
Four entry points, the same three parts
What shape is your agreement?
Bring an agreement type you send often. We go through which terms vary, which roles must sign, and what becomes an obligation.