Work orders, dispatch, and owner reports, automated inside your property system. Leasing and resident platforms like EliseAI cover prospect and resident messages. Work orders, vendor dispatch, and owner reporting still sit in AppFolio or Yardi and in someone's inbox. We put an engineer with your operations team to decide what to buy and to build the rest.
Bring a month of maintenance requests for a few properties.
Published results in property management
Asset Living, with more than 445,000 units, put one platform across leasing, collections, renewals, and maintenance.
Asset Living's EliseAI-enabled communities gained 278 basis points of occupancy from the start of 2025 through Q3.
One platform across leasing, collections, renewals, and maintenance, rolled out alongside onsite teams across a portfolio of more than 445,000 units.
Figures as reported by the vendor or customer at the linked source. They are not OpenNash results.
Where our engineer comes in
Asset Living chose one platform and rolled it out alongside onsite teams, which takes people who can run both the evaluation and the rollout. These are platform-wide numbers, not a result for maintenance triage alone. Our engineer runs that evaluation for you and builds the maintenance and reporting steps, with a login to your property system and time with your regional managers.
| Decision | What we look at | Outcome |
|---|---|---|
| Buy a leasing and resident platform | Message volume, after-hours share, and cost per unit for each platform. | A recommendation with cost per unit. |
| What to build | Work-order triage, vendor dispatch, and owner reports from your system data. | Built in your accounts. |
| What the agent may decide | Applicant decisions and emergencies. | People make every applicant decision. Emergency rules route to on-call with a tested fallback. |
| Which properties first | Request volume and staff time per property. | A pilot on a few properties, then the portfolio. |
Why forward-deployed engineers
Built for their largest accounts, deploying their own models. OpenAI's deployment company launched with more than $4B. ↗
Configure their own product, priced per seat or per resolution.
A small senior team, ex-Palantir, Meta, and Databricks. Any model, any vendor. Free pilot, then a flat monthly fee.
Even OpenAI closes the gap with engineers in the room. Source: OpenAI, What FDE means at OpenAI, Oct 2026.
The first eight weeks
Written down with your team in week 1. The pilot is free, and it has to pass these before anything goes further.
Example acceptance tests, not results from a customer deployment. Yours are written with your team.
Systems we work in
Rules from day one
FAQ
We confirm the available API, export, or approved integration route for your product and account before scoping the pilot. The property system stays the record.
No. A person makes every applicant decision.
Requests that match your emergency rules go to the on-call contact at any hour. If the notification fails or is not acknowledged, a documented fallback runs.
Why you need one
A senior engineer joins your team on a laptop you issue, tests the options on your data, and puts one property management workflow into production in 4 to 8 weeks. It starts with a free 14-day pilot judged against test cases you agree in writing.
After launch, we run and improve the workflow on a flat monthly fee, or your team takes it over. The code, tests, and runbook are yours either way.
Bring a month of maintenance requests for a few properties.