01 / Source
Property management and ERP
Yardi, MRI, RealPage and Entrata.
- General ledger
- Rent roll
- AP / AR
- Leasing
CREx Consulting
Two practices for real estate owners and operators.
CREx Core is a separately scoped Consulting engagement for data, reporting and AI foundations, including work on Microsoft Fabric. CREx Blueprint covers technology selection and implementation. Neither is a prerequisite tier of CREx OS.
01 CREx Core
Core is a separately scoped Consulting engagement. Agree the Microsoft Fabric data, reporting and AI workstreams, source coverage, deliverables and handoff requirements for the project.
Different source systems and reporting definitions can create recurring preparation work. Core scopes a data and reporting project around the sources, environment and handoff your team needs.
A governed data foundation first. Then reporting. Then analytics. Then AI. In that order. Skipping steps is how firms end up with a chatbot that hallucinates on their rent roll.
How it flows Three layers Report library Deployment Questions
Core / How it flows
One pipeline, four hops. Governance and observability are scoped for each stage, and all of it runs on Microsoft Fabric.
01 / Source
Yardi, MRI, RealPage and Entrata.
02 / Warehouse
A governed CRE semantic model.
03 / Reporting
Reports and dashboards in Power BI.
04 / AI
Governed AI on your data.
Powered by Microsoft Fabric: OneLake, Lakehouse, Direct Lake, Purview governance and Copilot Studio, with end-to-end lineage.
Core / Three layers
Each layer builds on the last. Agree the data foundation first; later work depends on its readiness.
See the deployment phasesSourcesYardiMRIRealPageEntrataERP
Select a layer to see what it does
01 / 03 Data Core
Data pipelines and source-specific integration work are scoped per engagement, including permissions, available connectors and acceptance criteria.
Assess the source access, available connectors and integration work required for the selected systems. Custom work is scoped per engagement.
A governed data model that speaks rent roll, fund and waterfall, not database.
Agree the refresh schedule, exception review and reporting acceptance needed for the project.
Deploy in your Azure tenant, in your on-prem environment or as a hybrid.
Payroll, expense, ESG and market data in the same governed layer.
02 / 03 Analytics Core
Dashboards and reports for CRE reporting needs. Scope the relevant roles, source detail and access requirements.
Discuss portfolio health, variance and capital-plan views, including the available drill-downs and source detail.
Tenant rollover, rent stability and NOI variance, with commentary, not just numbers.
Waterfall, commitment and returns reporting for LPs.
AP/AR, work orders, leasing and property management KPIs on your cadence.
Compare your portfolio to market data and peer comps in the same workspace.
Bring your own logic. Analysts build their own measures on the governed model.
03 / 03 AI Core
Agree the data prerequisites, access controls, permitted actions and logging requirements before enabling AI.
Natural-language questions on the semantic model, answered from the governed data.
Discuss anomaly review, variance analysis and risk questions against the available source data. Confirm the scope, inputs and reviewer responsibilities.
Define the access roles, AI environment and audit records required. Confirm the implemented controls before rollout.
What changed in NOI at Juniper Plaza between Q2 and Q3?
NOI fell quarter over quarter. Repairs ran over plan after a roof repair, and two suites moved to vacant in August.
Income statement · Q3Rent roll · Sep 30
Core / Report library
Discuss the report library and configuration needed in your environment. Deployment timing, inputs and acceptance are agreed for the engagement.
4 reports
5 reports
5 reports
Core / Deployment
Timing depends on source access, data readiness and scope. Milestones, handoff and acceptance are agreed for the engagement.
| Phase | Sequence | What happens | Output |
|---|---|---|---|
| Foundation | First | Agree the sources, data model, controls and acceptance criteria. | Agreed foundation outputs |
| Reporting | Next | Scope and configure reports, then review them with the team. | Accepted reporting outputs |
| Analytics | Then | Define access and analysis needs for the agreed reporting model. | Reviewed analysis scope |
| AI | When ready | Evaluate an AI pilot after data and access prerequisites are accepted. | Agreed pilot scope |
Documentation & support · Scoped for each Core engagement
Everything your team needs to own the platform. Trained, documented and handed off.
01 / Documentation
Every field documented: what it means, where it comes from and how to use it.
02 / Documentation
The semantic model made visible for your architects, auditors and new hires.
03 / Documentation
Role-specific guides for executives, analysts, accountants and asset managers.
04 / Reporting
Excel-native starter reports connected directly to the governed model.
05 / Training
Structured training for your IT and data teams, with a runbook and escalation tree.
06 / Training
Discuss hands-on sessions for the roles that use the reporting. Format, documentation and recordings are agreed in scope.
Core / Questions
Source access, available connectors and any custom integration work are scoped per engagement.
Timing depends on source readiness, the required reporting and agreed milestones. AI work follows the data and control prerequisites.
Multifamily and commercial portfolios. The semantic model normalizes entities, accounts and metrics across property types and operators.
CREx Core is separately scoped Consulting for data and reporting foundations. Define the sources, reporting model, controls and any AI prerequisites for the project.
Discuss how new sources or systems affect the agreed model, integration work and delivery scope.
CREx OS includes its portfolio data and reporting foundation. Core is separately scoped Consulting for specific projects, not a prerequisite platform layer.
02 CREx Blueprint
Technology and ERP consulting for selection, configuration and implementation. Agree the delivery responsibilities and vendor relationships for the project.
Modernization stalls when tools, data and ownership don't align. Most CRE firms don't have a software problem. They have an ownership problem: six platforms, three data teams and nobody on the hook for the rent roll that ends up in the investor report.
Blueprint starts with the org chart and ends with a go-live. You leave with the right tools, the right processes and the right people accountable for each.
Services
Discuss the technology decision, relevant project experience, delivery responsibilities and acceptance requirements.
/01 · Advisory
Evaluate the relevant systems and alternatives against your requirements. Confirm the scope and any vendor relationships before engagement.
/02 · Diagnostic
Consolidate overlapping tools, retire shelf-ware, and design a platform map that scales with your firm.
/03 · Operations
Re-engineer workflows for reporting, lease administration, and capital planning with defined owners.
/04 · Implementation
Implementation, module configuration and custom reporting are scoped around the selected system, available access and acceptance requirements.
Yardi practice
Discuss the relevant Yardi implementation experience and project responsibilities when Yardi is the selected system.
/01 · Implementation
End-to-end Yardi® deployments, including services such as discovery, project management, implementation, and comprehensive organizational change management. All focused on your specific future operating model and needs.
/02 · Migration
Data cleansing, migration, and validation from legacy systems.
/03 · Reporting
CREx, with a depth of understanding of the Yardi data model and schema, is well-positioned as your partner for custom report development using SQL, YSR or Power BI.
/04 · BAU Support
Support framework to provide stability and confidence for your end users.
Blueprint / Questions
No. CREx is a trusted partner with a decade of experience helping clients through successful Yardi implementations, working in partnership with Yardi PSG (Professional Services Group).
Each engagement and relationship is different. We spend time up front on your strategic objective, needs and projects, then send a Statement of Work and a proposal built around them.
Team availability and project timing are confirmed after the scope and required skills are understood.
Discuss your technology architecture, required systems and delivery needs so the supported scope can be agreed.
Contact CREx with the service or project you have in mind and the work you need today. We will confirm the relevant scope and next step. Existing engagement terms continue to be governed by their own agreement.
Book a scoping call
Share the systems you run, the decision in front of you and your timing.
If the form does not load, email contact@crexsoftware.com. Share a business question and leave confidential documents and personal resident details out of this initial enquiry.