Embedded Factory Logo

A property firm where the system does the work.

Your headcount tracks your housing stock, and 70% of the work is still admin. Here, a notice to quit, unpaid rent or an owners' meeting moves forward by itself; your teams step in only to decide.

See how it works ↓
01

A notice arrives.

Today, that letter sets off fifteen steps, tracked in a spreadsheet and an inbox. Here, it opens a file that fills itself in, then stops at the one question that is yours.

Filled in by the system
  • Notice matched to lease07:52
  • Notice period checked07:52
  • Acknowledgement drafted07:53
  • Owner informed07:53
Repairs before re-letting
B-204 · 07:53

Refresh the kitchen first?

Three human decisions; the system does the rest.

Three decisions in 90 days
  1. Day 0

    The file opens: four steps done before noon.

  2. Day 10 · Repairs?

    The pre-inspection comes back with photos; a quote follows. You decide.

  3. Day 45 · Applicant?

    Applications are screened and ranked. You choose; the lease is drafted.

  4. Day 90 · Deduction?

    Move-out inspection, differences priced, a deduction proposed. You approve, the file closes.

02

What each desk sees.

Each role has its desk, a screen holding only its pending decisions.

Weeks later, the manager picks the applicant and the contractor, nothing else.

Mock-up. People and data are fictitious.
03

What your tenants and owners see.

The same file, seen from the other side: the tenant acts from their phone, the owner decides from theirs.

The tenant

They pay by QR-bill, read their lease, report a stuck blind with a photo; the assistant answers from the house rules.

Home
New request
Assistant
The owner

They follow rents collected and repairs under way, receive their monthly report, and approve a contractor's quote with one tap.

Owner — decisions

A tenant's request, sent from the app, lands in their move-out file; the manager receives it prepared, answer drafted.

Mock-up. People and data are fictitious.
04

The system proposes, learns from your validations, then runs on its own.

Nothing is automated by default. Every action carries a confidence score and a threshold you set per type of action.

Match the notice
ProposedRuns on its own
A lease is proposed for this notice; the manager confirms or corrects with one keystroke.

A lease is proposed for this notice; the manager confirms or corrects with one keystroke.

Never an agent
  • Legal deadlines, amounts, due dates: versioned, tested rules
  • Anything sent to a tenant, an owner or a court is still validated by a person
In the log
07:41 · System · Notice read, lease found

Every line is dated, signed, and undone with one click.

05

Integrated, not layered.

An AI layer on what you have automates retyping. We build the whole system: six parts around a single file.

The ERP
records
Accounting, payments, payroll, leases, statements, on a proven base.
The DMS
keeps
Letters, quotes, minutes: every document filed in its case, retrievable ten years on.
The files
move
Notice, unpaid rent, claim, meeting: each knows its steps, its legal clock, its next action.
The orchestration
dispatches
It puts the AI, the rules and your desks to work; you receive only the decision.
Mobile
captures
Visits, inspections, repairs: photos from the field go straight into the file.
The portal
answers
Tenants and owners pay, ask and decide from their phone.

Your CRM and your bank keep their role: they publish their events, the file picks them up.

06

This project is already under way.

Embedded Factory designs and runs this system; here is what exists.

The field
A week-long audit in a French-speaking Swiss firm, from accountant to director: notices were tracked by hand.
Where it stands
Desks and portal as clickable mock-ups; base installed; build started.
Who builds it
Zurich, two products live: Property360 and Typr.
Hosting
Own infrastructure, in Switzerland.
07

How do we roll it out?

We migrate buildings, not an organisation. You upload a building's documents, it rebuilds itself on screen; your senior checks instead of retyping.

  1. Kick-off

    Migration plan within two months: order of buildings, first batch, calendar.

  2. Wave 1

    Private owners, simple mandates: your key users correct quickly, each file type tested on your portfolio before it goes live.

  3. Next waves

    Portfolios, then institutional owners, once the gain is proven on the first buildings, measured continuously.

  4. Condominiums

    Switch between two financial years.

Your current tools stay live until each building switches; each step is paid when it is delivered.