Private capital operations, structured in one view.
Fundamental View is private financial and asset accounting for family offices: every transaction and asset across entities and currencies, with the documents behind each record and a clean cash-flow register.
Anonymised before AI. Your records stay in your workspace.
Software for a family office usually starts at the report.
Not another spreadsheet. Not another generic dashboard.
An operational layer between documents, transactions, crypto confirmations and the people responsible for keeping private capital records accurate.
Private capital operations rarely fail because of strategy.
They fail because of fragmented records.
Family offices operate across banks, brokers, wallets, custodians, entities and jurisdictions. Without a structured process, every report becomes a reconstruction exercise.
One controlled workflow in place of six disconnected ones.
Structured transaction records for family office operations.
A personal interface, anonymised document recognition, storage in your own Drive, blockchain links, FX conversion and a structured register, each step handing off to the next.
Liquid and illiquid belong in the same structure.
One register across your operating structure.
Define the entities, transaction categories and currency conventions that your operation needs. Agree the supported cases before configuring the register.
A record is only as good as the paper behind it.
Every document named, stored and connected.
Documents are converted, merged and stored using the same PCD logic as the register. Months later, the team can still trace the operation back to its source.
A recorded figure needs its context.
Keep the supporting evidence within reach.
Connect statements, confirmations and on-chain references to the relevant record. Agree how unmatched items are raised and who resolves them.
Operational questions do not wait for a desk.
The register in the principal's pocket.
A register connects transaction records, supporting documents and movements across the operation. Mobile access and views are agreed with the people who will use them.
A family is not one audience.
Agree access before connecting the workflow.
Your records stay in your own workspace. Define who needs access to each entity, record and document, and grant or remove it in one place.
Start with a representative example.
See how your workflow would become a record.
A private demo uses an agreed fictional or redacted example to show the path from information received to a reviewed record. Describe the workflow first; keep confidential documents out of the initial enquiry.
How a record is made.
Six steps, in the same order every time. The sequence is the product: it is what makes a number in a report answerable months later.
The row it produced
| PCD | Date | Counterparty | Amount | Evidence |
|---|---|---|---|---|
| PCD-2026-0417 | 14.04.2026 | Meridian Holdings Ltd | 41,280.00 | Tronscan |
Add transaction
A record starts in your personal interface. The user selects the category: external, internal, or not relevant.
Attach proof
A PDF, a photo, an iPhone screenshot, a crypto TXID, both together, or none where the policy allows it.
Recognise data
The system extracts what it can read from the document and maps it onto the register fields.
Confirm fields
Every recognised field is reviewed and confirmed by a person before the record is saved.
Store evidence
Documents are merged into a PCD-named PDF in Google Drive. A TXID becomes a link to its explorer.
Update register
The record is written to the configured Google Sheets register with its links, rates and status. SQL migration can be scoped separately.
What the infrastructure is made of.
Personal interface
Each user records transactions, files, TXIDs and comments in their own interface, without opening the register. A customisable application is in development.
Anonymised recognition
Names, account numbers and other identifiers are masked before a document reaches the recognition model. It proposes the fields; a person confirms each one before it is saved.
Transaction register
PCD number, date, issuer, currency, amount, USD amount, counterparty, instrument, document links and status.
Drive evidence storage
Quarterly folders, PCD file names, merged PDFs, and a link back to the row the document belongs to.
Crypto layer
TXID, token and network held with the record, with a duplicate check across network and transaction id.
FX and USD conversion
Historical rates retrieved where they exist, manual override where they do not, and the rate status kept on the record.
SQL scalability
Start on Google Sheets. Assess SQL migration against defined access, reporting and volume requirements.
Connects to
Your records stay yours. We keep them in order.
Your data stays with you
The register and the evidence live in your own Google Workspace. Fundamental View is the tool that keeps them in order, not the place where they are kept.
Anonymised before AI
Names, account numbers and other identifiers are masked before a document is read by the recognition model. The model sees figures and structure, not who they belong to.
Controlled access
Only authorised users can add records. The register and folders use your workspace's own sharing controls, so access is granted and removed in one place.
Human confirmation
Recognised data is confirmed by a person before it is written to the register.
Traceable records
Each operation carries a stable PCD number and can be linked to a document or to blockchain evidence.
What we never do
We do not hold your records, move money or ask for banking credentials. The full list of services involved, with regions, is provided before implementation.
Retention, change history and support access are set out in writing for your implementation before the first record is saved.
Where it is already the right tool.
Cash-flow reporting
For teams that maintain a cash-flow report and need clean transaction records with the documents that support them.
Investment operations
For recording securities, instruments, ISINs, quantities, prices, commissions and counterparties.
Crypto confirmations
For operations where a blockchain transaction is the primary proof of a payment or transfer.
Multi-entity structures
For private structures operating across departments, companies, accounts and jurisdictions.
Assistant-led operations
For cases where an assistant adds records through their personal interface while the principal reviews the register.
Crypto confirmations, held in the same record.
For blockchain transfers the register stores the TXID, the token, the network and the explorer link as part of the operation. An explorer reference records the on-chain movement; its business purpose and supporting context still need review.
| PCD | Date | Counterparty | Instrument | Amount | Evidence |
|---|---|---|---|---|---|
| PCD-2026-0417 | 14.04.2026 | Meridian Holdings Ltd | USDT TRC-20 | 41,280.00 | Tronscan |
| PCD-2026-0418 | 15.04.2026 | Private — internal transfer | EUR | 250,000.00 | Notarised deed |
| PCD-2026-0421 | 18.04.2026 | Ardenne Capital SA | USDT BEP-20 | 96,210.00 | BscScan |
Implemented around your existing operating process.
A typical first implementation takes about four weeks, from discovery to the first live records.
Discovery
Week 1. Review of the current reporting process, transaction types, documents and users.
Register structure
Week 1. Fields, categories, required data and PCD logic are defined against your operation.
Interface and automation
Weeks 2–3. Personal interfaces, anonymised recognition, Drive storage and register integration are configured.
Testing
Week 3. Agreed sample documents, transaction references, rates and exceptions are tested.
Launch
Week 4. The system is deployed, users are connected, and the first operating cycle is monitored.
Scale
When needed. SQL migration and additional integrations are scoped when the operation needs them.
Private implementation. Annual support.
Fundamental View is implemented as a private operational infrastructure. Scope, integrations and the support model are defined after reviewing your reporting process, document types and transaction volume.
There is no tier table, because there is no standard operation. What the work costs follows from what the work is.
Discovery and structure
Your reporting process, transaction types and document flow are reviewed, and the register is defined against them.
Implementation and testing
Bot, recognition, storage and register are configured and tested against agreed sample records.
Annual support
Ongoing support and agreed adjustments as the structure changes. SQL migration is scoped separately.
Questions we are asked first.
Is Fundamental View related to fundamental analysis?
No. Fundamental View is the name of a family office accounting service, not an investment method. It keeps transaction and asset records with their documents; it does not analyse or value stocks.
Is this a portfolio management platform?
No. Fundamental View is the financial and asset accounting layer underneath reporting: transaction records, supporting documents, confirmations and cash-flow reporting.
Is Fundamental View family office software?
Yes. It is private financial and asset accounting for family offices: transactions, assets, entities and currencies in one register, with the documents behind each record.
Can it track assets across several entities and currencies?
Yes. Each record carries its entity, currency and USD value, so liquid and illiquid assets, companies and accounts sit in one register.
How is it different from wealth management software?
Wealth platforms report performance. Fundamental View is the accounting layer underneath: every transaction recorded, evidenced and anonymised before AI reads it, with your records kept in your own workspace.
Does it replace our accountant?
No. It keeps the financial and asset records that accounting and reporting work from. Accounting judgements, tax positions and filings stay with your professionals.
Where are records and documents stored?
In Google Sheets and Google Drive, in the workspace configured for your operation. A move to SQL can be scoped later.
Can it connect directly to our bank or custodian?
Not in the first version. Statements and confirmations are added as documents and linked to the record they support.
Does the AI see our clients' names?
No. Identifiers are masked before a document reaches the recognition model; it reads figures, dates and structure. The confirmed record is written to your own workspace.
Which interface do users work in?
Today each user works in a private messaging interface set up for your operation. A dedicated, customisable application is in development.
Can it replace our current spreadsheet?
It can start from your Google Sheets structure and move to SQL later, when that becomes the right place for it.
Can we keep adding records manually?
Yes. The register is updated manually or through the personal interface, and the two can be used side by side.
Does it support crypto transactions?
Yes. A TXID is stored together with its token, network and explorer link as part of the record.
Which blockchain explorers are supported?
The first version supports Tronscan, BscScan, Etherscan and BTC Explorer.
Does it verify the transaction on-chain?
The system can retrieve available transaction data from supported explorers. Depth of verification depends on the API and network.
Can it process iPhone photos?
Yes. Common image formats are supported, including HEIC and HEIF.
What happens if recognition fails?
The user confirms, corrects, clears or enters the data by hand. Nothing is saved without a person agreeing to it.
Can the system scale beyond Google Sheets?
A SQL migration can be scoped when the register needs different storage or application controls. It requires mapping, testing and an agreed handover.
Is this a standard SaaS product?
No. It is implemented as a private infrastructure adapted to the way your operation already runs.
Bring structure to private capital operations.
Connect transactions, documents, crypto confirmations and reporting into one controlled workflow. For family offices, private investment structures and capital operations teams.
Who reads it
The team that implements the system reads every request and replies personally. There is no sales desk in between.
What the demo is
We agree a representative workflow using fictional or redacted examples, then walk through the resulting records.
What it is not
This form is for an implementation enquiry. Please do not include confidential records. Enquiries are kept in our CRM, hosted in the EU; see the privacy notice for details.