The data layer under your whole portfolio.
Every system you run lands in a warehouse you own. The same resident, unit and number read the same across all of them, and your team and your agents work from that one version, each answer traced to the system it came from.
One question, four layers
Follow one renewal question from the source systems to a signed offer.
Connect lands the data and Data Map makes it agree; Propexo MCP and Agents both work from what Data Map holds.
-
01 · Connect
The rows land in your warehouse, from every system that holds a piece of the answer.
The lease and its rent sit in the PMS, comparable rents in the pricing tool, work orders in maintenance and reviews in your reputation tool. Connect keeps all of them current in an account you own.
See Connect →ReadFromAs ofLease and current rentPMS06:10 todayComparable rentsPricing tool06:10 todayOpen work orders on the unitMaintenance06:05 todayLatest review of the unitReputationyesterday -
02 · Data Map
Three spellings of one unit become one unit, and “under market” gets one definition.
Each system names the unit its own way. Data Map links them, scores every link, and holds the one definition every answer below uses.
See Data Map →- PMS · “Bldg 1 Unit 12B”
- Pricing tool · “1-12B”
- Maintenance · “Unit 12-B”
Unit 12B 3 records linked · each link scoredDefinition · under market Current rent below comparable rents by more than the margin your team sets, written once. -
03 · Propexo MCP
Your asset manager asks in the AI tool they already use, and the answer arrives with its sources.
No request to the data team and no export. The question was approved once, and the answer carries the definition and the systems it came from.
See Propexo MCP →Which May renewals are priced under market?
14 leases renewing in May are under market, across 6 properties.
Definition: under market (your team’s) · Sources: PMS 06:10 today, pricing tool 06:10 today
-
04 · Agents
An agent drafts the renewal offers, and nothing goes out until you sign.
It reads the same linked records and the same definition, checks the open work orders on each unit, and stops where your rules say a person decides.
See Agents →Renewal agent · MayOffers drafted12Held for an open work order2Sending the offers needs your signature.
Building software on top of a property management system? The Unified API gives you one normalized API across the major systems.
Where you start
Start where your data is today.
Most portfolios begin with Connect. If your systems already land in a warehouse, you begin a layer up.
Data is scattered
Start with Connect
Every system you run lands in a warehouse you own, and stays current.
See Connect →Data is in one place
Start with Data Map
The same resident and unit recognised everywhere, and one definition of every metric.
See Data Map →Data is trusted
Add Propexo MCP
Your team asks the questions you approve in the AI tools they already use, answered from what Data Map holds.
See Propexo MCP →Data is actionable
Hand the next job to an agent
Each agent runs one job end to end on the same records and rules, so the next one starts from everything already in place.
See Agents →Where it runs
Your account holds the data. Ours holds the engine.
Leave tomorrow and everything in your account stays with you.
Your warehouse account · Snowflake, BigQuery or Databricks
- Raw data from every system
- The links between matching records, each with a confidence score
- Your definitions of every metric
- What your agents learn about your portfolio
Propexo
- The pipes, and their upkeep
- The engine that runs your rules
- Answers change nothing. Propexo MCP is read-only and answers only the questions you approved.
- Signatures where you want them. You choose which agent actions run on their own and which wait for a person.
- Every link can be checked. Each match between records carries its score, and the source records stay as they were.
Frequently asked questions
What is the Propexo Platform?
The Propexo Platform is the data layer for a multifamily portfolio: it moves the data out of every proptech tool you run and into a warehouse you own, makes it one trustworthy portfolio, and puts AI access and agents on top. It has four components, each compounding the one beneath it. Connect lands every system in your warehouse and keeps the connectors maintained. Data Map makes that data one portfolio: entity resolution links the same resident, unit, vendor, property and lease across systems; governed metrics give every number one definition; the ontology maps how the portfolio fits together; and the context layer attaches your rules, decision logs and notes to the data. Propexo MCP answers the questions you approved inside the AI tools your team already uses, with the definition and the source on every answer. Agents run a job in your portfolio end to end on those records and rules. Every answer can be traced to the system it came from, and everything built from your data stays yours.
What does Connect do?
Connect moves the data out of every proptech tool you run and lands it in a warehouse you own: PMS, leasing, maintenance, payments, access and the rest of the catalog. Propexo builds and maintains the connectors, so a vendor API change is handled for you. It deploys immediately, with the managed Snowflake warehouse as an option if you do not want to run your own.
What does Data Map do?
Data Map makes the landed data one portfolio. Entity resolution recognises the same resident, unit, vendor, property and lease across systems and links them, with a score on every link and the sources left as they were. Governed metrics give each number one definition, written once. The ontology maps how properties, units, leases, residents, vendors and work orders relate, and the context layer attaches your rules, decision logs and notes to the data they describe. It is configured to your spec.
What does Propexo MCP do?
Propexo MCP puts your data inside the AI tools your team already uses, such as Claude and Copilot. It answers the questions you approved, read-only, with the definition and the source attached to every answer, so a figure that reaches an investor can be traced back. It is configured to your spec.
What do Agents do?
An agent runs one job in your portfolio end to end: renewals, applications, work orders, delinquency, or any job you can describe. It reads across your systems through Data Map, decides inside the rules you set, acts, and records what it did. You choose which actions run on their own and which wait for a signature. Agents are configured to your spec.
Do we have to buy the whole platform?
No. Connect is sold on its own, and most customers start there. Data Map is sold on its own when your data is already landed in a warehouse. Propexo MCP and Agents require Data Map, because both work from the resolved records and governed definitions it holds; they are added on top of it, one workflow at a time.
What do we need in place to start?
Credentials for the systems you want landed, and a warehouse account or the managed Snowflake option inside Connect. No data team, and no custom build on your side.
What happens if we stop working with Propexo?
Everything built from your data stays with you: the raw data from every system, the links between matching records with their confidence scores, your metric definitions, what your agents learned about your portfolio, and the warehouse account itself. Your data, and every insight generated from it, is yours to keep.
Do we need a data team?
No. Propexo builds and maintains the connectors, and the managed Snowflake warehouse when you choose that option. No data team is required.