Verani is an AI system for property managers and portfolio owners. It knows every lease, every side agreement, every deadline — and drafts your correspondence. Nothing is sent until you approve it.
Who it serves
Which describes you better?
You manage properties for owners — with a team, mandates, and a growing book of units.
The page adjusts a few passages to your situation. Everything else stays the same.
The status quo
Every management firm fully owns the knowledge of its portfolio — spread across folders, inboxes, and the memory of individual staff. Using it takes manual work, every single time.
Requests
Every tenant question requires someone to open a contract.
Side agreements
Commitments live in someone's memory or someone's inbox.
Deadlines
Dates from service contracts surface when they are already late.
Growth
More units mean more hiring — and the same knowledge scattered across more heads.
The Inbox — Leverage
The following six scenes show the system at work: an overflowing inbox, the ingestion of every document, a question asked across the entire portfolio, a drafted reply held for approval, deadline monitoring, and the effect on your capacity.
Act I / VI — The day begins with forty messages.
An inbox fills with forty mundane tenant requests: a dripping tap, a rent certificate, a noise complaint. One message is lifted out: the Hartmann family asks whether their lease permits them to keep a cat.
Act II / VI — Every document becomes readable. For people and for machines.
Leases, side agreements, house rules, maintenance contracts, and handover protocols are ingested, segmented into units of meaning, and indexed into a searchable body of knowledge. 1,284 documents become 41,902 queryable segments — illustrative figures.
Act III / VI — Ask your portfolio.
A question in plain language — how many tenants may keep a cat under their lease — is answered across every contract at once: 47 of 312 leases expressly permit small pets, a further 12 only with the landlord's consent (illustrative figures). Every statement carries a reference to the exact clause in the exact document.
Act IV / VI — Written in your voice. Sent on your word.
The Hartmann family's request arrives in the channel. The assistant — you choose its name and personality — checks the lease and the building history, then lays out a complete reply in your tone of voice, with your signature. The draft waits for approval. Only after you approve is anything sent: Verani drafts, you decide — always.
Act V / VI — Deadlines that raise their own hand.
From maintenance and service contracts, the system extracts obligations and deadlines — heating maintenance, smoke detector inspection, legionella testing, notice periods — and arranges them on a twelve-month timeline. Ahead of each date it drafts the outreach to the responsible tradesperson, proposes two appointment windows, and waits for approval. The confirmed appointment snaps onto the timeline.
Act VI / VI — More units. Not more people.
The effect in numbers, illustrative: hours per week returned to the team. Response times falling from days to minutes. More units per full-time employee. Your portfolio grows — your team doesn't have to.
Scope
After the demonstration, the reference: what the system ingests, answers, drafts, and monitors — and what it categorically does not do.
Knowledge
- 01Document ingestionLeases, side agreements, house rules, service contracts, protocols, correspondence — fully ingested and indexed.
- 02Semantic searchFinds content by meaning, not by keyword — even when the document phrases it differently.
- 03Portfolio-wide analysisOne question, every mandate: answers across all contracts and buildings at once.
- 04Clause-level citationsEvery answer points to the exact clause in the exact document.
- 05Side agreements includedCommitments outside the main contract are read and taken into account.
- 06Continuous ingestionNew documents flow into the body of knowledge as they arrive.
Communication
- 07Drafted repliesIncoming tenant requests receive a complete draft with verified contract context.
- 08Your voiceTone, salutation, punctuation, signature — configured to your house style.
- 09Your own personaThe assistant carries a name and personality that you define.
- 10Escalation rulesDefined cases go straight to you, without a draft.
- 11Multilingual correspondenceRequests in other languages are understood and answered in yours.
- 12Complete audit trailEvery draft, every edit, every approval remains traceable.
Coordination
- 13Obligation extractionDeadlines and recurring duties are read out of contracts.
- 14Deadline monitoringDates announce themselves with lead time — not after they've passed.
- 15Tradesperson outreachOutreach to service providers is drafted, appointment windows included — across every mandate.
- 16Appointment coordinationProposed windows, confirmed dates, reminders.
- 17Follow-upOpen matters stay open until they are resolved — and are chased.
Control
- 18Human approvalNo message leaves the system without your explicit approval. Structural, not configurable.
- 19Roles and permissionsWho sees what, who approves — mapped to your organisation.
- 20Complete historyEvery action carries its timestamp, its author, and its context.
- 21No autonomous sendingThe system drafts. It does not send on its own. Without exception.
- 22Clear limitsWhat the system doesn't know, it says so — and hands over to you.
Working together
Discovery & scope
We look at your portfolio, your workflows, and your documents. The shape of the engagement follows from that.
Implementation
For you or with your team: document ingestion, configuration of voice, persona, and rules.
Go-live
The system goes live inside the chat tool you already use. No new software, no migration.
Support & improvement
We stay: support, adjustments, and improvements shipped to you continuously.
Scope, integration depth, and rollout follow your organisation — not a plan we picked for you.
After go-live we stay: support, adjustments, and improvements we ship to you.
Financing arrangements are available where they suit the structure.
What that means for you specifically, we'll clarify in fifteen minutes.
Security
Human approval
Nothing leaves the system without explicit approval. That is how it is built — not configurable, not optional.
Data residency
Processed and stored within the European Union. The region — Ireland or Germany — is agreed with you during implementation.
No training on your data
You decide which AI model is used. We work with providers and contracts that exclude the use of your content for training.
Traceability
Every answer carries its source. Every action carries its history.
Who is behind it
Verani was built inside a real portfolio. We manage property ourselves — and the problem this system solves was ours first: knowledge in files, work on demand, deadlines in one person's calendar.
So we built the system we needed. It runs on our own portfolio today, every day. What we implement for you is the same software — shaped to your organisation.
Reference logos and review stars we cannot offer. An operation that runs on it, we can.
Questions
No. It removes the file work: looking things up, retyping, chasing. Decisions — and every approval — stay with your people.
No. Verani works inside the chat tool you already use — typically Slack. There is no new software to learn and no migration project.
They are ingested, segmented into units of meaning, and indexed — leases, side agreements, protocols, correspondence. From then on, the entire portfolio is answerable, not just individual files.
That depends on the size of your portfolio and the depth of integration you want. A blanket figure would be guesswork. We set the timeline after the discovery phase — once we know your documents and your workflows. It forms part of the proposal, not an estimate we revise later.
The scope determines the price: portfolio size, integration depth, level of support. We'll put a number on it in the conversation — after fifteen minutes you'll know the order of magnitude. Financing arrangements are available.
No. Every outbound message passes through your approval. That is structural and cannot be bypassed — not even on request.
Then it says so — and hands the matter to you. Answers are grounded in your documents rather than a model's memory, and every statement carries its source, so you can check any figure against the clause it came from. Where the files don't answer a question, that gets said rather than filled in.
Requests in common languages are understood; replies are written in your language and your tone. German and English are the standard.
Verani runs as its own system alongside your property management software — not inside it. We set up an instance that belongs solely to you: your documents, your configuration, your chat tool. Your existing software stays as it is; there is no migration and no interference with running processes. Our own access is limited to maintenance. Whether a direct connection makes sense later is something we'll discuss — it is not a prerequisite for running the system.
A live walkthrough of the running system, your questions, no obligation. Longer, if your questions warrant it.
Scheduling
Booking runs through Calendly and loads only when you click it. Nothing is sent to Calendly before then.
Or write to us directly:
contact@verani.ai