Skip to content
Skip to content

Method

How we think about the number

Escalake is opinionated about a narrow problem: the price adjustment written into a long commercial contract. These are the ideas the product is built on.

01

The number is a shared fact, not a position

Both sides should compute and confirm the same figure. If they cannot, that gap is the finding, and it belongs on the record where both parties can see it.

02

Interpretation is human. Arithmetic is not

A person decides what a clause means and which indices it points to. Once that is fixed, the maths must be deterministic and identical on every run, with every component shown.

03

Every number needs a version and a date

Official statistics are revised. A value is only meaningful alongside the version you used and the day you received it. Escalake keeps preliminary, final and revised, always.

04

The record must outlive the software

The output is a document for finance, legal and an auditor. It should make sense on its own, without a login to Escalake, years after the adjustment was made.

05

A disagreement is data, not a dead end

Questions and declines stay attached to the adjustment they concern. The history shows what was asked, by whom, and how it resolved. Nothing important happens in a side channel.

06

Automate the mechanism, not the judgement

Escalake removes the spreadsheet and the retyping. It does not decide whether an adjustment is fair or whether a clause was well drafted. That stays with the parties and their lawyers.

Built on those six ideas.

See how they show up in the product.