The software a residential building actually deserves.
Every category of property — offices, hotels, warehouses, hospitals — has its own industry of software. Residential, the one most people actually live in, does not. This essay is about why that is, and what we are doing about it.
A founding essay · 8 minute read
Chapter 01
The gap
Software has eaten almost every category of property. Offices have enterprise facilities platforms. Warehouses have logistics platforms. Retail has store operations. Hotels, hospitals, airports, schools — each one has an entire industry of vendors, conferences, and acquirers dedicated to the specific job of running that kind of building.
Residential housing — the category in which most people spend most of their lives, into which most household wealth is poured — has nothing of the sort. The largest purchase a person will ever make is coordinated for handover on a WhatsApp group. The annual general meeting is run on paper ballots. The minutes, if they exist at all, live in a Google Drive owned by a secretary who may or may not still be the secretary next year.
The tools that do exist pick a slice. Accounting SaaS for boards. Snagging software for developers. Noticeboard tools for residents. They do not talk to each other. More importantly, they do not remember each other. A building that changes accountant or board or developer effectively starts again, because no piece of software is designed to own the continuity of the building itself.
That is the gap. Not a missing feature — a missing category.
Chapter 02
One building, one platform
A residential building is one continuous thing. The contract a buyer signs in 2025 is the same unit their children may inherit in 2065. The defects recorded on handover day are the same defects a board will point to when it files a warranty claim four years later. The monthly maintenance payment is the same flow that, fifteen years on, funds the reserve that pays for the roof.
The software should be continuous too. This is the single principle Yuniyo is built around. One platform, from the pre-purchase contract through handover day, into every year of community life that follows. The resident who signs off-plan today is on the same building’s community board, in the same platform record, a decade later.
Stitching pre-handover, handover and post-handover into one product is harder than building three disconnected tools. It is also the point. A building isn’t three problems — it’s one long problem that looks like three, because nobody has built the platform to see it whole.
Chapter 03
The 18-month wedge
In most European markets, a buyer signs the pre-purchase contract eighteen to twenty-four months before the keys change hands. For that entire window — the most anxious stretch of the whole transaction — the buyer hears from the developer through whichever channel the sales team happens to prefer. Email. A portal nobody logs into. A WhatsApp group with a salesperson who changes jobs halfway through. In the rare happy case, a shared Excel spreadsheet of milestones.
This is the wedge. It is the phase where no software currently lives, and where everyone involved has the most to gain from structure. For the developer, it is where brand trust either gets built or broken, and where the next project’s referrals quietly originate. For the buyer, it is where future neighbours become known people. For the board that will one day run the building, it is where a community identity begins to form.
We think this is where the modern residential platform actually starts. The buyer who joins the building’s community on contract day — watches the build rise, meets the future neighbour across the hall, votes on the colour of the lobby — is not an idle user to be retained. They are the first customer of the post-handover platform, eighteen months before it even runs.
Chapter 04
Why Europe first
Europe is the market where the institution we are building for — the apartment association, called korteriühisus in Estonia, Wohnungseigentümergemeinschaft in Germany, copropriété in France — is a legally defined entity with statutory powers, quorum rules, minute-keeping obligations, and a defensible audit trail. The institution already exists. What doesn’t exist is software fit to serve it.
We start in Estonia for three reasons at once. Its apartment-association law is among the most developed in Europe. Its digital identity stack — Smart-ID, Mobile-ID, eIDAS — is the best in the world at the job the platform most needs it to do. And the density of recently-handed-over residential projects puts the pre-handover wedge squarely in reach. Estonia is where we prove the platform end to end. The same compliance discipline then extends into the rest of the EU, one statutory framework at a time.
Europe is where the institution is strong enough to hold the platform. Starting elsewhere — in a market with weaker association law and stronger chat-tool inertia — would tempt us to build a lighter product that never becomes the system of record. The whole point is to build the system of record.
Chapter 05
Infrastructure, not features
The temptation in any consumer-adjacent category is to ship things that look good in a screenshot. A prettier feed. A nicer push. A cuter way to file a maintenance ticket. None of it is the job.
The job is the quiet, boring, compounding work that turns a building into a well-run building. Votes that satisfy statutory law. Payments that reconcile to the bank statement to the euro. Minutes that will still be readable in year thirty. Handover records that hold up in a warranty dispute. Done properly, this work becomes invisible — and that is the point. Nobody should have to be a hero to keep a well-functioning building that way.
Yuniyo is built as infrastructure for residential life. The consumer-grade surfaces — the resident interface, the community feed, the amenity booking — ride on top. They matter. They are not why the platform exists. The platform exists to make the fundamentals of residential life — payments, votes, records, communication, handover — infrastructure-grade across every market we enter.
Chapter 06
What comes next
Describe Yuniyo in five years and it is the shared source of truth for the institutions that run residential buildings across Europe. Start in Estonia, extend through the Nordic and Germanic markets, continue across the EU as each statutory framework gets integrated. One building at a time, one country at a time, one decade-long operational life at a time.
In parallel, our footprint in India is seeding a second product thesis. Rent and maintenance payments, reported to credit bureaus at scale, become the foundation of a portable tenant credit layer for a market where most households don’t own their home. That is a longer arc. A separate essay.
For now, what we are working on is the European residential building — one at a time, from pre-sale through handover into year one, year two, year ten. If that sounds like something you should know more about, we would like to hear from you.
If this essay resonates, we’d like to talk.
Whether you are a developer planning a residential project, a board thinking about the next decade of your building, or an investor — we reply within one business day.