Use case: aggregator trying to build pipeline for 97 compliance in market rate housing
Portfolio Search within a particular portfolio that allows an aggregator user to triage and prioritize
Why: We are dealing with 100 - 1000 buildings per aggregator
MVP: Columns based on currently available static fields
Nice to have: Also being able to sort by work scope attributes
Go deeper / better on presentation of two basic pathways: optimization and heat pumps (making a better case for heat pumps!). Over time, etc.’
Why: Deeper investments with longer horizons require more/better analytics
MVP: For heat pumps: NYSERDA window HP PON; refine cost estimating for market rate cases, tariff (is there a near term automatic blended rate change for heat pump buildings hack before full tariff engine?); Show J-51 eligibility as a pop up with a note that flags how important this could be to economics (stay tuned);
Nice to have: for heat pumps: add a new battery measure with $0 cost and $X savings; for optimization…. Show ongoing EMS service costs, analyze data on EMS installations to better predict savings (can we provide projections that you can’t get anywhere else based on data across 1000+ EMS installs?) – this is important to showing limits of optimization.
More obvious communication of fines BEFORE any scope of work is implemented
Why: For this segment, fine liability is THE entry point
MVP: Get this more front and center… not just in scope builder but in the read only scopes sent out. Should also communicate fine risk through at least 2040 (more on that below).
Nice to have: some more data driven context on a particular buildings fines – everyone loves to be compared to comps – a lot of my voice over is stuff like “you fines are about average for a typical pre-war building”... or I do the Urban Green “well on way” vs “tough but doable” vs “leapfrog potential” thing
Making it easier for power user to see potential data issues
Why: Scope builder outputs needs to make sense
MVP: Focus on data issues that impact fine liability. Maybe some sort of pop up or second tab that puts this in the same place. Includes historic context for assessing energy data
Nice to have: Other data issues
Push out a read only scope to owner (current share scope) that includes some cover email and a scheduler form (to be coordinated with other user needs)
Why: saves time
How Potential AI projects could enhance pipeline building… in order of priority
ML on streetview images – could be immediately helpful to scoping: window vs 30” sleeve vs PTAC; SF checks (setbacks, etc). Yes this will also be even more helpful to other markets but has immediate value to NYC
AI Chatbot
Accurate pricing (need more data)
Doc Scraper (least related to immediate pipeline building but definitely foundational)
Strategy Notebook
What we want to build pipeline
Created: February 3, 2026
What We Want (In order of priority)
Use case: aggregator trying to build pipeline for 97 compliance in market rate housing
Portfolio Search within a particular portfolio that allows an aggregator user to triage and prioritize
Go deeper / better on presentation of two basic pathways: optimization and heat pumps (making a better case for heat pumps!). Over time, etc.’
More obvious communication of fines BEFORE any scope of work is implemented
Making it easier for power user to see potential data issues
Push out a read only scope to owner (current share scope) that includes some cover email and a scheduler form (to be coordinated with other user needs)
ML on streetview images – could be immediately helpful to scoping: window vs 30” sleeve vs PTAC; SF checks (setbacks, etc). Yes this will also be even more helpful to other markets but has immediate value to NYC
AI Chatbot
Accurate pricing (need more data)
Doc Scraper (least related to immediate pipeline building but definitely foundational)