This is the pattern we reach for whenever a client has Yardi, a portfolio of properties, and a stakeholder who wants live numbers without getting a BI license.
The shape of the pipeline
Yardi exports to Sigma on a schedule. Sigma handles the modeling — we write the SQL, they do the caching. A thin Node service pulls materialized views from Sigma into a static JSON artifact, which the website reads at build time (or, for hotter data, at request time with a short cache).
It is not the fanciest pipeline. It is, however, one you can understand at a glance, and hand off without a two-week runway. We’ll take that trade most days of the week.