Every company reports progress. Few can evidence it.
Assettia is the data and AI programme record: one place where an organisation keeps what its programme owns, what it has decided, and what it has proved.
An operating team can ask eight portfolio companies how their data and AI programme is going, and get eight confident answers in eight different shapes, none of which can be checked. Assettia produces the same read in every company, from its own records, so the answers are comparable and the evidence is there.
- Assets in scope
- 39
- in one portfolio company
- data assets on the register
- Register entries complete
- 27 of 39
- twelve entries are incomplete
- assets with a complete register entry
- Assets feeding a use case
- 20 of 39
- the rest are not yet in use
- assets linked to at least one use case
The alternatives
What you can do instead, and where each one stops.
| Approach | What you get | Where it stops |
|---|---|---|
| Ask the company | A confident answer | Nothing behind it to check |
| A management deck | A narrative, quarterly | Assembled by hand, different in every company |
| A diligence exercise | A snapshot, at cost | Out of date by completion |
| A technical audit | The estate | Not the programme, not the value |
| Assettia | The record in each company | Produced from records, same definitions everywhere |
Diligence with evidence, not assertions
A target's AI claims are usually a slide. A structured read of the use cases actually in production, the data they depend on, the decisions behind them and the risks they carry gives the deal team something to price, and a list of the questions still open. Where the target has no record, the empty registers say so; that is a finding in itself.
Bring one portfolio company's situation and see the read you would get.
Request a walkthroughThe same question, answered the same way, in every company
Comparability comes from shared definitions, not from a template someone filled in. Each company keeps its own record: its use cases scored against the same criteria, its data assets, its decisions with the person and the reason, its risks with their attestations, and its value evidence. Every figure names what it counts and opens to the records beneath it. When two companies are set side by side, the shapes are the same because the definitions are the same.
One record per company, one view across the portfolio
Each company runs in its own tenant, isolated at the database, with its own board report produced from its own record. The operating team sees a portfolio view across companies: the state of each programme in the same three states, the decisions taken since the last review, the value proved, and the gaps. Nothing is pooled and nothing is copied; the view reads each company's record where it lives.
Data and AI Board Report
[Portfolio company]
[Period] · Prepared from the programme record
Every figure in this report traces to a record. Gaps are shown as gaps.
Value tracked to exit
Baselines are recorded when a case is approved, so the value story at exit is a record rather than a reconstruction. Committed value sits beside realised value, with the evidence linked. Where a case did not deliver, that is filed as evidence too, with the reason. A buyer's diligence team can be shown the record, not a narrative about it.
Regulatory exposure, named
Each company's risk register holds the AI risks it carries, the controls in place, the regulatory obligations it is subject to, and the named attestations that controls are working. Exposure that would otherwise surface late in a sale process surfaces while there is still time to act on it, and it is visible across the portfolio in one place.
Owned, decided, proved, across the portfolio
Three states, derived from each company's records and never assigned by opinion, give an operating team a portfolio picture that cannot be talked up. A company that has decided a great deal and proved little looks exactly that way. So does one that has proved what it set out to do.
How operating teams use it
Before a deal: a structured read of the target, or the questions to put to it. On acquisition: the company's programme starts on the record from day one, with the investment case as the first decision. During the hold: the same board report at each review, produced from the record, with what changed stated. At exit: the record itself as the evidence pack.
Questions people ask
Does each portfolio company see the others?
No. Each company's record is its own tenant, isolated at the database. The portfolio view belongs to the investor's operating team and reads each record where it lives.
Can a portfolio company keep using the record after exit?
Yes. The record is the company's. On exit it stays with the company and the investor's portfolio view no longer includes it.
What does the deal team get in diligence?
A structured read of the target's use cases, data assets, decisions, risks and value evidence, produced in the target's own tenant, with empty registers stated as empty.
Is pooled benchmarking across the portfolio possible?
Only under explicit agreed rules, anonymised, or not at all. The default is no pooling.
How is this different from asking each company for a slide?
The slides are assembled by hand and differ in shape. The record is produced from each company's own records to one set of definitions, and every figure can be opened and checked.
Bring one portfolio company.
A walkthrough takes forty minutes and uses a synthetic organisation. Bring one portfolio company's situation and see the read you would get.