Weekly Update

Just the facts this week.

Metrics

Traction

• Unique Buildings: 6,648 (May, +300 MoM)
• Annual Run Rate: $1.49M

Financials

• Monthly net burn (accrual basis): $54,857 (3-month avg, -28.59% MoM)
• Year-to-last-month net burn (cash basis): $75,214 (-8.87% MoM)
• 2025 Transaction fees to date: $16,560
• Outstanding invoices as of today: $286,723 (+$72,990 WoW or +34.15% WoW)

Development

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

Last Week’s Highs and Lows

• Release 97 went out on time! It included improvements and fixes to the advanced search feature, showing LL97 fines all the way out to 2050, and updates to two measures. (JB)
• Marc and I had a good conversation with KC3, who liked the project feature so far. Let’s stay focused on this so we can get an MVP into their hands as soon as possible! (JB)
• Robin gave a demo to NYSERDA of a “stress test” to show the performance of the building data platform in a worst case scenario. This derisks our technical choices for the next phase. (FH)
• Third time the charm? Looks like ephemeral environments/MFD/mayflies are finally working for everyone. May they help us test smaller, ship faster. (FH)

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?

Jason’s List

Carryovers with some tweaks:

• Using AI tools to help us move faster THese definitely come with a learning curve and changes to more than our processes, but I think it’s good that we’re incorporating these more. We need to work differently and move faster to stay relevant and deliver all the features that we’ve been promising the market.
• Local politics Good news–Zohran > Cuomo! There’s still a lot that could happen between now and the general election in November, but I’m pleased with the outcome so far.
• NYC Accelerator and ConEd Recompete These are both big contracts with outsized impacts on revenue and product roadmap. Both interviews are done now, and eager to hear back.
• Balancing new feature development with cleaning up debt We have a lot of new features to build, but also a lot of legacy code debt that can make adding those features take longer than it otherwise should. How much time do we spend pushing new features out to the door to keep current and potential clients happy vs. time spent getting our codebase cleaned up so we can move faster in the future. Hopefully AI tools will enable to do both these more quickly, which would make the tradeoff less.
• Portfolio/program reporting Users want the ability to look at groups of buildings in our software, whether it’s looking in their own collections for buildings that meet certain criteria or looking at trends across projects in a program. We haven’t done anything in this vein yet, but we’ll need to start. L+M, CFHF, FirstService, and more want and expect this set of features from us.

François’ List

(repeats with tweaks)

• AI tooling and fun: We are feverishly integrating new AI tools and processes to help us move faster, and it should be a lot of fun, yet it sometimes feels to me like the opposite: the joy of creating is being replaced by the drudgery of assessing massive amounts of AI-generated code and documents. Finding ways to pass the baton human-AI-human more effectively is work in progress.
• Growing the team: the “$2.5M demo” is not only motivating on its own, it also re-opens the door to hiring. Let’s prep for it, so that we can identify the right skills, attract the right candidates, and welcome them efficiently. Ahead of permanent hires, and to flex our onboarding muscles, could it make sense to get help from consultants for Laravel expertise, or interns for testing help?
• Automated Testing: I’m convinced that reliable tests that run quickly and reflect our users’ experience are table stakes to move faster and with more confidence. Are we going to find the bandwidth to get this party going?

Erika’s List

Carryover from last week

• Budget for 2H 2025 Carryover from last week but will be finished by June close (not the end of the month as mentioned last week) - seeking some outside support to ensure we are able to look at our scenarios with a high level of confidence. Completing the scenarioes will support strategic decision-making around hiring and other resources over the second half of the year and beyond.
• Growing the team This requires conversation amongst the team leads post mid-year budget review, but also want to think ahead as far as resources and needs that could support a search such as salary comps and regional employment considerations and guidelines. This would also require getting the documentation on worldwide work into the handbook, along with other policies, asap so everyone is aware of how we should proceed with hiring, onboarding and integration moving forward.
• Hiring Process Along with growing the team, also thinking about how we interview and how we could screen for things that are important to a new hire being successful in the company. How we hire is directly related to how we onboard and it’s important to have an idea of how we evaluate not only the ability to do the job/background but capacity to work in our horizontal environment.

Marc’s List

Carryover from last week

• Momentum Need to make sure we are making progress with market engagement even as we wait for dust to settle on big rfp’ss
• Looking over our shoulders What would an AI native start up do to this space in 2026 or 2027 and how can we build a moat?

On Deck for This Week

• Wrapping up L+M first deliverable (JB)

• I’ll be meeting with CPC and Bright Power this week to discuss how we can support reporting project, and program, results. (JB)

• Kickoff the Causal updates (EP)

• Prep for closing the books for Q2 and June (EP)

• Marc’s 360 (EP)

• A lot of customer success for Related (MZ)

• Chat with Dale Bryck, Director of State & Regional Policies at Harvard Environmental & Energy Law Program about how Momentum can be a potential resource for states outside NY (MZ)

• Here’s what’s on the Company Radar

Upcoming Release

No release this week, but the focus should be on:

• Projects MVP
• L+M deliverables - measure updates and improving the portfolio view they want (via spreadsheet for now, but with links back to the Momentum)
• Owner- vs. tenant-paid end uses

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?