Happy fall, y'all!

Somehow, the summer is behind us and it’s back-to-school time already! I’ve never really gotten over thinking of Sept as the “new year,” and this year, it really does feel like a new “school year” is upon us, with NYCA starting up in about a month (fingers crossed!)

Jason and I are going to really focus on getting a tight happy path defined for November, which is when the incumbent vendor rides off into the sunset.

Meanwhile, I caught up with the horizontal meeting I missed and had Claude draft a FAQ based on that discussion and our handbook contents. You can preview it here, and comment/edit in the PR here.

And to answer the question about whether we still have a public handbook: YES!

Metrics

Traction

• Unique Buildings: 9,219 (+1,502 MoM)
• Annual Run Rate: $1.6M

Financials

• Monthly net burn (accrual basis): $56,996, +32.9% MoM
• Year-to-last-month net burn (cash basis): $60,959, -10.35% MoM
• 2025 Transaction fees to date: $32,099
• Outstanding invoices as of today: $365,441

Development

• Bug Count (P-0 and P-1): 3

Last Week’s Highs and Lows

• Release 102 went out smoothly, and 101 turned out to be the most stable release we’ve had in a while (ever?), with no new pre-acknowledged Sentry issue, despite a user adding 2000 buildings to their collection… and it’s fast, too! (FH)
• The team met the NYSERDA BDP demo deadline on Thursday, and the demo went really well. Looking forward to their feedback now that they have access. (FH)
• The brown bag demos were great–I really enjoyed seeing people share what they’ve been working on. (JB)
• Jeremy’s 360 was super smooth, I thought. Kudos to him and to the whole team for developing that muscle (BJ)
• Jason got the HPD subscription one step closer to getting finalized in a scope/legal meeting with HPD (MZ)
• Delivered a portfolio decarb analysis of ~20 buildings for our customer Related that was well recieved. Friday Demo day also gave me a chance to communicate to our wider internal team what Momentum can and can’t do for this particular customer (MZ)
• Delivered an initial national MF market segmentation to our customer CPC Climate Capital (yes that CPC CC) and showed them sample “archetype” buildings in Momentum from NYC and MA (MZ)

Any missing highlights? Please share in Slack comments.

Crow’s Nest

Looking out for icebergs: What are the risks on the horizon that we’re watching for and navigating around?

François’ List

• Lego sets, not Playmobils: we’re chasing multiple deadlines for a variety of customers. Sometimes we’ll have to build a custom one-off (Playmobil) for the sake of expediency, but let’s go after Lego sets when we can, trying to anticipate on user needs that are around the corner. We are learning from CPC -> Generic Project ; BKB -> BDP to build datasets, APIs, and UI components that can scale with us.

(repeats with tweaks)

• Defining the contours of back-end as a product: the NYSERDA Building Data Platform (BDP) initiative, the recent L+M analysis work, E3 research for ConEd, HPD, individual users loading large (~2000) lists of buildings, and other opportunities ahead of us have common themes of enabling analysis on large groups of buildings, with data integration and processing at their core. Should we turn this into a product we sell, or are we OK making it a service we offer tactically?
• Making our Code Base more welcoming: staffing is hard, making new folks successful quickly is not easy either. One of the major wins I’m hoping to get from outside senior help (Laravel architect, Senior data engineer, etc) is to help define structures that make it easier for new folks with different profiles to be productive faster and safer.
• Growing the team: the NYCA news further raises the priority of onboarding the right talent to help us deliver quickly from data processing to front-end. We’re making progress identifying places where we need the most help, we have a candidate pipeline for data processing and a Laravel architect helping us - but are we ready to welcome new folks and help them be productive?

Jason’s List

Some carryovers, tweaked, and slimmed down:

• Improving clarity around our roadmap and prioritization process–I really want/need to put more time into this.
• How will the ConEd MFEEP/AMEEP program pilot go? I’m eager to get actual folks using this new workflow!
• We need to move faster, and I hope we can grow the team and integrate more people quickly and smoothly!
• We’ve increased our feature set quite a bit lately, and it’s going to continue growing for some time. How can we scale our our testing to keep pace?
• AI Document Scraping–will this make it easier for users to find value?
• Local politics There’s still a lot that could happen between now and the general election in November. At this point, it’s not just local; the boundaries are blurring, and none of it’s good.
• NYC Accelerator We have a lot of build for this–and we need to pave the happiest of paths first before exploring the foliage along the sides.
• ConEd Recompete Still waiting for news
• Portfolio/program reporting I think aggregating results across buildings is one of the key selling points of our software as compared to a traditional energy audit report. Metabase looks pretty promising, and I know we need bulk calculations as well. Many of our clients will want some version of this, so we need to find the commonalities to avoid building custom features.

Bomee’s List

• Getting Marc a product he can sell Delivery cadence feels unpredictable - hopefully trying out the new “work 1 release ahead” thing will help!
• Team dynamics Chuck’s making a big transparency push. Are we feeling more basketball-y?
• Planning for growth on the team Jobs are posted. Now it’s a competition between ticking clock and good process
• NYCA, ConEd Recompete and HPD – Waiting for contracts - still!
• Uptake of AI tools - I feel like interest in tooling has plateaued?
• Cash. We have deployed about half our cash in hand. We need to replenish soon.
• Over-all architecture 8-ball says outlook still murky.

Erika’s List

Same as last week:

• Budget through the end of the year and thinking about next year for hiring and operating expenses. Also, making sure it is clear for all to understand and make decisions from.

• Also, getting paid on time or at least on a schedule that is more closely aligned with our needs. Our customers have been pretty consistent the past year but lately I have had to do a lot of follow-up for amounts big and small and it’s impacting the money we have in the bank.

• The hiring process and how we will bring people in and ensure they have everything they need and that new hires and the team are aligned on what makes for a successful transition and how we account for a successful transition.

• Marc’s List

• Execution We are the dog that caught the car with NYCA and other stuff brewing. Stakes of everything we do will be increasingly high. So many eyes will be on us. How do we best expand the team?
• Continuting to stay ahead of the curve How much of scope builder will be able to be recreated by an AI native start up in the mid term? What are we doing to build the flyseheel so that our customers experience every project making the next one easier and we deepen our moat?

On Deck for This Week

• Bomee and I will be discussing UX/UI for developments. I’m eager to get more defined requirements and a phasing plan for this; it’s been lingering for far too long. (JB)

• I’m really going to be spending time on recruiting for the next few weeks. The first offer of several just went out today (BJ)

• Reviewing results of 50 decab plans with owners rep partner Aurora Energy Advisors to kick off process for supportinig them on delivering as many as 1000 decarb plans to their customers this fall (MZ)

• Finalizing details of a NYC building science “Nerdfest” event in partnership with NYSERDA and Steven Winter Associates that will be fun and also continue to position ourselves as thought leaders to win the mindshare game (MZ)

• Here’s what’s on the Company Radar

Upcoming Release

• Sharing projects with owners
• Email notifications related to projects
• Adding an external key to buildings–starting with Viewpoint ID to support the ConEd program projects

Please Leave Feedback

Please note your reaction to this update in the Slack channel. It helps us to know what is resonating, what is unclear, etc. Thanks!

• What are your highlights / low-lights?
• Did we miss a highlight? Something else you want to react to?