Where the money is going this month
Spend by property
Recent alerts
Accounts
| Account / Property | Supplier | Commodity | Usage | Cost/unit | 12-mo | MoM | YoY |
|---|
Contracts
Third-party supply contracts riding on the utility account — same meter, same delivery, but the supply half is bought from an ESCO. Fixed and index agreements across the portfolio, flagged at 60 days to expiration.
| Property / Account | ESCO supplier | Commodity | Rate | Locked rate | Term | Days left |
|---|
After hours, the line answers itself
A natural AI voice takes every maintenance call, triages it against per-property emergency criteria, files the work order with the full transcript attached, and dispatches the on-call super — call, then text, then the next super. Routine calls never wake anyone. Work orders file via a non-Yardi path.
Tonight — live line
The call
Dispatch ladder
The 7 AM board
Alerts
Every threshold is adjustable per portfolio. Changes apply to the next scrape cycle.
Contract expiration
Cost spike
After-hours maintenance line
Recipients & delivery
AI anomaly & seasonal flags
Bill audit & recovery
Sources
Every input is something the team already has or can authorize in a click. One provider to start — ConEd. The dashboard reads from a secure mirror — never directly from Yardi or a shared password.
The branded PDF invoice for every meter — captured per account (MFA handled), archived on arrival, then parsed line-by-line. This is the piece a usage feed does not deliver. A direct authenticated portal fetch stands by as the in-house contingency. Access is organized as a handful of portal logins, each holding many accounts — count confirmed at kickoff.
ConEd usage + cost data, authorized by ownership in a click — no stored passwords, revocable any time. Green Button does not deliver the PDF invoice; the capture layer above does.
ESCO supply statements billed separately land in a dedicated address and are parsed automatically — every charge line extracted, matched to its ConEd delivery account.
After-hours calls answered by the AI voice agent — transcribed, triaged, filed as work orders via a non-Yardi path, supers dispatched. Full recording + transcript stored with each ticket.
Account → property → units, from the master sheet the team already keeps (or derived from bills + public NYC building records / BBL). No Yardi login.
Encrypted storage, least-access inputs, and a full audit trail of every file and feed received. The dashboard reads only from here.