Every Yardi operator eventually hits the “we need a custom report” wall. The wall is almost never the hard part. The hard part is that Voyager gives you six different places to build a custom report — each with different skills, costs, and longevity. This post is the decision framework we walk clients through.
The six places you can build a custom report in Voyager
- YSR (Yardi SQL Report) — SQL-powered parameterized reports. Runs in Voyager directly. Outputs to screen, Excel, or PDF.
- SSRS — Microsoft SQL Server Reporting Services. More capable than YSR for complex layouts, less Yardi-native.
- Yardi Report Builder — drag-and-drop report authoring inside Voyager. Lower ceiling, no SQL.
- Power BI (direct) — via Data Connect, Replicate, or direct SQL if available.
- External warehouse dashboards — Looker, Tableau, Sigma, Power BI in your warehouse.
- Third-party productized dashboards — Lobby CRE, RealSage, Stratafolio, Memowright, and similar.
Each one is the right answer for some scenario. None of them is the right answer for every scenario. Here’s the decision flow.
Decision 1: How often will this report change?
Changes rarely (one-time investor ask, audit support): YSR or Report Builder. Low overhead. Your Yardi admin can probably build it.
Changes seasonally (quarterly investor reporting, annual budget cycle): SSRS or Power BI on Data Connect. Enough structure to survive quarter-to-quarter, not so rigid that you need to rewrite it every time.
Changes constantly (weekly ops reporting, leasing KPI evolution): External warehouse dashboards. Dashboards are meant to be iterated. You don’t want every tweak to require a Yardi change management process.
Decision 2: Who maintains it?
Your Yardi admin (no SQL background): Report Builder. Everything else will eventually exceed their comfort zone.
Your in-house SQL analyst: YSR is the Yardi-native path; Power BI via Data Connect is the BI-native path. Pick based on whether they’re stronger in SQL or DAX.
Your BI/data engineering team: External warehouse. You’re not doing yourselves any favors by keeping business logic inside YSR or Power BI datasets when you have a dbt-capable team on staff.
No one — you need vendor maintenance: Productized third-party (us, Lobby CRE, etc.). Vendor maintains the reports; you maintain the relationship.
Decision 3: Where does the report live longest?
A useful thought experiment: in five years, when the person who built this is gone, the Voyager version has been upgraded three times, and the BI tool has been reskinned, where does this report need to still be running?
- In Voyager forever: YSR or Report Builder. Yardi will carry the schema forward.
- In your BI platform forever: Power BI / Looker / Tableau. BI platforms are generally stable carriers for dashboards.
- In a warehouse layer that outlives the BI tool: dbt models. This is the highest-leverage answer for anything that’s structurally business-critical (investor reporting, covenant monitoring, fund rollups).
A scenario-based recommendation
Scenario A: 500-unit multifamily operator
Profile: 2 properties, one Yardi admin who also handles AR, budget reporting done in Excel today.
Recommendation: Report Builder for ops reports. Excel pivot tables off a YSR export for anything financial. Skip Data Connect — at this size, the cost/benefit is wrong. If you’re generating more than ~20 hours/month of reporting work, consider a part-time fractional analyst (us or similar) rather than hiring a dedicated resource.
Scenario B: 5,000-unit multifamily operator with 3 funds
Profile: 35 properties across 3 funds, quarterly investor letters, active acquisition pipeline, one in-house SQL-literate analyst.
Recommendation: Nightly YSR export into a Snowflake warehouse. dbt models for the six core tables (rent roll, T-12, AR, BVA, leasing, rollup). Power BI dashboards off the warehouse. Investor letter drafting via an AI narrative layer on top.
This is Memowright’s sweet spot, and the architecture we default to. The total all-in cost is $7–9K/month including warehouse, dashboards, analyst seat, and AI layer — less than 1.5× the cost of Data Connect alone and a third the cost of an in-house hire.
Scenario C: 50,000-unit enterprise multifamily operator
Profile: 300+ properties, 5 in-house BI analysts, Replicate already licensed, Snowflake already running, mature dbt practice.
Recommendation: You have the team. Replicate + Snowflake + dbt + Looker is almost certainly what you’re already running, and the missing piece is the AI narrative layer. Memowright plugs in as a narrative-layer vendor; your team keeps everything else.
This is a different engagement — smaller, more focused, with the scope defined around variance commentary, investor letters, and the Q&A tier. Typically $4–6K/month rather than full retainer.
Scenario D: 2,000-unit affordable housing operator
Profile: LIHTC + HUD compliance reporting is the hard part, not the BI.
Recommendation: Compliance reporting stays in YSR because the audit trail is vendor-sanctioned. BI for asset-management and fund reporting sits in a separate warehouse layer. Don’t try to do both in one tool — the compliance audit pressure is different from the asset-management cycle pressure.
Why “just use Power BI” is usually wrong
The most common advice we hear from Yardi sales is “license Data Connect and do it in Power BI.” That advice is right about 40% of the time. It’s wrong when:
- You have any non-Power-BI preference on your analytics team.
- You need to join Voyager data with non-Yardi sources.
- You want sub-hourly freshness.
- You have compliance reporting that needs to stay in Yardi.
- You need dbt-level lineage for your audit trail.
- You’re likely to change BI platforms in the next 3 years.
None of those are rare. Push past the “just use Power BI” default and you’ll often end up in a warehouse-centered architecture that survives longer.
The short version
If you’re trying to decide for one specific report, the heuristic is:
- One-off, low-change, Yardi-admin-owned: Report Builder or YSR.
- Structural, quarterly-cycle, finance-owned: Power BI on Data Connect (if already licensed) or a warehouse-based dashboard.
- Strategic, frequently-changing, or AI-enabled: Warehouse + dbt + your BI of choice. AI narrative layer on top for the outputs that used to take a senior analyst a day each.
If you’re trying to decide for your whole reporting strategy, book a gap review and we’ll map it out.
Related reading