AION is the record of what your deal team has accepted — and whether it is still true.
From the first financial model to IC and financial close, the accepted case lives across Excel, advisor reports, emails and committee packs. AION holds it in one place: which assumption, on which model version, on what evidence, accepted by whom, and what is still open.
One entry in the record reads: EPC contingency 7% · Excel v14 · accepted by the Deal Lead on 2 June · basis: technical advisor estimate · open: contractor confirmation.
Excel stays the model. AION does not calculate.
Fragmented inputs
AION
The accepted case
A record around the tools you already use
Structured outputs
Every team has a working case. Almost none have a record of it.
Infrastructure teams rarely lack information. The problem is that the assumption, the model version, the evidence and the memo language all move at different times — and nothing holds the version the team actually agreed on.
Assumptions drift
The advisor's note says 11%. The model says 7%. The memo says 7%. Nobody is wrong — they were written on different days.
Context fragments
The model is in Excel. The evidence is in a PDF. The rationale is in an email thread. The decision is in a committee pack.
Materials go stale before IC
Someone re-reads the memo against the model to check that every number still holds. It is done by hand, under time pressure, days before the meeting.
Decision memory is lost
Two years later someone asks how 11% became the accepted number. The answer is in an inbox, if the person who owns it still works there.
By the time a transaction reaches IC, the accepted case is usually reassembled from files, threads and memory.
What AION will not do.
The limits are the product. A record is only worth relying on if it cannot quietly invent things.
It does not calculate
Excel produces every number. AION never computes a return, a ratio or a valuation of its own.
It does not decide
AION proposes; a named person accepts. Nothing changes the accepted case without a human decision on the record.
It refuses out loud
When a question cannot be answered from the accepted model, AION says so, names the cell it cannot resolve, and sends the work back to the analyst — rather than producing a number it cannot stand behind.
AION never advises, never approves, and never speaks for the team.
AION does not manage documents. It governs the accepted working case.
AION works around the tools you already use. It does not replace Excel, VDRs, Outlook, advisor reports, IC materials or the financial model. Nothing is migrated.
Disconnected. Hard to lock. Hard to reconstruct.
One relied-upon record of the accepted working case.
When an advisor note, a new model version, an email or a memo draft disagrees with the accepted case, AION puts the difference in front of the deal lead. The deal lead decides what happens. AION records the decision and flags anything the decision made stale.
Six stages, from setup to close.
Excel remains the calculation layer at every stage. AION reads, checks, proposes and records.
Set up once
The fund's own model templates, deal types and thresholds are profiled once and reused on every deal after that. AION applies the team's rules. It does not set them.
Read the package
When the sponsor materials arrive, AION reads them and proposes an assumption register: every decision-relevant value, with the document and page it came from. Each assumption gets an ID that never changes.
Populate and hand back
AION writes what it can into a copy of the fund's own model template, leaves the gaps empty and flagged, and reports the coverage. The analyst then works the model in Excel and uploads it back.
Admit the workbook
AION checks the returned model against the fund's template: which inputs it can write to, which outputs it can read, and what has broken. Every finding names a cell and can be checked by opening the file. Nothing downstream runs until this passes.
Govern the case
As advisor notes, emails and new versions arrive, AION flags what diverges from the accepted case and raises it for the deal lead. The deal lead confirms, revises, rejects or retires it. Each outcome becomes one entry in the decision record.
Keep materials aligned, then close
Before IC, AION checks the memo and the circulated pre-read against the accepted case and reports what is stale. At close, the whole record is preserved: every assumption, version, evidence item and decision, in the order it happened.
Ordinary value changes stay inside AION. Structural changes to the model go back to the analyst and through the admission check again.
Ask the accepted model a question without touching it.
When a new number arrives, someone usually opens the model, changes a cell, writes the answer on a notepad, and changes it back. That answer is real for about a day and then nobody can reproduce it.
AION opens a temporary copy of the accepted workbook, writes only to input cells it has already confirmed are safe to write to, lets the model's own calculation run to completion, and reads the results back. The original file is never modified. The fund's own scenarios are never touched.
Move the contingency. Read the model's own answer.
The accepted case is 7%. Drag to ask the model what happens at a different contingency.
9.2%
Accepted 9.2% · 0.00pp
1.35x
Accepted 1.35x · 0.00x
Within threshold
Running on a temporary copy of the accepted workbook. The original file is not modified. The fund's own scenarios are not touched.
The model's own numbers, read back. The original is never modified.
Refused with the cell named. Returned through the admission check.
Every run reports how it was produced: that the copy reproduced the model's existing results before anything was changed, which cells were written, that the model's own solve procedure ran to completion, and that the model's own check cell agrees. A number the team cannot trace is a number the team should not use.
Nothing the cockpit produces changes the accepted case on its own. A validated run and a named person's acceptance are both required.
One advisor note, end to end.
A technical advisor sends a note. Here is everything that happens, and everything that does not.
Threshold matched
The change is larger than the tolerance the team set. AION raises it. AION does not act on it.
Deal lead triages
Log it, hold it for evidence, ask Structuring for a preliminary sensitivity, or accept it as a working-case change.
Signal
Advisor note proposes EPC contingency 11%. The accepted case is 7%.
Assumption
EPC contingency
Advisor signal
11%
Accepted case
7%
4pp proposed change
Final state
Accepted case updated
Memo flagged stale until rewritten. Decision, basis, evidence and rationale preserved.
The model answers
The new numbers come from the model, not from AION.
Evidence closes the blocker
Written contractor confirmation is required before the change can be fully accepted.
Trigger
Advisor note proposes EPC contingency 11%. The accepted case is 7%.
Assumption
EPC contingency
Advisor signal
11%
Accepted case
7%
Threshold matched
The change is larger than the tolerance the team set. AION raises it. AION does not act on it.
Deal lead triages
Log it, hold it for evidence, ask Structuring for a preliminary sensitivity, or accept it as a working-case change.
The model answers
The new numbers come from the model, not from AION.
Evidence closes the blocker
Written contractor confirmation is required before the change can be fully accepted.
Final state
Accepted case updated
Memo flagged stale until rewritten. Decision, basis, evidence and rationale preserved.
AION does not act on the advisor note. It shows the deal lead the divergence and records the human triage decision. The model produces the numbers; the deal lead produces the judgment; AION holds the record of both.
What a pilot looks like.
One transaction. Your existing files. No migration and no change to how the team works.
One infrastructure transaction, from an existing financial model and a draft IC memo through to IC submission.
A kickoff session, a short check-in each week, and a review at the end. The team keeps working in Excel and email throughout.
The current model, the memo draft, advisor notes, evidence documents, and whichever email context you choose to include.
A record of the accepted case: assumptions with their evidence basis, model-version history, open blockers, exceptions carried to IC, memo alignment state, and a full decision log you can export.
We are taking a small number of design partners for the first deployments. The first conversation is a walkthrough, with no commitment.
From first model to a reviewable IC state.
Kickoff
One transaction selected. The team confirms the current model, the IC objective, and the questions that actually matter.
Files collected
Existing files only. No migration, no new folder structure, no change to where anything lives.
Record built
AION profiles the model, builds the assumption register, and captures evidence, owners, thresholds and open issues.
Review pack
Accepted case, change register, memo alignment state, open blockers, exceptions, model-version history and decision log.
Team reviews
The team checks the record against what it knows to be true, exports it, and decides whether to continue.
The test is simple. Is this record more reliable than the one the team is carrying today?
Where we are.
We would rather be clear about what exists today than imply more.
Prototype
in build nowThe core of the system: reading deal materials, building the assumption register, admitting model versions, and recording decisions with their provenance.
MVP
nextThe full arc on a controlled transaction package: intake, assumption register, workbook admission, change triage, interrogation of the accepted model, alignment checks before IC, and the close-basis record.
Pilot deployment
thenThe MVP running on one live transaction inside a fund, from the current model through to IC, configured with the fund's own templates and thresholds.
Design-partner conversations are open now. Early partners shape what the MVP has to handle.
Where your data sits.
Infrastructure funds do not move deal data lightly.
AION can run inside the fund's own cloud environment or on-premise.
Deal data does not leave the fund's tenant.
Customer deal data is never used to train or improve any model.
The language-model layer is swappable. No single provider is required, and the provider can be chosen by the fund.
Full detail available on request, under NDA.
Who is behind this.
Theis Lindegaard
Product, governance doctrine, partnerships and pilot development.
Alfonso Sanjuan
Eight years in infrastructure development and consulting.
Umed Saidov
Former EBRD and World Bank Group. PPP structuring, bankability and project finance.
Further engineering and project-finance expertise is in place and not yet public.
Start with a walkthrough.
We show the system on a worked infrastructure transaction and talk through how it would sit against your own model and IC process. No commitment.