Tasks, vendors, and the calendar—finally talking to each other.
Operations is where the working surfaces of the day live together: tasks, calendar, team messages, vendor tracking, site health. None of it is glamorous, and all of it is where a portfolio actually gets run day to day—which is exactly why scattering it across a sticky note, a forwarded email, and three separate logins is where things fall through.
The task points at the property. The property points at the vendor.
Most PMCs run operations across whatever tool was cheapest or already installed when someone needed it—a shared calendar for inspections, a group text for the maintenance team, a spreadsheet for vendor certificates of insurance, email for everything else. Each piece works fine on its own. None of them know about each other, so every task that touches more than one of them means opening two or three systems just to get the full picture.
In Operations, a task carries the property it belongs to; the property carries the vendor doing the work; the vendor carries the last message about that job and the status of their insurance. Click into any one of them and the rest is right there—not a separate search in a separate tool.
What’s due, and when, without the sticky note.
Every open task shows up where the person responsible for it will actually see it—on their list, on the calendar, in the hub they already have open—instead of living in whoever’s memory happened to be free when it came up. Renewal batches, inspection windows, make-ready approvals: each one carries a due date and a status, and each one is visible to more than one person, so coverage doesn’t depend on one specific manager not taking a sick day.
The calendar isn’t a separate app bolted on afterward—it’s the same task and event data, just viewed by date instead of by list. An elevator inspection window and a renewal offer deadline show up on the same week without anyone having to reconcile two calendars against each other.
The rest of the job, where the task already is.
Team messages stay attached to the property and the task they’re about, not scattered across a group chat where context disappears after a hundred messages. Vendor tracking keeps bids, certificates of insurance, and response times visible so an overdue vendor is a status on the board, not a surprise. Site health rolls up the physical condition items—the things that turn into emergencies if nobody’s watching—alongside everything else, not in a separate binder.
None of this needs to be exciting to matter. A missed vendor follow-up or a task nobody remembered becomes the emergency work order that shows up in next week’s briefing as a problem instead of the routine item it should have been. Operations exists so the boring, essential parts of running a portfolio stay visible and connected instead of quietly slipping between systems.
Site health and vendor status feed the same watch/critical logic that drives Performance’s property status—an overdue certificate of insurance or an aging emergency ticket isn’t just sitting in a list somewhere, it’s part of why a property shows as watch instead of healthy.
Kick the tires. Then bring us your portfolio.
We’re onboarding early-access partners now—PMCs who want a real say in what gets built next. Bring your unit count and your worst operational headache.