How RE-Brain works.
Many inputs, one brain, work that gets done, and you in control.
01
Inputs
- Shared mailbox
- Teams and Slack
- Documents
- Connected systems
02
The brain
- Structured portfolio
- Site briefs
- Event history
- Playbooks
- Rule engine
Isolated EU workspace
03
The work
- Cases
- Supplier follow-ups
- Review packs
- Answers
- Digests
04
Approval and audit
- Approval cards
- Sending rules
- Activity log
05
Outputs
- Emails
- Live dashboard
- Registers
- Exports
- Weekly digest
Inputs.
Every input goes through the same steps: classify, link to the right site, lease or contract, extract facts with a quote and confidence, then either update the record (with approval) or add it to the site's history. When RE-Brain is unsure which site something belongs to, it asks. A wrong link is worse than one question.
The brain.
Three kinds of memory, kept apart: facts (sites, leases, contracts, SLAs, people, each with a source), events (an append-only history per site) and team conventions (rules you give it, editable). On top of these, a living one-page brief for every site.
The rule engine.
The AI reads; code calculates. Notice deadlines, indexation dates, contract end dates and SLA clocks are computed by tested rules.
- 1. Extract. The AI quotes the clause and page it read the term from.
- 2. Confirm. A person confirms anything that matters or is unclear.
- 3. Calculate. A tested rule computes the deadline. The AI model never does the maths.
- 1
Extracted by AI, with the source
"Break option 31 May 2027, 6 months notice" Prague lease, clause 7.2, page 14
- 2
Confirmed by a person
Confirmed by Sophie Laurent, 14 Oct 2026
- 3
Calculated by a tested rule
Notice deadline 30 Nov 2026
Calendar months, end-of-month rule
Approvals.
RE-Brain proposes; people approve. You decide which message types it may send after approval and which stay as drafts.
Proactive, not noisy.
A daily scan finds upcoming dates, stalled cases and SLA risks. RE-Brain speaks first only when a decision, a deadline or a risk needs you.
Getting started.
Week 1
Shared mailbox and first documents.
Week 2
First site live, first case handled.
Weeks 3 to 4
Remaining sites, Teams or Slack, team invited.