Our technology
We integrate best-in-class tools, and we build what they don’t do.
Most of what a manager does is paperwork: collecting, chasing, convening, filing, reconciling. We build the systems that handle it in house. Decisions, emergencies and difficult conversations stay with people.
Figures as of August 31, 2026, available on request
multiRent’s solution is built on open technologies. For each building block we pick the strongest tool in its category — the portal your owners use, the accounting ledger — then build in house everything that connects them and makes them work: collection and follow-ups, insurance certificates, meeting notices and voting, electronic signature, bookkeeping, a voice assistant.
Every capability described here is in service. We say which part of the portfolio it runs on, because not everything is deployed everywhere — and each one leaves a verifiable trace on your file.
Your building runs on French legal documents. Your board doesn’t have to.
The gap English-speaking boards actually live with — and one reason we build our own tools.
In Quebec, a condominium is governed by a declaration of co-ownership registered in French, minutes that must hold up in French, and a body of law written in French. That is not going to change, and it should not: those records have to be legally sound.
What can change is whether your board understands them. On the buildings we manage, the official record is produced correctly in French, and the explanation you get — the summary of a resolution, the reason behind an assessment, the answer to a resident’s question — comes to you in plain English. Our systems keep both, side by side, on the same file.
Boards in the West Island, Westmount, Notre-Dame-de-Grâce and downtown Montreal tell us the same thing: they are not looking for an English-only manager. They are looking for one who will not let them sign something they did not follow.
What we integrate, and what we build
Nobody builds everything. What matters is knowing where the tool stops and who writes the rest.
For the portal your owners log into and for the accounting ledger, we use specialised, proven tools maintained by teams who do nothing else. A management firm that claimed to rewrite a general ledger would be charging you for its own vanity, and the result would be worse.
What we build is everything around them. Those tools store a document and record an entry; they do not chase an owner who is late, pursue two hundred insurance certificates until they arrive, check calendars before a meeting date is set, or draft an answer from your building’s own rules. That is the work that fills a manager’s hours, and that is what we automated.
Our internal platform tracks around fifty buildings across some forty modules: resident requests, meetings, votes, proxies, insurance, notary files, parking, water heaters, arrears, mail.
Why open technologies
Every building block talks through a public, documented interface. That choice has one direct consequence for your syndicate: nothing that belongs to you is locked in. Your registers, financial statements, minutes and request history can be exported, and the day you decide to leave, they leave with you. A manager whose tool holds your data holds you with it — we would rather keep you because the work is done well.
It is also what lets us replace one block without rebuilding everything, and add one when a board needs it.
The test
When a board asks for something the tool does not do, the usual answer is “that isn’t possible”, or waiting for a vendor’s next release. Ours is to build it: the team that writes the code is the team that manages your buildings, and it is not waiting on anyone’s roadmap.
The consequence shows up in the price. Automation absorbs the repetitive work, which is why our rates start at 10 $ per unit per month in a market where 35 $ to 50 $ is common.
What our systems do on their own
These run across the whole portfolio, without anyone starting them.
Collection and arrears
Pre-authorised debit of condo fees, handling of returned payments, automatic follow-up, and late interest applied as set out in the declaration. The board sees where accounts stand without compiling anything.
Insurance certificates
Certificates are chased automatically until they arrive. One sweep, in August 2026, closed 117 files with no failures — an obligation that otherwise depends on somebody remembering to pursue two hundred people.
General meetings
Notice, agenda, quorum sheet and online meeting are generated and sent. Before anything goes out, the system checks the real calendars of the people who must attend and flags a conflict — because once the date is public, changing it costs a full re-notice.
Voting and proxies
Online voting, proxies signed by link, and a register the board can consult. A change of date automatically invalidates the proxies it affects.
Electronic signature
Built in house: a personal link, identity verified by a code sent to the signer’s email, timestamp, IP recorded, full audit trail. A document counts as signed only once every signatory has signed.
Registered mail
Formal notices go out as tracked physical mail from the same file, with the cost charged to the right building.
The phone is answered, even at 11 p.m.
A voice assistant takes the call when the office is closed. Emergencies still reach a person.
During office hours, a person answers. Outside them, our voice assistant takes the call, recognises the caller from the building’s file, and captures a structured message: what the request is, which unit, which building, how urgent, what happened, and where. The message goes straight to the right mailbox, attached to the right file.
An emergency is never left as a message. It is routed to a human answering service, at any hour, including nights and weekends. And if the technical bridge fails, the call falls back to ordinary voicemail: no call is lost.
The assistant also knows who it is speaking to. A notary, a broker, a supplier, an inspector or a municipal officer is not handled like a resident — and none of them gets an access code or a commitment.
What we can show you. Every call is logged with its transcript and can be reviewed: 184 calls handled and retained as of August 31, 2026, across two separate client lines. We do not publish a response-time figure — that would be a commitment, and we do not make ones we could not keep on every call.
Assisted answers to resident requests
On part of our portfolio, routine requests get an answer drawn from that building’s own rules.
When a resident opens a request in the portal, the system reads it, classifies it, and — on buildings where the feature is switched on — drafts an answer taken from that building’s rules, not from a generic template. twenty-six situations are codified: noise, pests, moving in and out, EV charging, roof access, ventilation, certificates, and the rest.
It is not switched on everywhere, and that is deliberate: a building only joins once its rules have been transcribed and checked. Any building not configured is held by default, and so is a request from a building the system does not recognise.
Five automatic stops before anything is sent
A drafted answer is not a sent answer. It is held and handed to a person if the building is not enabled, if a file is already open on the subject, if the request touches safety, if it touches law or sensitive information, or if it carries an approval-required marker. A delay precedes sending, during which a manager can intercept the answer.
All of it rests on an analysis of 1,960 real requests received from September 2025 to August 2026, and 291 automated tests check on every change that the safeguards still hold.
Bookkeeping that refuses to guess
Supplier invoices are entered automatically, with the original document attached.
An invoice received by email is read, understood, and entered in the right building’s books with the source file attached to the entry. Matching does not rest on a single reading: three independent checks establish which building is liable — the address and references on the document, the extracted content, and a dedicated verification. When the three disagree, nothing is entered: the invoice is held.
Taxes are recomputed, the total is checked arithmetically, and the same invoice cannot be entered twice. Every automatic entry can be reversed from the administration screen, with its trace.
For a board that means three concrete things: the books are structured per building rather than in a spreadsheet, every entry carries its supporting document, and a doubt produces a hold rather than an error.
What our AI does not do, and will not do
The limits matter as much as the capabilities — more, for a board that has to answer for its decisions.
Never, in any automated answer
- Quote a section of law word for word, or take a legal position
- Name another resident, or confirm that someone lives in the building
- Promise a response time
- Send a building contractor into a private portion
- Apologise in terms that would admit liability
- Present itself as a person
Always handed to a person
- An emergency or a safety issue
- A formal notice, a dispute, a question of law
- A conflict between residents
- Sensitive information or a complaint naming someone
- Any request from a building that is not configured
One clarification. Our systems handle administration. They do not give legal advice, and neither do we: for the interpretation of your declaration of co-ownership, we work with the building’s lawyer.
Who watches the automation?
An automation that stops without saying so is worse than a forgotten manual task: nobody notices.
We learned that the hard way. A scheduled task went quiet and forty-seven files sat untouched for a month before anyone spotted it. Since then every automation writes to an execution log, and a watchdog raises an alert as soon as a job stops reporting in.
- Portal availability
- Probed every minute
- Third-party services
- Probed every 15 minutes
- Calls to external services
- Logged individually, with latency and cost
- Backups
- Every 6 hours
- Staff access
- Two-factor authentication, per-module permissions
- Internal tool access
- Inherits each person’s own rights, and is read-only on the books
Frequently asked questions
Will an artificial intelligence make decisions instead of our board?
No. No decision of the building is made by a system. Automation handles what is repetitive and documented: collection, follow-ups, notices, filing, bookkeeping. Decisions belong to the board and the general meeting, and sensitive matters are handed to a person before an answer is even drafted.
Do we get our records in English?
The official record — minutes, notices, the registers — is produced in French, because that is what has to stand up legally in Quebec. Everything we send your board to read and act on, we will explain in English: summaries, budgets, correspondence, and the reasoning behind what we recommend.
Does our data leave Quebec?
The platform we build is hosted in Canada, on infrastructure we administer ourselves. The portal and the bookkeeping rely on market tools whose hosting terms are documented by their publishers. Some language processing relies on external services, to which we send only what is needed to handle the request. We are glad to answer, in writing, the specific question your board has on this.
What happens if the system goes down?
The phone line falls back to ordinary voicemail, and emergencies keep reaching a person. Data is backed up at regular intervals. Pre-authorised debits, once scheduled, run without depending on our platform.
How do we know any of this actually works?
Through what is traceable. Every call is logged with its transcript, every accounting entry carries its supporting document, every automation writes to an execution log, and your handover milestones are dated from signature. A board seriously considering a proposal is also given named references at buildings we manage.
Let’s talk about what your board has to settle.
Fifteen minutes is enough to know whether we are the right manager — and to tell you plainly what we will not do.
