Engagement
Prove it on your own book
Before you commit, you run your own portfolio through the engine and set the result beside your own. Every difference is explained, line by line, by a named person.
The steps
Five steps, in the open
Each step says what you bring, what we do and what you leave with. The first two cost nothing. You can stop after either.
-
Scoping call
Week 0
No charge
Thirty minutes to agree what would be run, on what, and by when.
- You bring
- The regime, the deadline and the systems that the engine has to fit.
- We do
- A methodologist for your regime and an engineer who knows the interfaces.
- You leave with
- A one page plan, with what we would run and an indicative price.
-
Sample book
Weeks 1 to 2
No charge
A portfolio of yours that holds no personal data, run in a sandbox.
- You bring
- A portfolio with no personal data in it. A synthetic one is fine, and so is a reduced copy of a real one.
- We do
- Run it, and send back each figure with its derivation and the receipt for the run.
- You leave with
- A result that you can reproduce on your own machine, and a first look at whether it is the one you expect.
-
Parallel run
Weeks 3 to 10
Priced
A full period of your own data, run beside the process you have now.
- You bring
- The data as you would file it, for the periods that you choose.
- We do
- Run it beside your process. Every difference becomes a case, with the line where it first shows, the clause, the cause and who has to change something.
- You leave with
- A list of closed cases, and a figure that agrees with yours or a reason that it should not.
-
Validation pack
Weeks 8 to 12
Priced
What model validation and internal audit ask for, written while the run is fresh.
- You bring
- The questions of your validators, in writing, as they arise.
- We do
- The derivation of each figure, the clause map, the statements that apply with their levels, the tests behind them and the receipts of the run. We answer in writing, so the answers are on record.
- You leave with
- A pack that a validator can follow without us in the room.
-
Going live
From week 13
Licensed
The engine runs where you put it, and each release says what it changed.
- You bring
- A choice of where it runs: on the device, at the edge, or inside your own estate.
- We do
- Release notes that name the publication each release answers. Older releases keep reproducing their receipts, so you choose when to move.
- You leave with
- A named person who explains a difference when you find one.
What a licence includes
Priced by regime, not by run
We price by regime and by legal entity. A number that you hesitate to recompute is a number that you cannot check, so a run costs nothing. Work out a price.
-
Every release
All releases for the term, including each change to a rule when a regulation moves.
-
The record
The statements for your regimes, kept current, with the tests and the proofs behind them.
-
Receipts
A receipt for every run, and the means to check one without us.
-
Named people
A methodologist for each regime and an engineer for each interface, by name.
-
Your choice of place
On the device, at the edge or in your estate. The price does not change with the place.
-
No lock-in on evidence
The receipt format is public. Anyone can check a receipt in about thirty lines of code, with or without a licence.
Questions
What people ask first
If yours is not here, ask it on the scoping call or write to us. A question that we cannot answer is useful to us.
Can the engine run without sending anything to you?
Yes. The calculators on this site run in your browser and send nothing. A licensed engine runs where you put it, which can be a network with no way out. We receive nothing from it.
Only when you choose the edge does data reach us. It goes over TLS, is worked on in memory and is not stored.
What happens when we find a difference?
It becomes a case. A case names the line where the figures first part, the clause that governs it, the cause, and who has to change something. The cause is sometimes ours, sometimes yours, and sometimes the text, which can be read two ways.
If the cause is ours, the fix is released and the changelog says so, with the date. If the cause is a statement on the verification page, the statement is corrected there too.
Can we reproduce last year’s figures?
Every result comes with a receipt. The receipt holds the inputs and the rule parameters that the figure was computed with, so a later release still reproduces it, to the last bit.
You keep the receipt. Anyone who has it and the inputs can check it without us.
What does our model validation team get?
The validation pack, written during the parallel run. It has the derivation of each figure, the clause that each rule implements, the statements that apply with their levels, and the tests that back them.
It also gets a way to ask. Questions go to a named methodologist, in writing, and the answers are kept with the pack.
What happens when a regulation changes?
The specification feed picks up the change and files it against the regimes it touches. A methodologist lists the rules that move, a test is written before the code, and a release says which publication it answers.
The earlier release stays available. You can run the two side by side before you move.
Who owns the results?
You do. We keep no copy of what you run in your own estate, and we do not train anything on it. What we keep from the sample book is what you agree to in writing, and we delete it when you ask.
How do you price it?
By regime and by legal entity. There is no charge for each run, for each user or for the volume of data, because a number that you hesitate to recompute is a number that you cannot check.
The scoping call ends with an indicative price. The parallel run is priced separately and is credited against the licence if you go on.