AI does the repetitive work; your people make the decisions. We're onboarding a maximum of three property operators as First Partners — not a free trial, but a structured arrangement with a defined start, a defined finish, and one number that tells us both whether it worked.
REA drafted a reply to a tenant about the water bill. Niko confirms before it sends.
That's where an operator's hours and risks actually live. REA is a working system that removes the repetitive half — but for the first partners, we don't want to guess at your operation. We want to map it, measure it, and prove it on your real portfolio.
A First Partnership is a two-sided ledger. Here is exactly what each side puts on the table.
Before REA touches anything, our founders personally map your operation — so the pilot starts on real, complete data, priced with knowledge of how you actually work.
The difference between the two is usually where the hours hide.
Where your operation lives today, and how the data moves between the pieces.
Together, so the pilot starts on real, complete data — not a blank system.
Where the labour goes, the bottlenecks, the decisions that depend on one person.
At the end of Phase 0 — and only then — we agree the pilot terms in writing: the success metric, its baseline plan, and the post-pilot price, set below the monthly savings the pilot measures. If REA doesn't save more than it costs, we haven't earned the contract.
The records prepared in Phase 0 go in — bulk import plus REA's OCR for documents. No manual retyping, no IT project on your side.
Your units, tenants/guests, vendors and message channels mapped into the twin. Your workflows, not a template.
REA starts drafting real work — replies, entries, inventories — but nothing goes out without your named person's confirmation. You watch it work on your actual operation before it touches anyone.
What REA handles reliably in shadow mode graduates to automatic, one workflow at a time, at your pace. A human always confirms decisions that matter.
At the end, three things are on the table: the process map, the measured number against its baseline, and the price agreed back in Phase 0 — set below the savings the pilot demonstrated.
You decide: keep the savings at your locked founding-partner price, or part as friends with your data exported and the map in hand.
We part. You keep the operation map and the measured findings, and you've spent nothing but your team's time.
If you want to continue anyway, the locked price still stands — the door doesn't close because a number did.
Because each partnership is founder-led and hands-on — we map your operation personally, adapt REA to it week by week, and are on a call with you every week. Three is the number we can do at that depth without diluting it. It also means the three shape the product before anyone else.
No. A trial is you, alone, poking at software. This is a structured, mutual arrangement: a paid-grade operation audit we do for free, a pilot on your real portfolio, one agreed success metric, and a price fixed before the clock starts. There's a defined start, a defined finish, and a written definition of what "worked" means.
During the pilot, nothing. The post-pilot price is agreed at the end of Phase 0 and is set below the monthly savings the pilot measures. If the target is missed, we part, you keep the operation map and the findings, and you've spent only your team's time.
Not until you let it. The pilot starts in shadow mode: REA drafts real work but nothing sends without your named person's confirmation. Workflows graduate to automatic one at a time, at your pace, and a human always confirms decisions that carry a date, a cost or a commitment.
You do. It stays yours throughout, on EU-hosted infrastructure, and is never sold or used to train models. If we part, you export everything and keep the process map.
Phase 0 is a few short interviews and a systems walkthrough over one to two weeks. During the pilot it's one named person working in REA as they already work, plus one 30-minute call a week. There's no IT project and no manual re-keying — intake is bulk import plus OCR.
Documents retyped, inventories built by hand, an endless message triangle between tenants, managers and vendors. Three operators get to fix it first.