A fiduciary copilot on Odoo
Ask the Odoo and it answers with the voucher. Send it a contract and it builds the data sheet, every field cited. Approve, and the case file is loaded into the ERP, or reverted. These twelve screens are the exact preview of the live demo, showing what Lacre does today: the prompt is the one we run on the call, and the answer is what it returned. Whatever does not exist yet, we say so.
Rather see it on your own contracts? Within 48 hours, no credentials to any of your systems (screen 12).
The demo walks four blocks
A product of WizardsLabs
→ to advance
Finding out how much was billed in fees for one trust in one month means opening Odoo, filtering by contact and by date, and trusting you picked the right trust out of a dozen look-alikes. Here, you ask:
In July 2026 the trustee billed ARS 87,300,000 in administration fees for FOFIS.
Invoice FA-2026-0713 · Jul 31, 2026 · issued to the Ministry of Public Health of the Province of Chaco.
We open FA-2026-0713 in Odoo in front of you, through the link the answer itself provides.
The block we show risk and compliance people first. Three trick questions, run as-is:
How much is left for FoGaCh to recover on the bounced Maderas del Impenetrable check?
It separates what was paid (ARS 14,800,000 for the bounce and ARS 444,000 in recovery charges) from what was recovered: there is no collection on record. As of the cutoff, nothing.
Not “couldn't find it”: it looked, it doesn't exist, and it says exactly that.
What is the balance of the Torre Costanera III trust?
It searches and finds nothing. It notes that Torre Costanera II does exist, and that it is a different one. No balance borrowed from the lookalike.
The costliest mistake: deciding on the wrong trust. It doesn't make it.
And the penalty interest accruing since it paid?
It follows the check question: the penalty rate is not among the ERP's queryable fields; it is a contractual condition. It gives the days elapsed and the charges already issued, and does not settle what it cannot back.
It was missing one datum. Instead of estimating it, it named it.
You pick the trick: ask it about something that doesn't exist.
A chart in the conversation is for looking at once. What gets used every day has to stay in your system, on live data:
Billing by month · Torre Costanera II
The chart appears inside the answer. It creates nothing in Odoo: you asked for a chart, not a dashboard.
Dashboard created in Odoo
Open “Arrears — Torre Costanera II”Unpaid-debt KPI · debt by unit · billing by month · period filter
It lives under Dashboards › the Lacre group, for you and your team. Not a snapshot: tomorrow your accountant opens it and it is current.
The “don't ask me for confirmation” works because creating a new dashboard breaks nothing. And if you later ask it to “add a table”, or “delete it”? Approval card. Touching what already exists never happens on its own: that is the rule of the “Nothing happens without someone approving” screen.
We create the dashboard during the call and open it together, period filter working.
Back to what the ERP doesn't know. This is a 40-page administration contract nobody has re-read since it was signed. You attach it to the conversation, and ask:
The trustee's removal and replacement regime is in the thirteenth clause:
“Upon cessation for any of the causes provided herein, the substitute trustee shall be appointed by the Settlor at the proposal of the Fiduciary Committee, and the outgoing Trustee shall execute the transfer instruments and render a final accounting…”FOFIS trust agreement · thirteenth clause
Not a summary of the Civil Code: the clause of this contract, with its text, verifiable by opening the PDF. Finding it by hand takes 20–40 minutes of case file; asking takes under one (illustrative estimate).
A 2018 contract, scanned, with no text layer: an image. It reads it through OCR and builds the same data sheet, each field cited. And whatever the instrument doesn't say is flagged as missing.
We run it on our 40-page contract, or on one of yours, if you bring it.
The work a person does by hand today. The contract and its addendum go in together, the way a real case file arrives, and out comes a sheet where every field declares where it came from:
FOFIS administration trust
The sheet is an editable card, not loose text. And if a reading seems doubtful, the field is flagged and the load stops until someone resolves it.
You tap a field and see the instrument, the clause and the text that back it.
A trust not yet in the system (Rentas “Timbó”, contract plus annex). The step that eliminates transcription:
It proposes the load plan: analytic account FID-012, 2 new contacts and 1 reused. The trustee company already exists; it recognises it by tax ID and doesn't duplicate it. And zero vouchers: it knows there is a monthly fee of ARS 1,050,000, but no instrument fixes since when. It could have issued 48 invoices; it issued none. It asks you for the range.
Card approved, Odoo holds the account, the contacts and the six invoices. And in each record's chatter, the note with the document, the clause, who approved and when.
We approve the load live and open the finished case file in Odoo.
See it live · book 20 minTrusts aren't loaded once: an addendum extends the term, minutes replace the trustee, an assignment changes the beneficiary. We send it the addendum alone, without saying which trust it belongs to:
It identifies which one it belongs to on its own: by the name, the constitution date and the tax ID of one of the parties.
And it says so explicitly: it does not recalculate or reissue the six invoices already posted. It updates the datum, not the books, and the previous value stays on record.
The before and the after, in front of you; you accept change by change.
We'd rather the demo show only what already runs. The rest is roadmap, and we present it as such:
Today · in the demo
On the roadmap
The full vision, and the arithmetic of the hours saved, in the general presentation: wizardslabs.com/lacre
If something on the roadmap matters more to you than what exists today, say so on the call: clients set the order.
The same five rules across the whole demo, and in the product:
Querying touches nothing. And creating something new breaks nothing: a dashboard goes out directly, no card.
Nothing that touches something existing goes through without explicit approval. And loading a case file, even when everything in it is new, goes out with its card too. The card says exactly what will change.
“Revert everything you loaded” lists what gets deleted (1 account, 2 contacts, 6 vouchers) and leaves intact what was merely reused. And if your Odoo holds on to an entry, it says so instead of forcing it.
If the trust might already exist under another name, it shows both and asks whether they are the same. It doesn't decide alone.
What standard Odoo cannot store is kept as a cited note on the case file. Adding fields to your ERP can only be your decision, at installation, never a side effect of loading a contract.
Everything runs on a standard Odoo, no custom modules.
The demo closes by deleting everything we wrote, in front of you: we refresh Odoo and nothing is left. That is why this can be tried without fear: nothing is irreversible, and nothing happens without someone approving.
The question a trust company asks first, answered with the same candour as the rest:
Lacre has no connectors watching your folders: it processes the document you send to the conversation, to answer that conversation. On the server they expire on their own after two hours; there is no document repository.
The conversation lives in your browser. Our servers do not keep the chat history: what you ask stays in nobody's custody.
Each user opens their Odoo session with their own user. Lacre sees exactly what your Odoo lets that person see: the permissions are still enforced by your system.
Processing runs under no-training terms: they improve no model. And the 48-hour pilot starts where it should: with the NDA, signed before anything is sent.
Bring your compliance officer to the call: this screen exists for that conversation.
The next step
Want to see it running?
The live demo takes 20 minutes and walks these same screens, in real time, on our demo environment. It is given by the person who built the product: ask whatever technical questions you need.
Rather see it on your own material? Send us two or three contracts (NDA signed) and within 48 hours you see it run on your own trusts. No credentials to any of your systems: just the documents.
The pilot that follows the demo is contained in scope and fixed in price. The concrete numbers, in those 20 minutes.
The demo environment's trusts are fictional. The prompts and answers on these screens were run against that environment and are shown as the product returned them.