About CREx / AI for institutional real estate
CREx Software builds CREx Intelligence and CREx OS for real estate owners and investment managers. Intelligence brings portfolio data, investment plans and the work of asset management into the same review. OS provides the data and reporting foundation beneath it.
Our focus is the owner whose properties are run by different property managers. Each manager has its own systems and reporting package. Your team needs a portfolio view that keeps the source, the reporting basis and the investment question connected.
01 / Platform
A financial result starts a conversation. The asset manager still needs to understand what changed, how it relates to the plan and what to review next. CREx is built around that relationship between property information and investment work.
The work layer
Intelligence sits above OS. Its role is to bring property information and the investment plan into performance review, investigation and analysis. The starting point is the question your team needs to answer.
Discuss the AI environment your organization uses and the work you want to support. Confirm the available capabilities, required inputs and review responsibilities for that scope.
Explore Intelligence ↗The portfolio foundation
OS includes the data and reporting foundation beneath Intelligence. Start with the property-manager roster, source packages and reporting definitions your ownership team needs.
Agree how source accounts relate to the owner's reporting chart, which periods are covered and how missing or revised inputs are handled. Keep property, entity and investor views clear.
Explore CREx OS ↗CREx OS delivery
Agentic Asset Management is how CREx OS is delivered. It connects the agreed reporting work with the people responsible for it on the CREx and customer teams.
Eligible accounts work with a named CREx operator. Responsibilities, shared capacity and coverage follow the account agreement. Your team reviews the evidence and makes the decision.
Explore OS delivery ↗02 / Our approach
The owner has to connect what happened at a property with the reason the investment was made. A useful portfolio review keeps both in view. This is the work we organize around.
A variance means more when the reviewer can relate it to the business plan, the relevant period and the assumptions behind the investment. Intelligence sits above the OS foundation to support that review. The intended output and available capabilities are agreed for your account.
Managers can use different account labels and reporting calendars. Begin with their actual packages and the definitions your team needs. Review a representative mapping question before treating similar-looking results as comparable.
Collection, mapping review and acceptance are different responsibilities. Agree who supplies each input, who follows up on an unresolved item and who accepts the reporting treatment. A named CREx operator works within the eligible account's agreed support scope.
Use the evidence to investigate the result and decide the next action. Keep supplied facts, calculations and proposed explanations distinct. An AI answer or a reporting draft still needs the appropriate human review before it becomes an investment decision or an external communication.
03 / Who we build for
Our focus is institutional owners and investment managers whose reporting crosses property-manager boundaries. The same ownership team may need to understand property operations, fund reporting and the investment plan without losing the differences between them.
04 / Team
Vimal Vachhani founded CREx in New York in 2021. The starting belief remains straightforward: an ownership team should be able to work from a clear portfolio record, connect it to the investment plan and spend its review on the questions that need judgment.
That belief connects our product and delivery work. We start with the property-manager handoff and the reporting questions owners bring to us. Intelligence and OS are the center of that work; Consulting provides a separate path when the requirement is a bespoke project.
Co-Founder & CEO
Vimal leads product and the company. His focus is the relationship between real estate reporting, portfolio data and the work of the asset manager. He is also an adjunct instructor at NYU's Schack Institute of Real Estate, teaching courses in real estate AI.
Vimal on LinkedIn ↗NYU faculty profile ↗
COO / CFO
Miriam leads finance and operations at CREx. Her work connects the company's operating responsibilities with client delivery, including how reporting work is organized and how the team supports the agreed account scope.
Miriam on LinkedIn ↗
Managing Director, CREx Advisory
Kash leads CREx Consulting work with real estate teams. He focuses on technology and transformation requirements, working with the client team to define the project, the responsibilities and the intended handoff.
Kash on LinkedIn ↗How the team works
CREx works from Texas and New York, with engineering and product working remotely. Our work brings product, finance, operations and client delivery into the same conversation. For each engagement, agree the reporting responsibilities and the people involved on both teams.
05 / Working with us
A useful first conversation identifies what your team needs to review, where the information comes from and what remains difficult today. From there, define the relevant platform and delivery scope.
Start here
Describe the portfolio, who manages the properties and the report or decision your team is working toward. Identify the question that took the most follow-up in the last review. Agree the permitted handling of any documents before sharing them.
The investment
Bring the purpose of the review and the plan it relates to. Identify the intended audience, the reporting period and the assumptions that matter. This gives the operating information a clear use in the investment team's work.
The sources
Work through the manager roster, source environments and available packages. Agree the fields, reporting definitions and refresh expectations. Keep access dependencies, missing inputs and source limitations visible while the scope is being defined.
Your account
Confirm the applicable plan, available capabilities and any eligible account support. Define who handles mapping questions, corrections and reporting acceptance. A named CREx operator works within the shared capacity and coverage set in the agreement.
The review
Use a representative source and reporting question to evaluate the proposed output. Keep the source version and unresolved items with the review. Your team accepts the treatment and decides what to do next.
As needs change
A new property manager or reporting requirement can change the work. Agree the effect on source coverage and delivery before adding it. Discuss a separate Consulting project when the requirement calls for bespoke work.
06 / Reference
A concise reference for describing the company and the relationship between the platform and project work.
| Company | CREx Software, Inc. |
|---|---|
| Focus | AI for institutional real estate asset management. |
| Founded | 2021, New York. |
| CREx Intelligence | The work layer above OS, bringing portfolio data and investment context into review and analysis. |
| CREx OS | The portfolio data and reporting foundation beneath Intelligence. The data foundation is included in OS. |
| Agentic Asset Management | CREx OS delivery, with account responsibilities and eligible support defined in the agreement. |
| Consulting | Separately scoped data, technology and AI projects. Core data projects belong in Consulting. |
| Built for | Institutional owners and investment managers, particularly portfolios run through different third-party property managers. |
| Working locations | Texas and New York, with engineering and product working remotely. |
| Plans | Review CREx OS plan scope and discuss the relevant portfolio and account requirements. |
| Source requirements | Property-manager integration and getting data from JVs. |
| Comparing options | Software buyer guide and RealPage AIM / MRI Investment Management comparison. |
| Security information | CREx Trust Center. Confirm the documentation relevant to your proposed scope. |
| Contact | contact@crexsoftware.com or book a demo. |
07 / FAQ
CREx builds CREx Intelligence and CREx OS for institutional real estate owners and investment managers. Intelligence is the work layer for portfolio review and analysis. OS includes the portfolio data and reporting foundation beneath it. The focus is the owner's view across properties, managers and investment plans.
CREx Intelligence brings investment context into the asset manager's review. CREx OS provides the underlying portfolio data and reporting foundation. Start with the question your team needs to answer, then agree the sources, reporting definitions and available capabilities needed to support that work.
Agentic Asset Management is CREx OS delivery. Eligible accounts work with a named CREx operator within the responsibilities, shared capacity and coverage set in their agreement. Consulting covers separate project work. Core is a separately scoped Consulting offering, not a prerequisite purchase for OS.
CREx focuses on owners whose property managers use different systems and reporting packages. Bring your manager roster and reporting requirements. Confirm the relevant environments, authorized access, available fields and delivery methods before agreeing source coverage. A system name alone does not establish access to a particular manager's records.
Bring the AI environment your organization has approved and the question you want to answer. Confirm the supported connection, portfolio sources, access requirements and available capabilities in the proposal. AI-client compatibility and data handling depend on the specific environment and scope.
Institutional owners, real estate investment managers and the asset-management and finance teams responsible for portfolio review. A common starting point is a portfolio spread across third-party property managers, with recurring work to reconcile reports and connect operating results to the investment plan.
Use Consulting for a separately scoped data, technology or AI project, including bespoke Core data work. Discuss the intended output, responsibilities and acceptance criteria. The OS data foundation remains included in OS; a separate Consulting engagement is scoped when the requirement calls for project work.
Review the CREx OS plan scope and discuss your portfolio, source requirements and working users. Available capabilities and any account support are defined in the proposal and agreement. Confirm eligibility, responsibilities, shared capacity and coverage. Consulting has its own agreed project scope and commercial terms.
Timing depends on source access, the reporting requirement, configuration and the work your team needs to complete. Agree the sequence and acceptance milestones during scoping. There is no universal implementation timetable for every portfolio or source environment.
Your team reviews the evidence, accepts reporting treatments and makes investment decisions. Agree who supplies sources, resolves mapping questions and approves outputs. Confirm access, export and delivery terms for your account rather than assuming every record is available through every interface.
Next step
Tell us who manages your properties, which reports your team relies on and what you need to understand next. Start a conversation about Intelligence, the OS foundation and the right delivery scope.
Book a demo