the method
History becomes a decision in three steps. Each one is auditable.
Not every record needs archaeology.
Records arrive in every state: monthly operating files, spreadsheets, structured exports, live databases — and, when a decision reaches for it, microfilm and paper. The method is the same at every depth. Revenue Engine runs it on the files an operation already produces each month: one workbook in, leakage found, recovery validated, actions owned. No digitisation, no integration project.
Start where the records are. Go deeper when the decisions deserve it.
01 · access
We meet the records where they are.
Access begins with the record, not the interface. Operating history rarely exports cleanly; it sits in spreadsheets and systems of record, in ledgers and registries — and in the memory of the people who kept it.
A record is taken in the state it is found, and its keeper stays part of it — a column heading from 1987 often needs the person who wrote it.
- sources
- operating files · system exports · paper ledgers · microfilm · public registries · auction sheets
- terms
- records stay yours; access is scoped and revocable
- simplest case
- revenue engine — one monthly workbook, nothing digitised
- start
- one decision that matters, worked backward to its records
02 · structure
One schema, every figure traceable.
Extraction is the easy half. The work is reconciliation: the same part under four names, prices in two currencies across a redenomination, a gap where 1994 flooded the basement.
We resolve entities, normalize units, and declare gaps instead of filling them silently. Every figure in the final tables links back to the page it came from — so a skeptical owner can check us against their own cabinet.
- output
- entity-resolved tables — the operation in one schema
- provenance
- page-level, kept for the life of the dataset
- gaps
- declared and dated — never imputed without a flag
03 · intelligence
Models that answer a named question.
We train forecasting and pricing models on the structured history — demand for a category next quarter, the price a contract should carry, the buy that decades of cycles argue for.
The output is a recommendation with its reasoning attached. The decision stays with the person who owns it.
- in operation
- revenue engine — observed leakage · validated recovery · owned, reconciled actions
- horizon
- quarters and cycles
What we do not do.
- We do not pool your data with anyone else's without a signed agreement that says so.
- We do not publish benchmarks built from partner records.
- We do not claim accuracy we have not measured on your history.
- We do not automate a decision you have not delegated.
Start the conversation.
Tell us what your records look like — one sentence is enough. Partner with twentii, or write to auto@twentii.ai.