---
title: "Lia, AI for property management and condominium managers: from system of record to system of action."
url: "https://simonebova.com/en/runs/lia"
lang: "en"
author: Simone Bova
alternates:
  it: "https://simonebova.com/md/it/runs/lia"
  en: "https://simonebova.com/md/en/runs/lia"
  pl: "https://simonebova.com/md/pl/runs/lia"
---

# Lia, AI for property management and condominium managers: from system of record to system of action.

Lia moves property management work forward for condominium firms: email, phone and WhatsApp become cases. What I learned building it with Raffaele Zarrelli.

Name: Lia

Terrain: Startup · property management · condominium administration

When: 2026 → now

Role: CTO and co-founder: architecture, engineering, product and adoption

| Fact | Value |
| --- | --- |
| Terrain | Property management · condominiums |
| Team | Simone Bova and Raffaele Zarrelli |
| Decides | The manager |
| Accounting | Coming soon |

## The situation

An Italian condominium management firm already has its management software: it keeps the accounts, the records, the history. It records what has already happened. Everything that still has to happen lives in the inbox, on WhatsApp, on the phone and in the manager's head: the resident's request, the supplier to call, the document to dig out, the payment reminder to send. Every firm has a system of record. None has something that does the work for them.

## What I did

With Raffaele Zarrelli we built Lia. Raffaele leads discovery, sales and partnerships; I lead architecture, engineering, product and adoption. Lia turns every request, from email, phone or WhatsApp, into a case linked to the right building, the people, the documents and the supplier, and proposes the next steps. Every answer shows the document it comes from. The manager approves, Lia executes. On money, legal acts, disputes and emergencies, the manager always decides.

We chose to work next to the accounting software the firm already uses, instead of asking it to switch. Accounting is coming soon, after operations, for a reason I explain below.

## What changed

Lia has been in production since June 2026. Inside the app, managers can ask Lia things and get them done by talking to it, and every action stays on record with who did it. The residents' portal and the supplier link are built and we are switching them on. The management software keeps recording. Lia moves forward what has to happen.

## What I learned

In a management firm, the manager is the cable between systems. A single request means reading the email, finding the building rules or the meeting minutes, updating the calendar, opening or updating the case. It looked like an overloaded inbox, and a good email summary looked like the answer. The real work was rebuilding context and carrying it from one tool to another, and a summary leaves all of it in place. That is why Lia acts on the case, where the context is already rebuilt.

The most frequent request was accounting, and it was not the main pain. “If I use management software without the accounting part, I'm using half of it”: we heard that often. When we asked managers to choose between concrete problems, they put repairs, suppliers and communications first. One said it plainly: “It's not the accounting. The problem is the practical side.” There is also a cost you can't see from outside: switching software means retraining the whole office and moving buildings one at a time, each after its own year-end close. So accounting comes after, as outputs ready to use inside everyday work.

Sending the request to the supplier is the small part of the job. One manager told us they often learn a repair was done only when the invoice arrives. Availability, appointment, silence, chasing and proof of the work are separate steps, and no management software follows them. My idea was a link tied to a single case, sent on WhatsApp: the supplier opens it, uploads the photos, and everything lands in the right place without learning any software. The link solves two problems at once: people who don't use management software don't have to start, and a photo arrives already attached to the right job.

A reminder that is right on the numbers can be wrong to send. One manager explained that some residents have payment arrangements agreed verbally, so reminders must not go out on their own: “not automatically, because there are very delicate balances.” Another checked every missed payment against online banking before chasing anyone, because they didn't trust the payment status. The second reason disappears with better data; the first stays even with perfect data. In Lia, the manager's approval protects the relationship with people, and it will stay even when the model makes fewer mistakes.

People choose writing because it leaves a trace. Lia started from voice, and at first we thought a more natural voice was the lever. Managers told us something else: “People prefer to write, because something written stays.” Request, acknowledgement and outcome serve as evidence, with residents and in building meetings. The phone remains an important way in, and the product is the case that comes out of it, with its history.

[Lia on yempik.com](https://www.yempik.com/prodotti/lia)

[Runs](https://simonebova.com/md/en/runs)

[simone@yempik.ai](mailto:simone@yempik.ai) · [Book a call](https://calendar.app.google/LKDrQPKGV2EAFCMN9)