An Enterprise Knowledge Platform powered by Artificial Intelligence
It connects to the systems your trust company already uses — Odoo, Google Drive, shared folders — and answers any question about the operation in natural language, always with the source cited.
In a typical trust company, the books live in Odoo, contracts and deeds in Google Drive or shared folders, deadline tracking in Excel spreadsheets, and instructions and approvals in email. Day to day, it looks like this:
Argentina's Civil and Commercial Code (sec. 1675) requires accounts to be rendered at least once a year — and settlors ask for them more often. Every one is built by hand.
Trustees are obligated subjects before the UIF, Argentina's anti-money-laundering authority (Law 25,246): client files, risk matrix, reports. Plus ARCA's information regimes. All of it means pulling data from several sources.
Trust terms, insurance policies, guarantees, renewals. Today they depend on spreadsheets and the team's memory — and a single missed date is expensive.
“What does the termination clause say?” means finding the right PDF and reading it whole. Multiplied by dozens of trusts.
The operation depends on two or three people remembering where everything is. One leave of absence or one resignation stalls everything.
The settlor asks and the answer takes days — not because the data is missing, but because someone has to go hunt it down.
Lacre connects to the existing sources and queries them all at once. Documents never move from where they are: the platform builds a smart index that knows where everything is and what it says.
Ask about contracts, minutes and case files. The answer cites the document, the clause and the exact page.
Balances, payments, invoices and projects in natural language, without knowing Odoo and without asking anyone for the report.
Combine Odoo numbers and contract clauses in a single question. No generic tool can do that.
Three examples, from the simple to what is outright impossible today without hours of work:
“This trust may be terminated early by unanimous decision of the Beneficiaries' Committee, notified to the Trustee no less than sixty (60) calendar days in advance, subject to prior settlement of the obligations assumed with third parties…”Contrato_Torre_Alvear.pdf · clause 14.2 · p. 23
| Trust | Expires | Auto-renewal |
|---|---|---|
| Torre Alvear | Sep 15, 2026 | Yes — clause 3.4 (24-month extension) |
| Mitre 1450 | Oct 12, 2026 | Yes — clause 2.7 |
| Los Nogales | Oct 30, 2026 | No — requires a signed addendum |
Fictional data, for illustration. In production, answers are generated from the trust company's real data and documents.
The third query is the key: it needs to read Odoo (dates and statuses) and the contracts (term clauses) at the same time. Today that is an afternoon's work for someone who knows the files. Here it is seconds, with verifiable sources.
It never makes things up in a confident tone. No verifiable source, no answer — that is design rule number one, made for a regulated entity.
Typical times for frequent tasks, before and after:
The math is run with each trust company's real numbers during the pilot. And it leaves out the most expensive part: a single missed deadline — an unrenewed policy, an expired term, a late addendum — can cost more than a whole year of the platform.
The knowledge of “where everything is and what it says” stays in the platform. A leave or a resignation no longer stalls the operation, and new staff become productive in weeks, not months.
Files with missing items flagged automatically, supporting documents locatable in an instant during an inspection or audit, and information regimes prepared in minutes instead of days.
Managing more trusts today means hiring more people to search and cross-check information. With the platform, the same team absorbs more operation.
Management checks the real state of the business in the moment, without waiting for someone to build the report.
How would this math come out with your trust company's numbers?
Book a 20-minute callThe heaviest task in the fiduciary calendar, step by step. Lacre gathers; the trust officer reviews and signs — professional judgement stays human.
Everything stays in the trust company's current infrastructure and accounts. The platform stores only the index and the references.
Processing runs under a no-training contract and a data-protection agreement. If internal policy demands it, an on-premises installation is available.
Existing permissions are respected: every search filters first by the user's permissions and only then by relevance.
Every query and every access is audited. Before a regulator or an audit, you can show who asked what, and when.
With the platform running, each new module reuses the same index and the same connections. The same goes for connectors: today's integration is Odoo, and Tango, SAP or whichever system the firm runs can be added next:
Tracking of UIF files and regulatory deadlines, and assisted preparation of ARCA's information regimes.
Contract review and comparison, detection of atypical or missing clauses before signing.
An automatic periodic brief for management: upcoming deadlines, deviations, critical pending items — with nobody having to build it.
Proactive notices of deadlines and pending items, and quick queries from the phone through the channels the team already uses.
No migrations, no process changes, no long-term commitment. Contained scope and a fixed price: one document source, one set of trusts, limited users.