All case studies
Repa Immobiliare · Real estate · Property management

Getting a property portfolio off paper, with software that never goes online.

A Windows application for Repa Immobiliare's property managers: every repair, deadline and owners' meeting across the properties they manage, held in one place, synchronised across their machines without ever connecting to the internet.

Development & Monthly Support3 months to launchSince 2026Switzerland2 people
Stylised illustration of a property task manager: a list of properties down the left, and a table of tasks with status, sub-task progress, due date and assignees.
An illustration rather than a screenshot: in agreement with the client, we don't show the real interface here. It gives the shape of it: properties on one side, and the tasks against each one, with an owner and a due date.

Context

Who they are.

Repa Immobiliare manage real estate on behalf of owners. That work is a steady stream of obligations across many properties at once: repairs to arrange, schedules to hold, owners' meetings to prepare and follow up. Until now, all of it was tracked on paper.

The problem

What they walked in with.

Paper meant things went missing: a deadline here, a repair there, and no reliable way to see what was outstanding across the portfolio. They needed one place to hold it all, running on their own machines, staying in step with each other, and not depending on an internet connection to work.

Our approach

How we worked.

[ 01 ]

One place instead of paper

Tasks organised by property: repairs, schedules, owners' meetings. Each one can be commented on, broken into sub-tasks and assigned to a person, so every item has a visible owner and a visible history.

[ 02 ]

In sync, off the internet

The application keeps their machines in step with each other without going online. The data stays on their own equipment, which is how they wanted it.

[ 03 ]

Updates that take care of themselves

New versions are distributed centrally, so every machine ends up on the current build without anyone installing anything by hand.

[ 04 ]

Electron, again for good reason

A single codebase delivering a proper desktop application, which is what let two people build and ship the whole thing.

Highlights

The interesting parts.

  • Every task carries comments, sub-tasks and an assignee, so a repair or a meeting has someone's name on it and a record of what happened.
  • The machines stay synchronised with each other without an internet connection.
  • Updates roll out centrally: everyone is on the newest version without doing anything.

Stack

What we built it on.

ElectronWindows

Timeline

How it unfolded.

Phase 1

Scope

How the work actually runs across the portfolio, and what has to keep working without a connection.

Phase 2

Build

The Electron application: properties, tasks, sub-tasks, comments and assignment.

Phase 3

Sync & updates

Keeping the machines in step with one another, and delivering new versions centrally.

Phase 4

Rollout

Onto their machines, and off paper.

A similar problem?

Let's see if we're a fit.