Atrium

Our own product: the operations layer for property managers

Atrium is a product we designed without a client: an AI native operations app for residential property managers in the US with 100 to 1,000 doors. It does not replace their property management system. It sits on top of it, reads the portfolio, and writes back only what the agents do, so the existing system stays the record. We sell it as a Figma kit for teams building property management and proptech products.

Four agents share the work. The orchestrator turns requests into plans and keeps each case in one timeline, the leasing agent answers leads and books tours, the maintenance agent triages requests and coordinates vendors, and the owner agent keeps owners informed and collects their approvals. People approve what matters from one queue, with the sources behind every decision.

The morning starts with three decisions

The Today screen opens on one sentence: 14 things handled overnight, 3 need you before noon. Below it sit the decisions, sorted by urgency, each tagged with why it needs a person: over the owner’s limit, a rent decision, a legal notice. Nothing is sent until the manager approves.

The rest of the screen answers the questions a portfolio manager asks before nine: how much the agents did this week and how much of it their policies covered, whether maintenance is on time, how full the buildings are, and how fast new leads hear back.

One queue, with the reasons attached

Approvals is a queue with the working shown. A $640 plumbing repair arrives with the vendor, the quote and the visit window, and with the agent’s reasons: the only licensed plumber free within a day, three vendors checked, a quote under the twelve month average, a slow drip rather than an emergency. A policy check lists what passed and the one thing that did not, the owner’s $500 limit, and the screen says exactly what happens if you send it.

What the policies cleared on their own is listed too, from tour replies to a $180 drain clearing under the limit, each with an undo.

A leak, from message to booked plumber

Every request becomes a case with a plan. A resident’s message about a leak at 8:12 turns into seven steps the orchestrator wrote: create the case, ask for a photo and access times, check three licensed plumbers, get a quote, ask the owner because it is over his limit, book the visit and tell the resident, then match the invoice and close. Each step carries its time, its agent and its evidence, and one rule sits under all of it: agents never spend above owner limits or enter a unit without notice.

The maintenance screen ranks work orders by SLA, so a bedroom without heat sits above a dishwasher with eight hours left, and it shows the requests the agent resolved with self help guides before a vendor was needed.

Leasing that replies in minutes

The leasing board follows each lead from first inquiry to a signed lease. The leasing agent replies to every new lead within five minutes, day or night, asks every lead the same three questions about move in date, budget and pets, offers two open tour slots and follows up on day one, three and seven. Deposits, fees and specials are drafted for a person to approve and never sent on their own.

Owners set the limits

Every owner has an approval policy written in plain rules. For one owner in the example, repairs under $500 are approved automatically and listed in his monthly summary, repairs up to $2,000 wait for his approval by text with a reminder after four hours, larger ones need two approvals and two quotes, and anything involving heat, water or safety is dispatched first and reported within the hour. Any rent change waits for him before anything is sent. The manager can be delegated to approve on his behalf up to a set amount, with an end date.

Agents with guardrails people can read

Each agent lists what it does on its own and what it always asks about. On top of that, guardrails apply to every agent: AI is disclosed in resident messages, quiet hours hold from 8 PM to 8 AM, screening, vouchers and pricing are never discussed, every legal notice needs approval, and writes pause if the sync with the property management system fails.

Leasing gets the most care, because that is where fair housing law applies. Every message is checked before it sends: the same answers and criteria for every lead, no questions about protected characteristics, and steering language blocked and logged.

Onboarding that shows what the limits mean

Setup takes four steps: connect the property management system, set approval limits, choose the agents, and run the first sync. The limits step is the one that matters. The last 90 days are replayed against the limits the manager picks, showing how many requests the agents would have cleared, how many would have needed the manager or the owner, and roughly how many hours a week that gives back. Nothing is sent until the limits are set.

The whole product on a phone

A property manager is as often in a building as at a desk, so the mobile app is the whole product rather than a companion: 42 screens at 430, from Today and approvals to leasing, maintenance, owners, agents, settings, the action sheets and onboarding. Owners get their own approval screens, opened from a secure link.

A system built to be reskinned

The file holds 72 components, 14 component sets with 64 variants plus 8 standalone components, on 49 variables in three collections for colour, status and layout. The colour collection keeps all three visual directions we explored, Jade, Amethyst and Lavender steel, as modes. There are 18 text styles in Geist, a data visualization kit, and contrast checked to WCAG 2.2.

The 80 screens are laid out in the same order on desktop and mobile, with 97% of frames in auto layout and five flows wired as clickable prototypes. The kit is on our products page.