twentii · a thesis
twentii turns decades of industry data into the decisions businesses make next.
01 · the problem
The dormant decades.
The most valuable dataset in most established industries is not on the internet. It sits in the businesses themselves — ledgers, ERPs, archives, filing cabinets — and in public records nobody has structured.
Feed the engine forty years of prices, orders, failures, and recoveries, and it does not see history. It sees the next decision, rehearsed ten thousand times. Yet in most businesses that record sits unread — and the decisions are still made on instinct.
The data exists. It has never been asked.
- 1962
- 1966
- 1970
- 1974
- 1978
- 1982
- 1986
- 1990
- 1994
- 1998
- 2002
- 2006
- 2010
- 2014
- 2018
- 2022
- 2026
Decades of records in one example business. Read once, if ever.
02 · in operation
Revenue Engine.
The dormant record is not always decades old. Some of it was produced last month. Revenue Engine turns the operating records an organisation already prepares into recoverable commercial action — a month of records in, a month of owned decisions out.
Last month's leakage is a diagnosis. This month's recoverable is a commitment — and at month end the engine reconciles the plan against realized recovery, line by line.
- begins
- with files your teams already produce at month end — no systems integration, no transformation programme
- rule
- recoverable never exceeds observed — by construction
in one operating context — a multi-branch vehicle dealer group
input — one workbook a month · five minutes
twelve commercial levers in this operating model — each computed from the operation's own records; a lever with no evidence stays at zero
Every month it runs, the operating memory compounds — what leaked, what was recovered, and who recovered it. The dormant decades, built forward from now.
Request a private walkthrough — auto@twentii.ai
03 · revenue engine
The film.
revenue engine · the film
What the records become.
04 · the method
Access. Structure. Intelligence.
Institutional memory and machine intelligence are worthless apart. Paired, they compound. The method is the pairing.
-
01 · access
We work inside the business.
History arrives in whatever form it was kept — paper ledgers, microfilm, ERP exports, public registries. We take it in that form. Nothing is required of you but the key to the cabinet.
- intake
- ledger scans · system exports · public registries · transaction archives
- premise
- your records stay yours, on your terms
-
02 · structure
Records become one schema.
Entities matched, units reconciled, gaps declared. Every figure stays traceable to its source page — a table you can interrogate, and audit back to the paper.
- output
- entity-resolved tables — the operation in one schema
- provenance
- page-level; gaps declared, never silently filled
-
03 · intelligence
Structured history feeds the decision.
Forecasting and pricing models trained on decades of your market, not last month's. The output is not a dashboard. It is the next decision, with its reasoning attached.
- models
- demand forecast · price recommendation
- horizon
- quarters and cycles, not clicks
Not every record needs archaeology. Revenue Engine runs the same loop on a month of operating files, exactly as they are. The cabinets come later, if the decisions deserve them.
05 · proof of craft
The assembly.
A month of loose operating records. One schema. Two verdicts — the leak found, the recovery owned. Every mark in the verdicts began in the scatter — records becoming a decision, drawn literally.
06 · contact
Partner with twentii.
If your operation keeps records — this month's files or forty years of them — they already hold decisions nobody has made. We want the conversation.
Write directly: auto@twentii.ai.